| Leonard Rosenthol on Wed, 10 Jan 2001 13:17:26 -0500 |
|
At 10:50 PM -0500 1/9/01, Beldon wrote: I said, "Because Unix handles tasks differently. There isn't the same amout of resource contention on equal equipment because it's all about process control, rather than threads. Each process has its own space that appears exclusive to that process. That's why when an app crashes, it doesn't bring the system down." As far as memory protection (ie. each process gets its own protected space) go, NT and Unix are indeed pretty similar - there aren't all that many ways to do a real memory protected OS ;). However, as Mike points out, there are LOTS of other things running around on NT that are playing where they shouldn't, that have known bugs and problems, and that eat up "resources". This becomes even MORE true the more processes/applications you start running on it. As you point out, an NT system can indeed be quite stable - as long as you reboot it often enough! They simply don't have the uptime that you really want in a REAL server OS. Unix doesn't have these problems because it was designed from the "beginning of time" (FYI: that's in 1970, just ask ctime(0)) to be a server OS with uptime being critical, so even things like drivers are protected as well (within limits as needed for hardware, etc.)
|
|