Linked by Adam S on Tue 28th Sep 2004 22:29 UTC
I've been using Windows as a network administrator for just over 6 years now. I've used NT4 servers, 2000 servers, and Windows 2003, and there has been a tremendous improvement with each version. There are still some things that drive me nuts in my job, though, and this is a chronicle of the top five.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
The rebooting is _almost_ understandable, atleast depending on
the tings that get updated. If it's a core program/library/kernel/driver that's updated, one might as well reboot, for all running things to pick it up.
Same thing on linux(almost), you update e.g. gtk or say libpng, you don't have to reboot, _but_ running programs still uses the old library. All programs affected have to be restared. If a core lib like e.g. glibc is updated, you migth as well just reboot. You don't want to risk having some program running with the old/insecure one ?
What is not understandable is the per update install/reboot ofcourse. Clicking through wizards, installing, reboot, process next update. Annoying as he**.
Please give us win-get update && win get upgrade