0

Yes, I have seen the previous answers to this sort of topic, but, they leave me a little bit confused.

For example, in here, the answer talks about modifying /boot/config.txt to load an initramfs with a specific filename that matches the kernel version (in his case, initrd.img-4.19.97-v7l+), and then actually generating the initramfs with mkinitramfs.

But, with all his configuring, it really really looks like everything is going to break and will have to be done again the moment a new kernel version appears.

Am I wrong? Am I missing something that makes this an automatic process for every single next kernel update? Because I really have the feeling this will have to be automated in order to make it actually work the next time a kernel update gets installed.

Also, why is this so much more involved? I've made PCs boot from LVM on Arch before, and, on there, the modifications needed for the kernel to actually support booting from LVM LVs takes less than 2 minutes. It really makes mkinitramfs look much, much more inferior than mkinitcpio, in my eyes.

I am using the Raspberry Pi OS Lite 64-bit image.

P.S.: This would have been a simple and short comment on that specific answer, but, I don't have the reputation to create a comment yet.

Andy3153
  • 1
  • 1

0 Answers0