Florian Lohoff schreef: > On Mon, Nov 17, 2008 at 03:01:09PM +0100, Tim Dijkstra wrote: >> > Suspend also takes down networking >> > (/usr/lib/pm-utils/sleep.d/10NetworkManager) whats the point in this? >> I >> > mean if you take down networking you also should take care of taking >> > down network filestems before disabling networking. This is >> inconsitent >> > behaviour ... >> >> That file is or should be part of NetworkManager. I must confess, I'm >> not >> using NetworkManager so I didn't notice it doing evil stuff. FWIW, I'm >> against bringing down network interfaces during suspend. > > Thats just a false assumption - suspend/resume is for 100% of the > Notebook users a mobility issue - so all assumptions about the outer > world dont hold up on a suspend/resume cycle. You might be away 10 > minutes and come back on the same network (unlikely) or stay away for > years or move thousands of kilometers. Thats why usb disconnects all > devices (user might decide to unplug) and all pcmcia devices should get > "ejected", network should be shut down and network filesystems should be > unmounted. The world will most likely look different when you wakeup so > dont take wrong assumptions.
There must be also quite some people that suspend their notebook on their desk. Besides that most modern desktops I've seen also suspend just fine. Anyway, what I wanted to say in all my argumentation so far is that bringing down the network (and with it networked filesystems) is IMHO a policy decision that could be presented as a question by some highlevel app. Also to maybe give the user some time so save their stuff, etc. It should not default to `bring down' at the lowest layer (pm-utils), exactly because there is no reason to do it. Since most wired and wireless network cards have been fixed to survive a suspend/resume cycle there is no _need_ to bring them down. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
