Comment 96 for bug 211631

@toobuntu:
The _netdev option tells the system (if it doesn't already knows it from the fstype) that the filesystem should be considered mounted on network (and therefore be unmounted in umountnfs.sh rather than umountfs).

@Steve Greci ("Seems when tracking down the cause of one bug, I encounter 3 more to that need to be fixed in order to solve it."):
I understand the feeling. That's part of why I said this bug is not so easy to fix. Looks like your bug is solved in Jaunty though... so let's try if we can completely fix it for that release :)

@Steve French:
Yes, there seems to be a major inconsistency between the way Gnome handles files on network mounts vs. how NetworkManager handles the network. Thanks for your analysis :) To mitigate the effects I agree we should hack umountnfs.sh so that it always uses "umount -i". Since that script is always run as root I suppose there wouldn't be any wrong side-effects ?

@Bart:
I agree that the different "network modes" are poorly documented (and checkbox behavior in n-m-applet to switch between them used to be very buggy). I am still not sure I got them right. I guess Alexander could confirm if what I said in comment 88 is indeed how it works.

@Alexander:
I think most of the users with wireless reporting failure are in use case (3) described in comment 88, since it's the default N-M mode of operation. However I agree wpasupplicant needs to be fixed as well, for the case where you would run on wireless with a system connection (is that even possible ?). Looking at wpa-ifdown though, it appears it already has some support for sendsigs omission (at least in Jaunty), so that might not be needed. I need more time on this.