On Fri, 4 Sep 2020 17:44:23 +0200 Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote: > On Fr, 04.09.20 17:10, Reindl Harald (h.reindl@xxxxxxxxxxxxx) wrote: > > > > No, that's not supported in sd-boot. A boot loader is a boot > > > loader, it should contain a fragile storage stack. It's kinda > > > what sd-boot is supposed to do better than grub. > > > > well, a boot loader should just *load* and not write anything so > > RAID1 is technically no problem and it shouldn't matter which of > > the 1, 2, 3 or 4 disks is there unless one survived. > > Robust boot loaders typically want to write boot counters to disk, so > that they can automatically revert back to older versions of the > OS/kernel if it doesn't boot. Thus some form of write access is > necessary if you care about robustness. But surely a boot loader of all things should never try to write to the place it is loading from? Booting should be idempotent (as long as it works, for sure). The only sane policy would seem to be that the loader had another path to a separate writable area? > Lennart _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel