Advocacy and mindlessness

Status
Not open for further replies.

IMarshal

Ars Tribunus Militum
1,956
In a bored moment today, I happened to stop by OSOpinion. There I found a particularly amusing "opinion", which is humorous not because of its poor writing, cluelessness or bias, which one has to take for granted on this site, but because literally every point the man makes is either wrong or inaccurate. And the sheer tone of it makes textbook reading for students of advo-psychology.<P>The only reason I regret posting this is that I'm preempting the usual 'OSOpinion exposes NT as poser OS' article from treatment.<P>While reading, ask yourself this: "if I were this clueless, would I be exposing my opinions to the world like this?"<P>Why Windows NT Sucks, Part 2 - Is WinNT Ready For The Enterprise?
 

IMarshal

Ars Tribunus Militum
1,956
Not bad. It beats mine for attitude, although mine has your beaten on cluelessness.<P>One gem from "Mike": after failing to understand the meaning of "RTM" and calling W2K an "unnecessary" and "unproven" OS, he goes on to say:<BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>I don't hate MS. But if they spent more time trying to fix what's wrong with Windows 95/98 and NT, and less time trying to kill off the competition, I'd like them more.<HR></BLOCKQUOTE><P>So what does he think Windows 2000 is, if not a major overhaul of the bad things in '98 and NT?
 

Zagato-sama

Ars Scholae Palatinae
1,010
Actually your's are just a copy of "Linux myths" by Microsoft. Only in reverse direction and not layed out proffesionaly View image: /infopop/emoticons\icon_wink.gif Ham radio aside, half the stuff stated about NT is either fluff, or is resolved in Win2K. Sound familiar? I think Linux advocats have exhausted the right to use the acronym "FUD" <P>Anyway time for me to go shopping for a two button mouse as this 3 button logitech is 'faking' working under NT. Don't you hate it when your hardware does that?
 
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.
 

Evil_Merlin

Ars Legatus Legionis
23,723
Subscriptor
Actually the whole anti-MS thing is rather amusing. The anti-Microsoft herd has been claiming all kinds of "wonderful" things about NT, Win9x and what-not for years now. The MacJihad and the rabid Linux people (not all Linux people are rabid) seem to know even less about NT and Windows than my wife does (who just installed Windows2000 last night with no input from me, she was happy she could finally help me with a computer...), as all the claims about "crashing a ship", "daily reboots", "slow system performance", and other crap gets amusing to hear as I continue using my Windows NT system (with a more than 2 year up time currently), wondering how the hell the people that supposedly run those computers still have jobs, or ever got jobs to begin with.<P>One read of the Mac pages listed below, or Slashdot prove that fanatics are indeed a bad thing....
 

IMarshal

Ars Tribunus Militum
1,956
Concerning the Yorktown, a reputable source such as comp.risks says:<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>in September 1997, the Yorktown suffered a systems failure during maneuvers off the coast of Cape Charles, VA., apparently as a result of the failure to prevent a divide by zero in a Windows NT application. The zero seems to have been an erroneous data item that was manually entered<HR></BLOCKQUOTE><P>Source: http://catless.ncl.ac.uk/Risks/19.88.html#subj1.1<P>In other words, the failure appears to have occurred in the Navy's custom software that was running on NT, and was caused by some kind of user input that wasn't expected by the program's authors.<P>I've always found it rather odd that so many Linux advo-drones use this as an example the inadequacy of NT. I mean, does Linux have a magic config file option that protects 3rd party software from its own bugs?
 

Coredog64

Ars Tribunus Angusticlavius
7,578
If you want to see some real mindlessness, check out the Kirch paper: http://www.unix-vs-nt.org/kirch/ <P>The guy is NT _3.51_ certified and passes himself of as an MCP (yes, I know that those tests don't expire for another few weeks View image: /infopop/emoticons/icon_smile.gif<P>Check out the age on all of his links. NT 3.51 vs. BSD? NT 4.0 vs RH 5.0 circa 1997?<P>I actually had a chance to correspond with the guy. I pointed out that most of the freeware that makes a Linux distro useable (i.e. Perl, gcc, mail and web servers) is available freely. His response? Doesn't count, because it doesn't come on the OS CD from the manufacturer!<P>Check it out. It should be good for a few grins.
 

_klamath_

Ars Scholae Palatinae
770
It's interesting that in a thread commenting on cluelessness, PeterB has contribued some of his own:<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>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.<HR></BLOCKQUOTE><P>What? If an FS predates NT4, then the FS would be out BEFORE NT4. Therefore, there is no reason NT4 shouldn't support it. If you meant that NT4 came out before FAT32 (i.e. NT4 predates the FS), then why couldn't M$ have added support in a service pack?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>Is Network FS the same as NFS? Windows NT can do that.<HR></BLOCKQUOTE><P>I'd be interested to see that....<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>Heh. Windows NT can format NTFS floppies, actually, but you have to trick it <HR></BLOCKQUOTE><P><sarcasm>gee, I *wish* I could be using WinNT right now</sarcasm><P> <BLOCKQUOTE><font size="-1">quote:</font><HR>NTFS has the capability [quotas], since NTFS 4, but it went unimplemented. I *think* that third parties implemented it, but I'm not certain.<HR></BLOCKQUOTE><P>Thats another thing that annoys me about WinNT - the core OS is expensive enough; but in order to be able to do anything useful, you need X 3-rd party add ons.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>So don't use the Explorer shell. There's nothing forcing you to use it.<HR></BLOCKQUOTE><P>Except for the fact that (nearly) all other shells suck. There is no point in denying that Linux gives you more choice than Windows - in GUI environment, shell, etc.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>NT, because of its different market, needs local storage and such. Gosh.<BR><HR></BLOCKQUOTE><P>And what "different market" would that be? Linux can be run on anywhere from diskless terminals and Palm-size PCs to supercomputers and Beowulf Clusters. If NT can't scale as well as Linux, well that is NT's fault.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>Such features are generally for terminals, not workstations or servers.<HR></BLOCKQUOTE><P>And since when is having more features, and more flexibility, a bad thing?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>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.<HR></BLOCKQUOTE><P>Are you trying to say that Windows has more scripting tools available for it than Linux/*NIX?<BR>[..]<BR>Too tired to shoot down the rest of your hair-brained points, PeterB. Sorry! <P>G'night.
 

Horatio

Ars Legatus Legionis
24,224
Moderator
I'm going to have to refute a few of klamath's points here...<BR> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>quote:<BR>--------------------------------------------------------------------------------<BR>Is Network FS the same as NFS? Windows NT can do that.<BR>--------------------------------------------------------------------------------<P>I'd be interested to see that....<P><HR></BLOCKQUOTE><BR>Actually, it's pretty easy. You just need to install MS Services For Unix, and you're ready to go. It's like Samba in reverse...<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>quote:<BR>--------------------------------------------------------------------------------<BR>NTFS has the capability [quotas], since NTFS 4, but it went unimplemented. I *think* that third parties implemented it, but I'm not certain.<BR>--------------------------------------------------------------------------------<P>Thats another thing that annoys me about WinNT - the core OS is expensive enough; but in order to be able to do anything useful, you need X 3-rd party add ons.<BR><HR></BLOCKQUOTE><P>Well quotas were implemented in some service pack or another... But most needed functionality is available out of the box. The only thing that I need a 3rd party app for is X Windows.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>quote:<BR>--------------------------------------------------------------------------------<BR>NT, because of its different market, needs local storage and such. Gosh.<P>--------------------------------------------------------------------------------<P>And what "different market" would that be? Linux can be run on anywhere from diskless terminals and Palm-size PCs to supercomputers and Beowulf Clusters. If NT can't scale as well as Linux, well that is NT's fault.<BR><HR></BLOCKQUOTE><P>Windows runs on many different platforms too... Windows CE to Windows NT Embedded to Windows2000 Datacenter... Admittedly not as many platforms are supported, but Windows does scale quite well. <P>If you've ever used a Beowulf cluster, you'd know that it has lousy parallel performance due to its slow network. We have a nice 64 proc cluster running linux, and it kick ass for trivially parallizeable apps (raytracing, TSP, etc...), but is lousy when there is a lot of communication (SPLASH2 bench). (OK, we're trying to use a 100BT network here, so it's partially our fault...)<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>quote:<BR>--------------------------------------------------------------------------------<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.<BR>--------------------------------------------------------------------------------<P>Are you trying to say that Windows has more scripting tools available for it than Linux/*NIX?<BR><HR></BLOCKQUOTE><BR>Are you trying to say that you write scripts in something other than bash, Bourne shell, Perl or AWK? Having 100 useless scripting languages is much worse than having 3 good ones. Really, all you need is Perl (IMHO).<P>
 
<BLOCKQUOTE><font size="-1">quote:</font><HR>What? If an FS predates NT4, then the FS would be out BEFORE NT4. Therefore, there is no reason NT4 shouldn't support it. If you meant that NT4 came out before FAT32 (i.e. NT4 predates the FS), then why couldn't M$ have added support in a service pack?<HR></BLOCKQUOTE><BR>Oh gosh, as you can, I'm sure, work out for youself, that was just a slip of the fingers. NT predates FAT32 is what I meant to say, as you well know.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>--------------------------------------------------------------------------------<BR>Is Network FS the same as NFS? Windows NT can do that.<BR>--------------------------------------------------------------------------------<BR>I'd be interested to see that....<HR></BLOCKQUOTE><BR>I'm sure you would. It's not very difficult. The thing you need are the NT Services for Unix -- one of MS's better kept secrets. That includes, amongst other things, full NFS support (accessing NFS shares and creating one's own) and a telnetd.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>--------------------------------------------------------------------------------<BR>Heh. Windows NT can format NTFS floppies, actually, but you have to trick it <BR>--------------------------------------------------------------------------------<BR><sarcasm>gee, I *wish* I could be using WinNT right now</sarcasm><HR></BLOCKQUOTE><BR>Just why would you want an NTFS floppy? It was a meaningless thing to say when discussing if NT is ready to be an enterprise OS. All I'm saying is that the original writer is wrong to think that NT can't do it.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>--------------------------------------------------------------------------------<BR>NTFS has the capability [quotas], since NTFS 4, but it went unimplemented. I *think* that third parties implemented it, but I'm not certain.<BR>--------------------------------------------------------------------------------<BR>Thats another thing that annoys me about WinNT - the core OS is expensive enough; but in order to be able to do anything useful, you need X 3-rd party add ons.<HR></BLOCKQUOTE><BR>One thing that annoys be about Linux is that it's only free if your time is also free. Mine isn't. I'd rather pay a 3rd party for an off-the-shelf drop-in solution, actually.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>--------------------------------------------------------------------------------<BR>So don't use the Explorer shell. There's nothing forcing you to use it.<BR>--------------------------------------------------------------------------------<BR>Except for the fact that (nearly) all other shells suck. There is no point in denying that Linux gives you more choice than Windows - in GUI environment, shell, etc.<HR></BLOCKQUOTE><BR>That all the other shells suck is nothing to do with Windows (IMO they don't all suck anyway). And how is this important for an enterprise class OS?<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>--------------------------------------------------------------------------------<BR>NT, because of its different market, needs local storage and such. Gosh.<BR>--------------------------------------------------------------------------------<BR>And what "different market" would that be? Linux can be run on anywhere from diskless terminals and Palm-size PCs to supercomputers and Beowulf Clusters. If NT can't scale as well as Linux, well that is NT's fault.<HR></BLOCKQUOTE><BR>The ability to run on diskless terminals isn't particularly relevent to an enterprise OS. That's what the article was about.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR><BR>--------------------------------------------------------------------------------<BR>Such features are generally for terminals, not workstations or servers.<BR>--------------------------------------------------------------------------------<BR>And since when is having more features, and more flexibility, a bad thing?<HR></BLOCKQUOTE><BR>We are discussing enterprise server OSes.<P><BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>--------------------------------------------------------------------------------<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.<BR>--------------------------------------------------------------------------------<BR>Are you trying to say that Windows has more scripting tools available for it than Linux/*NIX?<HR></BLOCKQUOTE><BR>Where did I say that? What I was saying was, the original author is just plain wrong to say that NT only comes with batch files, and is wrong to cite (say) Bash as a *nix-only advantage.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>[..]<BR>Too tired to shoot down the rest of your hair-brained points, PeterB. Sorry! <BR>G'night.<HR></BLOCKQUOTE><BR>Yeah, well, I feel well and truly shot down....
 
And here are a few useful links:<P>Download the beta of the NT services for UNIX: http://www.microsoft.com/windows2000/library/planning/interop/sfu.asp <P>The link is at the bottom of the page.<P>Dynamically load and unload NT device drivers: http://www.osr.com/resource/files/osrloaderv22.zip <P>It creates and removes the necessary registry entries for kernel-mode drivers, and allows them to be loaded and unloaded at will. I've used it with, for instance, the SBLive device driver (emu10k1.sys I should think), and it damn well works. No rebooting for new drivers 99% of the time.
 

.劉煒

Ars Legatus Legionis
54,024
Subscriptor
Hey .. since when is USB support availible for NT4? ..<P> View image: /infopop/emoticons/icon_smile.gif<P>And, also .. the lack of DX gamepad support really does suck. My uber whizzer gravis Xterminator detects as a ... 4 button gamepad. Go fig.<P>Yeah, yeah, it's all fixed in NT5 .. rigggghhhht.<P>Heck, I'd just be happy with full DX7 and Device support in NT4. Dunnae need no active services.. no IE bundleing.. <P>Oh, and if you don't like exploder.. check out geoshell .. (www.geoshell.com)<P>(and dont' mind the blathering, I've been awake for a bit.)
 

Coredog64

Ars Tribunus Angusticlavius
7,578
Re: USB and NT<P>IIRC, Blue Water Systems makes a driver SDK that allows IHVs to write<BR>USB drivers for NT 4.0. I don't think it's the same 100% support you<BR>get in 98/2000. So USB is doable in NT 4.0 (or at least as doable as kernel 2.4 View image: /infopop/emoticons/icon_smile.gif )<P>However, WTF does USB support have to do with an enterprise class OS? Does someone make a RAID that only interfaces using USB?<P>
 

_klamath_

Ars Scholae Palatinae
770
Horatio + PeterB, thanks for the info re: MS Services for Unix. Cool...<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>Are you trying to say that you write scripts in something other than bash, Bourne shell, Perl or AWK? Having 100 useless scripting languages is much worse than having 3 good ones. Really, all you need is Perl (IMHO).<HR></BLOCKQUOTE><P>Good point - but more choice is always good. And is there a Wintel equivelent of <I>expect</I>? Or has that been ported to Wintel?<P>(PeterB):<BR> <BLOCKQUOTE><font size="-1">quote:</font><HR>Oh gosh, as you can, I'm sure, work out for youself, that was just a slip of the fingers. NT predates FAT32 is what I meant to say, as you well know.<HR></BLOCKQUOTE><P>You mean a slip of the tongue? *smile*<P>
 
Oh, and NT can do load balanced clustering too. Cluster aware applications will spread their load across multiple machines. It's not the same as Beowulf clustering, but NT *can* cluster and *can* distribute load across multiple machines, and it can do redundant clustering and so on.<P><BR>No, I mean slip of the fingers; I was typing, wasn't I?<P>
 

IMarshal

Ars Tribunus Militum
1,956
<BLOCKQUOTE><font size="-1">quote:</font><HR>more choices = good only applies in the case of "good choices" <HR></BLOCKQUOTE><P>In general, I disagree with this. More choices usually leads to better choices, eventually, so I think espousing this view implies a very short term view of markets. I do agree that in your particular example and in others your statement is accurate. But in general, I think it's obvious that an abundance of choices leads to greater competition and better products.<P>In the case of NT scripting vs. Linux scripting, more is only better if the particular package you want on one platform is only available on the other or is less functional. While WSH on NT is extraordinarily powerful, and NT has Perl and most of the good Linux scripting options, the UNIX design philosophy leads to applications that are a lot easier to script than your average Windows application. Passing judgement here almost requires a subjective decision, so I think I'll pass.
 

.劉煒

Ars Legatus Legionis
54,024
Subscriptor
Well .. View image: /infopop/emoticons/icon_smile.gif SOmeone earlier did mention USB as a strongpoint of NT. (4) ina rebuttal. <P>IHV's may be able to write drivers, but, point is, they don't exist for the hardware I use right now. Which is the important part, n'est-pas?<P>As for w2k (ick.. I prefer NT5 as a name,go fig) .. I tend like a long, stable enviroment, not one that'll expire in .. oh, however many days, for my personal boxen.<P>So, when I can upgrade without killing my settings, I'll go. Otherwise.. *whine* ... And seriously, the *only* features of nt5 (pttpt) that are valuable to me are DX7 and better PNP support. *shrug*. Don't need active directory, etc .. in an enviroment, imho. View image: /infopop/emoticons/icon_smile.gif At least not until it fully supports (and is supported by) more OS's than just win32 stuff.
 
Status
Not open for further replies.