On 12/15/2011 10:16 AM, Anton Aylward wrote:
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.
No he does not at all except in the most simple and static situations. Not any more than you should have to know at boot time, or any other time, what nic will be needed to reach an ftp or ntp or http or smtp or any other kind of service.
OK?
No not at all. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org