On Mon, 18.05.15 17:53, Igor Bukanov (i...@mir2.org) wrote: > On 18 May 2015 at 17:18, Lennart Poettering <lenn...@poettering.net> wrote: > > Well, my recommendation is to avoid daemon-reloads during the normal > > boot process if possible, since there are some unresolved issues: > > What is then a canonical way to implement initialization when the > configuration comes from a drive that is not available during early > boot like virtio mount or uploaded from a network connection? Clearly > I can write a new persistent config and reboot the system for the new > changes to take an affect, but I would prefer to keep all the config > changes under /run so reboot always brings the system into a clean > state. I.e. how one should implement a staged boot when the system > performs a minimal initialization like mounting some paths or > initializing a minimal networking, gets the rest of the config via > that and then run the rest of initialization?
One option is to do this from the initrd: mount your alternative config source from there, and then when doing the full root transition already have all the data you need around. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
