In article ,
Roger Bell_West   wrote:

>It will need to be told that this particular filesystem shouldn't be
>mounted before the network is up. That may happen automatically.

The general order of scripts in Linux startup stuff usually ensures
the "network is up" phase happens before "now mounting NFS/SMB filesystems"
because it's just common sense.

However, that can't account for 1) Bring "*my* network interface up" (that's
as far as YOU can manage, from here) 2) Try and mount a networked drive that's
not plugged in/powered off :)

It would need to flag that the mount failed, and retry later (either by
sitting and waiting forever -- bad, or by queueing a job to keep trying
until it works).

>However, my experience of systemd has been that if it tries to mount a
>networked filesystem before the network is up, it will spot the
>failure and happily hang the entire system rather than let you get in
>and fix it.

Even better.

--
--------------------------------------+------------------------------------
Mike Brown: mjb[-at-]signal11.org.uk  |    http://www.signal11.org.uk

--- SoupGate-Win32 v1.05