Michael W. Ryan on Fri, 18 Feb 2000 15:05:52 -0500 (EST) |
On Fri, 18 Feb 2000, Adam Turoff wrote: > So, MS is trying to lull the networking public into a false sense of > accomplishment and security by defining "good enough" as something > that is as insecure or unstable as NT. Being 20% better than NT isn't > any better, since it's still falling short. Okay, hang on a sec. Let's make this concrete (it's easier to discuss). How is it falling short? It's a semi-rhetorical question (I'm not sure if the answer is germaine to here), but if we just say "Windows isn't good enough" without being prepared to state how, we run the risk of using the same FUD as Microsoft. > For many uses, Windows/NT/etc. does not provide the bare minimum > requirements; other times it does. But once the argument has > successfully shifted, those advocates of the better way (e.g. > linuxfolk) are forced to be defensive and address the 'overly perfect' > or 'overly pure' critiques, when perfection and purity aren't the issue. Okay, assuming we're actually discussing something that could be turned into an "advantages of Linux over Windows" argument, we don't want to declare Linux to be the "better way" in such general terms. > Mike has pointed out deficiencies in Active Directory for small businesses. > I'm sure there are other things that Win2k won't do, even if it makes > a better effort than NT. I didn't say "won't". It's not even a matter of "too difficult". It's a matter of requiring more up-front planning/design than a small business may want to devote. > All of that aside, what is Win2k doing *well*? Why is Linux not an > option for these uses? Well, given that the only production deployments that anyone has really done so far are on laptops (it takes to a laptop like a duck to water), this isn't really a fair question. Instead, I'll address the stanard WinNT gripes: 1) 100,000 reboots I believe the current reboot conditions number only a couple dozen. I have WATCHED a Win2k system do a complete PnP redection of its hardware, including the PCI bridge, and not require a reboot. I've uninstalled and reinstalled services and not required a reboot. Oh, and this was beta 3. 2) Blue Screen of Death I've only seen BSoDs due to either hardware or BIOS problems. Win2k Adv. Svr. Beta 3 + Exchange Platinum Beta required doings something EVIL to the system to get it to crash (incidentally, the "bug" was that it let us do it, and it was fixed in the RC version). 3) Driver Nightmare PnP that works combined with a HUGE HCL makes this a moot point. Where people are running into problems is with wierd, third party, fly-by-night hardware. 4) DLL Hell Win2k has had some significant changes in how it handles DLLs in order to deal with this issue. I'm not real up on the details, however. 5) Cost No real improvement here. 6) System Requirements Yeah, P-166/64MB is a bit hefty for a minimum. Michael W. Ryan, MCP, MCT | OTAKON 2000 mryan@netaxs.com | Convention of Otaku Generation http://www.netaxs.com/~mryan/ | http://www.otakon.com/ PGP fingerprint: 7B E5 75 7F 24 EE 19 35 A5 DF C3 45 27 B5 DB DF PGP public key available by fingering mryan@unix.netaxs.com (use -l opt) ______________________________________________________________________ Philadelphia Linux Users Group - http://plug.nothinbut.net Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|