On Mon, Nov 17, 2008 at 04:17:04PM +0100, Tim Dijkstra wrote: > 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.
I see it the other way round. Making assumptions about the situation on
resume is a policy decision - IMHO suspend/resume should be more like
init s, init 2 e.g. half a reboot environment wise. Assuming the network
setup is the same and storage is still there is an assumption i guess
can not hold up 90% of the time.
And its not about the wired/wireless drivers not surviving. Bringing
down the network is done because the network environment will most
likely change and releasing a DHCP lease on suspend is polite behaviour.
I am not network connected while suspended so tell the network about it.
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
