this post was submitted on 20 Mar 2025
70 points (100.0% liked)

Linux

60203 readers
727 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

My crippled kernel count is around 6, how about yours?

top 50 comments
sorted by: hot top controversial new old
[–] ada@lemmy.blahaj.zone 11 points 9 months ago (10 children)

The "starting over" part is what made it take so long for linux to "stick" with me.

Once it became "restore from an earlier image", it was a game changer!

[–] ArsonButCute@lemmy.dbzer0.com 6 points 9 months ago* (last edited 9 months ago) (1 children)

My game changer was circa 2014 when I broke something and got dropped to a basic shell and for the first time instead of panicking and immediately reinstalling I thought for a moment about what I had just done to break it, and undid the change manually. Wouldn't you know it booted right up like normal.

The lesson here: if it broke, you probably broke it, and if you know how you broke it, you know how to fix it.

[–] deadbeef79000@lemmy.nz 6 points 9 months ago* (last edited 9 months ago)

100%

The alternative being variations on:

Hi my name is [redacted], I have [X] years experience.

Please run sfc /scannow.

You can find more help at [Irrelevant KB URL].

Please rank me 5 stars.

Ticket closed

[–] fmstrat@lemmy.nowsci.com 1 points 9 months ago

Every time I install or configure anything, it's done via CLI and added to a script. Makes setup a breeze.

load more comments (8 replies)
[–] TimeSquirrel@kbin.melroy.org 11 points 9 months ago (2 children)

Another big part is learning how to set it up in a way that it's functional and productive the first time and then STOP FUCKING WITH IT.

[–] ada@lemmy.blahaj.zone 2 points 9 months ago (2 children)

That also sounds like a good way to stop learning!

[–] deadbeef79000@lemmy.nz 1 points 9 months ago

Not quite. But sorta, yeah.

Learning to "not fuck with it" or ways to do so and rollback are valid lessons themselves.

Being able to segregate "production" and "development" environments is very valuable.

load more comments (1 replies)
load more comments (1 replies)
[–] mvirts@lemmy.world 10 points 9 months ago (3 children)

It's even better if your only internet connection is that computer you broke.

[–] Cyber@feddit.uk 4 points 8 months ago (1 children)

Ah yes, reminds me of messing with my 1st pfSense firewall... I learned how good their recovery process was that evening

[–] ohshit604@sh.itjust.works 3 points 8 months ago* (last edited 8 months ago) (1 children)

Just bricked my Proxmox install an hour ago and I had the pleasure to learn their recovery process sucks. (At least for my case)

[–] Cyber@feddit.uk 2 points 8 months ago

Ah, yeah, you've just reminded me, I must move my stuff off proxmox when I get a chance.

I tried that proxmox backup thing when I first set it up, good god what a complex mess... backup & recovery needs to be as simple and as smooth as possible.

[–] sockpuppetsociety@lemm.ee 2 points 8 months ago (1 children)

Great incentive to learn even faster

load more comments (1 replies)
[–] OhVenus_Baby@lemmy.ml 2 points 8 months ago

This is the nightmare of my last 2 weeks. Well 11 days.

[–] cmhe@lemmy.world 9 points 8 months ago (4 children)

No no no! When you break something in Linux systems you fix it. Starting over and reinstalling everything is what you do when you mess up on Windows.

[–] sockpuppetsociety@lemm.ee 3 points 8 months ago (1 children)

Funny I did not expect so many people that resist starting over. Next time I'll give fixing stuff a shot :)

[–] cmhe@lemmy.world 3 points 8 months ago

It is more about being lazy.

In most cases, where you havn't destroyed your filesystem, you can just boot another Linux from a USB stick, mount your filesystems to /mnt, chroot into it, and then investigate and fix there.

See the Archlinux wiki, even if you do not use Archlinux, it is great: https://wiki.archlinux.org/title/Chroot

load more comments (3 replies)
[–] Cyber@feddit.uk 5 points 8 months ago (2 children)

Pretty much everytime I try to do fancy stuff with the bootloader I get pretty close to nuking systems. Worst was my 1st UEFI system where I was trying to get rEFInd to show multiple OS to boot from... eventually gave up and went back to the warm embrace of GRUB

[–] flubba86@lemmy.world 2 points 8 months ago (1 children)

If you take the plunge and switch to systemd-boot it's worth it. It's the only boot manager I've tried in the last decade that feels like an upgrade from GRUB.

[–] Cyber@feddit.uk 1 points 8 months ago

🤔 Maybe I'll try that next time... I kinda feel loyal to Grub, it's been my friend for sooo looong.

[–] OhVenus_Baby@lemmy.ml 2 points 8 months ago

I just had 8 titles in boot menu all for the same OS. 🤌😅 I know exactly what I'm doing. It's a dual boot system.

[–] lightnsfw@reddthat.com 4 points 9 months ago (2 children)

Never the kernel but just about every time I touch /etc/fstab I fuck something up. I've done that a lot....

[–] zenpocalypse@lemm.ee 3 points 8 months ago

Oh, I typed that line wrong to mount the drive and because the non-os drive isn't detected you're only going to boot to emergency mode?

Cool cool cool.

load more comments (1 replies)
[–] Shanmugha@lemmy.world 4 points 9 months ago (1 children)

Uhm, zero? With ten years of using Linux? What did you do to fuck up the damn kernel? o_O

[–] unhrpetby@sh.itjust.works 2 points 9 months ago* (last edited 9 months ago) (1 children)

It can be done if you mess with the initramfs.

The kernel starts everything else by unpacking an archive containing a minimal environment to set stuff up for later. Such as loading needed kernel modules, decrypting your drive, etc. It then launches, by default, the /init program (mines a shell script).

That program is PID 1. If it dies, your kernel will panic.

After it finishes setup, it execs your actual /sbin/init. These means it dies, and that program (systemd, openrc, dinit, runit, etc) becomes PID 1. If an issue happens, both could fail to execute and the kernel will loop forever.

load more comments (1 replies)
[–] teawrecks@sopuli.xyz 3 points 9 months ago

So, when you say crippled kernel, do you actually mean you tweaked the kernel params/build to the point that it failed to boot? Or do you just mean you messed up some package config to the point that the normal boot sequence didn't get you to a place you knew how to recover from and need to reinstall from scratch?

I think I'm past the point where I need to do a full reinstall to recover from my mistakes. As long as I get a shell, I can usually undo whatever I did. I have btrfs+timeshift also set up, but I've never had to use it.

[–] golden_zealot@lemmy.ml 3 points 8 months ago* (last edited 8 months ago) (1 children)

Maybe 1 or 2 back when things were less stable, but any time I have used Linux in the past 7 years or so, and particularly since I started using Debian as my primary OS, I haven't had any problems outside of trying to get some windows applications to emulate correctly, and one time when I echo'd into sources.list with > instead of >>. Anything else is just stuff I had to learn, like my boot folder filling up with old images that have to be cleaned out occasionally.

[–] OhVenus_Baby@lemmy.ml 2 points 8 months ago (1 children)

If you want shit to just work when you want and stay out the way when you aren't using it. Debian of whatever source is what they call stability. I've done rolling, and bleeding edge. It's all a constant pain. Becomes a job to maintain or bug track or check logs. I'll never go back.

load more comments (1 replies)
[–] MoonMelon@lemmy.ml 2 points 9 months ago (2 children)

It's the same as learning anything, really. A big part of learning to draw is making thousands of bad drawings. A big part of learning DIY skills is not being afraid to cut a hole in the wall. Plan to screw up. Take your time, be patient with yourself, and read ahead so none of the potential screw-ups hurt you. Don't be afraid to look foolish, reality is absurd, it's fine.

We give children largess to fail because they have everything to learn. Then, as adults, we don't give ourselves permission to fail. But why should we be any better than children at new things? Many adults have forgotten how fraught the process of learning new skills is and when they fail they get scared and frustrated and quit. That's just how learning feels. Kids cry a lot. Puttering around on a spare computer is an extremely safe way to become reacquainted with that feeling and that will serve you well even if you decide you don't like Linux and never touch it again. Worst case you fucked up an old laptop that was collecting dust. That is way better than cutting a hole in the wall and hitting a pipe.

[–] techclothes@lemmy.world 3 points 9 months ago

So this is why I'm bad at drawing. I have 954 more drawings to go!

[–] lord_ryvan@ttrpg.network 2 points 9 months ago (1 children)

May I introduce you to my lord and saviour NixOS?

[–] OhVenus_Baby@lemmy.ml 2 points 8 months ago (1 children)

Knock Knock Knock.

We (Jehovah's Witness) would like to know if you had a minute, so we could come inside, and talk to you about OUR Lord and Savior... Linux Mint.

load more comments (1 replies)
[–] collapse_already@lemmy.ml 2 points 9 months ago (1 children)

I tried to use dd with too much hubris once. I had to restore from backups (which ironically, I had made with dd). I'm usually overly cautious, but I was in a hurry.

[–] cevn@lemmy.world 2 points 9 months ago

I did this one a few weeks ago lmao. You think once would be enough. But I am a truly special being.

[–] PillowTalk420@lemmy.world 2 points 8 months ago* (last edited 8 months ago) (1 children)

I would actually be amazed if I ever bricked a PC fucking around with installing software to it. At the very worst, I might have to move a jumper pin to flash the CMOS and start fresh like I never even touched the thing. If somehow even that fails, it would be a unique experience.

load more comments (1 replies)
[–] Eyck_of_denesle@lemmy.zip 1 points 9 months ago
[–] arsCynic@beehaw.org 1 points 8 months ago

Nearly always it's been during the live USB install of a dual-boot that a distro messes with the grub or installed grub to the USB disk itself. The fault lies with me because I'm almost blindly trusting the distro, but also with the distro for lacking proper yet succinct documentation during the install or configuration of partitions.

[–] DarkMetatron@feddit.org 1 points 9 months ago

Making errors and analysing them to figure out what went wrong and why is a huge part of learning. You can only learn so much from theory, some things can be learned best by trial and error and the experience gained from it.

When I started with Linux I did choose to use Gentoo Linux because it was the most complex and complicated option, so I had the most opportunities to learn something by ducking up!

[–] nfreak@lemmy.ml 1 points 9 months ago

I haven't majorly fucked up any recent systems (almost botched the steam deck once or twice but nothing that required a reinstall), but god 10 years ago I probably reset my arch dual boot like five times lmao

[–] mybuttnolie@sopuli.xyz 1 points 9 months ago

Two. The first time I had nvidia related issues with nobara, so I removed nvidia drivers for reinstallation... And couldn't figure out how to get them back. The second time I had used mint for long enough that I felt confident enough to nuke windows partition. I used gparted and nuked the whole disk instead.

Not counting the times I tried fedora and it killed itself with the first updates and then with multimedia codecs.

load more comments
view more: next ›