Ruediger Meier said the following on 12/15/2011 08:45 AM:
No, just wanted to mention that in general nobody (including systemd) can't find out for sure which network device is needed to mount a specific NFS directory before actually trying to mount it.
So your above idea "...they could be made dependent on the specific Ethernet port that leads to the NFS server ..." is IMO not possible. It has to be generic like "waiting for complete network setup" and then try nfs mount (hoping that there is a device to reach the server).
Of course if admin knows what he is doing then he could replace the generic deps by more specific ones but no way to do this in systemd's default config.
Lets make sure we agree. The system by itself can't tell which port a NFS mount needs until it happens. OK The sysadmin, the guy who configured the system, knows which network segment the NFS server is on and which Ethernet port connects to that network segment, so he (or she) can configure the specific mount unit files for SystemD. This knowledge is "external to the system" and part of the human-level design. OK? -- Of all things, good sense is the most fairly distributed: everyone thinks he is so well supplied with it that even those who are the hardest to satisfy in every other respect never desire more of it than they already have. - Rene Descartes (1596-1650), Discours de la Methode (1637) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org