[Bush2000]

But with servers, Windows still can't touch Linux or BSD for continuous uptime.

As long as you cover your eyes and forget about the last two critical Linux kernel vulnerabilities.

To begin with, there are the DLLs which cause conflict and require reboots after updates (say hello to downtime).

Actually, these don't require a reboot. The DLLs can actually be renamed and replaced. The fact that the installer asks you to reboot is really a bug in the installer.

Then there's the lack of the Unix equivalent of the separation of Administrator and Root so if you want to do anything, you're running with more privileges than you need. Then you have various installers that turn on services previously turned off.

Wrong. You can create Windows users with arbitrarily complex masks of capabilities -- which provides the same functionality.

[antiRepublicrat]

As long as you cover your eyes and forget about the last two critical Linux kernel vulnerabilities.

You mean like the one you don't have to apply if there's physical security for the system, as is for most server farms? I don't know enough about these particular bugs, do you have to reboot after applying the patches?

Actually, these don't require a reboot. The DLLs can actually be renamed and replaced. The fact that the installer asks you to reboot is really a bug in the installer.

Then it's been a bug for many years, and even Microsoft isn't that bad. The fact is that if you don't reboot you risk DLL Hell, and some things do absolutely require reboots.

You can create Windows users with arbitrarily complex masks of capabilities -- which provides the same functionality

Then from the point of any user except for places where a Windows expert has taken hours to create a new group, it's a flaw.