On Mo, 11.12.23 11:42, Eric Curtin (ecurtin@xxxxxxxxxx) wrote: > I am also thinking, what is the difference between "make the > bootloader load the erofs into contiguous memory" part and doing > something like storage-init. Well, from my PoV there's value in reducing the stages of the boot process, and reducing the amount of storage stacks you need in the mix. Hence, the boot loader can load stuff from disk into memory anyway, it always has done that, typically the kernel and the initrd. just swapping out the format of the initrd to get better behaviour is relatively cheap there, means no additional storage logic, no additional stage of the boot. You basically only have "boot loader" (which loads kernel and initrd), and the "host os" (which runs of the final rootfs). Otoh if you let your storage-init load the initrd, then you basically have a third step in the middle, which shares a lot of props with the last step, but also is distinct. I mean, you probably would reinvent your own udev and DM stack for that, to get verity in the mix (because that depends on DM, and udev, to some degree) In my ideal model, initrds are just part of the UKI btw, so they end up being loaded together with the rest of the kernel, and need no verity becaused signed along with the UKI itself. Lennart -- Lennart Poettering, Berlin
