this post was submitted on 20 Mar 2025
315 points (97.6% liked)

Linux

52460 readers
725 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
[–] cmhe@lemmy.world 9 points 6 days ago (2 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 6 days 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 6 days 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

[–] Longpork3@lemmy.nz 1 points 6 days ago (1 children)

Generally yes. My exception was the time i accidentally nuked python in it's entirety...

[–] cmhe@lemmy.world 1 points 6 days ago (1 children)

Well, that could have been fixed by booting from an usb stick, chrooting into you real system and either downloading and (re)installing the python package this way, or, if your package manager depends on python, download the package in the Live Linux and extracting the python package into your system, and then reinstalling it, so the package management overwrites your "manual installation".

Could be tedious, but less so that having to reinstall everything IMO.

[–] Longpork3@lemmy.nz 1 points 6 days ago

Fair, unfortunately it was a work machine that i needed operational again asap.

Luckily i image my machine monthly, so it was fairly straightforward to roll back.

[–] Cyber@feddit.uk 5 points 6 days 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

[–] OhVenus_Baby@lemmy.ml 2 points 6 days 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.

[–] flubba86@lemmy.world 2 points 6 days 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 6 days ago

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

[–] BaumGeist@lemmy.ml 1 points 5 days ago

Not any moreso than learning any other OS. I'd just argue that it's the case if you're averse to research, reading, listening, watching, or just generally learning from others... or if you're delving into unknown territory

Personally, i'm a learn-by-doing type of lady, so I've fucked up my share of devices (I'm allergic to reading unless it's fiction), but I have yet to mess around in the kernel (it's on my todo list, for my LFS build which is TBD)

[–] golden_zealot@lemmy.ml 3 points 1 week ago* (last edited 6 days 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 6 days 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.

[–] golden_zealot@lemmy.ml 1 points 6 days ago

That was my thought as well.

Back when I was new to Linux, I tried a lot of different distros in virtualization for shorter periods of time, and of course ran into the issues that come with the cutting edge stuff.

Last year I wanted to install a distribution to my laptop properly as a test before putting it onto my desktop, and I came to that same conclusion because at the end of the day I couldn't justify using bleeding edge, because I couldn't really even name anything I NEEDED from it. Yes, it is fun to have cool, new things, and it can be a lot of fun to play around with in a VM or something, but I don't actually need any of that stuff for what I do on a computer day to day right this second.

After that, the answer was pretty clear for me as to what distribution to use.

[–] PillowTalk420@lemmy.world 2 points 6 days ago* (last edited 6 days 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.

[–] OhVenus_Baby@lemmy.ml 1 points 6 days ago

Not sure you can fully brick a PC. Simple BIOS update and your back to scratch load an OS and go again. Hardware failure. That's where the bricking happens.

[–] arsCynic@beehaw.org 1 points 6 days 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.

[–] OhVenus_Baby@lemmy.ml 1 points 6 days ago (1 children)

I just spent 11 days on a dual boot repair in fstab, passwd, loads of ecryptfs, amongst other boot and login issues. Before restoring from the full system backup after getting mad to finally want to use my PC. 11 fucking days almost all day in terminal. TOO many partitions and too many folders inside of folders to get to my ecryptfs files. I got so lost LSing around.

After it all though, and it was an aneurism and a half. I still want to finish my goal and reinstall my dual boot this time correctly aiming the folders correctly.

[–] Cyber@feddit.uk 1 points 6 days ago

Might help to draw it out on paper

But, when you're done, you'll be the Encrypted Dual-Boot God !

[–] ada@lemmy.blahaj.zone 52 points 1 week ago (18 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 32 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

load more comments (17 replies)
[–] TimeSquirrel@kbin.melroy.org 32 points 1 week ago (6 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.

[–] OhVenus_Baby@lemmy.ml 1 points 6 days ago

😂 My gosh this hits home. If only I could stop tweaking. It's always just this one little thing. Then another and on until it's so fucked I don't even know where to begin. But it's magical when she works.

load more comments (5 replies)
[–] floofloof@lemmy.ca 20 points 1 week ago* (last edited 1 week ago) (6 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.

load more comments (6 replies)
[–] Shanmugha@lemmy.world 16 points 1 week ago (2 children)

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

load more comments (2 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 14 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.

load more comments (2 replies)
load more comments
view more: next ›