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.
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.
That is not a replacement for “arrow-key down during boot to select an older kernel”.
I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.
It’s not crazy, it doesn’t take long, you just need to know how the system works.
I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.
That is not a replacement for “arrow-key down during boot to select an older kernel”.
I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.
I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.
As said: installing the LTS kernel also works, I think.
And you wouldn’t use Arch for servers, you want something stable (as in “rarely changing”) there.
I wouldn’t use arch for anything.
I really like rolling release. So much better to deal with updates one-by-one than in a giant batch every half year or so.
Neat