Most books and courses introduce Linux through shell commands, leaving the kernel as a mysterious black box doing magic behind the scenes. In this post, we will run some experiments to demystify it: the Linux kernel is just a binary that you can build and run.
I agree that it’s be useful, and I think you can just install e.g. the LTS kernel next to the regular one.
But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.
Case in point: I dimensioned the EFI partition too small, so at some point, me using the zen kernel (which comes with a backup kernel image) messed things up and I couldn’t boot a half-written kernel.
then I
created and booted a live USB stick,
Mounted my / and /boot partitions manually into /mnt/root/ and /mnt/root/boot
Bind-mounted the live system’s /dev and /proc into /mnt/root/{dev,proc}
chrooted into /mnt/root (resulting in an environment using /dev and /proc from the live system and the rest from my system),
Used regular package manager commands to uninstall the zen kernel and install the regular one, and finally
rebooted into the now working system.
It’s not crazy, it doesn’t take long, you just need to know how the system works. Upside is that nothing ever breaks permanently, everything is fixable (except hardware failure)
That’s… Insanity. Keeping at least one old kernel is amazingly useful if you run into issues with an update.
I agree that it’s be useful, and I think you can just install e.g. the LTS kernel next to the regular one.
But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.
Case in point: I dimensioned the EFI partition too small, so at some point, me using the zen kernel (which comes with a backup kernel image) messed things up and I couldn’t boot a half-written kernel.
then I
/and/bootpartitions manually into/mnt/root/and/mnt/root/boot/devand/procinto/mnt/root/{dev,proc}/mnt/root(resulting in an environment using/devand/procfrom the live system and the rest from my system),It’s not crazy, it doesn’t take long, you just need to know how the system works. Upside is that nothing ever breaks permanently, everything is fixable (except hardware failure)