Am 28.01.2014 19:00, schrieb Michael Biebl: >> If systemd is intended to mount the filesystem the first place then that >> means we should somehow kill off /etc/network/if-up.d/mountnfs since it >> gets run really early (during coldplug, via /lib/udev/net.agent). > > This is all pretty tricky. For now we explictly use the if-up.d > mechanism in favor of mounting remote file systems in systemd. I don't > remember all the details anymore but I know this needs some more work to > be done properly. > > See also > http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commit;h=d1047601af94714f8e26e91c42d265d12803436a
The problem here is, that network.target or the new network-online.target are not properly set up / hooked up in Debian yet. So while remote mounts get an ordering against those targets, the way ifupdown is currently hooked up in the boot process (via /etc/init.d/networking and the net.agent [email protected]) doesn't ensure that network.target and network-online.target do the right thing. We need to define when we consider network.target and network-online.target to be ready: All interfaces defined in /e/n/i, only the ones with auto, when one interface is active, and then we probably need a tool like nm-online for ifupdown, which pulls in those targets and blocks until either a timeout is reached or the conditions are met. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
