On Mon, Jul 13, 2020 at 12:14 PM Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote: > > On Mo, 13.07.20 09:23, Chris Murphy (lists@xxxxxxxxxxxxxxxxx) wrote: > > > Since it's mostly bootloader domain, and relates to a snapshot and > > rollback paradigm as well, I think it's properly addressed in design > > and planning that feature. > > It's not just a boot loader thing. By requiring this to be specified > explicitly, you make sure that "systemd-nspawn -i" and the various > other tools cannot make sense of it automatically. > > Quite frankly, I don't see why the boot loader should care about the > btrfs subvolume the initrd later picks at all.. > > > > I think a system that automatically discovers what it needs and works > > > without configuration and everywhere the same is what we should strive > > > for. Requiring configuration for this kind of stuff just makes stuff > > > fragile... > > > > Is the root parameter fragile? > > Yes, because you have to propagate it everywhere, and if you omit it > things break, since it's a secondary place you store information about > the root disk in that you strictly need to have to be able to make > sense of the file system. As it relates to Silverblue, how is the 'ostree=' parameter any different or less fragile than 'root=' or 'rootflags=' and how could it be made automatically discoverable? That information is currently in the bootloader configuration file, and the means for switching between roots is by bootloader menu item. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
