by denysonique on 8/13/23, 8:13 PM with 52 comments
by nisa on 8/13/23, 8:47 PM
by londons_explore on 8/13/23, 10:25 PM
That bootloader needs to mount a filesystem to find the kernel.
The kernel needs to mount the filesystem to run the system.
Each of those mount operations is done with different code, and normally each involves some config or search process to find the right disk/partition. If any of the searches finds the wrong partition or is misconfigured, you get a boot failure.
It really feels like the boot process is more complex than it needs to be, with more opportunities for failure than necessary.
by aborsy on 8/13/23, 9:03 PM
by dsp_person on 8/13/23, 9:02 PM
One concern I had with zfsbootmenu was I couldn't figure out how to load microcode. With kexec, zfsbootmenu can only load one image and late loading microcode may be "dangerous" [1]. I don't know practically if that is a real security issue or not. I tried cat'ing my images together as below, but it still didn't work for me:
mv initramfs-linux.img initramfs-linux.img.orig
cat intel-ucode.img initramfs-linux.img.orig > initramfs-linux.img
[1] https://docs.kernel.org/arch/x86/microcode.html#why-is-late-...by contingencies on 8/14/23, 10:52 AM
In case 2 portage changes are automatically synchronized to system snapshots, but multiple system instances (VMs, diskless nodes, etc.) will have to redundantly update portage. However, in case 1 they are de-facto desynced and this can cause gentoo issues (yet saves duplicate network operations so is nominally desirable). Does ZFSBootMenu have a built-in system for managing ZFS root system snapshots with co-dependent dataset snapshot versions to enable case 1?
by anotherhue on 8/13/23, 8:41 PM
This wouldn't apply if you needed to have divergent state though, though it's hard to imagine a use case for that unhandled by fs snapshots.
by vermaden on 8/13/23, 11:28 PM
I will wait ...
by prabir on 8/13/23, 9:41 PM