This is long.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>1) File Systems.<P>WinNT supports only four file systems; NT's own NTFS, FAT16 (the old DOS FS, without support for long filenames), NetWare and Macintosh file systems. It does not even support FAT32, the Win98 FS.</small><HR></BLOCKQUOTE><BR>Oh yeah? It does, through third part support. Win2K does it natively. But gosh, NT 4 doesn't support natively an FS that predates it. Well, lummy, that's a surprise.<P>And what about FAT 12? Or are you telling me that NT can't read floppies?<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Linux supports ca. 30, including all the preceding, and the Network FS, which makes it possible to combine all the computers on a LAN into a single directory structure.</small><HR></BLOCKQUOTE><BR>Is Network FS the same as NFS? Windows NT can do that.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>The Windows 2000 equivalent is an Active Directory, which will be available in 2001, D.v. Linux can format NTFS floppy disks, but WinNT cannot!</small><HR></BLOCKQUOTE><BR>Heh. Windows NT can format NTFS floppies, actually, but you have to trick it (details are, IIRC, on the sysinternals site). NTFS has far too high overheads for floppies; that's why FAT 12 is used for floppies. When NT formats an NTFS partition it *deliberately* writes a 2 Mb file (I think into the $Extend directory) to prevent the usage of NTFS on floppies.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>2) Administration.<P>WinNT does not have disk quotas, so it is possible for a user to fill up an entire file system and bring the WinNT server to a halt.</small><HR></BLOCKQUOTE><BR>NTFS has the capability, since NTFS 4, but it went unimplemented. I *think* that third parties implemented it, but I'm not certain.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Win2k will have this feature,</small><HR></BLOCKQUOTE><BR>Will have? Does have, ducky. My CD's in the post.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>D.v. Linux and WinNT both have Access Control Lists, but WinNT does not have the concept of file ownership by group and user.</small><HR></BLOCKQUOTE><BR>I'm not sure what this means; I can set a file to be viewable by, say, the "Administrators" group, and it's accessible as you might expect; by any member of "Administrators" but that might be Win2K-only.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>This means that the WinNT sysadmin has to set the permissions for every file... unless he is proficient in Perl.</small><HR></BLOCKQUOTE><BR>I also have lovely little tickboxes that let me decide if permissions are inherited or not. I can also select a bunch of files at a time and set their permissions, even if they're in different folders and/or hard disks.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>3) Graphics. <P>Linux supports a dozen graphics libraries from the simple (svgalib) to the highly complex (X11, or the X Window System).</small><HR></BLOCKQUOTE><BR>NT doesn't support X? Er, since when? And what does it matter than NT doesn't supply Linux (or *nix)-only graphics APIs? Where's DirectX for Linux?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>With WinNT, you can have either the Windows window manager or text. Linux will let you have 12 full-screen text sessions open.</small><HR></BLOCKQUOTE><BR>NT allows as many as you have memory for; you can have loads of full-screen command prompts and alt-tab between them, if you want.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Under X11, you have a choice of window managers such as KDE, Gnome, WindowMaker and AfterStep. KDE has many, many more features than the Windows desktop.</small><HR></BLOCKQUOTE><BR>So don't use the Explorer shell. There's nothing forcing you to use it.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>4) Hardware.<P>Windows NT does not support?<P>? AX25, packet-switching ham radio.</small><HR></BLOCKQUOTE><BR>All it takes is an IHV to write a driver.<BR> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? USB (Universal Serial Bus).</small><HR></BLOCKQUOTE><BR>Interestingly enough, the Win9x USB core components are all version stamped "Windows NT".<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? Infra-red modules on the motherboard.</small><HR></BLOCKQUOTE><BR>All it takes is an IHV to write a driver.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? Plug'n'Pray PCI cards. Very odd, when you consider that Microsoft was one of the driving forces behind this technology. But don't expect Win98 to have the right driver for a PnP device.</small><HR></BLOCKQUOTE><BR>Plug and Play is properly only applicable to ISA, and yes, the pnpisa.inf driver is not 100% reliable. But Win2K handles me swapping cards and resources like a dream.<P>And what does Win98 have to do with this? It's got the widest range of drivers I've ever seen....<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>?remote or diskless boot-up. A Linux machine can download its boot image over a LAN.</small><HR></BLOCKQUOTE><BR>NT, because of its different market, needs local storage and such. Gosh.<P>Such features are generally for terminals, not workstations or servers.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? 3-button mice. This isn't trivial if you use the mouse a lot.</small><HR></BLOCKQUOTE><BR>So, lemme get this straight, I'm only imagining that I can use my wheely mouse in NT am I? Yeah, I thought so.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? game controllers, such as joysticks.</small><HR></BLOCKQUOTE><BR>Hmm. I have a game controller in device manager. I don't have a joystick to test it with, though.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>WinNT does not support many high-end video cards of the type favored by gamers.</small><HR></BLOCKQUOTE><BR>Like? Last time I checked, it was a damn sight easier to get OpenGL and such working for any video card in NT than in Linux. Maybe you mean it doesn't have support for hardware released up to three years after its release in the box. Well, gosh. Just use the driver from the IHV.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>? processors other than the Intel Pentium.</small><HR></BLOCKQUOTE><BR>AMD Athlon? AMD K6? Intel PPro/PII/PIII/Xeon?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Microsoft progressively dropped support for the MIPS, PowerPC and finally Alpha.</small><HR></BLOCKQUOTE><BR>MIPS machines became very rare and very niche -- no market. PowerPC machines are rare, no market. The Alpha did have some kind of a market, but AFAIK Compaq didn't much care for NT, so MS dropped it.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Win2000 will be available for the Itanium (aka Merced, Intel's new 64-bit processor) in 2001, D.v. Linux has been ported to many platforms--including the Merced.</small><HR></BLOCKQUOTE><BR>So have all manner of RTOSes, and other things. But that doesn't make them good.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>5) Scripting. <P>Most of WinNT's tasks require the admin to be sitting in front of the monitor and clicking menus with the mouse. WinNT has scripts (batch files) and a shell (cmd.exe) but they give the admin little control over the machine.</small><HR></BLOCKQUOTE><BR>Evidently you've never heard of WSH (windows scripting host). That can use OLE automation to control almost anything. That can be programmed in whatever languages you have installed. ATM, I can use VBScript, JScript and PerlScript.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>A lot of the admin's time can be saved by automating tasks such as cleaning up directories while the machine is idle, monitoring users and processes, making reports from event logs, etc. Scripting languages such as Tcl/tk and Perl for Win32 go a long way towards rectifying this deficiency. Microsoft owes the open source community a big "Thank you" for turning WinNT into an approximation of an operating system. Linux offers several shells (command interpreters), such as bash, zsh, tcsh and pash, and each one can be customized to the user's taste.</small><HR></BLOCKQUOTE><BR>Bash, at least, is available for Win32 anyway. Windows has a whole host of scripting tools available for it; WSH comes out of the box.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>6) Parallel processing.<BR>Some memory-sharing NT clusters have been built, but they are small (4-8 machines) and require a Linux server! Linux MPPs can be configured for SIMD, MIMD, SPMD, message passing, shared memory and aggregate functions--whatever they are. Without the source code, you cannot get the requisite low-level memory access. Look at
http://cnls.lanl.gov/Internal/Computing/Avalon/FAQ.html, particularly question 17.</small><HR></BLOCKQUOTE><BR>So, NT can't do very well that which it isn't designed for. That's amazing.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>7) Kernel.<P>Several studies have shown that Linux is a faster web server than WinNT on all but the most expensive equipment.</small><HR></BLOCKQUOTE><BR>And several have shown the opposite, from which we conclude, studies are worthless.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>(Okay, *BSD is faster still). WinNT lacks a number of kernel optimizations for Web serving, such as telnet in kernel,</small><HR></BLOCKQUOTE><BR>Please, someone, explain why you need telnet in kernel for good webserving. Actually, explain what telnet in kernel even means. A telnet daemon? Or a telnet program? Or what?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>kernel sockets, real time protocol, etc. Linux has insmod and delmod, but WinNT cannot load and unload device drivers while running.</small><HR></BLOCKQUOTE><BR>Horseshit. Tomorrow I shall post a link to a piece of software that does just that. I use it all the time, and it works perfectly. I'd post the link now, but my PC is sitting upstairs, and I'm not going all the way upstairs.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>That is something you should consider if you are planning on buying a server with hot-swappable drives.</small><HR></BLOCKQUOTE><BR>Um, no, it evidently isn't. Our servers (IBM Netfinity 5500 M20 PoSes) have hot-swappable drives. And they run under NT. And they have hot-pluggable PCI cards. Which all work. Under NT.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>8) Software Development Cycle.<BR>WinNT lacks ca. 20 Unix-specific system calls, so that cumbersome workarounds are required when porting Unix apps to WinNT.</small><HR></BLOCKQUOTE><BR>And how many Windows-specific system calls does Unix lack? If you want POSIX compatibility for NT, just go out and buy it. IIRC, MS have bought a company who sold just that, recently.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>The Win32 API implementation of inter-process communication does not distinguish among the various classes of IPC, requiring the developer to perform back-flips through flaming hoops to keep track of one particular thread. For these and other reasons, the software development cycle is longer under WinNT than under Unix. Estimates vary from "twice as long" to "orders of magnitude" longer (see
www.opensource.org/halloween/halloween1.html). Debugging WinNT kernel device drivers is particularly difficult, and requires the use of two machines connected by a serial cable!</small><HR></BLOCKQUOTE><BR>Debugging by serial link is hardly unique to NT. As for the rest, I'd like something a bit harder than 'estimates'.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Okay, now for the flip side. Linux does not have . . .<BR>b) ?drivers for the latest hardware, particularly scanners and printers that use the Windows Printing System. If there isn't a Linux driver, it's because the manufacturer has not published the card's specifications. Linux can't operate Winmodems, but now there are Linmodems!</small><HR></BLOCKQUOTE><BR>Can't argue with this....<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>c)?registries. All the information about a WinNT box is kept in the Registry. Since it is not human-readable, and it is accessible only from the GUI, you are in deep doo-doo if it gets munged.</small><HR></BLOCKQUOTE><BR>Uh, since when? Since when has it been impossible to get a text version of the registry, editable in DOS edit, and reimportable into NT? I can edit the registry with a text editor just fine. It doesn't need any fancy third party tools or anything.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>d) ?defraggers. Ext2, Linux's file system, is designed to make defragging unnecessary.</small><HR></BLOCKQUOTE><BR>Linux has no defraggers? News to me. Fragmentation is unavoidable (it seems -- both EXT2FS and NTFS are designed to avoid fragmentation, both EXT2FS and NTFS suffer from it anyway).<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>e)?the Blue Screen of Death. Yeah! All right! Woo-hoo!</small><HR></BLOCKQUOTE><BR>No, it just has kernel panics and dumped cores.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>But my experience with WinNT has been that you're lucky if you DO get a BSOD, because you can then shut down the app.</small><HR></BLOCKQUOTE><BR>Er, no, BSOD means blue screen *of*death*. The machine needs rebooting. Perhaps you're confusing NT with Win9x which throws up all manner of non-fatal gr[ae]y text on blue background error messages.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Usually the machine just locks up and you have to reboot.</small><HR></BLOCKQUOTE><BR>If it's a BSOD, that's always.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>I'm always amused by the message, "This application has performed an illegal operation . . ." What kind of operation? A lobotomy?</small><HR></BLOCKQUOTE><BR>No, an illegal operation. Illegal as in, not allowed, operation as in, operation. An operation that's not permitted, normally because it would require reading from or writing to memory that's not allocated to a particular task.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>I must mention other OSes so their devotees won't feel slighted. If you're a Macophile or a BeOS fetishist . . . well, I don't understand how anyone can have a taste for that sort of thing, but I won't pass judgment on those who practice alternate lifestyles.

</small><HR></BLOCKQUOTE><BR>Ho ho ho. How very decent of you. Wanker.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><small>Recently the mainstream media have been asking, "Is Linux ready for the enterprise?" They should be asking, "Is WinNT ready for the enterprise, after all this time?" If we're talking about aircraft carriers or starships, the answer to the latter question is a resounding "No!" Remember that a WinNT crash left the USS Yorktown dead in the water for four hours.</small><HR></BLOCKQUOTE><BR>Gosh. What I've not been able to find out about that (perhaps someone can enlighten me) is was that an NT problem, or a screwed up device driver, or a piece of hardware going AWOL?<P><BR>Well, there we have it. All in all a pretty dumb piece of writing by whoever did it. Evidently they don't know much about anything.