Originally Posted by Plan9
If you configure the network in a GUI network manager then the network it's being connected / disconnected in your X session. if you configure your network in a start up daemon then it will behave as you expect, but obviously you then have an issue if this device is portable and you want to connect to hotspots (though in those instances yourSMB mounts wouldn't be accessible anyway)
Fstab , and to a degree autofs too, aren't designed for roaming devices in much the same way that GUI network managers aren't designed for static systems with static network shares.
I will grant you this seems really counter intuitive to a Windows user, but that's just a facet of the different directions desktop and server Linux has gone.
Fair enough. Well it seems to work the same as Windows ... until you restart or shutdown (i.e. log off doesn't effect the network). I think its a poor decision to take the network down that early. Why should it follow the X session? Why can't the GUI just configure
the network, and the kernel handles the rest?
Unfortunately network-manager doesn't implement pre-up or pre-down (just up and down) so I can't even do anything before it rips the network right out under me.
So that means CIFS mounts are never actually cleanly unmounted. How horrible. Oh well.
Anyway the root issue (mounts hung after resume from sleep) still isn't fixed after updating to Jessie with the latest kernel. Its only a minute or two but ... meh. I'll get used to it. I like you Linux but you need to fix some weird ass crap before I'll take you seriously on my desktop