Michael Biebl wrote: > Raphael Champeimont (Almacha) wrote: >> >> My (dirty and inappropriate for that bug) fix was to add a initscript >> that is called first when the machine is rebooted/shut down, and that >> umounts all network shares. >> > > I don't think, that this fix is such a bad approach. Actually, the > current way network shares are handled in Debian is a complete mess imho. > The big problem is, that Debian wants to support /usr via NFS (which I > doubt is such a common use case anymore these days). This makes > everything very complicated, especially if you consider that NM is > installed in /usr. > If you look at /etc/rc[06].d/, you see that S31unmountfs.sh (which > umounts network shares, but also /proc, devfs,... WTF? ) is run after > S20sendsigs (which sends all processes the TERM signal. > If we could drop the assumption, that /usr lives on NFS, we could move > the network umount script to, let say, K86remotefs, and stop > NetworkManager afterwards, e.g at K88network-manager. > > This would make everything much simpler. >
Or maybe we could have 2 scripts to unmount network shares: - one that is run before NM is stopped, and that umounts every NFS/CIFS mount except /usr - and the other that is still run after NM stops, and that umount /usr if it is on NFS This way we still support /usr over NFS, the only condition is that the interface used to mount /usr must not be handled by NM, but this looks like a safe assumption as NM cannot be started without /usr anyway, so no one would could rely on /usr being mounted using a NM-managed interface. Almacha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]