[Pkg-sysvinit-devel] Bug#388761: initscripts: Moving NFS mounts to /etc/network/if-up.d/mountnfs breaks my diskless system

[Tim Phipps]

On Friday 22 September 2006 14:17, Petter Reinholdtsen wrote:
> [Tim Phipps]
>
> Why do ifup -a hang on your system?  This seem to be the most obvious
> bug to fix to solve this issue.
It's hard to tell since it locks totally. I think ifup is deconfiguring the 
interface before it starts to up it. If it does anything after deconfiguring 
the interface (like looking for a pre-configure script) it will fail since 
any file access (even stating /dev/null since / will be locked) will lock 
things up. Whatever it is doing it's causing the root nfs-mount to not work. 

It would be better if "ifup -a" would just skip any interfaces that are 
already up. If that can be done then maybe this is a bug for ifup. Even so it 
must execute /etc/network/if-up.d scripts.

Thinking about this some more. Moving nfsmount to /etc/network/if-up.d isn't 
going to be nice for people with more than one network interface. My reading 
of the ifup man page says that the scripts are run for _each_ interface 
brought up (with some env variables to say which interface). The new nfsmount 
script is going to be run twice. Worse, if you have mounts from both 
interfaces it will run the nfsmount script after the first interface is up 
but before the second interface is up. I don't know what would happen then, I 
guess you're about to find out.

What's the problem with having the old systems of an init.d script running 
after ifup?

Cheers,
Tim.