On Mi, 21.08.19 09:32, Colin Hogben (systemd@xxxxxxxxxxxxxxxx) wrote: > On 20/08/19 16:54, Silvio Knizek wrote: > > > The NFS root needs to be mounted in the initrd step. Else everything > > will break. With systemd in the initrd you gain the possibilty to > > depend on those units in the actual system. > > Booting with an NFS root is working fine. I'm not sure how to tell whether > or not I have "systemd in the initrd" as you describe; I built the initrd > with dracut, and I get the > random: systemd-udevd: uninitialized urandom read (16 bytes read) > messages before > dracut: Mounted root filesystem ... > > > Why not systemd-networkd, > > systemd-networkd is inadequate for the task. Even though I could > potentially parse the ntp servers out of the lease file (is that even a > public interface with stable format?), I didn't find a way, documented or > undocumented, for getting the log-server. Indeed, from scanning the source > code it seems that any DHCP options other than some core ones and those in > the private range, e.g. 7 (log-server), are just ignored. (Bizarrely, > systemd-networkd does include a DHCP server - WTF?! DOTADIW? But I > digress...) Please file an RFE issue that asks for the syslog field to be exposed in our interfaces. It's easy to do just, noone did this so far. Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel