Yeah, and I can't wait for Linux to support POSIX threads
BSD has POSIX threads. Since most of my "serious" machines use NetBSD, and don't really need threads, this is no biggie. If I need them, I've got 'em!
If you want remote accessibility, what's wrong with BackOrifice?
Good point. Maybe some user authentication would be good though. And anyway, it's slow as a week in the jail trying to change a simple config file through a gui interface remotely.
My Windows 2000 machine goes for months without rebooting. The only time it needs to be rebooted is when I want to move it or upgrade hardware.
Bully for you. My Windows 2000 machine runs for a couple of hours between reboots, running Adobe Premiere, AfterFX, and Illustrator. Since most of my work at the moment is video compositing, I can't really get away from these programs. Windows 2000 is not stable, and is not ready for the prime-time yet. Sorry chaps, if it needs rebooted *ever* outside, as you say, physically unplugging the machine to move it, then it isn't a stable OS.
My NetBSD servers haven't needed rebooted in many months, but frankly I don't want to get into a pissing contest about it.
My main contention is that I don't want to use a GUI for a server. It adds nothing, and only makes maintaining servers over flaky connections even more difficult. So can anyone tell me, why is a GUI a good idea for controlling a server?