On Wed, Dec 21, 2022 at 10:16:58AM -0600, Chris Adams wrote:
Once upon a time, Zbigniew Jędrzejewski-Szmek
<zbyszek(a)in.waw.pl> said:
> Without an initrd we immediately have the following limitations:
> - all kernel modules needed to mount root must be compiled in
> - all that code is always loaded and remains in unswappable memory
> - root= syntax is limited to what the kernel understands, i.e.
> no root=UUID=… o root=/dev/disk/by-path/… or other udev links,
> no encryption or dm-verity.
> - no bluetooth keyboards or other fancy peripherals
> - recovery is pretty hard
Also, the security lock-down for the kernel command line means:
- no network root filesystem
- no boot-time-only kernel/module configuration
The idea of switching from grub2 to sd-boot would also drop network boot
and BIOS support. Supporting boot loaders seems to be a bit of a issue
sometimes, so trying to support multiple boot loaders seems like a bad
idea to me.
I'm using network boot without grub2, just iPXE and kernel+initrd.
It worth noting that NFS root doesn't work with dracut from rawhide,
for months now.
--
Tomasz Torcz “God, root, what's the difference?”
tomek(a)pipebreaker.pl “God is more forgiving.”