A big part of learning Linux is screwing up computers and starting over.
-
My crippled kernel count is around 6, how about yours?
I haven't had any issues with the kernel yet. The worst thing that I can remember doing is messing up the systemd boot entry on my Arch Linux install.
-
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)It's the first rolling distro I have tried, and I've been running it for about 3 years now without any real problems. I think maybe twice there have been updates that cause issues, out of hundreds of updates per week. It's surprisingly solid.
Not everyone would want hundreds of updates per week of course, but it's up to the user to decide how often to install updates. Unlike Windows, the updates don't intrude, and they are fast.
-
Didn’t quite follow what you were saying completely.
Are you suggesting a new program over time shift or change the file system type like ZFS and Btrfs?
I’m using Ubuntu and not sure if I seen those before.Snapshots are one of the features of copy on write filesystems like ZFS or btrfs.
It looks like Ubuntu has btrfs support, so you could do things like configure the package manager to automatically snapshot before a system upgrade.
https://blackstewie.com/posts/install-ubuntu-24.04-with-proper-btrfs-setup/
That looks like a current guide for setting it up
-
My crippled kernel count is around 6, how about yours?
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.
-
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.
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.
-
My crippled kernel count is around 6, how about yours?
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.
-
Snapshots are one of the features of copy on write filesystems like ZFS or btrfs.
It looks like Ubuntu has btrfs support, so you could do things like configure the package manager to automatically snapshot before a system upgrade.
https://blackstewie.com/posts/install-ubuntu-24.04-with-proper-btrfs-setup/
That looks like a current guide for setting it up
Thank you for sharing!
-
It's the first rolling distro I have tried, and I've been running it for about 3 years now without any real problems. I think maybe twice there have been updates that cause issues, out of hundreds of updates per week. It's surprisingly solid.
Not everyone would want hundreds of updates per week of course, but it's up to the user to decide how often to install updates. Unlike Windows, the updates don't intrude, and they are fast.
It seems to hit that right balance of bleeding edge while SUSE are still testing the packages for a bit to ensure there aren't bad updates. Fedora sounds interesting to me as well, but I'm not going to fix what isn't broken.
-
My crippled kernel count is around 6, how about yours?
I think we are using linux very differently.
Mine is two and one of those was a dead ssd. -
My crippled kernel count is around 6, how about yours?
Uhm, zero? With ten years of using Linux? What did you do to fuck up the damn kernel? o_O
-
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.
-
My crippled kernel count is around 6, how about yours?
-
My crippled kernel count is around 6, how about yours?
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.
-
My crippled kernel count is around 6, how about yours?
I've never in 15 years of Linux use and tinker have ever screwed a kernel. And I compiled LFS once.
-
My crippled kernel count is around 6, how about yours?
Both, to the point it doesn't boot, and just tweaking enough bugs that it's easier to jist start over.
-
Uhm, zero? With ten years of using Linux? What did you do to fuck up the damn kernel? o_O
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 will fail to execute and the kernel will loop forever.
-
Both, to the point it doesn't boot, and just tweaking enough bugs that it's easier to jist start over.
Reply fail?
-
My crippled kernel count is around 6, how about yours?
as a kid, when i was learning linux it was slackware on a massive stack of floppies. and this was before plug and play mind you, there were all sorts of things DOS did one way but linux expected another way.
Well i only had the one computer. So you would get so far through a linux install (many hours, overnight was common) and run into a real issue such as how do i properly terminate the scsi chains differently than dos expected so i could get it to see the discs, or what jumpers did you have to move around to free up irq's so that ionic could see the modem.
well if the hastily printed docs i had amassed didn't cover it, no choice but to re install dos and telemate and hope for help on usenet. which always did come. then you print that and cross your fingers and hope it worked.
I don't recall exactly how long it took me to get slackware on that old family 286 but the joy when i finally had it all working.
then i learned linux had no dialup scripts yet for slip/ppp yet so i had to reinstall dos to go learn bash so i could teach the thing how to connect to my isp, since it was a little different for all of them at that time.
as an autistic kid this was my secondary special interest and i loved every second of all of this. it prepared me for a fruitful if frustrating career as a very full stack software engineer!
-
My crippled kernel count is around 6, how about yours?
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.
-
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 will fail to execute and the kernel will loop forever.
Thank you for explanation
I suspected something like that - mess up with some internals, you do have a chance to bring the thing down. Which is why I always have a bootable usb around before doing anything risky
