Wed Dec 18 22:12:02 UTC 2024
a/lilo-24.2-x86_64-13.txz: Rebuilt.
liloconfig: add a line for /boot/initrd-generic.img if it exists, if not try
/boot/initrd.gz, and if that's not there do not use an initrd.
Lilo is still the default, and partially automated. I don't understand his recommendation to use an initrd even though the generic kernel is the same as the old huge kernel. I only used an initrd with the old generic kernel. Custom kernels don't need an initrd. I do have it included on his kernel....meh.
That's not true anymore, the generic kernel isn't the same as the old huge kernel. There is no more huge kernel, and the generic one may not be able to boot without an initrd, if drivers are needed early in boot, that aren't baked in.
Of course, the best thing to do is just use your own custom kernels, then you'll build in what you need and won't need an initrd. I DETEST initrd/initramfs, and refuse to ever deal with it. I don't even install distro kernels.
You still build your own kernels? If so, you can remove the distro kernel and just keep a fallback one of your own.
I build a mostly monolithic kernel. The only hardware driver that's not in my kernel is amdgpu, for two reasons. One, I want that to initialize last... motherboard stuff first. Secondly, it's impractical to build that in statically because you also have to build in every firmware file it needs, because the filesystem won't be mounted yet for it to get them from /lib/firmware/amdgpu early in boot.
Except for that, my rule of thumb is, everything I use all the time goes right in the kernel image. I build stupid shit like netfilter drivers as modules, KVM as modules, even modules for usb storage, but the USB stack is built right in because I use my keyboard and mouse always, for example.
If you need help with kernel stuff, that's what I'm here for. We can tune your kernel for your hardware and usage.