this post was submitted on 20 Mar 2025
313 points (97.9% liked)

Linux

52626 readers
638 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 5 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 52 points 1 week ago (14 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 31 points 1 week ago* (last edited 1 week 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 25 points 1 week ago* (last edited 1 week 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

[–] sharkfucker420@lemmy.ml 14 points 1 week ago* (last edited 1 week ago) (1 children)

I could be weird for this but the starting over part actually contributed to me continuing to use linux tbh. Trying out a new distro, figuring out how to use it, and building a new user interface each time I killed my system kept me engaged with linux beyond its utility. It functioned essentially as a way to learn about computers and as a creative outlet. I don't fuck around and find out as much as I used to but I still swap distro every year or so.

[–] ada@lemmy.blahaj.zone 8 points 1 week ago

It was similar for me, but not quite the same. The thing I hated was starting from scratch. I'm very much not a distro hopper. Back in the day, I enjoyed the challenge of trying to troubleshoot issues and get the system working again, and that kept me interested, but eventually, I'd hit a problem I couldn't resolve, and I'd have to start again from scratch, and at that point, I'd just go back to Windows.

Now, I still get to do the same thing. If I break it, I get to learn how I broke it and try and fix it, and I find that process compelling. But because I'm using btrfs restore points now, I don't get to the point where I have to start again from scratch. So I can work at solving it to the limit of my abilities, with confidence that if I can't work it out, it's not a huge issue.

[–] Spaniard@lemmy.world 6 points 1 week ago (3 children)

"Starting over" is how we learnt Windows in the 90's too

[–] sockpuppetsociety@lemm.ee 5 points 1 week ago

Giving our computer ghonorrea by downloading Napster mp3s

[–] ada@lemmy.blahaj.zone 4 points 1 week ago

I'd just re-install Windows over the top of the fucked up install normally. It was a bit easier to recover from, and a bit harder to fuck up

load more comments (1 replies)
load more comments (11 replies)
[–] floofloof@lemmy.ca 21 points 1 week ago* (last edited 1 week ago) (4 children)

OpenSUSE Tumbleweed helps because you can create a btrfs snapshot at any moment and then roll back to it if you get in trouble. And it does this automatically whenever you update the packages.

[–] pumpkinseedoil@mander.xyz 9 points 1 week ago

👍 never had to start over

[–] overload@sopuli.xyz 6 points 1 week ago (2 children)

OpenSUSE Tumbleweed Gang. The only distro I haven't been able to break after 6 months (well, I have, but I've been able to snapper rollback every time)

load more comments (2 replies)
load more comments (2 replies)
[–] Shanmugha@lemmy.world 17 points 1 week 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 6 points 1 week ago* (last edited 1 week 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 15 points 1 week 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.

[–] MoonMelon@lemmy.ml 13 points 1 week 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 8 points 1 week ago

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

[–] easily3667@lemmus.org 7 points 1 week ago* (last edited 1 week ago)

See that would be a good analogy if the fail was fun.

Making a shit painting is still fun.

Having to reinstall my OS because I ran pacman -Syu and now my computer won't boot, and now I have to spend hours making things work again: not at all fun.

Having my server run out of memory and freeze up instead of having a sane out of memory behavior the day before a long trip: not fun

It's also archaic, niche information. Do I want to learn how to make a kernel version that didn't get installed right show up in grub? Fuck no. Do I want to google for the 100th time what command exists to register the encryption key for my hard drive in the TPM? Fuck no. What an absolute waste of life.

Linux isn't "I cut a hole in my wall" it's "my electrician only documented the wiring in hieroglyphs and now I have to reverse engineer everything to turn on a light bulb".

[–] mvirts@lemmy.world 12 points 1 week ago (4 children)

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

[–] Cyber@feddit.uk 4 points 1 week 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 1 week ago* (last edited 1 week 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)

load more comments (1 replies)
load more comments (3 replies)
[–] TimeSquirrel@kbin.melroy.org 12 points 1 week ago (3 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 4 points 1 week ago (2 children)

That also sounds like a good way to stop learning!

load more comments (2 replies)
load more comments (2 replies)
[–] DarkMetatron@feddit.org 12 points 1 week 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!

[–] thedeadwalking4242@lemmy.world 10 points 1 week ago (2 children)

I’m not sure I’ve ever actually killed a system, I’ve booted from UEFI shell manually just to recover systems. Back when I was using arch id just chroot into the system from a flash drive and fix whatever ¯\_(ツ)_/¯

load more comments (2 replies)
[–] cmhe@lemmy.world 9 points 1 week 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 1 week 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 1 week 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)
[–] lord_ryvan@ttrpg.network 8 points 1 week ago (2 children)

May I introduce you to my lord and saviour NixOS?

load more comments (2 replies)
[–] bad_news@lemmy.billiam.net 7 points 1 week ago (2 children)

I started nearly 30 years ago and cannot count the dead systems I have left in my wake. Just on the 2000-ish thing where Dell first offered Linux but it was inherently unstable after booting the pre-written disk image if you touched it, alone... So many kernel sanity failures...

[–] sockpuppetsociety@lemm.ee 4 points 1 week ago (1 children)

They died for a reason, for yor growth

load more comments (1 replies)
load more comments (1 replies)
[–] bert_brause@lemmy.world 7 points 1 week ago

Recently I accidently deleted the contents of /boot/ on my first arch install. The lesson that followed was something I would have rather saved for later ^^

[–] collapse_already@lemmy.ml 7 points 1 week 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 5 points 1 week ago

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

[–] lightnsfw@reddthat.com 6 points 1 week 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 1 week 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)
[–] nfreak@lemmy.ml 5 points 1 week 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

[–] Cyber@feddit.uk 5 points 1 week ago (3 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

load more comments (3 replies)
[–] easily3667@lemmus.org 4 points 1 week ago* (last edited 1 week ago)

Unbootable systems in the dozens. I think I've only fucked up the kernel itself a few times. But grub or other bootloader tons, desktop environment tons, and getting into states so broken the only readily available option was reinstall, dozens. Thankfully most of these were right after a fresh install. For example dual booting just doesn't work right for some OS installers and grub fails. Manjaro bricked itself after an update. Etc. etc.

[–] needanke@feddit.org 4 points 1 week ago

I think we are using linux very differently. Mine is two and one of those was a dead ssd.

[–] mybuttnolie@sopuli.xyz 4 points 1 week 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.

[–] daniskarma@lemmy.dbzer0.com 4 points 1 week ago* (last edited 1 week ago)

I remember managing to install two DE one above the other, and having them, somehow working at the exact same time. That was trippy.

I didn't even know how I did it. I'm pretty sure that I couldn't replicate that on purpose.

I'm on my second install now. I fucked up the first one pretty handily by accidentally wiping the boot partition in gparted. (Like a complete idiot, because the partitions are labeled.)

[–] Dudewitbow@lemmy.zip 3 points 1 week ago

i broke debian on my plex server and said fuck it and migrated to endeavor because im more familiar with arch

[–] circuitfarmer@lemmy.sdf.org 3 points 1 week ago

I used to have a side system with /home on its own partition precisely to learn different distros and setups. It makes it much easier having a partition which is retained.

These days, qemu is your friend for playing around with random Linux stuff.

[–] wesker@lemmy.sdf.org 3 points 1 week ago

It do be like that, at least for the first couple years, and typically with decreasing frequency.

[–] Eyck_of_denesle@lemmy.zip 3 points 1 week ago
load more comments
view more: next ›