Slashdot Mirror


Should The Next Windows Be Built On Linux?

scrm writes "The next version of Windows should be built on top of Linux, according to this article by Robert Cringely of PBS." If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they?

763 comments

  1. Re:No, it should be built on FreeBSD by Anonymous Coward · · Score: 0, Funny

    Are you sure? I heard a rumor that FreeBSD was dying.

  2. And compromise compatibility with drivers, etc by Uksi · · Score: 3, Insightful

    I'm sure that a lot of Windows driver developers will enjoy porting their drivers over to the Linux architecture.

    1. Re:And compromise compatibility with drivers, etc by perotbot · · Score: 2, Funny

      You mean we'll finally get winmodem drivers for linux??? whooo hoooooooo! I can use by thinkpad!

      --
      ~corporate tool, but employed~
    2. Re:And compromise compatibility with drivers, etc by GrenDel+Fuego · · Score: 3, Informative

      They already exist. Not for every modem, but a number of more common ones.

      IBM even provides links to some of the drivers I believe.

    3. Re:And compromise compatibility with drivers, etc by miu · · Score: 5, Insightful
      Have you read this dope's article? I'm begining to wonder if he even knows what a computer is much less an operating system. There are so many holes/problems with this guys article and way of thinking that I don't even know where to begin. I mean damn!

      Yeah, Cringely is either incompetent or trolling for readers. A couple of glaring errors are worth pointing out:

      Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.
      Wrong. cmd.exe != DOS
      Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux.
      Wrong again. explorer.exe != Windows
      Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve. As Mike Class points out, by not having to develop its own OS, Microsoft could also save money. They wouldn't need however many people are presently devoted to maintaining the underlying OS that isn't supposed to be there.
      Strike three! There are lots of things to like like about Linux, but these claims are ridiculous.
      --

      [Set Cain on fire and steal his lute.]
    4. Re:And compromise compatibility with drivers, etc by JonathanX · · Score: 1

      Agreed. He seems to have a total lack of understanding about how the NT based kernels work.

    5. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 1, Informative

      Try linmodems.org.

    6. Re:And compromise compatibility with drivers, etc by LostCluster · · Score: 4, Informative

      The C:\ prompt within a window has always been an illusionairy thing. Think about this for a second...

      In Windows 3.1 you could run DOS-atop-Windows-atop-DOS... but if you ever tried to run "Win" in that environment, you would get a message that indicated that Windows-atop-DOS-atop-Windows-atop-DOS just wan't going to happen, you're not at a "real" DOS prompt. You didn't have a full-featured version of DOS there, just the interface level.

      If you carry that forward to XP, the "DOS" in XP doesn't directly control the low-level stuff anymore. Some nameless, faceless part of Windows does.

      DOS-within-Windows is now just an alturnate wacky skin for Windows Explorer. It's just a familiar text-based way to do things, not a low level OS anymore.

    7. Re:And compromise compatibility with drivers, etc by EvilNTUser · · Score: 4, Interesting

      "Yeah, Cringely is either incompetent or trolling for readers."

      Yes he is, but he's just one person. What really saddens me is how pervasive this kind of thinking is. People who genuinely believe XP is based on DOS are a real threat to getting intelligent users to migrate.

      When I was younger, I was originally turned off by the Mac platform because of all the ignorant users. It wasn't uncommon to hear them condescendingly say that Windows is based on DOS and Macs do true multitasking etc. And there I was, sitting in front of a box running a *preemptively* multitasking kernel (NT 4.0 at the time), thinking "there's no way I want to associate myself with these retards".

      When I grew up, I realized how stupid I'd been and acknowledged that I didn't really hate Macs, but their users. Today I might even consider buying one because of OSX, but my earlier feelings show just how much a platform can be hurt by bigoted users.

      --
      My Sig: SEGV
    8. Re:And compromise compatibility with drivers, etc by Grrreat · · Score: 1

      Windows 9X/ME was indeed built on DOS 7.X. I don't believe that Win NT/2000/XP are built on DOS, but rather the NT Kernel, which could easily be consider like the DOS kernel, but built more sturdy. Show XP would be the Windowing system running atop the NT Kernel.

      Please people its imature to believe otherwise.

    9. Re:And compromise compatibility with drivers, etc by NortWind · · Score: 1
      In Windows 3.1 you could run DOS-atop-Windows-atop-DOS

      I think that is the real point, the DOS-atop-Win3.1 was a fake DOS, but the DOS-under-Win3.1 was in fact a real MS-DOS. There is no real MS-DOS under WinXP, or Win2K, or WinNT, it is really OS/2! :-)

    10. Re:And compromise compatibility with drivers, etc by miu · · Score: 2, Informative
      but rather the NT Kernel, which could easily be consider like the DOS kernel, but built more sturdy.

      DOS was pretty much a driver loader built for a real mode cpu. NT is a modern OS. That means:

      • Virtual Memory
      • Protected mode
      • Task Scheduling
      • A filesystem manager
      There is another huge difference is the size of the NT kernel vs. DOS. NT is built "more sturdy" because it would colapse under its own weight if it were not.

      Windows 3.0 had more features of a modern OS than DOS did. It used DOS pretty much the way DOS used the BIOS, bootstrap with it and then shove it into the background.

      --

      [Set Cain on fire and steal his lute.]
    11. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 1, Insightful

      Just to further support your argument, if I install Cygwin on my machine and get a bash prompt, does that automatically mean that I have turned Windows into *NIX?

    12. Re:And compromise compatibility with drivers, etc by shepd · · Score: 1

      >Windows 3.0 had more features of a modern OS than DOS did. It used DOS pretty much the way DOS used the BIOS, bootstrap with it and then shove it into the background.

      Well, DOS would keep running if I ripped the BIOS chips from my XT, IIRC.

      So, if I were to overwrite the memory DOS had loaded itself into with random info after windows 3.0 had loaded, would it have kept running happily?

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    13. Re:And compromise compatibility with drivers, etc by miu · · Score: 2, Insightful
      Well, DOS would keep running if I ripped the BIOS chips from my XT, IIRC.

      Not quite, because DOS itself sometimes used the BIOS services, it just added a "system call" interface over them.

      So, if I were to overwrite the memory DOS had loaded itself into with random info after windows 3.0 had loaded, would it have kept running happily?

      No. Windows 3.0 used plenty of DOS services. Not least of which were real mode device drivers, but also INT 21h.

      Although Windows 3.0 was not an OS ("thing on a thing" was the most common title I remember), it was closer to the CS definition of an OS than DOS.

      --

      [Set Cain on fire and steal his lute.]
    14. Re:And compromise compatibility with drivers, etc by tzanger · · Score: 1

      Not quite, because DOS itself sometimes used the BIOS services, it just added a "system call" interface over them.

      Yes, this was physically possible. The trick was that the BIOS often copied itself into RAM (i.e. it was shadowed) -- so the physical ROM wasn't necessary.

      This was often done (and even current BIOSes do this, although why is often a question) because ROM access is quite slow compared to RAM access. It's a non-issue these days because just like Linux, there really isn't a whole hell of a lot Win2k/XP uses of the BIOS once it's booted.

    15. Re:And compromise compatibility with drivers, etc by spongman · · Score: 2, Interesting
      The idea that NT is OS/2 is complete myth. Sure some of the user-mode API names are similar (mostly because they're similar to their common Win16 ancestors - for ease of application porting) but the underlying kernel architecture is completely different.

    16. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      Not quite, because DOS itself sometimes used the BIOS services, it just added a "system call" interface over them.

      Yes, this was physically possible. The trick was that the BIOS often copied itself into RAM (i.e. it was shadowed) -- so the physical ROM wasn't necessary

      Yes, most BIOS ROM code was shadowed into RAM, however that still renders the earlier point invalid. The BIOS code was still there, even if the ROM was perhaps pulled. Nearly every DOS application made use of both BIOS and MS-DOS interrupt service routines. To even imply that the BIOS was essentially irrelevant once the machine was up-and-running reveals a serious lack of understanding.

    17. Re:And compromise compatibility with drivers, etc by rabidcow · · Score: 1

      DOS-within-Windows is now just an alternate wacky skin for Windows Explorer.

      Technically, no.

      Explorer is three things:
      1. the taskbar
      2. the desktop & its icons
      3. the file/web browser

      Explorer and the command prompt may both provide interfaces to the same sort of thing, but they are completely independant.

    18. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0
      Nearly every DOS application made use of both BIOS and MS-DOS interrupt service routines. To even imply that the BIOS was essentially irrelevant once the machine was up-and-running reveals a serious lack of understanding.

      Using BIOS rather than the DOS interrupts was often needed beause DOS did so little. It made for porting headaches because different hardware vendors made changes to accomodate their devices and some software vendors used ISRs as some sort of library.

      But you are right, many applications used both.

    19. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 5, Informative

      In Windows 3.1 you could run DOS-atop-Windows-atop-DOS... but if you ever tried to run "Win" in that environment, you would get a message that indicated that Windows-atop-DOS-atop-Windows-atop-DOS just wan't going to happen, you're not at a "real" DOS prompt. You didn't have a full-featured version of DOS there, just the interface level.

      Actually, it was the "full-featured version of DOS" running in that DOS prompt under Win3.1 and Win9X.

      The X86 architecture has 2 main modes of operation: real mode (compatibility with 8086/186 processors -- all PCs to this day boot in this mode) and protected mode.

      Under protected mode, it was possible to create something called a Virtual 8086-mode task. This allowed for real mode simulation within a protected mode environment, thus allowing real mode programs to work.

      Each V86 session can, for most practical purposes, be made to think it is the only thing running (with no knowledge that it is being virtualized and having various instructions, operations, and interrupts intercepted by the protected mode operating system.)

      Getting into protected mode from V86 mode is not possible, hence why Windows wouldn't run in a DOS box. It is also possible for real mode programs running in V86 mode to detect V86 mode by checking the appropriate processor status flag (I'm not sure if the OS can intercept this.)

      DPMI (DOS Protected Mode Interface) is what eventually allowed 32-bit DOS programs to run in true real mode or in DOS boxes. In DOS boxes, Windows would be the DPMI server; but in real mode, you'd need an external program to get you into protected mode first -- CWSDPMI, for example.

    20. Re:And compromise compatibility with drivers, etc by buswolley · · Score: 2, Funny

      Microsoft M$ has so much cash on hand they could:
      1)decide they are going to sell refrigerators
      2)spend ten years in refrigerator R&D
      3)flood the refrigerator market
      4)still have cash
      5)profit lol

      so. Linux? no problem.
      this question should have no relation to the relation between programming for windows and Linux etc. it is purely about how rich they are.

      --

      A Good Troll is better than a Bad Human.

    21. Re:And compromise compatibility with drivers, etc by timmyf2371 · · Score: 1
      Perhaps a way to look at DOS and Explorer is that they are both (for lack of a better title) Window Managers. Explorer provides a GUI interface similar to KDE/Gnome, whereas DOS provides a text-based interface, similar to something like Twin.

      Tim

      --

      Backup not found: (A)bort (R)etry (P)anic
    22. Re:And compromise compatibility with drivers, etc by lvdrproject · · Score: 1

      Ah, Microsoft M$. Is that like a sub-division of the real Microsoft, or...?

    23. Re:And compromise compatibility with drivers, etc by runderwo · · Score: 2, Insightful

      Why are the other clueless idiots getting modded up, and this post with correct and informative content gets left at +0?

    24. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      because to be able to mod it up, people would first have to understand it?

    25. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 1, Funny

      He didn't include any digs at Windows.

    26. Re:And compromise compatibility with drivers, etc by ernstp · · Score: 1

      It's kindof like people suggesting that Apple should move everything to x86! Just a stupid idea! "Yeah, I know, they should rewrite everything from scratch!!"

    27. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      absolutely right. one more thing you need to also think about is the fact that acording to the linux licence it cannot be changed then distributed for profit. Micorsoft already has enough legal problems they wont risk trying to build windows on a linux system simply because if they did they wouldnt be able to charge for it. We all know Micorsoft is not going to make any os if they are not going to make any money off of it

    28. Re:And compromise compatibility with drivers, etc by Ponty · · Score: 1

      Right. Everybody knows that it's actually VMS.

    29. Re:And compromise compatibility with drivers, etc by IceFreak2000 · · Score: 0

      So how do they flood the market? Do we assume that the motors would crash, thus causing a Kitchen Flood of Death?

      --
      Life is like a sewer; what you get out of it depends on what you put into it...
    30. Re:And compromise compatibility with drivers, etc by squiggleslash · · Score: 3, Interesting
      The idea that NT is OS/2 is complete myth.
      It's not a myth, but it's a misleading fact that is doubly misleading because there's an OS/2 subsystem in NT that people use as evidence that it's based on the same code as the OS that was marketed as OS/2.

      NT, as a project, started out as "OS/2 version 3". Microsoft and IBM worked together on OS/2 version 1, and planned to split their resources so that IBM would create a version two, that was fully thirty two bit (wouldn't run on the much maligned 80286 and so wouldn't need the kinds of grafts and fixes running on that chip required), and Microsoft would concentrate on producing version three, a complete rewrite that would make use of the latest ideas in operating system design, be secure, genuinely multiuser, run on non-Intel architectures, etc.

      When IBM and Microsoft had their spat, the projects continued, but without Microsoft seeing any need to make the "next generation" OS have anything to do with OS/2 at all. Compatability requirements were dropped to just the command line environment, the operating system was renamed (choose your own favourate urban legend, and about the only real sign that the operating systems were related was that the very first version, 3.1 (yeah, 3.1 - I could be cynical and suggest it's because Microsoft figured they never got anything decent out the door until "version 3" so they might as well jump the line... but I believe the real reason was that they wanted the version numbers to match those of the DOS/Windows line, NT had a Windows 3.1 compatable subsystem after all) could optionally be installed on an HPFS partition - HPFS being the OS/2 file system. This feature was dropped from later versions (I'm trying to remember that far back, but I think one issue was that NTFS wasn't implemented until 3.5 or 3.51 or something. Can anyone help me here?)

      Unfortunately, this story has been misunderstood by a lot of people to mean "NT is just a version of OS/2". It isn't. It owes its history to OS/2, and maybe if OS/2 hadn't happened, Microsoft would be migrating its customers to "Xenix Windows". But that doesn't make it the same code and it isn't.

      --
      You are not alone. This is not normal. None of this is normal.
    31. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      Yeah, Cringely is either incompetent or trolling for readers.

      Or both.

      His website has a section with reader's comments.
      That section is called "baloney".
      I wonder if that's how high he thinks of his readers, or if he just picked the word that occurs the most frequently in the reactions he gets.

    32. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      > In Windows 3.1 you could run
      > DOS-atop-Windows-atop-DOS... but if you ever
      > tried to run "Win" in that environment, you
      > would
      > get a message that indicated that
      > Windows-atop-DOS-atop-Windows-atop-DOS just
      > wan't going to happen, you're not at a "real"
      > DOS prompt. You didn't have a full-featured
      > version of DOS there, just the interface level.

      Not true. Not only could you do this we had users who did and it was a regular support call. The user would boot up, type "win" to get into Windows. Start a full screen DOS shell. Then want Windows again so type "win", then start a DOS shell. Then type "win" again. At this point Windows would fail to start up due to lack of memory and they'd phone support saying, "Windows won't start up". You then just told them to type "exit", then exit Windows, then type "exit" again and they were back to their original base copy of Windows.

      You are however correct in saying that it's different in XP.

    33. Re:And compromise compatibility with drivers, etc by Anonymous Coward · · Score: 0

      I think the better title you're looking for is "shell". Explorer is a graphical shell. COMMAND.COM/CMD.EXE is a command line shell.

    34. Re:And compromise compatibility with drivers, etc by epiphani · · Score: 1

      Good point. Maybe we should get MS to fund a jaunt to mars.

      --
      .
    35. Re:And compromise compatibility with drivers, etc by sqlrob · · Score: 1

      It's not a myth, but it's a misleading fact that is doubly misleading because there's an OS/2 subsystem in NT that people use as evidence that it's based on the same code as the OS that was marketed as OS/2.

      True, but not accurate anymore. The OS/2 subsytem went the way of the dodo as of Win2K

    36. Re:And compromise compatibility with drivers, etc by NeuroMorphus · · Score: 1

      hehe, nice sig:

      "my other head is a tail" :)

      --

      python >>>
      reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
    37. Re:And compromise compatibility with drivers, etc by zod1025 · · Score: 1

      Try reading the license sometime. They can of course distribute their own 'distribution' for profit - they just have to leave the source open and note their changes.

      Stop spreading falsehoods, please.

      --

      -ZOD-
    38. Re:And compromise compatibility with drivers, etc by Dunkelzahn · · Score: 1

      Ya ever hear of um... Darwin/x86?

      --
      .
    39. Re:And compromise compatibility with drivers, etc by Pope · · Score: 1

      Maybe they would do well in the refridgerator market, but would they ever pay a dividend there either?

      --
      It doesn't mean much now, it's built for the future.
  3. OS X by pr0nbot · · Score: 1, Offtopic

    You mean, like OS X?

    1. Re:OS X by Anonymous Coward · · Score: 1, Insightful

      Since when was OS X built on Linux?

      I know you Linux guys live in your own world, but come on...

    2. Re:OS X by Znonymous+Coward · · Score: 1, Insightful

      >>Since when was OS X built on Linux?

      Actually OS X is built on UNIX (BSD).

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    3. Re:OS X by Anonymous Coward · · Score: 0

      Yes. My point exactly. You still don't get it. . Unix is not Linux. FreeBSD is not Linux. OS X is not built on Linux.

      Welcome to reality!

    4. Re:OS X by dolson · · Score: 3, Funny

      You mean, like OS X?

      No, he means like Lindows.

    5. Re:OS X by Znonymous+Coward · · Score: 0, Redundant

      >> Unix is not Linux. FreeBSD is not Linux. OS X is not built on Linux.

      -1 Redundant

      What is your point?

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    6. Re:OS X by Anonymous Coward · · Score: 0

      His point is that, contrary to the root poster in this thread, OSX IS NOT LINUX.

      Next time, try reading, assface.

    7. Re:OS X by Anonymous Coward · · Score: 0

      Might as well be fuckwad :)

    8. Re:OS X by eggsovereasy · · Score: 3, Insightful

      Did you ever consider that he was makeing an analogy... "MacOS is to Darwin (BSD) as Windows is to Linux" just in case you can't figure it out.

    9. Re:OS X by Anonymous Coward · · Score: 0

      I wonder what the mean IQ of this place is ...

    10. Re:OS X by Anonymous Coward · · Score: 0

      Heh - it's (-1, Stupid). And (-2, Dumbfuck) for moderators.

    11. Re:OS X by Anonymous Coward · · Score: 0

      Actually OS X is built on UNIX (BSD)

      No.

      It's built with Apple's proprietary Mach kernel, with some BSD utilities glued on (stolen as per the BSD license). I can download some GNU utilities and copy them to C:\WINNT, now is my OS based on GNU?

      No.

    12. Re:OS X by cscx · · Score: 0, Troll

      I can download some GNU utilities and copy them to C:\WINNT, now is my OS based on GNU?

      According to RMS it is.

    13. Re:OS X by Twirlip+of+the+Mists · · Score: 2, Informative

      It's built with Apple's proprietary Mach kernel

      How do you define "proprietary?" Mach started at CMU as a totally open-source project; NeXT used CMU's Mach kernel as the basis for NeXTstep, which evolved into OS X. Apple's fork of Mach (which really isn't Mach any more, in some important ways) is still open-source.

      All too often, "proprietary" is a dirty word that's thrown around Slashdot to mean "not what I'm using."

      I can download some GNU utilities and copy them to C:\WINNT, now is my OS based on GNU?

      Well, considering that GNU is neither a kernel nor an operating system, but rather just a loosely associated collection of utilities, I'd say that no operating system is "based on" GNU.

      --

      I write in my journal
    14. Re:OS X by JohnFluxx · · Score: 1

      Why has it become a /. sport to bash rms at any chance?

      Find me where rms says this. In fact, RMS has said the opposite.(Which is why you don't hear GNU/freebsd or whatever)

    15. Re:OS X by pr0nbot · · Score: 1

      Did you ever consider that he was makeing an analogy... "MacOS is to Darwin (BSD) as Windows is to Linux" just in case you can't figure it out.

      That's exactly what I meant. Perhaps I was overestimating the intellect of the slashdot crowd.

    16. Re:OS X by Anonymous Coward · · Score: 1, Insightful

      How so "offtopic"?

      This is exactly the point the article conveys.

      I wanna lend my sympathy here to Cringely and, Robert, stupid people abound... Don't let your articles be limited in the future by jerks lacking imagination.

    17. Re:OS X by Ponty · · Score: 1

      Yep, because when you adhere to the license, you're stealing.

      Get over it.

    18. Re:OS X by cscx · · Score: 1

      A loose interpretation of this

    19. Re:OS X by Anonymous Coward · · Score: 0

      RMS calls systems GNU/___ if the system environment is based on GNU tools. Linux is based largely on GNU tools, thus GNU/Linux.

      Windows is not. Thanks for the troll, though.

    20. Re:OS X by cscx · · Score: 1

      Wow, you've really got this down pat -- first reply as Anon Coward, then mod -1 Troll. Thanks for playing. HAND.

  4. Yeah right by KilljoyAZ · · Score: 5, Funny

    That's about as likely as Jack Valenti saying, "We actually don't need copyrights to last this long," or Duke Nukem Forever being released.

    --
    This .sig is currently on hiatus for retooling.
    1. Re:Yeah right by Anonymous Coward · · Score: 0

      Yes they could become an open source endeavor if they really wanted to, but doesn't that contradict Microsoft's capitalist demeanor? The whole point of M$ is to make as much money as possible.

    2. Re:Yeah right by xingix · · Score: 2, Funny

      And capatlistic tendencies are bad? God forbid anyone try and make money.

      --

      Confucious says: Man who runs behind car gets exhausted.

      // jeku.com

    3. Re:Yeah right by Tsian · · Score: 3, Insightful

      And capatlistic tendencies are bad?

      No, but then again, its not like we have (or want) pure capitalism. Pure capitalism would be NO government aid. No major tax cuts, no negative net taxes paid back to corporations. No corporations being handed publically funded projects (aka the phone lines, the railways etc).

      Today's capitalist system thrives because of the socialist controls imposed on it...

      Afterall, who needs the FDIC anyway?

    4. Re:Yeah right by jonman_d · · Score: 0, Offtopic

      Today's capitalist system thrives because of the socialist controls imposed on it...

      Should I use the 'r' word?

      IMHO, it seems that, as we increase socialist reforms, we increase economic problems. Look at the Social Security fiasco, for example. May I recommend, Ayn Rand's Capitalism: The Unknown Ideal?

      No major tax cuts
      Rather, no major taxes in the first place.

    5. Re:Yeah right by Tsian · · Score: 1, Offtopic

      I realise this is getting slightly off the topic at hand, but....

      No, you may not reccomend Ayn Rand. I may as well reccomend Chomsky to you. They are both fairly extreme in their views and not likely to find either of us on middle ground.

      So, remove the FDIC, that's a socialist control. Remove any tax on corporations (I mean its not like any of the big one's pay taxes now anyway...). Institute a flat rate tax. The rich will continue to get richer and the poor will continue to fall. Hardly seems like an ideal world...

      Get rid of those Canadian's pesky social health care idea (even though in ever poll conducted, over 50% of questioned American's have expressed a want of government funded health care. Politicians still call such a proposition 'political suicide').

      Remember, with social security they never actually save any money. What use is the government putting money in a bank which could otherwise be in circulation. Actually saving notes for social security would harm the economy. Rather, the government writes itself handy little IOU's (I Owe Me 10 Billion...). In this way, present contributions are always paying past contributors out (and the system works wonderfully until you get too many people wanting money and not enough workers supplying it).

      Heck, the only reason we have avoided depressions greater then "the big one" is because of socialist controls and government bail outs.

      Pure capitalism would mean there wouldn't be any airlines in bussiness from America right now. Pure capitalism would be when Johnny gets sick and mom can't pay, johnny dies. Pure capitalism would not have government funded schools or utilities, and we all know how well deregulation has worked....

    6. Re:Yeah right by eyeball · · Score: 1

      No, but then again, its not like we have (or want) pure capitalism. Pure capitalism would be NO government aid. No major tax cuts, no negative net taxes paid back to corporations. No corporations being handed publically funded projects (aka the phone lines, the railways etc).

      Be careful not to blame all corporations for taking hand-outs. If polititian gives $x to company A, company B has to take it as well, otherwise they are at a disadvantage. Blame the polititian and company A.

      --

      _______
      2B1ASK1
    7. Re:Yeah right by Anonymous Coward · · Score: 0

      Institute a flat rate tax. The rich will continue to get richer and the poor will continue to fall. Hardly seems like an ideal world...

      The rich and their fat cat accountants use every loop-hole and exemption to pay as little tax as possible. Institute a flat tax and remove all loop holes and deductions and the rich will likely pay more taxes than they do now.

      Get rid of those Canadian's pesky social health care idea

      The current wait in the ER is bad enough, I would hate to be put on a waiting list for every proceedure I wanted to have done.

      is because of socialist controls and government bail outs

      Or rather, in spite of...

      Pure capitalism would mean there wouldn't be any airlines in bussiness from America right now.

      Yeah, without the major airlines, there are no alternatives.

      Pure capitalism would be when Johnny gets sick and mom can't pay, johnny dies.

      Because without the government, we all become heartless bastards who don't give a damn about our neighbors. Just like without religion and the fear of eternal damnation, we all would turn into homocidal maniacs.

      Pure capitalism would not have government funded schools or utilities, and we all know how well deregulation has worked....

      Half-asses deregulation will always be a failure.

    8. Re:Yeah right by Anonymous Coward · · Score: 0

      The current wait in the ER is bad enough

      As someone in the UK, with the NHS waiting lists, I agree

      I would hate to be put on a waiting list for every proceedure I wanted to have done.

      Neither capitalism nor socialism work much better than each other, here. The way I see it, I can walk into a doctors at any point and get treatment, even if I don't have a penny in my pocket. If I had no money but had to pay, I would have to wait an indefinatly long time to get treatment.

      The waiting lists for procedures may be long, but my wifes sister in law is currently waiting for tests to be carried it. The problem is that their insurance only pays out after the procedure, and they sure as hell don't have $5000 lying around (Just for the tests, remember). She is currently waiting to have these tests done while they battle with the insurance companies and employers to get the insurance changed so that it will pay out before the procedure is done.

      In other words, my wifes sister in law would currently be better off under a socialist health care system than she is under a capitalist health care system. Swings and roundabouts.

    9. Re:Yeah right by apweiler · · Score: 2

      Because without the government, we all become heartless bastards who don't give a damn about our neighbors. Just like without religion and the fear of eternal damnation, we all would turn into homocidal maniacs.

      Actually, yes, for the first part. 'Neighbours'? The general tendency as far as I can tell is that poor people and rich people tend to live in different neighbourhoods. And so you think my $10k-a-year neighbours would pay for my kid's $50k cancer therapy? And even if they did, I'd rather have a government-administered welfare system that I can *depend* on if I'm in trouble rather than having to hope for my neighbours' charity.

      Anyway, an interesting thought crept into my brain here:
      Half-asses deregulation will always be a failure

      Some people I know and have been around a fair bit recently are active in the anti-neoliberalism movement or whatever you want to call it, FWIW the far-left area of the spectrum. Some of those actually lean toward anarchism, obviously not in the sense of chaos and destruction, but in the sense of building a society where everyone will get along without any government. (While this sounds nice, my optimism about it being possible is rather limited.) The interesting bit is: Isn't that exactly the same thing that a) communism was originally about, and b) that radical capitalists like you are proposing - if the government keeps out of things (deregulation etc.) (and eventually, hopefully, disappears) people will just get along and everyone will be happy. I'm not saying your idea is bad, though I doubt it can work; what I want to point out is that this is really where right and left meet (well, certain types of right & left - not the anti-abortion anti-drug hard-line religious right, and not the Stalinist/IngSoc 'left', obviously). Something to think about, innit?

    10. Re:Yeah right by shumway · · Score: 1
      Get rid of those Canadian's pesky social health care idea (even though in ever poll conducted, over 50% of questioned American's have expressed a want of government funded health care. Politicians still call such a proposition 'political suicide').

      Well, in our current system, listening to voters instead of the {health care, energy, agriculture, etc.} industry is political suicide.

      Off-topic and proud of it,

      --
    11. Re:Yeah right by cas2000 · · Score: 0

      >> Pure capitalism would be when Johnny gets sick and mom can't pay, johnny dies.

      > Because without the government, we all become heartless bastards who don't give a damn about our neighbors.


      what's all this "become" nonsense?

      americans are already heartless bastards who don't give a damn about their neighbours. *especially* the Libertarians who spend all their time whining about the fact that someone, somewhere in far worse and shittier circumstances than themselves may have got something that they didn't.

      that's why you all whine about social welfare programs and government medical insurance - while turning a blind eye to the hundreds of billions wasted on corporate welfare programs....or the $25 billion bribe currently being offered to Turkey in exchange for letting US troops attack Iraq from Turkish soil.

      you heartless bastards actually believe that poverty isn't a circumstance or a trap, but that it is a moral failing - anyone who is poor *deserves* to be poor. it's their own fault that they chose poor parents and grew up in a shit neighbourhood with crap schools and no job prospects. truly exceptional people can make it out of poverty traps like that due to luck or intelligence or skill or ruthless selfishness, but most people are stuck in it for the rest of their lives - and their children and grandchildren too.

  5. No. by tshak · · Score: 4, Interesting

    No, but it should be built on a BSDish *nix ala OS X. Heck, MS could even use Darwin - wouldn't that be an interesting turn of events!

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    1. Re:No. by CptNoSkill · · Score: 5, Funny

      Yea Microsoft would never base their products on something that apple made.. oh.. wait a minute....

    2. Re:No. by cuyler · · Score: 1

      No, but it should be built on a BSDish *nix ala OS X. Heck, MS could even use Darwin - wouldn't that be an interesting turn of events

      That would be funny. Both Apple and Windows based on BSD. Do you supposed if that day ever arrived the "BSD is dying" posts would stop?

      Can't imagine BSD dying if it had 95% of the market.

    3. Re:No. by Twirlip+of+the+Mists · · Score: 1

      alot of the little config wizards and such look so similar it isnt even funny

      I use OS X all day, every day, and apart from the little tool that runs when you first turn on your computer, I can't think of anything in OS X that would qualify as a "little config wizard."

      Is it possible-- not necessarily so, but just possible-- that you don't know what the fuck you're talking about?

      --

      I write in my journal
    4. Re:No. by IamTheRealMike · · Score: 1
      Heck, MS could even use Darwin - wouldn't that be an interesting turn of events!

      Considering that NT was once in fact also based on a microkernel architecture, which was later dropped due to serious performance issues, yeah, it'd be fascinating.

    5. Re:No. by spongman · · Score: 1
      It's still a microkernel. you're probably referring to the fact that parts of the user-mode stuff (GDI, IIS) have been made to run in the executive. They're not really part of the kernel, they just run at the same privilege.

      Here's a good article that covers the details of the changes.

    6. Re:No. by SN74S181 · · Score: 1

      Yes. "Oh, wait a minute..."

      Apple didn't make the core OS of their current offering. They failed, dismally, several times to come up with the 'next generation MacOS' that they huffed and puffed and made up cute names for in the 80's and early 90's. Finally they threw in the towel and threw a layer on top of NextStep, which they conveniently got for "free" by bringing Steve Jobs back in.

      I am not sure if that was the 'oh wait' that you wanted, but no, Apple didn't invent BSD.

    7. Re:No. by Vaughn+Anderson · · Score: 1

      Yea Microsoft would never base their products on something that apple made.. oh.. wait a minute....

      Yea and Microsoft also would never base their products on something similar to unix but stinks.. oh.. wait a minute....

    8. Re:No. by Anonymous Coward · · Score: 0

      Actually, NeXT took over Apple and wrapped NeXTstep up in a Macesque Gui.

  6. They'll use FreeBSD or NetBSD if anything by m0nkyman · · Score: 4, Interesting

    GPL licensing is anathema to them, but they seem to enjoy using BSD licensing....

    --
    ~ a low user id is no indication I have a clue what I'm talking about.
    1. Re:They'll use FreeBSD or NetBSD if anything by BandwidthHog · · Score: 4, Insightful

      GPL licensing is anathema to them, but they seem to enjoy using BSD licensing....

      But only in the one direction, no? Do they ever license their own work as BSD?

      --

      Quantum materiae materietur marmota monax si marmota monax materiam possit materiari?
    2. Re:They'll use FreeBSD or NetBSD if anything by robbyjo · · Score: 3, Insightful

      IMHO, considering what Microsoft has done in the past, the right word here is not "use", but "cannibalize".

      --

      --
      Error 500: Internal sig error
    3. Re:They'll use FreeBSD or NetBSD if anything by sl3xd · · Score: 5, Insightful

      Of course they don't. That's why they like the BSD licence (and hate GPL): With the BSD licence, they can take all they want, have some obscure reference to the original authors in the documentation, and re-sell the work as if it were their own. The BSD licence doesn't ask anything more than to give credit where credit is due-- it's worth noting, however, that Microsoft has even violated that licence in the past. (They ripped off some fairly large chunks of BSD code, and never gave credit to the original authors).

      However, the GPL licence: It requires that Microsoft give back; the thing to remember is that Microsoft is like a roach motel for source code -- it checks in, but it doesn't check out. The GPL would require Microsoft to make available any code they change under the GPL; it takes away their absolute control over the code, and takes away their ability to (over)charge for said code. Plus, a good roach motel doesn't let anything escape.

      --
      -- Sometimes you have to turn the lights off in order to see.
    4. Re:They'll use FreeBSD or NetBSD if anything by ender81b · · Score: 1

      They did up to a point... the tcp/ip stack in Win2k/XP is no longer based on the BSD tcp/ip stack. Of course there might be other things they use but the tcp/ip stack is no longer one of them.

    5. Re:They'll use FreeBSD or NetBSD if anything by Ctrl-Z · · Score: 2, Funny

      However, the GPL licence: It requires that Microsoft give back; the thing to remember is that Microsoft is like a roach motel for source code -- it checks in, but it doesn't check out.


      Sorry, I hate to be picky, but don't you mean that Microsoft checks code out but it doesn't check in?
      --
      www.timcoleman.com is a total waste of your time. Never go there.
    6. Re:They'll use FreeBSD or NetBSD if anything by cscx · · Score: 1

      The only things from BSD are the simple TCP/IP tools like ftp, telnet, finger, nslookup, chargen, MOTD, etc... TelnetD might be, but if it was, Microsoft modified it to encrypt the authentication, and to authenticate against NT domain passwords.

    7. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 0

      Everything is relative ... I get your meaning, but in this case the original analogy is fine ... Microsoft is the rotel and the code checks in to the rotel and never checks out.

    8. Re:They'll use FreeBSD or NetBSD if anything by Elwood+P+Dowd · · Score: 2, Interesting

      Um. The BSD license *used* to require credit. Depending on what BSD license the original project used, a copyright notice may or may not have been required. I'm sure you wouldn't just say that because you couldn't find the copyright notice, so it's still entirely possible that MS did something wrong. I'll just need more to convince me. They've got a lot of well paid people that try to limit their liability, so...

      --

      There are no trails. There are no trees out here.
    9. Re:They'll use FreeBSD or NetBSD if anything by jericho4.0 · · Score: 1

      This is a k5 link with some interesting info on the subject.
      And the software was licensed perfectly legally, since the inclusion of the copyright notice satisfied the BSD license.
      That statement is really funny when you realize he's talking about dissasembling the exec to see the notice.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
    10. Re:They'll use FreeBSD or NetBSD if anything by toxcspdrmn · · Score: 3, Funny

      That's because the misread it as the BSoD licence and thought it fitted their products perfectly.

      --
      "E pur si muove!" - attributed to Galileo Galilei, 1564-1642
    11. Re:They'll use FreeBSD or NetBSD if anything by Jeremy+Erwin · · Score: 1

      They could use linux, but use Palladium, or other nefarious means to "sign" code so that MS Office (and possibly, their version of Linux itself) would only run on a properly validated system. I'm not sure if it would be worth the accompaning legal hassle of fighting off Richard Stallman and FSF.

      MIcrosoft could use BSD (taking some advantage out of whatever reputation is associated with *BSD code-- be it security, "professionalism", or code quality, but unless Microsoft releases code (a la Apple), the PR effect will be muted. And Apple might be able to eat in to MS's sales by pushing their own version of BSD.

    12. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 3, Informative

      No, all versions of the BSD license require that credit is given to the copyright holder. You might be thinking of the advertising clause in older versions of the BSD license that required that the phrase "this product includes software written by [name of copyright holder]". That clause was removed from the BSD code by Berkeley some time ago.

      If you want to see some examples of the BSD license "in action" so to speak, see Microsoft's release notes for Windows XP. There credit is given to a lot of people who have released BSD licensed software; not only to Berkeley, but also to people like Luigi Rizzo who have done a lot of work on the FreeBSD kernel.

    13. Re:They'll use FreeBSD or NetBSD if anything by Dahan · · Score: 1
      sl3xd claimed that MS "ripped off some fairly large chunks of BSD code." I would hardly consider an ftp client and a few other utilities "fairly large chunks of BSD code"... and MS didn't violate the BSD license by distributing those utilities either. So where's this alleged license violation sl3xd's talking about?

      Answer: there is none.

    14. Re:They'll use FreeBSD or NetBSD if anything by jez9999 · · Score: 2, Informative

      Lol.

      (at the bottom of relnotes):
      "Portions of this software are based in part on the work of Luigi Rizzo. Because Microsoft has included the Luigi Rizzo software in this product, Microsoft is required to include the following text that accompanied such software:"

      After all that, is it really worth having your credit given at all? How about requiring that the user have a good chance to see it, instead? So they have to put it in bold on the desktop or something. :-)

    15. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 0

      YUO = TEH FUNNEY!!!111

    16. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 1, Insightful
      is that Microsoft is like a roach motel for source code -- it checks in, but it doesn't check out.


      A further suggestion related to "shared source". Shared source is like the Hotel California, "You can check out any time you like but you can never leave." Great, now I've got the guitar solor running through my head all day. (But hey it's better than some ad jingle or the latest boy toy band ballad implanted in a mall or elevator. )
    17. Re:They'll use FreeBSD or NetBSD if anything by 1010011010 · · Score: 1


      I'd like to see a list of what parts of each Windows these people/institutions wrote:

      Mark H. Colburn
      University of California
      Greg Roelofs
      Hewlett-Packard Company
      University of Southern California
      Luigi Rizzo
      Phil Karn
      Robert MorelosZaragoza
      Hari Thirumoorthy
      Massachusetts Institute of Technology
      The University of Michigan

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    18. Re:They'll use FreeBSD or NetBSD if anything by Elwood+P+Dowd · · Score: 1

      Right. But the copyright notice may also be in printed documentation, or buried in online help, or in some about box that we aren't looking for. There are a million places they might have put the notice.

      *And* if they're using BSD tools that were covered under the latest licenses, then they don't have to include the copyright notice anyway. I want to see a really well laid out accusation before I bother worrying about the quality of the counter-argument.

      I'd consider microsoft innocent until proven guilty. Certainly when it comes to accusations made on /.

      --

      There are no trails. There are no trees out here.
    19. Re:They'll use FreeBSD or NetBSD if anything by istartedi · · Score: 1

      The GPL would require Microsoft to make available any code they change under the GPL; it takes away their absolute control over the code, and takes away their ability to (over)charge for said code

      Nope. This is a very common falacy put forth by GPL advocates. BSD does not grant you the right to overcharge for code, and GPL doesn't revoke it. Microsoft cannot "overcharge" for BSD. They can only charge what the market will bear for the value they add.

      If Microsoft took a BSD distro and made minimal improvements, I could legally "clean room" their minimal improvements and charge the same ammount, more, or (more likely) less. I could even advertise that my improvements "do the same thing that MS BSD does at half the price".

      Now, on the other hand if MSFT decided to link to GNU/Linux in a manner that required their code to be GPL'd, there is nothing to stop them from pricing MSLinux servers at $5000/copy. This is of course a rather straightforward technique used by some GPL vendors to discourage GPL software from becoming free in the "beer" sense. MSFT would have to get trickier because at $5000/copy too many customers would balk and some hackers would organize donations to "liberate" a copy. Instead, MSFT is more likely to do something like set the price at $1,000,000/copy and offer discounts to vendors who already have a certain number of MSFT licenses. So then our hypothetical group of hackers has to form a corporation and buy hundreds of thousands of MSFT licenses to get the "discount". Then you get into the whole issue of whether or not employees who have access to the code have GPL rights (as opposed to the corporation), then you can imagine herds of MSFT lawyers battling the FSF and the EFF for years until Operating Systems as a class of software are totally commoditized under BSD-like licenses anyway, rendering the whole thing moot (much like the antitrust case).

      That last paragraph is moot anyway (yes, a moot on top of a moot) because MSFT will never staticly link to GPL'd code anyway. If they wanted to co-opt *NIX, they would do like Apple--start from the top down, writing a GUI and apps, and gradually replacing all the components except probably the kernel and a few GNU utilities (grep, etc.).

      Hmmm... actually, this whole article is moot because as others have surely pointed out, MSFT getting involved with Linux is about as likely as Osama Bin Laden marching in a Veteran's Day parade with our local VFW.

      (Submitting without preview because /. is a little shaky today)

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    20. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 0

      What kind of drugs are you on? Who ever said
      that you can't "overcharge" for code that is
      BSD licensed? Last I checked, there was no clause that determined how someone selling the code could do so. Then you say, "Microsoft cannot `overcharge' for BSD. They can only charge what the market will bear for the value they add."
      What the fuck are you talking about ???? They can repackage FreeBSD and charge whatever the fuck they like, if that's what they want to do!

    21. Re:They'll use FreeBSD or NetBSD if anything by istartedi · · Score: 1

      What kind of drugs are you on?

      I'll assume that's a rhetorical question.

      Who ever said that you can't "overcharge" for code that is BSD licensed? Last I checked, there was no clause that determined how someone selling the code could do so.

      I wasn't referring to a clause in the license. I was referring to the practical matter of not being able to charge for something that is synonymous with "free".

      Then you say, "Microsoft cannot `overcharge' for BSD. They can only charge what the market will bear for the value they add."

      As a practical matter, the market would look at MS BSD, compare it to FreeBSD, and the market would only be willing to pay for the stuff that MS added to BSD. In other words, I am saying that MS's brand name has no value in the market for enhanced BSD distributions.

      What the fuck are you talking about ???? They can repackage FreeBSD and charge whatever the fuck they like, if that's what they want to do!

      Yes. They can also re-release BOB, but the chances of either product succeeding are about equal.

      If you had wanted, you could have counterpointed my argument quite nicely by saying that MS's marketing muscle was sufficient to sell branded BSD distros with no value added. You might have employed the bottled water analogy too (although I don't believe it applies because bottled water is a question of convenience and taste). Instead you went for the adhominem attack. Pity. Where can I find some people who really know how to debate?

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    22. Re:They'll use FreeBSD or NetBSD if anything by Anonymous Coward · · Score: 0

      Congrats on the troll istartedi.

      Some people just don't appreciate the approach of the clueless moron from left feild act.

  7. sure by Anonymous Coward · · Score: 0
    If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they?

    When you have 95% of the world on your platform, what's the point?

    1. Re:sure by MORTAR_COMBAT! · · Score: 3, Insightful

      The world == several billion people.

      95% of the world would be several billion people.

      There are not several billion people running Windows. There are not even a billion people running Windows.

      There are not even a billion people with computers.

      --
      MORTAR COMBAT!
    2. Re:sure by Anonymous Coward · · Score: 1, Funny

      Not literally the world, dumbass.

  8. wait..... by skinnedmink · · Score: 5, Funny

    If anyone could ruin the stability of Linux.....it would be Microsoft.

    --
    peace be with you.
    1. Re:wait..... by skinnedmink · · Score: 1

      yep, reduce the ammount of software you get with the average distro....add $100 dollars....and up the crash rate to at least once a day and you have Windows built on Linux

      --
      peace be with you.
    2. Re:wait..... by Anonymous Coward · · Score: 0

      Sorry, Windows 2000, XP, and 2003 server all completely destroy linux when it comes to stability. Uh oh, my Kernel panicked.

    3. Re:wait..... by Anonymous Coward · · Score: 0

      Or better yet, keep the amount of useless, half-baked shit software the same, perhaps add a few more crashes per day, give it away for free, and you've got.... your average linux distribution

      --igloo

    4. Re:wait..... by Znonymous+Coward · · Score: 1, Offtopic

      $ uptime
      9:18pm up 125 days, 22:04, 1 user, load average: 0.00, 0.00, 0.00

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    5. Re:wait..... by zcat_NZ · · Score: 2, Funny

      Linux stability doesn't need ruining. the plethora of shit that comes with your average distribution does more than a good enough job.

      so don't run redhat then.. sheesh!

      --
      455fe10422ca29c4933f95052b792ab2
    6. Re:wait..... by Anonymous Coward · · Score: 0

      $ startx

      *reset*

    7. Re:wait..... by Anonymous Coward · · Score: 0
      yeah, that says it all, really, doesn't it? 1 single user on a box running under no load.

      I should imagine even the dimmest brain-dead linux zealot could get an NT-based box to do that.

      --igloo

    8. Re:wait..... by Znonymous+Coward · · Score: 0, Offtopic

      Here is my system at work. Maybe everyting has a low load load because we have bad ass hardware.

      $uptime
      09:26PM up 165 days, 12:16, 13 users, load average: 0.26, 0.19, 0.19

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    9. Re:wait..... by Anonymous Coward · · Score: 0

      or maybe it's because you work at the high-school as the leader of the linux-fan club.

      how's that going, by the way? got any real members yet?

      --igloo

    10. Re:wait..... by Anonymous Coward · · Score: 0

      Hey look, I can make up uptime statistics on the spot too!

      $uptime
      10:37PM up 9999 days, 11:48, 100000000 users, load average: 0.51, 0.21, 0.21

    11. Re:wait..... by skinnedmink · · Score: 1

      I believe that anonymous coward has either been dropped on his head one too many times or has some unresolved anger. Anonymous Coward I can fix all of your trouble get to a C prompt and type: DEL TREE /Y C:/

      --
      peace be with you.
    12. Re:wait..... by Anonymous Coward · · Score: 0

      Why do you read /. if you hate linux so mutch?

    13. Re:wait..... by Anonymous Coward · · Score: 0

      that would try and remove the directory 'tree' under your pwd. if it didn't error out.

    14. Re:wait..... by Stardate · · Score: 1

      You can't. I have had to apply so many security patches in the last 125 days that I have had to reboot it at least once every 4 weeks.

      --
      "... I declare our city to be a free and independent state to be named Tri-Insula!" --Fernando Wood, Mayor of NYC 1861
    15. Re:wait..... by igggy · · Score: 1

      you might have a couple of problems with that, ace.

      1) the 'deltree' command was all one word.

      2) windows stopped shipping with the deltree command after '98 or thereabouts.

      3) you'll want to make that a backslash after 'c:'

      4) I don't use windows.

      thankyou, please come again.

      --igloo

    16. Re:wait..... by igggy · · Score: 1, Troll

      well, for one thing, about 80% of slashdot's traffic is sent out to internet explorer, so even if i'm not alone in 'hating' linux, I might as well be when I come reading slashdot with it. For another thing, I don't hate linux. I love linux! What I hate are the horrible little linux zealots. People who take a core kernel developed by a team of professionals, a few 'killer apps' (like apache, mysql and samba, developed largely with 3rd party commercial backing) a load of shit products (like xfree86 and everything that sits on top of it) and then proceed to parch themselves on a mountain high and preach their own superiority to the masses below (who are getting along wonderfully with their industry-standard, fully supported systems) all the while boasting how much better they have it, before going back to re-compile ide-scsi emulators into their kernels and re-configuring their bootloaders to ignore /dev/hdc, just to use a simple fucking atapi-cd writer. I like to compare linux zealots with goths. they're both groups of people who have made a concious decision to 'non-conform' - even when their choices offer them no real advantage in life, and indeed often only prooves to make things harder for themselves. But what they don't realise is, when they think they're raging against the machine and fucking the man, they're doing nothing more than conforming wholey to just a different group. I'd actually like to see linux hit the main stream, just for the simple pleasure of watching all these fuckwits realise that they're no longer plucky underdogs or pioneers. then they'll all jump ship to the next small thing and start slating everyone else for using linux.

    17. Re:wait..... by skinnedmink · · Score: 1

      http://www.computerhope.com/deltree.htm

      --
      peace be with you.
    18. Re:wait..... by igggy · · Score: 1

      C:\>deltree c:/windows /y
      'deltree' is not recognized as an internal or external command,
      operable program or batch file.

      C:\>_

      and also with you, faggot.

    19. Re:wait..... by JW+Troll · · Score: 1, Troll

      yeah, or maybe you could just run KDE or GNOME or Konqueror or Mozilla or any of the other thousands of apps that crash regularly.. Those sure do a good job of making Linux look like shit to any desktop user who's used to Windows 2000/XP. Especially the Kicker or whatever panel app might be running. I think it's a joke that my frigging panel app can crash (and frequently has, BTW) whereas under Win2K I haven't seen ANYthing crash in over 8 months of daily usage. Curious dichotomy, that..

      --
      just like the humble blood clot... turboporsche@telus.net
    20. Re:wait..... by Anonymous Coward · · Score: 0

      yah, but you've only been running galeon (so you can read /.) and a nethack console that whole time.

    21. Re:wait..... by MattCohn.com · · Score: 1

      *cough* DELTREE C:\*.* /Y *cough*

      Oh, and don't use so many caps. It's like YELLING. Remember that children.

    22. Re:wait..... by cscx · · Score: 1

      I have a .NET server beta RC1 version that runs Windows Media Server that I built last month... haven't had to restart it yet.

    23. Re:wait..... by Anonymous Coward · · Score: 0
      I'd actually like to see linux hit the main stream, just for the simple pleasure of watching all these fuckwits realise that they're no longer plucky underdogs or pioneers.

      The word pioneers should be enveloped by quotation marks. Those who make real contribution to the OSS movement are not bad people by nature, the idiot 14 to 35y/o "1337" consumer demographic is. They just feel special by capitalizing on other's work and never contribute anything worthwhile, other than "RTFM" and "STFU n00b".
    24. Re:wait..... by jjeff · · Score: 2, Insightful
      I crash linux 20-30 times an hour doing simple stuff - why do people continue to feel linux is stable?


      You are so full of shit - you would have to be using a machine which takes less than 1 minute to boot.
      What the hell are you doing to cause this?
      I use my desktop/personal web/mail server for any number of things such as browsing the web with a number of different browsers, playing games both with wine and native linux ones (using supposedly "unstable" nvidia drivers - they have always worked great for me) and I havent had a crash for months. In fact the only time its been rebooted was when my fiancee's brother came to stay and couldnt sleep with the computer fan going.

      I dont know why you people spout such crap.

      --
      when everything is working perfectly.. BREAK SOMETHING before something else FUCKS up!
    25. Re:wait..... by JW+Troll · · Score: 2, Interesting

      he's referring to the crappy applications that run on top of Linux, obviously. I've experienced the same thing and it pisses me off. Every three months I try the latest Red Hat, Mandrake, and Lycoris.
      Yes, I'm a geek with waaaay too much time on my hands, but I shouldn't be beta testing applications that are marked stable for crying out loud. KDE should be labelled "alpha 0.3.1" by commercial standards.

      --
      just like the humble blood clot... turboporsche@telus.net
    26. Re:wait..... by dknj · · Score: 1

      I went into our server room the other day to update a users account on our .net server and decided to check the uptime (well how long the network connection has been enabled which is close enough :) and it was at 95 days. I wasn't surprised that .NET had held its own for so long, I was surprised we hadn't had a power outage that took out our servers in so long =)

      -dk

    27. Re:wait..... by Anonymous Coward · · Score: 0

      echo y | format c:

    28. Re:wait..... by Anonymous Coward · · Score: 0

      trolltrolltrolltroll

      1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19. .. .post

    29. Re:wait..... by Hard_Code · · Score: 1

      "then they'll all jump ship to the next small thing" ...*BSD, watch out...

      --

      It's 10 PM. Do you know if you're un-American?
    30. Re:wait..... by Hard_Code · · Score: 1

      User: Linux crashed!
      Zealot: No it didn't, that crappy X app crashed you l00ser, the kernel is just fine!
      User: Huhr? WTF do I care? I'm switching back to Windows.

      --

      It's 10 PM. Do you know if you're un-American?
    31. Re:wait..... by Zorikin · · Score: 1

      This rant got modded up? But it's so -1, Redundant.

      > a load of shit products (like xfree86 and everything that sits on top of it)

      Sounds like a subjective claim. -1, Flamebait.

      > before going back to re-compile ide-scsi emulators into their kernels and re-configuring their bootloaders to ignore /dev/hdc, just to use a simple fucking atapi-cd writer

      Modern distributions handle this automagically. -1, Troll.

      > I like to compare linux zealots with goths.

      -1, Mean :(

      > their choices offer them no real advantage in life, and indeed often only prooves to make things harder for themselves.

      Adversity breeds strength. Anyway, there are advantages (such as automation/scripting and configurability), they're just not the advantages you want, apparently. -1, Overrated.

      All this and yet you love linux? Next time, stick to your story, friend.

    32. Re:wait..... by igggy · · Score: 1

      Aparently you either didn't read what I posted, or you just couldn't get the concept around your puny mind. At the risk of repeating myself, I'll re-iterate, trying to keep to nice, simple words this time. I like Linux. I don't like you, or people like you.

      > Sounds like a subjective claim. -1, Flamebait.

      Rating my arguments like how slashdot moderates posts. How refreshingly original and funny. You are a comedy golden God. Have you by chance seen the comedy genius that is the "in soviet russia" meme yet? I think you'd like it, it's mind-numbling banal too.

      Anway. That all depends on what you want out of your windowing system, really, doesn't it? OK, I'll make an ass out of myself with an assumption here, (see what I did there? that was funny) if you want something that is unstable, under-developed and shows no real direction as a GUI, go ahead and install xfree86. If you want something that will stumble and crash when faced with the most trival of tasks, install xfree86. If you want something that only barely supports the most basic features of most old and new hardware, install xfree86. However, anyone who actually uses their hardware for more than just playing with should look elsewhere.

      These aren't subjective claims. If you'd take off your tickly rose-tinted glasses and take a look at xfree86, you might just catch a glimpse of the shambles that everyone in the real world knows it to be. At the risk of having you go off on a tangent and start arguing points that I haven't even made claim to (again), I'll be the first to say that the concepts behind the X windowing system blow the socks off anything that redmond have to offer. And if someone could go ahead and develop some usable software, you and your ilk would finally have something worth shouting about.

      Here's a hint: start by catching up on functional multi-monitor support. Xfree is coming up to a whole 5 years behind MS on that one. And after your knee-jerk reaction to shout 'Xinerama!' has subsided, let me advise you to save your keystrokes. I'll repeat myself just in case you didn't catch it the first time: I said 'functional' not 'laughable.'

      Modern distributions handle this automagically. -1, Troll.

      Strange! Every version of Debian i've deployed since 2.0 doesn't. And that's going back a lot futher than what I'd call "modern." But I don't suppose that really matters, does it? I'm sure you're more than capable of finding a distribution that probably does, which would be furhter testament to my ignorance and foolishness for not knowing to avoid the major distribution Debian if I wanted to use my domestic consumer common-or-garden CD-writer. Silly Me!

      > Adversity breeds strength. Anyway, there are advantages (such as automation/scripting and configurability), they're just not the advantages you want, apparently. -1, Overrated.

      If you're anything to go by, adveristy breeds nothing more than tiny-minded peons who will tout their own wares as superior, even without the slightest understanding, or indeed an acknowledgement of the existance, of the features the competetion has been offering for years now.

      > All this and yet you love linux? Next time, stick to your story, friend.

      Next time, read my post and the thread its in before trying to pidgeon-holing me, fucktard. If you'd even caught the most basic jist of my post you could have saved yourself the time and embarrasment of making yourself look so foolish with such weaksauce retorts. Of course, more fool me for replying to them, but even I need some light entertainment occasionally. :) I'm not adverse to using whatever I have to to get the job done. I don't view companies and products as characters like in some bad TV drama series. (oh no! what will EVIL M$ do to thwart plucky young Linux now?!?!?!!) They're just fucking tools produced by businesses, nothing else. If you feel the need to assign personalites to them then I suggest you seek medical help, or at least some real-life friends. I use linux for what its good at, and i use windows for what its good at as well. What I don't like are the people who tell me that linux is the sollution to all my problems, and that I don't need to use windows even though it is vastly superior at what it does.

    33. Re:wait..... by Anonymous Coward · · Score: 0

      The only logical evidence of this is his name. All of JW's facts are too true, and I find it sad that you feel compelled to rant "troll" and have no way to disprove his points in an intelligent public manner on this forum.

    34. Re:wait..... by Zorikin · · Score: 1

      I think you are the one who looks foolish, whining, cursing, and calling me names over simple problems that are already solved.

      But I will be useful and advise you, thusly: hamm is obsolete. Try woody. Or therapy.

    35. Re:wait..... by igggy · · Score: 1

      I'm surpised you've managed to draw any conclusions at all, seeing as how once again you've failed to read my fucking post. I said I've trying everything SINCE 2.0. including woody. I will be useful and advise you: try learning to read and comprehend English. Fucknaught.

    36. Re:wait..... by Zorikin · · Score: 1

      Are you like this in real life? If you are, I feel sorry for your parents. And for anyone who asks you for tech support, since your claims suggest that you have a talent for breaking things.

  9. If you ask me... by Coke+in+a+Can · · Score: 0, Troll

    this is about as plausible as Fred Phelps marching for gay rights.

  10. wow.. i'm shocked by Anonymous Coward · · Score: 0

    possibly the first smarting Robert XXX Cringley has EVER said!

    now watch.. in 3 months he'll go against his word and bash Apple as well for no apparent reason..

    1. Re:wow.. i'm shocked by Anonymous Coward · · Score: 0

      possibly the first smarting Robert XXX Cringley has EVER said!

      You are kidding right? That article was so full of factual errors it's not even funny.

  11. hmmm by geekindustries · · Score: 1

    that would be interesting to see. Maybe a linux based windows wouln't be so bad? I don't see why not. What do you guys think? Why or why not?

    --
    Hard work usually pays off over time, but procrastination pays off now.
    1. Re:hmmm by Anonymous Coward · · Score: 0

      If microsoft could work their usual magic and actually produce a stable, usable GUI to sit on top, I'd be all for it. (XFree86. AHAHAHAH.)

      But the flip side of the coin would be all the DRM shit that would have to come with it.

    2. Re:hmmm by Anonymous Coward · · Score: 0

      MSFT did this in '96 when they released NT, time to pull your head out of your rear. Thanks

      The only Gui I see crashing on a consistent basis are the ones I see on Linux desktops. What a pitty to have to reboot your Linux machine simply because of a GUI mis-hap.

    3. Re:hmmm by Anonymous Coward · · Score: 0

      read -> comprehend -> post, brother. I'm a massive worshipper at the church of microsoft. my laughter at xfree86 was simply an illustration in the same vein as the point you made.

      I know all too well how crap xfree86 is.

      --igloo

    4. Re:hmmm by Luke-Jr · · Score: 1

      Except that M$ didn't make NT. They bought it from someone else. Since then, the NT/2k/XP have lost stability if anything...

      --
      Luke-Jr
    5. Re:hmmm by pVoid · · Score: 0
      Let me put it this way... there are three things microsoft has done very well, regardless of whatever anyone here would admit:

      MS SQL 2000

      MS VC

      Windows NT kernel

      The NT kernel is good, it's stable. Security compromises on the Windows platform mostly come from user mode applications not behaving while they're under power (under the system or admin accounts).

      There is no point whatsoever to make such a retarded move. If anything, I'd like to see an OS Xish shell on top of the NT kernel.

    6. Re:hmmm by Anonymous Coward · · Score: 0

      You are talking out of your ass..

      MS SQL 2000 - Bugs, open bugs and outright failures still haven't been fixed.

      MS VC - I'm not gonna even comment this is obviously to make people laugh

      Windows NT kernel - Stable? Ummmm maybe for hosting your web log or something. When you need die hard stability it's Unix or a RTOS or a stripped unix kernel. Anyone with common sense will tell you the same.

      Stop talking out of your ass

    7. Re:hmmm by igggy · · Score: 1

      wow. ANOTHER thoughtful and intriguing addition to the discussion. and yet it gets modded up to +2!

      I WONDER WHY!!

    8. Re:hmmm by Anonymous Coward · · Score: 0

      because the whole world is plotting against you.

  12. Well.... by captainclever · · Score: 2, Interesting

    Well if i was calling the shots i'd set MS developers to write an alternative to X, perhaps in opengl or directx, that had all the same interfaces as QT and GTK and Motif so existing apps could be recompiled. A really fast graphical subsystem (instead of X) running on a Linux base, would make for an excellent and powerful platform, suitable for games aswell as general work.

    --
    Last.fm - join the social music revolution
    1. Re:Well.... by GrenDel+Fuego · · Score: 1

      Well, QT and GTK are already available for win32, and often will allow you to just recompile programs.

      I doubt that Microsoft would try to get the compatability on their own. That would eat into the sales of their programming suites.

    2. Re:Well.... by Anonymous Coward · · Score: 0

      I'm all for an opengl accelerated windowing system that doesn't have a network layer on it.

      Then you're wrong. Even Microsoft has added network transparency, more or less, to their windowing system.

    3. Re:Well.... by Anonymous Coward · · Score: 0

      You're fucking stupid.

    4. Re:Well.... by Anonymous Coward · · Score: 0

      X is pretty fast, considering what it does.

      And, I don't think that opengl or directx are able to have a graphics client and server on different boxes. Those technologies may be faster only because they assume the program and display on the same computer. Hmmm?!?

    5. Re:Well.... by Anonymous Coward · · Score: 0

      Considering they are way faster than X11 (both local and remote) and their network protocol uses an order of magintude less bandwidth, that was a wise decision.

    6. Re:Well.... by Anonymous Coward · · Score: 0

      I'm sitting on an old sparc 20 w/debian right now with an xdm X session to a machine in the basement, on the same machine an
      additional local X session on display :1 to
      upload some stuff to my daughter's palmpilot.
      All I had to do was 'X -bpp :1'
      and voila. Doing that in any windows environment is either impossible or would require some slapped on crap like pcanywhere or citrix or remotelypossible. Old and tubby right, try big complicated and prepared to kick your ass.

    7. Re:Well.... by Osty · · Score: 1

      Ahem. Bullshit. They have added it sperately. There is no network layer that is built into the windowing server.

      I'm going to have to call bullshit on your bullshit. Investigate XP's "Fast User Switching" system. You'll find that Terminal Services/Remote Desktop has become a core part of the Windows UI -- every login session, from the console or remotely, is a terminal server session. When you "suspend" a session to go back to the login screen to login as someone else, you're simply detaching from that terminal server session and creating a new one for the new user. When you log out, you're closing the current terminal server session. In short, no matter what you do in XP (and .NET Server/Windows 2003), you're using terminal services (obviously with optimizations for the local case).


      If anything, Windows' efforts are more advanced than X, since you can keep sessions around and log into them locally or remotely, while any apps you left running will continue to run, and pick up properly when you reconnect. Like screen, but for a GUI.

    8. Re:Well.... by spitzak · · Score: 1

      I also agree this would be a good idea, though they would probably go with Direct X rather than OpenGL, which would be bad.

      In any case other toolkits can be made to work with Xlib emulation, much like X is done on Win32 right now.

    9. Re:Well.... by Anonymous Coward · · Score: 0

      OpenGL can but it needs an underlying windowing system which supports it. Why do you think they glEnable and glClientEnable?

    10. Re:Well.... by Anonymous Coward · · Score: 0

      They don't like the font support? Then they can hack up XFree86 to their liking. It's not GPL, so they don't even have to release the source.

      Using something other than X is stupid wheel-reinvention. It'd also give Microsoft the convenience of having even statically linked apps not run on anything other than their product.

      Of course, this whole topic is a pipe dream anyway, so what the hell? Dream all you want.

    11. Re:Well.... by koa · · Score: 1

      Actually, this sounds almost as if the argument here is stop the competition between Microsoft and the Linux folks, and start a NEW conflict between Microsoft and the XFree86 folks. Becuase if this were to happen, the underlying OS would be a moot point, thus thrusting MS into a GUI Server war.

      Would it be called MSClosed86 as opposed to XFree86?

      heh.

      --
      ....move along....nothing to see here....
  13. Right. by Renraku · · Score: 1

    Ever heard that company's slogan that says something about better ingrediants means better products? Lets attempt to break MS programmers' vision of what an OS should be and change it to Linus' vision. Now lets all remember that MS wants to put a cap on copying and copywrite violations whereas Linus wants everything to be open and within grasp. Conflict of interest and all.

    --
    Job? I don't have time to get a job! Who will sit around and bitch about being broke and unemployed then?
    1. Re:Right. by Anonymous Coward · · Score: 0

      Linus wants everything to be open and within grasp.

      you obviously haven't read GNU's"GNU/Linux FAQ".

      according to the FSF, your idea of Linus's vision is completely wrong. see how the GNU crowd turn on each other like a pack of wild dogs when they have nothing better to do?

    2. Re:Right. by Renraku · · Score: 1

      I'm not part of this GNU crowd. Free software is good, and I usually don't agree with licences and crap that most commercial software attempts to enforce, but don't associate me with some Linux advocate.

      --
      Job? I don't have time to get a job! Who will sit around and bitch about being broke and unemployed then?
  14. I'm sorry by Znonymous+Coward · · Score: 1

    but this really seems like tabloid style news. Shocking and not true.

    --

    Karma: The shiznight, mostly because I am the Drizzle.

    1. Re:I'm sorry by _Sprocket_ · · Score: 1


      but this really seems like tabloid style news. Shocking and not true.


      Where was the claim that this is any kind of news or reporting of an event? Cringely's piece is simply a "what if". Even he says its not likely to happen.
    2. Re:I'm sorry by Anonymous Coward · · Score: 0

      Sig: I can't understand why people who hate Linux and Apple read slashdot.

      And I can't understand why anybody with a long enough memory to remember Apple trying to shut down the entire computer industry with their touch-n-feel lawsuits doesn't hate Apple.

      Certainly all the geeks and tech type people who I know hate Apple. Some with a passion.

  15. It's time to be realistic by scyta1e · · Score: 2, Insightful

    Let's be realistic now, Windows and Linux do different things. If you want actual control over your computer and a nice development environment, use Linux. If you want to access any kind of file type or hardware simply and easily, you're gonna use Windows. Sure one could be brought to perform like the other, but that would take a damn long time.

    1. Re:It's time to be realistic by abartlett_219 · · Score: 1
      Sure one could be brought to perform like the other, but that would take a damn long time.

      Not exactly. Linux can do good file support/hardware with vendor support. May not be open source. OpenOffice is a good example of a good Office replacement. May not be exactly right, but unless MS was to open the Office file formats we can never get it exactly right.

  16. The question is by Anonymous Coward · · Score: 5, Funny

    Will Linus accept the BSOD patch for the kernel?

    1. Re:The question is by Ivan+Raikov · · Score: 1

      Will Linus accept the BSOD patch for the kernel?

      I'd be more curious to find out whether he would accept the IE patch...

    2. Re:The question is by Anonymous Coward · · Score: 0

      Oh, you're already curious enough, "Miss" Raikov.

    3. Re:The question is by ddent · · Score: 1

      We had the server aspect (khttpd), but it was ripped out in 2.5 since other things were found to be faster ;).

    4. Re:The question is by kasperd · · Score: 1

      Will Linus accept the BSOD patch for the kernel?

      Of course not, Linus never accepts anything for the kernel if it can be done just as good in user mode.

      --

      Do you care about the security of your wireless mouse?
    5. Re:The question is by Anonymous Coward · · Score: 0

      I'm more curious if MS would accept splitting it up in kernel panics and file system panics, and putting them on a black screen.

  17. first post by Mungkie · · Score: 0, Offtopic

    new version of 1diskxwin available at:
    http://freshmeat.net/projects/natld

  18. no, it shouldn't by Tha_Zanthrax · · Score: 1

    no it shouldn't.
    The next Windows should not be built on top of Linux. why not? I wwould require to many workarounds to get some backwards compatability.
    Microsoft should be forced to rewrite the entire code allover. part of their code has probably change since windows 3.11.

    1. Re:no, it shouldn't by jcast · · Score: 1

      part of their code has probably change since windows 3.11.

      I'd expect so, yes. Not even M$ can change the UI *that* much without changing some code...
      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    2. Re:no, it shouldn't by Twirlip+of+the+Mists · · Score: 1

      It seems that most people posting to this thread aren't even bothering to discuss the question in any serious fashion. It's nice to see that at least one person is staying out of the "M$ SUCKS!" "LUNIX SUCKS!" fray.

      Now let's think about this for a second. When Apple went from OS 9 to OS X, they had a huge compatibility problem to deal with. Part of it was dealt with my completely reimplementing a large subset of the Macintosh Toolbox API's on the new OS-- that's what we call Carbon now. It still required most apps to be recompiled, but the changes to the API's were so small that most could be Carbonated very quickly and easily.

      But Apple also provided what basically amounts to a VM: Classic, a.k.a. Blue Box. Inside Classic, old-style Mac apps can run without modification, and without having to be emulated. Classic provides the old apps with a shared address space and the basic infrastructure they need to run.

      Why could Microsoft use one or both of these approaches? They could either implement Win32 and whatever else in a UNIX environment, or they could provide a VM that runs full-fledged Windows for compatibility.

      --

      I write in my journal
    3. Re:no, it shouldn't by Anonymous Coward · · Score: 0

      Forget about rewriting code. Forget, even, about redoing the design. What is needed is a change to Microsofts *attitude*.

    4. Re:no, it shouldn't by Henk+Poley · · Score: 1

      I still think it's strange that Microsoft didn't include Win9x/Win3.x emulation in WinXP/2k. I mean a 'hard' emulator/VM. Just fire up a VM-Ware or Bochs (the latter one is 'just' an x86 emulator, I know) styled virtual machine and run the program in it's native environment.

  19. Erm... it isn't already? by Mapultoid · · Score: 1

    Wait, Windows isn't already free? Hmmm... odd, I don't remember paying for my copy...

    --
    Ben Garrison, a mindless idiot who will be the first against the wall when the revolution comes.
    1. Re:Erm... it isn't already? by Znonymous+Coward · · Score: 1

      Even by pirating Windows you are supporting it. Linux can't begin to gain support as a platform until it is widely used. We need to gain market share, please support Linux by throwing away your illegal copy(s) of Windows!

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    2. Re:Erm... it isn't already? by Anonymous Coward · · Score: 0

      You never would have guessed, but there is a reason that people use windows! its a great OS, with a stable GUI with tons and tons and tons of software available for it! its the x86 standard platform for games, office software, and comes pre-installed on nearly every PC sold over the counter.

      compare that to linux. thats why 'you' don't have the market share.

    3. Re:Erm... it isn't already? by Znonymous+Coward · · Score: 1

      If you hate linux so mutch then why do you read slashdot?

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    4. Re:Erm... it isn't already? by jguthrie · · Score: 2, Insightful
      It may come as a shock to you, but I don't particularly give a damn about 'my' market share. I don't need zillions of people choosing what I choose to make it the right choice for me. I use what I like and I will continue use Linux as long as I like it.

      I am fortunate that my employers think Linux is worth using, and it's nice for Linux to have enough popularity that the software tools I need get developed, but they would be there even if the Linux usage had peaked in 1992. Maybe there will be a revolution. Perhaps it's even under way right now. Who knows? I'm not in it for your revolution. It isn't important to me.

    5. Re:Erm... it isn't already? by Anonymous Coward · · Score: 0

      Everybody used windows before it was "stable" too... So stable can't be a reason for using it now.

    6. Re:Erm... it isn't already? by igggy · · Score: 1

      no, but as far as GUIs go, stability is a plus that windows has over linux.

      well, at least where xfree86 is concerned.

    7. Re:Erm... it isn't already? by Anonymous Coward · · Score: 0
      I don't need zillions of people choosing what I choose to make it the right choice for me.

      Yes you do. If Linux didn't have such huge support, it wouldn't be as good as it is.

    8. Re:Erm... it isn't already? by jguthrie · · Score: 1

      Actually, most of the increase in user base recently is from people who don't contribute software. That means that I need Linux's popularity to be a tiny fraction of what it is in order to be happy with it. That's why I was happy with it even back in 1992.

    9. Re:Erm... it isn't already? by Anonymous Coward · · Score: 0

      We don't hate linux, we hate little whiny bitches such as yourself.

  20. still built on DOS? by Yosi · · Score: 1

    The article implies that WinXP is still biult on DOS.

    While that was true through WinMe, WinXP is built on NT, which is a completely independant kernel, whose history others can tell better than I can. So technically, they have already done something similar to what is being suggested -- switching to a modern kernel.

    Only the one they used was (mostly) developed in house.

    1. Re:still built on DOS? by Jeremiah+Cornelius · · Score: 1
      It's not built on DOS.It's built on what I'd call VMS-NG .

      The NT family of OS's can be veiwed as being divided into what happens in "Cutler-space" and "Allchin-space". It's a little bit of an over-simplification, but almost accurate. The device-manager in 2000/XP crosses the Cutler/Allchin axis, and even NT4 moved graphics drivers from the user subsystem to the "NT Executive" (Ring-0) space.

      Cringely advocates moving the most arcane, esoteric, unreliable and unmanageable layer - with it's legacy Windows 1.0 baggage - on to a free OS. A better idea (technically speaking) would be the creation of a REAL integrated POSIX subsystem to replace Win32, etc. This would be Son-of-OpenVMS!

      Pigs will fly sooner than this.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    2. Re:still built on DOS? by Dunkalis · · Score: 1

      Wasn't the original plan for WNT to be a completely POSIX-compliant OS, with complete source compatibility with Unix? Anyway, where'd you get that information? I'd really love to read some more about the NT kernel (I love kernel architecture and design stuff)

      --
      Slashdot is a waste of time. I enjoy wasting time.
    3. Re:still built on DOS? by Anonymous Coward · · Score: 0

      Yeah, but the POSIX subsystem hasn't been updated in a very long time. I think they might've even scrapped it in more recent Windows. But I don't do Windows.

    4. Re:still built on DOS? by Anonymous Coward · · Score: 0

      creation of a REAL integrated POSIX subsystem to replace Win32, etc. This would be Son-of-OpenVMS!

      Microsoft SFU/Interix is a UNIX subsystem for the NT kernel. $99.

    5. Re:still built on DOS? by Jeremiah+Cornelius · · Score: 1
      The original plan was for a 32-Bit, OS/2 3.0. This was the MS roadmap - which conflicted with IBM's desire to have 3.0 remain 16-bit, with a true object-oriented Presentation Manager. This was part of the fallout between the two companies in the late '80's.

      By the time Cutler's development on the NT kernel was far enough along to support the PM layer, Windows 3.0 was already a runaway success, beyond the dreams of OS/2 adoption.

      It was a nail-biting decision by Gates and Ballmer to turn their backs on IBM and supplant Presentation Manager with a 32-bit Windows environment for the graphic shell to the new OS. They were scared, but the gamble paid off.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    6. Re:still built on DOS? by Jeremiah+Cornelius · · Score: 1
      Interix is interesting, but not particularly good. It relies on the MKS Korn shell code - which is not fully compatible with AT&T ksh. This is from Dave Korn himself.

      You are right, though. MS SFU integrates as a real subsystem, unlike Cygwin - which runs on top of the Win32 subsystem.

      Have you gone through the hell it takes to get a GNU toolchain and build environment running on SFU? If Solaris is a five, and Irix is a seven, this is about eight and a half - just because of how much work you need to do. Cygwin may have big latencies, but once things launch - they are fast and compatible...

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
  21. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  22. But no backwards compatiblity by shoppa · · Score: 2, Interesting

    The reason that "new" Windows releases still have a MS-DOS command line is backwards compatiblity. (And force of habit, by now.) Linux doesn't automatically offer that advantage (though the DOS emulators that run under Linux were useful to me in the mid-90's, and I'm sure they still exist now.)

    1. Re:But no backwards compatiblity by beebware · · Score: 1

      Agreed, I run Windows 2000 which doesn't have DOS as an underlying operating system - but I'm glad it's still got the command line functionality. There's just some things that you need a command line for...

    2. Re:But no backwards compatiblity by jcast · · Score: 1

      Oh common. Linux is backward compatible all the way back to Version 7!

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
  23. Pardon? by Acidic_Diarrhea · · Score: 5, Interesting
    "Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right?"
    This article posed an interesting proposition but in order for the whole premise to fly, this snippet really has to be a "Well, duh" type of question. I really don't know that it is. Without any definitive proof of this, the author is merely picking at straws. How does anyone know where the clunkiness of Windows comes from? I mean, the NT kernel isn't exactly a slouch and I'm not sure that Linux is vastly superior. How are we to know that the windowing system isn't the problem? Perhaps the real Operating System-type services provided by the kernel are faster and more powerful than the ones provided by Linux. We just don't know because a separation of the windowing system from the real OS isn't possible with MS's closed source system. Thus, this argument isn't really credible to make. It's an interesting hypothesis but there's nothing solid to say, "Yes! You're right!" There's really no way to know which underlying OS services are better provided by XP or Linux.
    --
    I hate liberals. If you are a liberal, do not reply.
    1. Re:Pardon? by wideBlueSkies · · Score: 2, Interesting

      >>We just don't know because a separation of the windowing system from the real OS isn't possible with MS's closed source system.

      I'll wager that the guys in Redmond have the Windows Kernel running on machines without the windowing system/fluff. They're not stupid people over there. There's no way that they could accurately benchmark kernel performance with all that crap running on top of it.

      I'll bet that they even develop the kernel seperately from the windowing system. They probably only test the 2 components together after a round of kernel changes, and standalone stability has been acheived.

      Even if the above isn't true, you know that somewhere in Redmond, some developer or group has got to have the Windows Kernel running standalone on a machine.

      Also, MS would be stupid to not benchmark their product's performance against the 'competition': LINUX and BSD. The only way to do so is with the raw kernel. At least it's the start of a good test.

      Would any MS developers like to comment?

      --
      Huh?
    2. Re:Pardon? by drinkypoo · · Score: 2, Interesting
      Not only that, but NT is a mostly microkernel-based OS. Right now it is targeted at the Windows NT HAL which does basically nothing but hardware access. Object management (Windows, devices, drivers, files, mutexes, processes, and threads, etc) is done entirely within the kernel. Perhaps some of that should be done by the microkernel. Mach, for example, manages hardware, memory, and threads; Windows currently manages threads.

      If it made sense for NT to use ANYTHING under it, it would make the most sense to stick with the NT kernel but target mach instead of the HAL, and move process/memory handling out of the kernel, allowing mach to manage these things. This is probably how linux should have been designed but as we know the microkernel/macrokernel debate has raged hotly since time immemorial and will not likely be finished any time soon. I do think it makes the most sense though, as it facilitates everything running in user space.

      Also I would not bother to port to any microkernel which does not support realtime scheduling (as does RTMach, but not normal Mach apparently) as you want to be able to use the same microkernel across all platforms, and microsoft has an embedded NT product. If you're going to move threading out of the kernel it has to do everything you've ever dreamed of. I guess they could add it to rtlinux if they hired a bunch of developers away from QNX or something :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Pardon? by Thatman311 · · Score: 1

      I have never heard of this sort of benchmarking but I don't work in the perf group. As for the having just the "kernel" running on a system without the windowing system...well...you can do this using the Embedded version of Windows.

      --
      Silly Rabbit...Sig's are for kids.
    4. Re:Pardon? by Anonymous Coward · · Score: 0

      You have no clue what you're talking about do you?

      Dispite what one "operating systems concepts" book might say, NT is not a microkernel in any way.

      All that the HAL does is allow drivers to work on different hardware platformes. What microsoft calls the kernel, which sits between the HAL and the executive, and handles such things a locks other services for the executive, is close to what mach does. However there is no real division of the components of the executive, and no formal message passing, so NT is not a microkernel, and the only easy way to make it run over mach would be to run the whole thing as a server over mach, just like how darwin works.

      And both NT and linux are proof that you do not need a microkernel for easy portability, which is the major argument for the microkernel.

    5. Re:Pardon? by xswl0931 · · Score: 1

      During the Text portion of setup, you are running basically only the NT Kernel with a simple text ui.

    6. Re:Pardon? by Anonymous Coward · · Score: 0

      Just a point.
      I believe that the NT Embedded is not an RTOS, just a Fast-Enough-Nearly RTOS.

      Linux is good enough for that.

      RTLinux and a few others (sorry, can't remember your names) turn it into a true RTOS.

      NT doesn't have that change.

      You're not wrong that a real RTOS ought be the base of the next system, since Multimedia and IO are the worst aspects of current OS's. Doing this may be a real pig to work with (which was BeOS's problem - good architecture, but you REALLY had to know your onions to program for it).

    7. Re:Pardon? by Anonymous Coward · · Score: 2, Informative

      Actually if you would like to see the Windows XP kernel running without the gui simply boot off of a Windows XP CD... or better yet, boot using a Windows Preinstallation Environment CD. Those are the CD's used by the tier-1 manufacturers.

      The Windows Preinstallation Environment boots up into a graphical interface but it only gives you a command window to use.

      If you think about it, trying to determine if your just using a kernel as opposed to a graphical interface is pointless. It is not like you can actually "see" the kernel. The kernel merely controls the rest of the OS and responds to commands that are given to it. Even different distributions of Linux show different graphical items and pictures while booting the kernel. It's not just a clear-cut thing.

    8. Re:Pardon? by wideBlueSkies · · Score: 1

      >>If you think about it, trying to determine if your just using a kernel as opposed to a graphical interface is pointless. It is not like you can actually "see" the kernel. The kernel merely controls the rest of the OS and responds to commands that are given to it. Even different distributions of Linux show different graphical items and pictures while booting the kernel. It's not just a clear-cut thing.

      I hear you. You're right. However a simple command line interface running on top of basic kernel or OS services is a LOT lighter than running all of windows networking/gui/'insert bloated service here' code on top of it.

      --
      Huh?
    9. Re:Pardon? by Anonymous Coward · · Score: 0

      At one point they were saying that Windows .NET Server (or Server 2003 or whatever they are calling it today) would run without a gui and completely headless. Several big PC manufacturers (Dell and Compaq to name a few) were developing PC server hardware that could boot without a keyboard and video card. You would be able to get to a command prompt over serial just like a Sun box.

      I haven't seen it mentioned in about a year, so I don't know if that made the final feature set.

  24. Um... by Anonymous Coward · · Score: 0

    Yes they could become an open source endeavor if they really wanted to, but doesn't that contradict Microsoft's capitalist demeanor? The whole point of M$ is to make as much money as possible.

  25. Yes... by trotski · · Score: 1

    it SHOULD but with Billy-boy and his crew running things, it never will.

    --

    "Entropy is the bad-guy, and he is everywhere"
  26. It already is (free) by Anonymous Coward · · Score: 0

    I've never paid for a copy of Windoze yet.

    1. Re:It already is (free) by Znonymous+Coward · · Score: 2, Interesting
      I postied this earlier...

      Even by pirating Windows you are supporting it. Linux can't begin to gain support as a platform until it is widely used. We need to gain market share, please support Linux by throwing away your illegal copy(s) of Windows!

      --

      Karma: The shiznight, mostly because I am the Drizzle.

  27. No... by autopr0n · · Score: 1, Insightful

    Well, IBM is larger, and they ship free software. So in order for Microsoft to be the largest company that sells free software, they would need to be larger then IBM.

    Otoh, if you're mesuring units shipped, M$ could probably do it. I don't know why they would want to, though.

    --
    autopr0n is like, down and stuff.
    1. Re:No... by Anonymous Coward · · Score: 0

      How are you defining larger? In square miles? Microsoft's market cap is slightly more than double IBM's.

    2. Re:No... by xswl0931 · · Score: 1

      How are you defining "larger"? MSFT market cap $287 Billion employees 50,500 earnings $8.9 Billion sales $29 Billion IBM market cap $138 Billion employees 319,876 earnings $5.5 Billion sales $79 Billion source: www.cnnfn.com

  28. Linux? by Anonymous Coward · · Score: 0

    No, Billyboy should buy AmigaOS or BeOS...

  29. Erm no. More like bankruptcy. by Anonvmous+Coward · · Score: 2, Insightful

    "If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they? "

    They'd also be the largest vendor of Free Software filing for bankruptcy.

    I don't intend that comment as a troll. I know some investors. (My uncle is one...) I've talked with them about MS etc and what they like/dislike about them. If they were invested in MS, they'd be upset about MS giving their moneymaker stuff away. They'd likely sell their stock in a heartbeat unless MS put one hell of a spin on it. There's the whole matter of how you make free software profitable. They want return on investment. They want what's tried and true.

    Now, as for MS porting Windows to Linux: Wouldn't everybody (at least on /.) get their panties in a bunch accusing MS of over-extending their monopoly into the Linux world?

  30. I bet... by jrwillis · · Score: 1

    that is MS wanted to make a BSD based OS that could still run dos/win32 based apps they could. Just my $.02

    --
    Keep Austin Weird!
    1. Re:I bet... by kasperd · · Score: 1

      they could.

      What makes you believe they haven't already done so? It could come in handy, if they suddenly realize they need such a thing in a hurry. Of course keeping it secret until then would be a major problem.

      --

      Do you care about the security of your wireless mouse?
  31. Correction by Anonymous Coward · · Score: 0

    Windows XP is built on the 2000 kernel, which is based on, not built on, the NT kernel.

  32. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  33. On top of Linux!!? by Thaidog · · Score: 1

    What possible advantages would windows gain from a Linux kernel? I can't think of one! Mac OS X did the switch to a unix kernel but that was only because of stability issues and the fact that they could port tons of software to a relatively small software base (compaired to windows software base)

    --

    ||| I still can't believe Parkay's not butter.

    1. Re:On top of Linux!!? by Raffaello · · Score: 1

      Stability, yes, but the BSD subsystem of Mac OS X is an *optional* install. Although Mac OS X runs on a Mach microkernel, the BSD tools in /bin and /usr/bin are not necessary for the proper functioning of the system. Realize that I am not talking about the Developer Tools, which is yet another separate and optional install, but he core BSD subsytem. (See http://developer.apple.com/techpubs/macosx/Darwin/ GettingStarted/PortingUNIX/compiling/Installing__p ment_Tools.html)

      Most Mac OS X users will never see, or use the BSD subsystem, and may not even have it installed; The "tons of software" that runs on BSD will never be used by most Mac users, nor will it be ported for them, just for a handfull of unix savvy technophiles.

      So Apple did not choose a Mach/BSD core for Mac OS X because of the the ability to port unix software. Popular Mac software is written by the likes of Adobe and Microsoft (and Apple too) and it isn't ported from unix versions. There's plenty of software for the Mac (look at VersionTracker's Mac OS X section sometime) and the most popular Mac software has never, and could never run on *nix because it was all written to Mac APIs (Core Services, Carbon, and Cocoa), and for Mac OS X's Aqua, not X11 and/or BSD Unix.

      You could make the argument that Mach/BSD was chosen in part because of the availability of familiar, time tested unix development tools, but end users never see these, just as they never see any other unix ports.

    2. Re:On top of Linux!!? by spitzak · · Score: 1
      Wrongo! Every program that calls open() uses the BSD system. Mach message passing is only used for ipc between NextStep applications.

      You seem to be confusing the user-level tools with the kernel. The tools are easy to add (take a look at cygwin for Windows) but they don't mean the result is Unix.

  34. What's wrong with the NT Kernel? by or_smth · · Score: 1

    Whenever I see an article like this I tend to think that some fanboy's trying to make a joke of us all.

    Sure, Windows COULD be built on top of the Linux kernel, but why in the hell would you want it to be? Other than being closed-source, what is wrong with the current NT Kernel? Despite what a lot of ./ers say it is pretty solid, runs cleanly and does everything the desktop OS could want. It seems to me that running the Linux kernel would just complicate things and try to fix something that isn't wrong. I'm really curious on what the horrors of the NT kernel are, as I've never seen them (I'm talking about desktop OS here).

    Plus, the last thing I want to see is "You've installed a new device! Please wait while Microsoft (R) Windows recompiles the kernel in order to have support for [device name]"

    1. Re:What's wrong with the NT Kernel? by Anonymous Coward · · Score: 0

      as far as recompiling the kernel goes-- this rarely needs to be done

      as opposed to what is constantly seen in MS:

      your computer needs to be rebooted for changes to take effect:

    2. Re:What's wrong with the NT Kernel? by Anonymous Coward · · Score: 0

      If by "rarely" you mean "whenever you install a new piece of software or hardware"

    3. Re:What's wrong with the NT Kernel? by ergo98 · · Score: 0, Troll

      Well generally when you're installing new hardware you'll be rebooting your PC anyways (and items like USB or Firewire devices don't require a reboot). However the software comment does concur with my pet peeve: Moronic installation teams that always click the "require a restart" button on the installation package despite there being absolutely no reason. There are times when it's replacing some particular system component and absolutely requires it, but that is absolutely a rarity, and instead it's just a installation team that puts the ease of their jobs ahead of the ease of the public.

    4. Re:What's wrong with the NT Kernel? by Anonymous Coward · · Score: 0

      Well, for one thing they could use any of the excellent journaling filesystems for Linux (XFS, JFS, Reiser, Ext3, and most importantly, the new Reiserfs, which is amazing) instead of the so-so NTFS.

    5. Re:What's wrong with the NT Kernel? by Anonymous Coward · · Score: 0

      The number one problem (that I have seen) with the NT kernel is printer drivers. The printing subsystem *appears* to be linked/related to the graphics subsystem, which resides in the kernel.

      In short, (whatever the actual/technical problem) I have seen printer drivers BSOD a NT kernel.

      Furthermore, I have seen Terminal Server (with Citrix client printer mapping) automagically map the client HP InkJet driver and kill the (Terminal) server.

      This problem exists to this day. My company is currently diagnosing a HP driver issue with XP that crashes the box.

      Printer rendering needs to be done in userspace, not in the kernel. The system might handle I/O between the device and driver - but that is a different story - where the kernel handles exceptions, that crapppy printer drivers (HP) always seem to forget.

  35. that would be by asv108 · · Score: 1
    One hell of a paradigm shift! Unfortunately bureaucratic organizations suffer from a phenomenon known as groupthink, plus people and especially organizations hate to admit they were wrong.

    If MS moves towards Linux then there is still hope that the republican party will move towards the legalization of drugs, the Catholic Church will embrace birth control, and the Bush Administration will read the constitution.

    1. Re:that would be by bofkentucky · · Score: 1

      and the Bush Administration will read the constitution
      ...and Presidential perjury is grounds for impeachment but not removal. Cute but the Clintonistas are far from snowy white on the whole "Constitutiona Evasion 101" exam. Don't even start with Al, I only want to count some of the votes, Gore.

      --
      09f911029d74e35bd84156c5635688c0
    2. Re:that would be by Anonymous Coward · · Score: 0
      and the Bush Administration will read the constitution.

      And liberals will stop the slander of people they don't like and other politics of personal destruction.

    3. Re:that would be by Anonymous Coward · · Score: 0

      Since we're now on the issue of politics. How about if the democratic/left-wing liberals admit to being racists about the affirmative action thing? They accuse republicans of being racist and at the same time support giving certain people preference because of the color of their skin!? The democrats take advantage of minorities to no end.

      BUSTED

  36. Microsoft on Linux... ughhh.... by _ministry · · Score: 1

    kernel segmentation fault, ignore, retry, fail?

    I wonder what the mascot would look like? Sorta like a blue mouse, with big ears...

    1. Re:Microsoft on Linux... ughhh.... by Anonymous Coward · · Score: 0

      A mascot? How bout clippy dressed in a penguin outfit?

  37. Erm. The "sitting atop" could be questionable. by Elwood+P+Dowd · · Score: 3, Interesting

    Cringly seems to misunderstand something...

    Apple released Darwin under the APSL out of the goodness of their hearts (and their PR department, I'm sure). They don't have any restriction against using Darwin source inside their closed source components, like Aqua. I think this means that there are certain kinds of linking that you're allowed to do with BSD code that you aren't allowed to do with GPL code, if you're going to keep your IP proprietary. So Apple may not have been able to do what they did had they used the Linux kernel. For example, wasn't there a recent flap over Linus changing the name of some kind of trap to GPL_ONLY?

    I guess Microsoft could make this ok by GPLing anything that linked in that manner to the kernel, but it's definitely something that would have to be a consideration were this ever to occur.

    Ooooh. This would be an excellent way for them to embrace and extend, wouldn't it? Couldn't they release a Linux variant that was practically useless without their proprietary components? They wouldn't have to do that at first, but they might be able to work up to it...

    Iduno. Just talking.

    --

    There are no trails. There are no trees out here.
  38. Four possibilities by yerricde · · Score: 1

    I don't remember paying for my copy

    I can see only four possibilities for running a computer: paying for Windows, pirating Windows, stealing a computer that contains Windows, or not running Windows at all. Which is it in your case?

    --
    Will I retire or break 10K?
    1. Re:Four possibilities by Anonymous Coward · · Score: 0

      How about being given Windows as a gift or prize?

    2. Re:Four possibilities by Anonvmous+Coward · · Score: 1

      "I can see only four possibilities for running a computer: paying for Windows, pirating Windows, stealing a computer that contains Windows, or not running Windows at all. Which is it in your case?"

      I think he was making a Windows monopoly joke. Now that that's come to light, he can be modded +1, Funny now.

  39. I'm Brian Fellows!! by Anonymous Coward · · Score: 0

    I'm Brian Fellows!!
    I dont like Microsoft. Its big and scary.
    I'm Brian Fellows!!

  40. um... Robert Cringely = WHAT? by Anonymous Coward · · Score: 0

    Lay off the pipe you tard. YUO MAEK KNOW SENSE!!!!!

    Who allowed this to be posted on /.? this is just crap. many incorrect statments and an ugly color too. PBS needs to fire him and air more of 'Star Hustler' and 'Sesame Street'.

    1. Re:um... Robert Cringely = WHAT? by Anonymous Coward · · Score: 0

      Cringely is a fucking dumbass. That's all there is to it, really.

  41. One More Time by CajunArson · · Score: 5, Insightful

    Since this article was already highlighted on OSnews and Newsforge, I am once again forced to repeat myself:
    Cringely has no idea wtf he is talking about.
    Windows XP is NOT a simple windows manager sitting atop MS-DOS.
    But it has a DOS prompt!! Yeah, so does Linux if you install an emulator, does that mean Linux runs on MS-DOS?? The DOS prompt in XP is just another program that happens to look like what you used in the 80's before there was Linux :)
    I could go on and on about how XP is based off the NT core which came from VMS and how different the X server is from how MS does its graphical shell, but I'm sure many other posters will put up the same info.
    OK: Even ignoring why Cringely was completely wrong from a technical standpoint, here's why he's still wrong even if he were right (does that make sense?)
    MS: Has spent a boatload of money copying and building there own versions of what everyone else already had. They are finally starting to get it right, and are making money hand over fist doing it (at least in the OS sphere which is what we are talking about). Moving to a Linux base would be a HUGE investment, and MS software would go back to the stability of Win98 for 3 generations as they worked out all the bugs. As much as the Linux gurus on Slashdot would love to see MS sabotage themselves like that, they aren't that stupid.
    Linux: Linux would NOT be helped by having MS grab the Linux kernel and use it as a base for their OS. I also don't give a fsck what you'll say about "but the GPL!!" If MS were to do this they would withouth question weasal around the GPL or hire an army of lawyers to get it thrown out or watered down to the point it wouldn't matter. Meanwhile, they would either not give any code back to the kernel, or more likely would inject code specifically designed to slowly build up an IP claim over the entire kernel.
    MS doesn't like Linux but believe me, they are doing it a major favor by not trying to subvert it, and despite how much everyone here loves to bash MS, a whole bunch of the software running on
    Linux owes some credit to MS for providing a model to follow, like it or not.
    Once again, Cringely is proved to be a whole bag of hot air.

    --
    AntiFA: An abbreviation for Anti First Amendment.
    1. Re:One More Time by Anonymous Coward · · Score: 0

      But Cringely never did say all of that would happen. RTFA!

    2. Re:One More Time by sl3xd · · Score: 3, Insightful

      MS: Has spent a boatload of money copying and building there own versions of what everyone else already had. They are finally starting to get it right, and are making money hand over fist doing it (at least in the OS sphere which is what we are talking about). Moving to a Linux base would be a HUGE investment, and MS software would go back to the stability of Win98 for 3 generations as they worked out all the bugs. As much as the Linux gurus on Slashdot would love to see MS sabotage themselves like that, they aren't that stupid.

      Of course, the actual logic of spending this money to build their own version of what everyone else already had is the troublesome part; There are major parts of the OS that have been quite literally 'carbon copied' from the Free/Open/Net BSD code, with a zero licence cost of any kind at all. Why they go about re-inventing the wheel when somebody is giving away a far better wheel (Such as the process scheduler, VM, file system, and network stack, to name a few) 'no strings attatched*', is beyond me... however it does reek of the NIH (Not Invented Here) syndrome. Of course that may not be the case, but Microsoft's apparent refusal to adopt larger portions of the BSD code seems like a bad business decision to me. There is just a lot less money that would have to have been spent, and the end result would have been a more flexible, stable, and secure system than what Microsoft developed in-house, and yet they get to keep all of the BSD-licenced code as tightly-controlled as the Windows source currently is. It seems like Microsoft shot themselves in the foot by not taking advantage of what amounts to thousands of man-hours of free (non-cost, no-strings attatched) work and research; passing up a free lunch is a very un-Microsoft like behavior.

      And I agree that it's crap to say that they would build the OS on top of Linux. Some people may idolize the GPL, and that's fine. Many feel the BSD licence is a more 'free' licence, again that's fine. Given the choice between the two, however, and Microsoft would almost certainly choose the 'no strings attached*' BSD code.

      *No strings attached meaning that there is zero cost to licence the code, and there are no terms on redistribution other than to give credit to the original authors; The GPL stipulates that any changes of the code must be redistributed, the BSD licence does not. This modified code redistribution is the disinguishing feature of the GPL to which Microsoft objects-- they do not wish to allow anyone access to their code (not without working out some scheme whereby Microsoft will recieve monetary 'compensation' for access to their modifications, at a minimum.)

      --
      -- Sometimes you have to turn the lights off in order to see.
    3. Re:One More Time by VoidEngineer · · Score: 1

      I could go on and on about how XP is based off the NT core which came from VMS and how different the X server is from how MS does its graphical shell, but I'm sure many other posters will put up the same info.

      Correct me if I'm wrong, but isn't VMS based off of Unix as well? I recall something about companies such as Digital and HP. Seems like XP would be more favorable to an underlying unix OS than otherwise.

      Moving to a Linux base would be a HUGE investment, and MS software would go back to the stability of Win98 for 3 generations as they worked out all the bugs.

      Perhaps. But don't they have their automated bug report systems in place nowdays? Seems like that would exponentially speed up the bug fixing problem. Didn't have automated bug-report systems back in the DOS days...

      Linux would NOT be helped by having MS grab the Linux kernel and use it as a base for their OS.

      Except for the fact that 95% of the world which currently uses DOS/NT based systems would actually migrate to Linux. Don't you think that people who now learn commands like 'dir' and 'copy' would, instead, learn 'ls' and 'cp'. Seems to me like that would be the foundation of learning and experience which could increase the numbers of future linux programmers and coders.

    4. Re:One More Time by DeepRedux · · Score: 1

      VMS and Unix are quite separate. They both date back to the 1970's.

      VMS was developed by Digital for its VAX hardware. Digital was later bought by Compaq, which was bought by HP.

      Unix was developed by AT&T's Bell Labs. Unix slightly predates VMS and was developed on older Digital hardware (PDP-7, later PDP-11). The PDP did not support virtual memory. VM support was latter added to Unix, on a VAX, at Berkeley by Bill Joy.

    5. Re:One More Time by Anonymous Coward · · Score: 1, Insightful

      There is just a lot less money that would have to have been spent, and the end result would have been a more flexible, stable, and secure system than what Microsoft developed in-house, and yet they get to keep all of the BSD-licenced code as tightly-controlled as the Windows source currently is

      BSD was not "open source" when Microsoft wrote NT in the early 90s -- you needed to pay royalties to AT&T to use it.

      Microsoft also wanted an OS standard that was proprietary that they had 100% control over. When NT came to market, the Unix vendors were in a big blood war with each other and were forming various standard bodies to push each other around.

      You'll not that people port software TO NT, but very rarely FROM NT. That's because they used "just enough" BSD code for some Unix-compatibility, but not enough that they became a Unix.

    6. Re:One More Time by Guppy06 · · Score: 1

      "MS: Has spent a boatload of money copying and building there own versions of what everyone else already had. They are finally starting to get it right, and are making money hand over fist doing it"

      So, what you're saying is that MS is just like the Linux community, except that they're making money?

      "Moving to a Linux base would be a HUGE investment,"

      Moving to OS/2 (or at least pretending that they were for a while) was a huge investment. Microsoft's fork of the OS/2 kernel (which we now call "Windows XP*") has proven to be wildly successful (and profitable). So much so that they finally killed off the original Windows line (and DOS along with it).

      They've done it before, there's no reason to believe they couldn't do it again.

      *To be accurate, XP is is MS OS/2 5.1 running Windows 5.1 with networking done by LAN Manager (you guessed it) 5.1

    7. Re:One More Time by InfernoBlade · · Score: 1

      No, no, and no. Windows XP is Windows NT 5.1, not OS/2 5.1. Read some of the comments above if you need a bit more proof. Windows NT was written from scratch, by a guy who worked on VMS, so it's close to VMS by design. It has an OS/2 emulation layer, which is where people get that stupid idea that NT is a fork of OS/2. It isnt, stop propigating that damn stupid meme, or shall we all start calling Linux a fork of Minix, because one shares a few design concepts with another?

    8. Re:One More Time by vistas · · Score: 1

      Correct.

      Since the company I worked for at the time was heavily involved in incorporating various networking systems into what was a network-less Windows 2.0, we got to see the early builds of MS-OS/2 3.0 and the first builds of NT. They were quite different beasts. I would much rather have run MS's OS/2 3 than what eventually came out as OS/2 3.0 from IBM.

      One thing that the previous poster got right was that MS Lan Manager was the basis of networking in both MS-OS2 3.0 and NT.

      When I went out to Redmond in 1990, six months after Win 3.0 came out with it's limited networking support, most people in the networking group had MSOS2 machines for their everyday machines and only used DOS/Win3.0 for testing.

    9. Re:One More Time by Chromonkey · · Score: 1

      "Of course, the actual logic of spending this money to build their own version of what everyone else already had is the troublesome part..."

      Why is that troubling at all? They wrote a competing application / OS.

      Isn't this all about competition?

      --
      There are very few real things in this world...this isn't one of them.
    10. Re:One More Time by Guppy06 · · Score: 1

      "It has an OS/2 emulation layer,"

      "Emulation" is an awfully strong word. Emulation is how NT handles DOS and Win16 apps. OS/2 has its own dedicated subsystem (what the config.sys file is for), just like Win32. The two are independent of each other.

      "or shall we all start calling Linux a fork of Minix, because one shares a few design concepts with another?"

      Linux was never marketed as "Minix NT." Before the success of Windows 3.x, the project name was "OS/2 NT."

    11. Re:One More Time by Anonymous Coward · · Score: 0

      The truly ridiculous claim is that NT is somehow VMS. Yes, there are a few similarities, but it's like saying that since the Eiffel Tower and the Statue of Liberty were designed by the same man and both have a form given to them by structural steel that the Statue of Liberty was based on the Eiffel Tower.

      The fact is, significant portions of the NT code (for example, NTFS) really were based directly on Microsoft OS/2 code (like the HPFS code), much like Internet Explorer was based on NCSA Mosaic.

    12. Re:One More Time by sl3xd · · Score: 1

      It is about competition; It takes far less effort to stand on the shoulders of giants than it is to do it all yourself. So while Microsoft is herniating their spleen trying to lift the boulder by hand, they could have just borrowed the BSD guy's front-end loader. It's redundant, wasted effort.

      It just doesn't make sense to keep a refrigerator running on the south pole.
      Just stick it outside.
      It just doesn't make sense to start a campfire within 2 feet of a lava flow.
      It's already hot enough to melt lead, what do you want?
      It just doesn't make sense to carry a bag of sand in the sahara.
      Just bend over and pick some up.
      It doesn't make sense to re-write an entire VM, process stack, and network stack.
      When BSD gives it to you for free with no strings attatched.

      --
      -- Sometimes you have to turn the lights off in order to see.
  42. Are they allowed to? by Banjonardo · · Score: 1

    I don't know much about the topic, but doesn't the liscencing disallow you from selling it for money? Or is it just a common misconception?

    --

    -----

    Score 3? For what? Being wrong, at length? - smirkleton

    1. Re:Are they allowed to? by ender81b · · Score: 1

      I don't know much about the topic, but doesn't the liscencing disallow you from selling it for money? Or is it just a common misconception?

      Common misconception. Otherwise how would all the linux distro companies make money? All the GPL states you have to do is make available your sourcecode. That's it. You can charge a nominal fee (whether it be cost of bandwith or cost of cd) to provide the source but yes MS could use the linux kernel and throw windows on top of it and still charge 299$ for it.

      Of course they won't. I see no combination of factors that would cause MS to use the linux kernel. I am not a kernel engineer or even that expierenced in computer science but I fail to see how switching to the linux kernel would give MS any real sort of gains. The NT kernel currently in use, stripped of all it's overhead, is an extremely advanced/nice/fast/stable kernel... I believe linus torvalds has been quoted as saying the stuff Microsoft does at the kernel level is quite good.

      Why windows gets a bad rap for security is basic fundamental flaws in it's system, not its kernel AFAIK. 90% of vulnerablities are the numerous buffer exploits that have been found (due largely to sloppy coding). Unstability is caused, usually, by a bad device driver or a problem with the GUI - same as linux. Indeed you could even argue that windows XP/2K are more stable, for the desktop user, than an equivalent 2.4.20 system + KDE/Gnome.

    2. Re:Are they allowed to? by ryants · · Score: 1
      You have a fairly low user ID # and have posted around 350 comments, so you've been around /. for a while.

      And you honestly have never heard of companies like say, oh, RedHat, selling GPLed licensed software?

      All I can say is "Wow". And read this:

      Selling Free Software.

      --

      Ryan T. Sammartino
      "Ancora imparo"

    3. Re:Are they allowed to? by Banjonardo · · Score: 1
      So would they have to release just the linux source or EVERYTHING? (In that case, there is no way in hell MS would release the source for windows.

      --

      -----

      Score 3? For what? Being wrong, at length? - smirkleton

    4. Re:Are they allowed to? by Banjonardo · · Score: 1

      I know they sell it, but I always thought it was more of a "sell it for the cost of the box + cd, keep the company alive" deal, but the other comment made it clear to me that they must release the source, thereby enabling people to download instead of buy their software.

      --

      -----

      Score 3? For what? Being wrong, at length? - smirkleton

    5. Re:Are they allowed to? by ender81b · · Score: 2, Informative

      Just the linux source. You can link to GPL'ed software/build stuff on top it/whatever. A number of distro's do this to set themselves apart (like SuSe with YAST).

    6. Re:Are they allowed to? by brain159 · · Score: 2, Informative
      that's a common misconception - but if I make some minor tweeks to GNUFoo and sell it as VisualFoo for $75 + tax, I have to sell it under the terms of the GPL, with everything that entails (i.e. every user would then be free to re-modify it and give it away or sell it better and cheaper to compete commercially with me).

      The Free Software Foundation (they who wrote the GNU GPL) have a good FAQ which tells you about as much as you can find out about it without needing a lawyer's advice.

  43. assinine by Anonymous Coward · · Score: 0

    If Microsoft built their next operating system on Linux, they be required to disclose all of the source code essentially making it free (ie. another Mandrake).

  44. Windows XP still built on DOS? by Handpaper · · Score: 1

    That's funny, I thought XP & 2000 were versions of NT, without any DOS subOS. Windows versions 1-3.1, 95 & 98 were DOS based, to the extent that DOSEMU will run Windows 3.0.
    As for being able to get a C:\ prompt, there are probably people running user-friendly Linux distros like Mandrake, which starts X & KDE on boot by default, who have never seen a login screen (I know I didn't for 3+ months), but Konsole, Xterm & RXvt will be there if needed.

    1. Re:Windows XP still built on DOS? by m1chael · · Score: 0

      it has dos emulation. dosine is not an emulator!

      --
      I know you are psychotic, but please make an effort.
    2. Re:Windows XP still built on DOS? by Anonymous Coward · · Score: 0

      ever heard of dosemu?

  45. Windows already IS built on Linux. Duh. by shamilton · · Score: 1, Insightful
    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    I can run cygwin bash, too.

    sh

    --
    "[A] high IQ is like a Jeep; you will still get stuck, just farther from help!" --Just d' FAQs, c.g.a
    1. Re:Windows already IS built on Linux. Duh. by Anonymous Coward · · Score: 0

      yeah, and if you try hard enough you can get a c: prompt in linux as well. That doesn't mean linux is built on DOS. Facts straight, please.

    2. Re:Windows already IS built on Linux. Duh. by stratjakt · · Score: 1

      3.1, 95, 98 and ME are built on top of DOS (or command.com).

      NT, 2K and XP are built around the NT kernel.

      Linux is built around the linux kernel.

      Building 'windows' on top of linux would mean replacing the kernel, and frankly with an inferior one.

      I'd much rather see linux built around an open sourced NT kernel.

      --
      I don't need no instructions to know how to rock!!!!
    3. Re:Windows already IS built on Linux. Duh. by Anonymous Coward · · Score: 0

      He was being facetious. Duh. Sense of humor straight, please.

  46. Nice idea, but... by kruetz · · Score: 3, Interesting

    Okay, this would be nice if Microsoft was purely interested in developing a great consumer OS. Unfortunately, they're not. They are only interested in their bottom line (hey, this is capitalism!). To this end, they want to remain a monopoly and have their software on everyone's computer. Which is fair enough.

    There are several problems stopping MS from using Linux:

    1) They have .NET server (which will Win2004 or something, now), all of their .NET software, LongHorn and the next SQL Server under heavy development. I'm sure they'd rather continue working on software they know will rake in billions of dollars than start from scratch writing a UI for Linux.

    2) Remember all the FUD about the GPL and Linux? Well, Microsoft probably doesn't feel like doing a three-point-turn and adopting Linux and proclaiming it as the underlying foundation to Windows. And I doubt they'll use Linux and just remain silent about the presence of Linux.

    3) If they use Linux, they will probably want to extend some of the kernel, or alter parts of it. But it's GPL!! Now, they can dynamically link to GPLed software and that's okay, but if they want to make any alterations, they hve to distribute them. Now, that might actually make a valid busines plan, but it isn't an option as far as Microsoft is concerned. They don't want anyone seeing any source, if they can help it. The past is evidenc.

    4) This would mean a re-write of either ALL of their software - Office, IE, VisualStudio, BackOffice ... hardly a good idea, giving competitors a few years to catch up in the software stakes. Or they could drastically improve WINE and run their unported Windows software. But what would be the point of moving to Linux and using it to run Windows programs through an emulator? I doubt Microsoft would even consider this option, especially as WINE is GPL, so they'd have to start from scratch.

    Basically, what it boils down to is: compatability with existing and under-development software, and a desire to keep the Windows platform closed to everyone outside of Microsoft.

    Also, MS wants to integrate DRM into the OS. And they definitely don't want anyone getting their hands on the code. So they'd be rather worried about how to distribute the DRM without any legal issues concerning the GPL. They'd have to keep the DRM right away from the core of the OS, which is where they appear to want it to be. (Okay, this is a rather flaky reason, but it may be a small factor).

    --

    This sig intentionally left bla... dammit!
    Who's got the whiteout?
    1. Re:Nice idea, but... by erpbridge · · Score: 3, Informative

      #4... see the OSI chart, Applicaton Layer

      It SHOULDN'T mean a rewrite of all of their software, as the software should just be written to reference to the OS layer below it, not to the Kernel layer below that. The only things that might have problems are things like Visual C++ which, as part of their programming language, has the ability to make direct device calls... which even then should be done via device drivers running in the OS layer.

      Theoretically, the OS should run as an abstraction layer, so that whatever it is running on top of, whether that be a DOS "kernel", NT kernel, Macintosh (before OSX), or Linux or BSD kernel, isn't even something that needs to be addressed by the individual apps.

      Of course, that's in a perfect world, where any windowing system, whether it be MS Windows based, Mac windowing based, or X-Window based, can run on top of any kernel. We don't have a perfect world, and application developers (especially Microsoft ones) are known to code quick and dirty for their specific setup only, not for global compatibility.

      So, yes, for the time being, you are correct.

    2. Re:Nice idea, but... by Anonymous Coward · · Score: 1, Informative

      It SHOULDN'T mean a rewrite of all of their software

      Sorry, their server software like MS-SQL and Exchange is optimized for various Windowisms. This probably extends down to MS Office too. Changing the kernel and low-level code would be a huge performance penalty (just as Unix-ports such as Apache and Sendmail run slowly on NT).

      Theoretically, the OS should run as an abstraction layer

      Not all OSes are equal. You can build in abstraction layers (like Wine or Cygwin), but they will be non-optimal.

    3. Re:Nice idea, but... by erpbridge · · Score: 1

      OK, I just realized my bit about the OSI chart was wrong... OSI is networking layers.

      But, I do believe there should be abstraction layers at the OS level and windowing system level.

  47. Cringely a bit confused.. by radon28 · · Score: 3, Insightful

    If you read the article, Cringely seems to have a misconception about how Windows NT works.. he still thinks that Windows is just a binary layer running over a DOS shell, something that hasn't been true since Win9x. The command line in Windows 2K/XP is just an emulation of DOS. Anyway, let's be serious. We all know Microsoft isn't worried about the quality of their products, and certainly wouldn't backpedal the last few years of Unix/Linux bashing (no pun) and do something revolutionary like this.

    1. Re:Cringely a bit confused.. by Reziac · · Score: 1

      The one value I can see in a "Windows for *NIX" would be if [fantasy] the linux desktop user base ever got large enough to cut into the market for M$Office [/fantasy] ... in that case, I think it would behoove M$ to either do a real linux port of Office, or to do their own incarnation of WINE so they could sell *all* their Windows-based apps to linux users. Of course the latter would also let competitors' WinApps run on Win-for-linux, so I doubt it would happen.

      As to Cringely's contention, I *think* the DOS he's referring to is like you get in NT/2K/XP when you start in rescue-disk mode. I *don't* think he was referring to the command interpreter.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  48. Just a little question ... by DogIsMyCoprocessor · · Score: 1

    Wouldn't that break a fair number of Windows applications that use the services of the Windows kernel? Cringely doesn't mention that Microsoft would have to undergo the same pain that Apple did in supporting Mac OS 9 applications.

    --

    "And this is my boy, Sherman. Speak, Sherman." "Hello." "Good boy."

    1. Re:Just a little question ... by bofkentucky · · Score: 1

      People forget that they also made inroads to PowerPC at the time that Apple switched over from the 68x00. NT 3 on Power PC was a flop and Apple had a bad bout of stability/performance issues for a long time and lost tons of software vendors with the switch. They learned a very important lesson at that time about making major architectural changes to their crown jewels, don't do it, no matter the advantadges. OS/2 is now 10 years old in released form and the general public is just now moving to its decendents (OS/2|NT3 -> NT4 -> 2000 ->XP) after they finnally convinced/bought enough ISVs, made good compatability tools, and waited for processors to be able to emulate the old without visable performace degredation.

      --
      09f911029d74e35bd84156c5635688c0
  49. a "disk operating system" by hackwrench · · Score: 1

    Microsoft never said that a disk operating system wasn't in NT, there's a disk operating system in linux as well, as long as by disk operating system you mean a system for interacting with disks and as long as you have disks in your system, that's what you are going to need.

  50. A Few parts already are. by Theros · · Score: 1

    If memory serves correctly NT5 already has the TCP/IP stack from BSD(*nix).

    1. Re:A Few parts already are. by Anonymous Coward · · Score: 0

      could someone direct me to a site which talks about other things like the tcp/ip stack ?
      just interested really.

    2. Re:A Few parts already are. by Anonymous Coward · · Score: 0
      DUH! This is a well known fact. Microsoft's TCP stack (the one in every version of Windows that has one) is directly based from 4.4BSD IIRC.


      For fun, open, 'grep', or 'strings' up ftp.exe from Windows (2000 ftp.exe tested, all others should work). You will find this:


      Copyright (c) 1983 The Regents of the University of California.
      All rights reserved.

    3. Re:A Few parts already are. by zjbs14 · · Score: 1
      Actually since (I believe) Win2K, the stack is completely different. But they are still using the BSD-ported command-line FTP client.

      --
      No sig, sorry.
    4. Re:A Few parts already are. by Anonymous Coward · · Score: 0

      ftp.exe != TCP/IP stack, idiot.

    5. Re:A Few parts already are. by Anonymous Coward · · Score: 0

      It's an urban legend. At some point they had pieces of the BSD TCP/IP stack in there temporarily during beta releases. They rewrote the stack before release but kept the Copyright in there just in case.

  51. text of the article by Anonymous Coward · · Score: 0
    What Lies Beneath
    Why Microsoft Should Build Its Next Version of Windows on Top of Linux
    By Robert X. Cringely

    I was exchanging e-mail recently with my friend Mike Class, SJ, who is associate dean of the Graduate School at Marquette University in Milwaukee, Wisconsin. Mike, who is a Jesuit priest and therefore naturally drawn to the whole idea of conversion, wants Microsoft to build its next version of Windows on top of Linux. And you know, it actually makes some sense!

    The idea of Windows as an operating system is purely a product of the Microsoft marketing department, and not some law of nature. When Windows 1.0 appeared, it was a separate program you loaded on top of MS-DOS. Same for Windows 2.0 and 3.0 up through MS-DOS 6.22, the last standalone version of DOS sold by Microsoft. That way, they thought at the time, if Windows ever proved to be a commercial failure (this was far from certain and it is easy to claim Windows WAS a failure before 3.0), it would have been easy for Microsoft to punt back to MS-DOS.

    It was only with Windows 95 that Microsoft decided that Windows was a success, dropped the second box and integrated the products. But are they really integrated? No. DOS 7.0 was under Windows 95 and DOS 7.1 brought the FAT32 file system to Win95, not the other way around. Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux. The idea of running a windowing system atop an OS or even having competing operating systems under the same OS has been around for a long time. Back when Unix meant typing on a command line, in the PC world there were versions of DOS from vendors other than Microsoft, and in fact, some of those products are still available. IBM will still sell you a copy of PC-DOS 2000, and you can download a copy of DR-DOS 7.03 for free from DeviceLogics Inc., in Utah. Up through Windows 3.11 both these products worked as well or better under Windows than MS-DOS, and some people have claimed to have made them work under later Windows versions, too.

    The history of DR-DOS is especially interesting because it went through so many hands. This MS-DOS-compatible operating system was written at Gary Kildall's Digital Research as a better version of DOS that would be Gary's revenge against Bill Gates, only it didn't work out that way, did it? Still, DR-DOS was a better product than MS-DOS at the time.

    DR-DOS was eventually sold, along with the rest of Digital Research, to Novell, which already had its own DOS clone inside the early versions of Netware. Novell's version of DOS was noteworthy because of its Indexed TurboFAT file system, which was a response to the painfully slow performance of the Hierarchical File System built into MS-DOS 2.0. Indexed TurboFAT was a flat file system that was kept all the time in a RAM cache so that it was incredibly fast. Like all the really industrial-strength applications of the time, NetWare (like Autodesk and others) did whatever it could to get beneath MS-DOS. It was the only way to get high performance.

    Novell eventually sold DR-DOS to Caldera, which at one point renamed it OpenDOS and started giving it away. Smart move, throwing away a brand name known by millions. What DR-DOS did for Caldera was give it an inherited anti-trust claim against Microsoft because Redmond kept changing Windows to make it incompatible with DR-DOS, which -- if you do it just to be mean -- is against anti-trust law. Caldera won more than $100 million from Microsoft in an out-of-court settlement, making their day, and then DR-DOS moved on to Lineo, a Novell/Caldera partnership for embedded software, and finally to DeviceLogics, which plans an 8.0 version for later this year, again aimed primarily at embedded apps.

    Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve. As Mike Class points out, by not having to develop its own OS, Microsoft could also save money. They wouldn't need however many people are presently devoted to maintaining the underlying OS that isn't supposed to be there.

    And it wouldn't devalue Windows, precisely because Microsoft has done such a good job of making people think there isn't a DOS under there. Windows is the brand, and would remain so. And the nature of the General Public License is such that Microsoft would not be required to divulge much, if anything, about either Windows code or its applications, specifically because they would be sitting atop -- not built into - Linux.

    Apple has made a virtue of doing exactly this with MacOS-X, heralding its Mach kernel and BSD roots. Couldn't Microsoft do the same? The last I looked, Rick Rashid was still a Sr. Vice-President and head of Microsoft Research -- the same Rick Rashid who, as a professor at Carnegie-Mellon Univerisity, was responsible for Mach in the first place. No biggie.

    Then look at what this does to Microsoft's anti-trust situation. Suddenly, they aren't this overbearing monolith, but just another company pushing a windowing system and apps. True, they have a broader offering of window systems and more apps (not to mention more money) than any possible competitors -- make that all possible competitors COMBINED. But that's not illegal. The Feds would simply go away, and even the current consent decree might no longer be required.

    What this would do is level the playing field just a bit. The best windowing system and the best apps would win where they best meet the needs of users, which would vary from constituency to constituency. This wouldn't be the end of Gnome or KDE by any means, but what it would do is give 95 percent of the computers in the world a relatively standard and robust OS that could run a wide variety of windowing systems equally well. And for Microsoft, it offers that delectable prospect of selling Microsoft Office for Linux by inserting a bit of middleware to interface its apps with other windowing systems, again without having to adhere to the GPL.

    It won't happen, of course, because Microsoft will want to maintain every advantage and would see this as giving-in. It would also have a negative impact on their language business, though that's not an absolute certainty. The part I love, though, is the idea of Bill Gates showing up at LinuxWorld to kiss Linus's ring.
    And if it ever happens (the ring-kissing, I mean), don't forget Mike Class in Milwaukee, who came up with the idea in the first place. I don't know if Jesuit friars are allowed to accept big checks from corporations, but I'm sure Marquette University could always use the money.

  52. Utterly ridiculous and wistful by erroneus · · Score: 4, Insightful

    It doesn't save much even when he concludes that it wouldn't likely happen. This is mainly because the idea of Microsoft moving their windowing system over to Linux has been thought of long ago. And If not also by other people, certainly by myself.

    Frankly, I think it would sell all over the place though clearly people would insist on running X with "Microsoft Lindows" anyway... look at people running X with MacOSX.

    It's clear that Linux users need a MUCH better windowing environment, but we've been geared to X for so long that another windowing environment is unimaginable... okay maybe not unimaginable, but so far, not projected to be in wide acceptance.

    I also fear for what would happen if Microsoft got control of the Linux desktop. Instability is a "feature" I firmly believe is part of their marketting strategy. (Provide patches for a while and then stop offering them while pushing the 'next version.') We would always have problems and would never get fixed.

    However, I also see people hackign Windows for Linux by writing compatible libraries and making it free. It is happening with a great deal of stuff in the WINE project... it would just be more complete and more compatible wouldn't it?

    Anyway... it's not going to happen. MS would sooner take FreeBSD and put Windows atop of that.

    1. Re:Utterly ridiculous and wistful by Anonymous Coward · · Score: 1, Interesting

      "It's clear that Linux users need a MUCH better windowing environment, but we've been geared to X for so long..."

      The problem isn't X. Enlightenment could be arguably more beautiful than Apple's latest offerings, if you had the right talent doing the skinning. (Which E had in droves.)

      Quake 3 runs fine in X. KDE runs fine in X. Gnome runs fine in X. Blackbox runs fine in X.

      I see no reason to replace X. The real problem of X lies not with X itself, but the windowmanagers and desktop environments availible for it.

      Blackbox is sleek and ultra fast, but minimalistic. There aren't really any 'Blackbox' apps, so everything looks ugly when merged together.

      Gnome, to me, just looks ugly. I can't stand the Gtk widgets. That's just me, however.

      KDE is more pleasing to the eye as far as I'm concerned, but I dislike having to install a group of programs just to get the one program out of a 'package' that I want.

      Add in the real problems now - the fact that you need to have a variety of extranneous libraries installed if you want compatability between Gnome and KDE. The fact that most windowmanagers these days are static in the sense that they're not configurable to any great extent.

      I want a bloody windowmanager that can look like something totally different then the 'default' setting. I want something a newbie can use, yet is still suitable for an advanced user.

      I want install options, damnit! I want to tell it if I want my desktop littered with useless icons, or that I'd rather set up my damnable menus myself!

      By the Gods, I want programs I run to look like they belong on the freakin' desktop. (Microsoft can somehow do this, and we can't?)

      The above will never happen. Why? Freedom of choice. Any person can just walk up and say, "Screw this, I'm gonna use Foo toolkit instead." and the game's over.

      Variety, choice, and the like is good for some things. It's great for food. It's great for culture. It's great for plots in movies and books, and it's great for music.

      It really sucks ass for making a consolidated desktop standard, because choice is at odds with that kind of unity.

    2. Re:Utterly ridiculous and wistful by tbuskey · · Score: 1

      It's clear that Linux users need a MUCH better windowing environment, but we've been geared to X for so long that another windowing environment is unimaginable... okay maybe not unimaginable, but so far, not projected to be in wide acceptance.

      There was a stab at it with the SVGA stuff. I remember hearing some people arguing the merits of NeWS vs X. I think Display Postscript is similar to NeWS in some ways.

      As a desktop user, on one machine, the "windows" model works pretty well. I'm usually sitting in front of one machine. I only need to go to another machine for file and web serving.

      As a user at a site with lots of machines, the "windows" model fails. I run programs on various machines (various compute servers, the time card application server, the database client server, etc) and I have an xterminal at my desk. When I need more compute power IT adds another compute server or upgrades one of the existing ones.

      Windows Terminal Server and Citrix Metaframe are an interesting extension to the "windows" model. It works pretty well if you have an IT dept to support it. It's overkill for a less then (N) users for some value of N. Some applications won't run well in this environment. Some due to the terminal server itself, some to latency over a network (graphical apps like visio and where precision mouse work is needed).

      The nice thing about X is that it works pretty well as a single user "windows" type system w/o having to do anything special to extend across the network.

    3. Re:Utterly ridiculous and wistful by Alomex · · Score: 1

      The problem isn't X.

      I beg to differ. X tried to be a design that supported both light weight and full fledged clients. In the end it always needs a full fledged client, but it doesn't make full use of it, because it hung on to the illusion of light weight terminals.

    4. Re:Utterly ridiculous and wistful by swillden · · Score: 1

      X tried to be a design that supported both light weight and full fledged clients. In the end it always needs a full fledged client, but it doesn't make full use of it, because it hung on to the illusion of light weight terminals.

      You need to elaborate if you want your post to say anything meaningful. What does "client" mean? The usual X definition of the term doesn't seem to fit your statements. Do you mean "server" (i.e. the display engine and hardware)?. What do you mean by "light weight" and "full fledged"? How does X fail to make full use of a "full fledged client"?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    5. Re:Utterly ridiculous and wistful by swillden · · Score: 1

      It's clear that Linux users need a MUCH better windowing environment, but we've been geared to X for so long that another windowing environment is unimaginable

      I see this anti-X bias all the time on /., but I've yet to see a reason for it. What's wrong with X? Sure, the bottom-level API is painful, but no one uses that except toolkit authors and X server implementers. Some people think that the network capability of X is pointless, but those are people who either don't have more than one computer to manage, or don't understand the concept. If it's useless, why does Citrix exist?

      OTOH, time has shown that the notion of extensibility built into X was excellent. As new video hardware comes out, new extensions are defined and standardized to make use of it. The result is that X servers today have very high performance, and open standards, and network transparency, and allow all kinds of interesting and useful trickery such as x2x, vnc, etc.

      I think a lot of the time that people are whining about X, they're actually whining about the available window managers, not X itself. There are some valid concerns there, but if you want to have a common, high-quality GUI, it seems like it would be easier to get most everyone to adopt the One True Window Manager (whatever that is; I vote for KDE) than to replace the entire display server.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    6. Re:Utterly ridiculous and wistful by salesgeek · · Score: 1

      Sheesh... Get over the semantics a little bit. X has always had some speed issues when running graphically intense apps over the network (and most all modern, skinned apps are somewhat intense). For most applications that require a high end cpu, the Xterminal is a point of delay - that's why most workstations have mondo graphics accelerators on board. On the flip side, I like the results with X much better than Citrix because it's easy to run multiple apps from multiple X clients (or application servers) on one Xserver (Xterminal).

      I think X's big problem is the ridiculous, fixation with getting what machine is the client and the server technicall correct. It's really fun to try to explain to an executive that the super-lightweight $500 box on his desk is an X-Server and that the box he laid out $50,000 for is an X-client. They talk like Scooby-Doo when you explain it to them:

      me: This is actually the server.
      Exec: Arrrrruuu?
      me: it connects to the client in the server rack in the noc.
      Exec: hhhhhhmmmmmm?
      me: the application in this window is actually running on a client in texas.
      Exec: So where's the server again?

      --
      -- $G
    7. Re:Utterly ridiculous and wistful by swillden · · Score: 1

      Sheesh... Get over the semantics a little bit.

      The problem wasn't terminology -- I was completely prepared to mentally substitute "server" for "client", but the statements didn't make any sense either way.

      X has always had some speed issues when running graphically intense apps over the network

      So what you're saying is that moving lots of data over a network is slower than moving it over a local bus. How is this X's fault? And how does it hurt X's performance when used locally?

      For most applications that require a high end cpu, the Xterminal is a point of delay - that's why most workstations have mondo graphics accelerators on board.

      Rendering high-quality, complex graphics is a point of delay; that's why most PCs have a mondo graphics accelerator on board. The fact is, on a local machine, X imposes a tiny overhead that is unavoidable unless your application is going to write to the graphics card directly (and X actually permits certain forms of that where it makes sense, e.g. XVideo). Locally, X is just as fast as the Windows GDI interface (sometimes faster, but that's mainly because XFree86 drivers often get a little more performance tuning than their Windows counterparts). Remotely, the X interface is identical, but has the network bandwidth constraints to deal with.

      I think X's big problem is the ridiculous, fixation with getting what machine is the client and the server technicall correct.

      That's not a problem with X. If it's a problem, it's a problem with X advocates, or with geeks who think it's cool that the terms are backwards from what "most" people would think.

      And, actually, I find that people get it straight very easily if you use the term "display engine" rather than "server" and "application" rather than "client".

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    8. Re:Utterly ridiculous and wistful by Alomex · · Score: 1

      So what you're saying is that moving lots of data over a network is slower than moving it over a local bus. How is this X's fault? And how does it hurt X's performance when used locally?

      No, what we are saying is that X moves more data than it needs to, because it assumed the client (terminal) had very few computational resources and hence could not possibly be asked to render, say, postcript.

    9. Re:Utterly ridiculous and wistful by swillden · · Score: 1

      X moves more data than it needs to, because it assumed the client (terminal) had very few computational resources and hence could not possibly be asked to render, say, postcript.

      That makes sense. Thanks for the clarification. A higher-level protocol like Display Postscript/PDF would improve performance for applications that draw. Makes me wish I would have fiddled a little more with remote displays back when I was using NeXT boxes. Wouldn't help with running, say, the Gimp remotely, but it would be a significant improvement for most apps.

      The interesting thing about this discussion is that *most* of the comments about how we need a replacement for X point to the network transparency as needless baggage. I've yet to hear a good argument from that side, though I keep asking. You're looking at the network performance as an important feature (which it is), and I agree that X could be improved upon significantly in that regard.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    10. Re:Utterly ridiculous and wistful by salesgeek · · Score: 1
      Thanks for the clarification. A higher-level protocol like Display Postscript/PDF would improve performance for applications that draw. Makes me wish I would have fiddled a little more with remote displays back when I was using NeXT boxes.

      NeXT had a great idea with display postscript... I still have yet to see anything really come close when it came to desktop publishing. I'd think for a more modern system though that 3d would be more the way to go...
      --
      -- $G
    11. Re:Utterly ridiculous and wistful by swillden · · Score: 1

      NeXT had a great idea with display postscript... I still have yet to see anything really come close when it came to desktop publishing.

      Well, OSX has gone with display PDF, which is essentially just postscript, but with some extra features including optional LZW compression, which seems like a very good idea for remote displays. OSX is seriously making me think about buying a Mac...

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  53. But then... by Loonacy · · Score: 3, Funny

    MicroSoft could say "Hey, look at how often Linux crashes now!"

  54. In Soviet Russia... by -1bynextweek · · Score: 0, Offtopic

    Linux is built on top of Windows!!!

  55. The same mistake by The+Bungi · · Score: 1
    ... over and over and over.

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux

    Windows 95 was not an OS because it sat atop a 16-bit protected mode bootloader (I can nitpick that to heck but still). Ditto Win 98 and ME. But Windows NT/2000/XP are as much an OS as BeOS, Linux, QNX and BSD are. The fact that they have a CLI doesn't make them any less an operating system.

    And a shell doesn't an OS make. If anything, I'd argue for Microsoft to make it easier to write a shell replacement. I've never found one that is as as stable and complete as the default, and writing shells for Windows is still a bit of a black art, unlike Linux which completely separates the kernel from the windowing system and doesn't have a shell by itself.

    Cringely writes good stuff, but this time he's planted his foot firmly in his mouth.

    1. Re:The same mistake by Anonymous Coward · · Score: 0

      Take a look at litestep.

      You can trim down your desktop down as I have done: the only thing I have visible is the system tray (transparent except for the icons) and that is always on the bottom of windows.

      I then use Litestep to allow for window/placement and resizing as is done in Enlightenment and for a set of keyboard shortcuts to allow for full window management.

    2. Re:The same mistake by Ashran · · Score: 1

      > Windows 95 was not an OS because it sat atop a 16-bit protected mode bootloader
      Hmm? Lets say I write a 16-bit protected mode bootloader for linux (lilo is a bootloader too) does that mean that linux wouldnt be an OS anymore?

      The flawed part in W9x was the sharing of the first meg of memory with every other application (think DLL's).
      This saved a meg of ram and brought W9x down to (i think) 5 megs min req.

      --

      Before you email me, remember: "There is no god!"
    3. Re:The same mistake by Anonymous Coward · · Score: 0

      Windows 95 was not an OS because it sat atop a 16-bit protected mode bootloader (I can nitpick that to heck but still).

      + Manages Memory (check)
      + Manages hardware (check)
      + Provides an API (check)
      + Provides a user interface (check)

      Sorry. Windows 9x might have been the biggest fucking DOS program ever written, but it's still an Operating System. So is Windows 3.1.

  56. WTF by nodrip · · Score: 1

    wtf are you people smoking?

    p.s. can i buy some?

    --


    -- "The best way to predict the future is to invent it."
  57. Yay, More Cringely by blacklite001 · · Score: 1

    Apparently it's necessary for absolutely everything written by this guy to have an article on Slashdot. Wonderful. Even though half of us are trolls, I think the average slashdot reader is at least as smart as he is. Oh well. Can't have useful things on Slashdot *all* the time.

  58. "Back when Unix meant typing on a command line..." by su007 · · Score: 1

    "Back when Unix meant typing on a command line..." I'm sorry, when did this change? Nobody informed me I don't have to use the command line. Can someone help me figure out how to recompile apache with out it?

  59. Displaying his ignorance by rufusdufus · · Score: 4, Insightful

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    The command processor has nothing to do with the operating system. This statement displays Mr Cringely's deep ignorance of operating sytems.

    Having worked on development of MSDOS,Window 95 and Windows NT, I can state authoratatively that DOS is not the foundation of windows XP (which is really NT with lipstick). Anybody who knows anything about OS's knows this anyway.

    1. Re:Displaying his ignorance by LostCluster · · Score: 3, Insightful

      It's amazing how many users will think that just because all of the elements visible on the screen are exactly the same, that nothing has changed when they installed a new OS.

      There were worlds of diffence under the hood of Windows ME and Windows 2000... yet they looked almost identical to the common user's eyes.

    2. Re:Displaying his ignorance by Sgs-Cruz · · Score: 1

      I don't really think that's all that 'amazing'. If you were to buy a new car that looked exactly the same, except that the engine was replaced with an incredibly better one, would you notice? Of course you would. Would you notice if you only ever drove the car at 50 km/h for 20 minutes a day? Probably not. You can see where I'm getting with this analogy.

      --

      Karma: pi (Mostly due to circular reasoning in posts).

    3. Re:Displaying his ignorance by Anonymous Coward · · Score: 0

      Yes I get it! Slashdot users drive like women.. Right??

    4. Re:Displaying his ignorance by Unregistered · · Score: 1

      windows XP (which is really NT with lipstick)

      And Xp has some pretty ugly lipstick

    5. Re:Displaying his ignorance by Tyreth · · Score: 1

      I was surprised when I saw Cringely had written this. I'd always assumed he knew more than this, since he's such a well known public figure.

      When I read that I guessed that he must have known something I didn't, but the way he wrote it sounded like "because it looks like the old command prompt, it must be the same".

      How could he make such a large oversight?

    6. Re:Displaying his ignorance by Francis+Avila · · Score: 2, Insightful

      Um, lets look at that quote a bit more closely...

      Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

      He says, somewhere there's a disk operating system, not "DOS". Is this false? Subsitute "disk operating system" for something like "kernel", and I think the jargon will be more clear to you.
      His intention is to counter the MS Market-speak that somehow those 'purty' windows you see is itself the operating system. Which is of course untrue, as you yourself say later...

      The command processor has nothing to do with the operating system.
      Exactly. There's a disk operating system hiding under that command processor, be it a GUI or a command line.

      Also take his statement in the context of the whole article, where it's clear that he understands this distinction. Why would he then act as if he didn't?

      I think you misread "a disk operating system" to == "{MS,DR}DOS"....

    7. Re:Displaying his ignorance by Klingensor · · Score: 1

      Which is really OS/2 with perversions.

    8. Re:Displaying his ignorance by Malor · · Score: 1

      I was also really surprised by this. He was right about all the earlier Windows versions, but he doesn't appear to understand that the whole POINT of NT was that "there is no DOS"; Windows XP is NT 6.0. (Win2k was 5.0).

      He makes another error, talking about MS-DOS 2.0 and its Hierarchical Filing System. As far as I know, HFS was Mac-only, wasn't it? DOS 2.0 used just regular old FAT, as far as I know. I don't think that changed until Windows 98 and FAT32. OS/2 used HPFS, and NT used NTFS. (they could both use FAT, and NT also spoke HPFS, but those were their primary filesystems.)

      He's way, way off base in this article. Usually Cringely is great. He sure blew it in this one.

    9. Re:Displaying his ignorance by Accipiter · · Score: 0, Flamebait

      windows XP (which is really NT with lipstick)

      That's a good analogy, but it'd be a bit more accurate to say "whore makeup".

      --

      -- Give him Head? Be a Beacon?
      (If you can't figure out how to E-Mail me, Don't. :P)

    10. Re:Displaying his ignorance by hyeh · · Score: 1

      Actually, Windows XP is NT 5.1.

      If you go to a NT command prompt and type ver, it returns "Microsoft Windows XP [Version 5.1.2600]".

    11. Re:Displaying his ignorance by Tim+Browse · · Score: 1
      He makes another error, talking about MS-DOS 2.0 and its Hierarchical Filing System. As far as I know, HFS was Mac-only, wasn't it?

      I don't think he really means 'HFS' per se, even though he capitalised it for some reason. He's just referring to the fact that subdirectories were available in DOS 2.0, so it was a hierarchical filing system. Which is true enough.

      Similarly, you could say MacOS had a Disk Operating System (the File Manager), but that doesn't mean MacOS had DOS under the hood.

      Tim

    12. Re:Displaying his ignorance by rufusdufus · · Score: 1

      Once other detail, if you ever come back and read this comment, is that FAT32 was first in Windows 95 OSR 2.

  60. They could, but won't (and probably shouldn't) by foonf · · Score: 4, Informative

    Although some of Cringely's comments about the DOS basis of Windows are off-base with regards to modern NT-kernel based versions of windows (the C:\ prompt is there because it has a compatibility layer) the idea that most of what we think of as "Windows" could be ported to a Linux or Unix base is basically correct. Just imagine an officially-sanctioned WINE with its own GUI system and configuration tools...it is not that far from reality.

    But the kernel is neither Windows' biggest problem, nor Linux's greatest asset. By all accounts, the Windows NT kernel is (or at least started out as) a very clean, modular microkernel system. It was built with a POSIX compatibility layer, and actually can host a traditional Unix userspace (and does, if you install the MS "Unix Services" package). On the other hand, Linux is a very straightforward, unexceptional reimplementation of a standard, monolithic Unix kernel, which has become very popular more or less because it works, it is free, and it was there when people needed it. Its novelty is that it allowed for the first complete Free Unix-like system (while *BSD was still in legal limbo). Microsoft could take that kernel, and modify it to run Windows, and neither they, nor we (Linux users), would gain anything...Microsoft would get an operating system more or less like what they have now, except with a pesky kernel under a free-software license, and we would get another version of Windows, which might, with the installation of an X11 server and a raft of libraries, be able to run Linux software, not that anyone would want to.

    If Microsoft tries to "embrace and extend" Unix, they probably won't use Linux, or BSD for that matter. Unlike Apple several years ago, they already have a modern kernel. According to another recent Slashdot story, they are already trying to build a new shell environment based on the existing "Unix services" package, and probably running under the .NET framework. This strategy makes far more sense, both considering the existing strengths of Windows, and Microsoft's emnity toward open-source software.

    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  61. Cringely by Wyatt+Earp · · Score: 1

    I'm sorry, but has lost it.

    Actually he stopped making any sort of sense along time ago, like Dvorak, Katz, and most of the Salon crew he stopped making sense or being original sometime between the 2000 election and the planes smashing into buildings.

    With the exception of his stuff about long range 802.11b, Cringely just doesn't matter. Its about the same as looking to Wired for insight these days.

    "Apple has made a virtue of doing exactly this with MacOS-X, heralding its Mach kernel and BSD roots. Couldn't Microsoft do the same? The last I looked, Rick Rashid was still a Sr. Vice-President and head of Microsoft Research -- the same Rick Rashid who, as a professor at Carnegie-Mellon Univerisity, was responsible for Mach in the first place. No biggie."

    No biggie? It took Apple from June of 1997 to August of 2001 to move about 75% of it's OS functionality from Classic to X, yea MS is bigger with more coders and more money, but it's also a much bigger project with many times more compatability issues to have to sort out. It'd be a biggie.

    I read the piece. It's about a pipe-dream and J.X.C's knowledge of DOS history. It's pointless.

    1. Re:Cringely by lottaletters · · Score: 1
      How about this from his site http://www.pbs.org/cringely/bobsworld.html

      "When it comes to information technology, I know what I am talking about. Twenty years in and around the PC business have earned me wisdom, if not wealth"

      What was he doing for 20 years. I know: He was the "COPY GUY... MAKIN COPIES.... TALKIN TO THE SMART PEOPLE..." When it comes to the PC business, he has a better chance of breaking out of a wet bag than breaking a real story. short: Cringly bad writer, bad article, we type away to get our frustrations out.
  62. Cringley needs to lay off the crack by CableModemSniper · · Score: 1

    I love how he claims that fact that you can get a command prompt in XP means dos must be underneath still. Call me crazy but I thought the NT series emulated dos for backwards compatibilty. I didn't think NT was just hacked on to DOS like Win9x, 3.11 , etc. were. He seems to think if someone tried REALLY hard they could still get XP to run on top of DR-DOS instead of...well instead of the imaginary DOS that isn't there now. Then there's the whole micro vs monolithic kernel thing. I hope no one reads this article and think, "Yeah! Why don't they?" There's a reason Apple had to provide the classic environment after they released OS X, and it ain't because some people prefer the old widget style.

    --
    Why not fork?
  63. This is just silly by galvanash · · Score: 1

    I usually like Cringly's pieces, they tend to be at least entertaining. But this one is just stupid... He was doing fine until he makes the ridiculous claim that XP is not an operating system. Im sorry, but that is just demonstratably false. Sure, 3.1, 95, etc. where basically just DOS shells, but NT, 2000, and XP certainly are NOT and have just as much a right to be called an OS as any Unix does. While you can make the case that the GUI can be seperated from the underlying OS, that does not mean the underlying OS is MS-DOS. The kernel of NT/2K/XP is VASTLY superior to DOS. I would even venture to say it somewhat superior to Linux (at least as far as raw performance/scalability goes). I like Linux, but facts are facts. Efficient threading, an excellent VM, overlapped I/O, memory-mapped files, excellent serialization primitives, etc... The "core" of XP is fairly advanced. Linux has most of the same features, but the spit and polish isnt there yet. Putting the Windows GUI on top of Linux might make a nice Linux Desktop, but it would definitely be a step backwards for Windows. Go ahead, flame away :)

    --
    - sigs are stupid
    1. Re:This is just silly by Ziviyr · · Score: 2, Interesting

      Hitting "MS-DOS Prompt" and getting bash would be sweet though. :-)

      --

      Someone set us up the bomb, so shine we are!
    2. Re:This is just silly by Cyn · · Score: 1

      I just finished implementing this TODAY - enjoy: http://www.cygwin.com/

      --
      cyn, free software and *nix operating systems enthusiast.
  64. I like this guy, but... by fireboy1919 · · Score: 4, Funny

    specifically, what a premise.

    Let me start thinking that way.

    You can get to a root prompt in Linux. You can do so in BSD as well. Solaris, also.

    Apparently, these are all actually the same thing - they're all running Linux, underneath it all. And because it's that simple, it's just marketing - since the product is free - Solaris is just hyping it up so that people will use CDE.

    Lets go further. Also, you can find a brain inside every animal. Cats have brains.

    So, deep down, we're all cats, right*?

    *Really old, bad movie quote

    --
    Mod me down and I will become more powerful than you can possibly imagine!
    1. Re:I like this guy, but... by Ashran · · Score: 1

      Why oh why did my mod points expire a few hours ago!
      This made my day ;)

      --

      Before you email me, remember: "There is no god!"
    2. Re:I like this guy, but... by deadsaijinx* · · Score: 1

      bad analogy... if we all had cat brains inside our human body, then we'd all be cats. oh, well. It's not like windows will ever run ontop of the linux kernel. what a silly notion.

      --
      YOU SUCK BALLS!
    3. Re:I like this guy, but... by Anonymous Coward · · Score: 0

      bad analogy... if we all had cat brains inside our human body, then we'd all be cats. oh, well. It's not like windows will ever run ontop of the linux kernel. what a silly notion.

      No surely we'd be a pussy but without the woman part?

    4. Re:I like this guy, but... by Anonymous Coward · · Score: 0

      fyi man, BSD and Solaris are both different from linux. like linux, they are both flavors of unix, but BSD was developed at berkley a long, long time ago as a proprietary version of unix and solaris is just Sun's version. BSD is now an open-source OS. i'm not sure about solaris... i'm just a mechanical engineer =(

    5. Re:I like this guy, but... by Anonymous Coward · · Score: 0

      fyi man you are an idiot and it's a damned shame they don't make mechanical engineers take a logic class.

    6. Re:I like this guy, but... by Anonymous Coward · · Score: 0
      bad analogy... if we all had cat brains inside our human body, then we'd all be cats. oh, well. It's not like windows will ever run ontop of the linux kernel. what a silly notion.


      Good analogy, bad logic. Which I do believe was the parents point...

      As for the linux kernel obviously not... but the BSD kernel is always a possibility.. it's been done before ;)
  65. Microsoft using Linux as a base OS? What's next? by Simeon2000 · · Score: 1

    Venkman: This industrty is about to face a disaster of biblical proportions.
    Linus: What do you mean, "biblical?"
    Ray: We mean real wrath-of-God type stuff. Plagues, darkness--
    Winston: Lotus rising from the grave!
    Egon: Forty years of uptime! Competition, open source--
    Venkman: Riots in Redmond, Ballmer and Ellison living together, mass hysteria!
    --

    --
    warn "Just Another Perl User" if $anyone_cares;
  66. Extremely common by jaaron · · Score: 1

    I don't know much about the topic, but doesn't the liscencing disallow you from selling it for money? Or is it just a common misconception?

    An extremely common misconception. See the GNU GPL FAQ:

    Does the GPL allow me to sell copies of the program for money?

    Yes, the GPL allows everyone to do this. The right to sell copies is part of the definition of free software. Except in one special situation, there is no limit on what price you can charge. (The one exception is the required written offer to provide source code that must accompany binary-only release.)

    --
    Who said Freedom was Fair?
  67. How unrealistic by The+Analog+Kid · · Score: 1

    If they did that people would abandon Windows all together. Not to mention that Microsoft would go down the tubes. What of Pallidium well that would be gone, because no one would use their Distrobution and its not like they can get the U.S. to force it upon us because not every distrobution operates in the United States and they don't have to listen. Also hackers will just remove the code. Its an optimistic point but an unrealistic one.

  68. MS vested interest in "OS" portions of Windows by MMHere · · Score: 1

    MS has a vested interest in the "OS" portions of Windows, now that they've finally moved their latest versions (Win2K, WinXP) over to something that can actually be considered a "real kernel" (The somewhat stable NT-based underpinnings).

    They also have strong coupling between this OS portion, and the desktop apps that everyone is forced to use (Excel, Word, Outlook, etc.) in ordeer to be compatible with everyone else. (By "everyone," I simply mean the large majority of users who use Windows on a PC, for what ever reason they do so.)

    This coupling / tight integration is a main technical component of MS's business strategy, which has allowed them to achieve their monopoly position.

    Why would they give this up?

  69. What an idiot by EvilNTUser · · Score: 5, Insightful

    Are we really supposed to take someone who says something like this seriously:

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    Clearly the NT kernel is just a big lie, just like NASA never went to the moon. Thank you, Cringely, you have shown me the light!

    And what the hell does he mean by "a disk operating system is hiding there"?? Please, someone, give him a non-disk operating system and see how far he gets after all his drives disappear.

    Besides, it's not the NT kernel that's the problem, it's all the crap MS has put around it.

    --
    My Sig: SEGV
    1. Re:What an idiot by Dixie_Flatline · · Score: 1

      Actually, it may very well be the kernel. I'm out of date on my Windows system design, but one of the things that they used to do was put GUI code into the kernel to increase performance. It's largely agreed that that's a pretty stupid move. If they're still doing that, instability in your graphics subsystem could mean kernel problems.

      I'd hope that they've moved away from that model, though. If they HAVE, in a final analysis, Cringely is SOMEWHAT right. The system has a kernel that handles drivers and IO and things, and tacked onto it is a GUI system that interoperates very closely. The NT kernel may not be DOS, but it's still the OS proper.

    2. Re:What an idiot by EvilNTUser · · Score: 1

      IIRC, you are correct. MS did put graphics stuff in the kernel, which does sacrifice stability for performance. But to be honest, XP as a desktop OS doesn't crash all that much anymore (although I admit it might vary between systems).

      The biggest problem for me right now (and I use XP) is that I simply can't get it to do what I want it to do. Cygwin is a good aid, but MS could really help me a lot by making the base UI less targeted to novices. Of course, that's not going to happen, because novices need to use computers too, but I'm really excited about that rumored new MS console.

      And no, Cringely isn't somewhat right. He implied that XP has a DOS-based kernel. That's just wrong, even if most kernels share some design characteristics.

      --
      My Sig: SEGV
    3. Re:What an idiot by Tim+Browse · · Score: 1
      IIRC, you are correct. MS did put graphics stuff in the kernel, which does sacrifice stability for performance.

      Yep, they moved GDI 'into' the kernel with Daytona (NT3.51), IIRC. Although in some respects you could say GDI isn't really part of the kernel, it just runs in ring 0 mode. But then running in that mode is a good definition of what the kernel is, so it's spliting hairs, really.

      But to be honest, XP as a desktop OS doesn't crash all that much anymore (although I admit it might vary between systems).

      Yes, I don't think GDI crashing is a big stability problem for Windows. I've only ever encountered one repeatable system crash that was attributable to GDI (the bezier drawing routines would stiff the entire OS/UI if you gave them a particular path to draw), but it's usually down to device drivers, in my experience. I've seen plenty of BSODs on NTs over the years that say "nv4disp.sys caused an IRQL_LESS_THAN_OR_EQUAL" or similar.

      I'm talking about real, hard OS crashes here, not the "Why isn't it working properly? Oh well, maybe time to reboot..." which is kind of a crash too :)

      By far the most common of those on NT/XP seems to be apps/services that don't cope with networking problems well, and tend to just hang.

      Tim

    4. Re:What an idiot by Dixie_Flatline · · Score: 1

      My biggest problem is that, as a developer, the development environment is unreasonably taxing on my machine. Every day, I have at least a cuople times where Dev.NET won't even scroll my code. A dual athlon 1800+, and scrolling code is somehow a chore. Multitasking OS my ass. :)

      Anyway, yes, Cringely is entirely wrong with the DOS based part of his argument, though he may be right in saying that Windows can be described as a Windowing system on top of a kernel. Either way, it doesn't much matter. His idea is one that would never get off the ground. Admitting defeat like that would slaughter them.

    5. Re:What an idiot by TummyX · · Score: 1


      he may be right in saying that Windows can be described as a Windowing system on top of a kernel


      The APIs define windows than the windowing system.

  70. Interesting idea, but the article is flawed by Anonymous Coward · · Score: 0

    This would be an interesting idea, but there are a number of factual errors in his article.

    1) Windows XP is not based on DOS. XP is the latest incarnation of NT, which is not based on DOS. Basing a Win9x varient on Linux is an interesting concept, but Windows was so horribly tied to DOS that it would make heavy use of undocumented DOS data structures.

    2) The HFS is a Macintosh file system and has nothing to do with DOS 2.0.

    3) Windows is far more than a windowing system he suggested. It also added protected mode preemptive multitasking and virtual memory, device independence, and all kinds of other things that DOS never had. Suggesting that KDE is remotely similar to Windows is completely wrong.

    4) Claiming that Linux is better, faster, stronger than anything under XP. This is total FUD. People's bias against Windows and its instability may have been rightfully justified under Win9x, but the NT line has been stable for me for years.

    There are a number of other errors that have me question the article. Its an interesting wish, but I'd rather see Windows go Open Source, or see Microsoft apps ported to Linux before I'd like Windows to be "ported" to Linux.

  71. one little problem by Anonymous Coward · · Score: 0

    There is no money in free software. Microsoft has shareholders that they need to answer to. If they aren't producing a profit, then the shareholders will get angry.

    It WOULD be smart for them to move into the Linux market though, as they will sell their office products. The Linux versions wouldn't be as complete as the Windows/Mac versions though, because there isn't the framework to tie into. I'm sure they'd still sell a lot of copies though.

  72. garbage in, garbage out... by nuckin+futs · · Score: 1

    even if MS decides to put the Windows GUI on top of Linux, they will still find a way to make it crash.
    It's all about the quality and skill of programmers/coders.

    1. Re:garbage in, garbage out... by Anonymous Coward · · Score: 0

      "even if MS decides to put the Windows GUI on top of Linux, they will still find a way to make it crash."

      The Xfree developers beat them to that. Not a week goes by that X11 doesn't go down on my (usually bringing the whole system with it, if only because it locks up my keyboard)

  73. New For 2003, Microsoft Linux? by NewtonsLaw · · Score: 1

    About a week ago in my daily Interent column I predicted that Microsoft would launch its own flavor of Linux sometime in the next 18 months.

    I still think it's a very real possibility for the reasons I listed.

    1. Re:New For 2003, Microsoft Linux? by praxim · · Score: 1

      People call this a crazy idea sometimes, but I think it makes sense from a marketing point of view. If they were feeling daring, they could make a Linux distro.

      And they could make it the worst Linux distribution ever. Nothing would work right. The stock kernel would be utter crap. Everything would be configured to maximize vulnerability and minimize performance. And it'd all be intentional.

      With Microsoft's level of brand recognition, they could make Linux seem like it was their own idea which never quite took off- sort of like Bob 2. Most people in the mainstream don't know what Linux is, or they've just vaguely heard of it, so this isn't far-fetched. Of course, I really don't think MS wants to destroy their karma like that, but it's an interesting idea...

  74. XP *IS* NT! by keith_nt4 · · Score: 0, Redundant

    This is driving me nuts. WINDOWS XP IS BASED ON THE NT KERNAL!! Windows 2000 is NT 5.0, XP is Windows NT 5.1! Got it?! The author is so STUPID! It uses NTFS, it has the 'nt boot loader', it has a file called 'ntloader' in the system directory (or the root). And if that's not enough evidence just look at it. IT'S WINDOWS 2000 WITH A COUPLE CHANGES HERE THERE. Damn ignorant people. It's not like it's a big secret. XP is *NOT* based in any way shape or form on MS-DOS or any other DOS. It is totally and completely a derivative of NT. Why doesn't anyone know this? Not trying to be inflammatory, this just drives me crazy.

    --
    "UNIX is very simple, it just needs a genius to understand its simplicity." -Dennis Ritchie
  75. What a thoroughly stupid article by I+Am+The+Owl · · Score: 0, Flamebait

    I was hoping that a respected institution such as PBS would be able to come up with a more competent technology columnist than Robert X. Cringley, but unfortunately, this has not been the case. There's no need to even read the article - the main proposal is so ludicrous and demonstrative of a fundamental ignorance of software as to be completely lacking credibility.

    I'm surprised that even Slashdot deigned to post this; it is such utter drivel as to rival and perhaps even surpass the ineptitude of the editors here who, for all their spelling errors and unabashed sensationalism, at least tend to get their technical facts right the first time.

    --

    --sdem
  76. Seriously. by Anonymous Coward · · Score: 0

    This guy should get a computer degree, learn a little bit about computer science and rethink his article. It's more than obvious that he doesnt have a clue about what he is talking.

  77. Microsoft could be a lot of things by Anonymous Coward · · Score: 0

    But they'll always be a reptile underneath. Expect them to experiment with all sorts of outward appearances, as all companies do. Apple built upon BSD. Did that make them a more ethical company at the core? Last I heard they'd turned on the "communities" that had previously been considered part of the big happy apple family.

    Don't expect any better from Microsoft. Anything they do, is calculated to turn a profit. Nothing wrong with that, unless you happen to be one of those who recieve a cease and desist because your community is no longer considered an asset!

    Reptiles people. A corporation is not a human being. It has no understanding of warmth, trust, or any sense of morals you or I are familiar with. There are grave psychological descriptions for real human beings who act like corporations. Anti social, psychopath, borderline personality disorder. Let the corps make widgets or whatever they do. But when they come at you talking like they want to be your buddy, the alarm bells should be going off in your head because /they are not ethical creatures/.

    1. Re:Microsoft could be a lot of things by Squidgee · · Score: 2, Insightful
      >Anything they do, is calculated to turn a profit

      So is anything ANY company does; even your beloved RedHat, or SuSe. The goal of a company is to make a profit. Those cease and desist letters are to protect that; and they have every legal/moral right to protect their own property. What don't the majority of Linux users get about this?

      *Sigh*. Once Linux users see that a business needs to make money, Linux will be viable on the desktop. Until then, none of them will buy Linux often enough to support the business until they gain the desktop. See the Mandrake story currently on the front page for more info on this topic.

  78. Cringly is poorly informed by ShooterNeo · · Score: 4, Informative

    Cringly is not very well informed in his article. He assumes Windows XP/2k ect are still built on top of DOS. Actually, if he'd read Showstoppers he'd know that the NT kernal was written from scratch, by a group of developers from Digital Equipment Co who set up essentially an independent shop within microsoft to make it. This is why NT is far more stable than earlier versions. The NT kernal is very similar to Unix in how it operates, and essentially is just as good. Also, if he'd read the book he'd know that the DOS command prompt is done via emulation, as well as legacy program support. The core of the system remains NT even when the emulator is running. Anyone who's actually used XP or 2k would find that the vast majority of problems are related to the underlying hardware drivers (this is the ONLY reason why Unix is more stable on some systems, because people building Unix servers use very solid hardware) or to the overlying windowing interface.

    1. Re:Cringly is poorly informed by gmhowell · · Score: 1

      Actually, NT was based on VMS moreso than Unix. What that means, I don't know, exactly, but prior to coming up with NT, the team had done extensive work on VMS.

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    2. Re:Cringly is poorly informed by Stardate · · Score: 1
      It is NOT as stable, but it is good enough. Linux and Unix servers stay up for years, Windows servers DO NOT. Weird things start happening, especially with the user interface, things which a logon/logoff do not fix. It also requires reboots for updating/patching system components that Linux/Unix does not require rebooting to update.

      Only recently I read an article from Microsoft engineers talking about how, in Windows Server 2003, they are improving uptime and reliablility, and seeing "crazy uptimes now, a couple of months!"

      But it's okay, they need to concentrate more on fixing Explorer (all those great new 'features' in XP are buggybuggybuggy) to make it more stable, not moving it to a new kernel.

      --
      "... I declare our city to be a free and independent state to be named Tri-Insula!" --Fernando Wood, Mayor of NYC 1861
    3. Re:Cringly is poorly informed by tommyServ0 · · Score: 1

      He assumes Windows XP/2k ect are still built on top of DOS.

      No, Cringely's exact words were:

      Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

      He's not saying it's built on top of DOS. He's saying it's built on top of an underlying disk operating system. It isn't DOS, but an operating system responsible for handling system calls and what have you. The C: prompt is just a low power shell that helps you interact with the underlying Operating System. The GUI doesn't need to be running at the same time as the Operating System. I guarantee explorer.exe is not running when you boot to the C: prompt.

      Microsoft has duped people into confusing the clickey-click cartoon world of Windows is the actual Operating System. It's not. It's a windowing environment. The operating system is underneath--it handles all the system calls.

      Cringely is saying replace the underneath part with Linux. Not the clickey-click. The underneath. You just change some #include's in gui.c, tweak a few macros, and it should be possible. Not easy, but possible. It won't happen, but it's fun to think about the possibilities, isn't it?

      --

      Consider the daffodil. And while you're doing that, I'll be over here, looking through your stuff.
    4. Re:Cringly is poorly informed by powerlinekid · · Score: 1

      Close but still somewhat incorrect on two points.

      NT was not written from scratch. NT was what Microsoft took from the OS/2 collaboration with IBM. IBM went on to future development of OS/2 and Microsoft took what they had rights to and developed NT (new technology).

      Second is that NT is not really similiar to Unix. Its similiar to VMS which makes sende since the guys from DEC had done VMS.

      Finally I don't think its emulation which does the command-line. IIRC the command-line is also rewritten from scratch but is just an application that mimics an old MS-DOS shell. Try to run any old dos game in the shell, you'll get an error like "This program can only run in MS-DOS" or similiar. If it was infact an emulator then it should have no problem running those programs. As for legacy applications, that probably has more to do with keeping the dlls for older apis around than any sort of emulation.
      However Cringly definitly needed to do some fact checking with this article (I read it a few days ago on OSNews).

      --

      can't sleep slashdot will eat me
    5. Re:Cringly is poorly informed by glenebob · · Score: 1

      "a disk operating system" is hiding there in Linux as well. He is trying to differentiate between Windows and Linux. Why would he cite a similarity to support Linux superiority?

      I think he really did mean DOS, as in MS-DOS, otherwise that statement would have been counter productive.

    6. Re:Cringly is poorly informed by Osty · · Score: 1

      NT was not written from scratch. NT was what Microsoft took from the OS/2 collaboration with IBM. IBM went on to future development of OS/2 and Microsoft took what they had rights to and developed NT (new technology).

      Yes, NT took some technology from the OS/2 collaboration (NTFS is the advancement of OS/2's HPFS), but NT as an OS and kernel was not based on OS/2. If it were, there would have been no reason for an OS/2 compatibility layer (just like the win16 compat layer and POSIX compat layer). In fact, even Win32 could be seen as a compat layer on top of the NT kernel, with the kernel interface being largely undocumented (by Microsoft, anyway).



      Finally I don't think its emulation which does the command-line. IIRC the command-line is also rewritten from scratch but is just an application that mimics an old MS-DOS shell. Try to run any old dos game in the shell, you'll get an error like "This program can only run in MS-DOS" or similiar. If it was infact an emulator then it should have no problem running those programs. As for legacy applications, that probably has more to do with keeping the dlls for older apis around than any sort of emulation.
      However Cringly definitly needed to do some fact checking with this article (I read it a few days ago on OSNews).

      cmd.exe is the app you're referring to, and it's as much an "emulator" as bash is an "emulator" of the original Bourne shell. cmd.exe is NT's console shell, and extends the original DOS batch programming language. It's not COMMAND.COM, but is functionally equivalent for 95% of the uses out there. However, the window that cmd.exe opens is a special window in Win32. Other apps can open so-called "console" windows, and there is a whole set of APIs dedicated to programming with console windows. cmd.exe just provides the interactive and scriptable shell inside the window. And maybe I'm just special, but I seem to be able to run many old DOS games out there under cmd.exe. Sound doesn't usually work, but there are solutions for that, too.

    7. Re:Cringly is poorly informed by Some+Dumbass... · · Score: 1

      "a disk operating system" is hiding there in Linux as well. He is trying to differentiate between Windows and Linux. Why would he cite a similarity to support Linux superiority?

      He didn't. He cited this to point out that you could replace that there was still a separate "disk operating system" layer which could be removed and replaced with Linux. The point is that _despite_ the fact that there is no longer DOS under Windows, there's still a non-GUI layer.

    8. Re:Cringly is poorly informed by VoidEngineer · · Score: 1

      This is why NT is far more stable than earlier versions. The NT kernal is very similar to Unix in how it operates, and essentially is just as good.

      Agreed. As an MCSE (Windows NT), I've supported all the flavors of Windows around (and some that were never officially released, via the TechNet program). NT works like Unix. In fact, the Chicago Board of Trade, nuclear power plants, and airports often use NT for mission critical systems.

      Also, if he'd read the book he'd know that the DOS command prompt is done via emulation, as well as legacy program support. The core of the system remains NT even when the emulator is running.

      Um. Not exactly 100% true, but not wrong either. As per the architecture, the Win16 APIs are just subsystems of the NT kernel environment, just the same as the POSIX and OS2 support. Now, I suppose one could describe a subsystem as an emulation program, if you wanted to, but methinks they are slightly different. Anyhow, the Win16, POSIX, and OS2 subsystems are actually considered supported, natively, as I understand. There is chunking involved with the Win16 APIs (padding of a 16bit vector with 16 '0' bits, in order to make it a 32bit vector), which is probably what you are describing as 'emulation.' It's mostly semantics, however.

      Sorry for splitting hairs. Not trying to flame or argue.

    9. Re:Cringly is poorly informed by ShooterNeo · · Score: 2, Informative

      Yes, I forgot that it was VMS the DEC guys were working on. I do know that the client/server architecture it uses (explorer and most NT services are "clients" of an underlying kernal, so if they crash the underlying system keeps running) is similar to Unix. I suspect that the NT kernel might even be better written than Linux (face it, it was written by experienced developers from top schools and there were dozens of em, with clear design goals set by their boss vs. a hacker who just wanted to write his own Unix clone). I don't have access to the code to do a comparion, obviously, but it wouldn't surprise me. From what I read in Showstoppers, 16 bit APP support, while done semi-natively, is done with a translation system that translates the API calls. It is basically emulation, and the developers despaired for a while when it seemed like they were training the OS to run certain progrms (not a general case emulator like they wanted). That is also how XP runs DOS stuff. Believe it or not, Microsoft has known their OSes sucked for a long time, and spent over a hundred million paying NT develepors to correct this (just for the initial development of 1.0. I suspect the tab is over a billion now).

      Their main problem now is that they feel they have to add too many features to keep selling new versions, which greatly increases complexity. This is why their software gets more and more bloated, and why new versions still have many bugs. Their other problem is they basically own their target markets, and to grow any further have to try other sectors, which may not even be profitable ideas. For instance, making web browsers may never be profitable for Microsoft.

      As for using NT in mission critical systems...well, depends on HOW mission critical. While it might be fine for archiving, say, medical data its not good enough to control the electronics of a radiation machine. Nor is it good enough for regulating the cooling system of a nuclear power plant, though it might be fine for running the visitor log at the guard shack. And while it might be fine for the interactive TV system on an airliner, its not for the fly by wire firmware. For this stuff NO OS is acceptable, it has to be written very carefully from scratch, with the software kept as simple as possible. Instead of using multiple threads, the developers will often break the different tasks into different cpus (so that way if one crashes, the other physical chips will keep running). For extreme cases (a rocket?) there will be 3 or more computer systems, each completely independent and running firmware written by completely isolated developers (often in different countries) from a central spec. If one of the computers disagrees, the others will override it.

    10. Re:Cringly is poorly informed by Anonymous Coward · · Score: 0

      There is no non-GUI layer in current versions of Windows. You can't even login if the window server hasn't started. The CMD prompt window only runs on top of the GUI.

      This will change with the Server 2003 release, which is able to boot to a console.

    11. Re:Cringly is poorly informed by borgboy · · Score: 2, Informative

      The command line to which you refer is the command shell cmd.exe. It has less to do with dos than the Korn shell has to do with bash - at least bash and Korn are 32 bit apps....dos, for all the extenders (such as what came with my old Borland Pascal 7.0 IDE, I think it was PharLap) was never a 32 bit beast. Cmd.exe is a 32-bit NT console-mode shell...that shares much of the old dos syntax. As far as any emulation goes, that's just yet another client subsystem (you do know that NT is a client-server OS, right? Win32 is not the native API on NT, it is just another subsystem, like OS/2 or posix. To run on this parenthetical comment on a bit more, I'll even mention that Win32 is certainly the preferred "language" on NT, though with .Net you can count on that changing. I'll stop Karma whoring now.) called the NT Virtual DOS Machine, or NTVDM. The Windows-On-Windows (WOW) subsystem runs on top of the NTVDM to extend this emulation to 16-bit Windows applications. All 16-bit dos/windows apps run in a single isolated process space by default, unless configured differently.
      In any case, the command shell is no more the OS executive in NT than bash is in GNU/Linux. The kernel houses the executive. And I mean both NT and GNU/Linux here.

      --
      meh.
    12. Re:Cringly is poorly informed by mattdm · · Score: 1

      Just because there isn't a command line layer doesn't mean there's nothing underneath the GUI -- a CLI would be on top of that too, of course.

    13. Re:Cringly is poorly informed by testm0nk3y · · Score: 1

      Would you expect them to see "crazy uptimes now, a couple of years!" on a product which hasn't been around that long yet? Not very fair, chief.

    14. Re:Cringly is poorly informed by Moofie · · Score: 1

      That seems like such a DUMB point to make, though.

      I mean, if NT were in any meaningful way based on a "separate" OS layer then he might have a case to make for changing the "separate" OS layer to something else. Of course, that's not the way things are, but then he's WRONG, not making a silly point.

      If he actually thinks that the fact that NT has a command shell will make it any easier to port it to Linux, then he's a big stupid head.

      So either he's really confused about how NT works, and thinking that there is a real command-prompt MS-DOS somewhere down there, or he's being absolutely ridiculous by saying that the presence of a command prompt indicates some useful platform that could be ported to or from.

      Meh. Silly article either way. MS will go (real) Free Software shortly after Gates and Ballmer go down to take over management of Hell.

      --
      Why yes, I AM a rocket scientist!
    15. Re:Cringly is poorly informed by rabidcow · · Score: 1

      Just because there isn't a command line layer doesn't mean there's nothing underneath the GUI -- a CLI would be on top of that too, of course.

      Well, there is the recovery console, which is a CLI you can run without starting the GUI. As a "disk operating system," it's pretty limited.

    16. Re:Cringly is poorly informed by Anonymous Coward · · Score: 0

      not to start the usual nt/*nix flamewar, but i do take issue with the claim a team of well-schooled developers led by a single organizational vision produced a better product.

      but i think it's safe to say that at this point, most early nt kernel design goals have been thoroughly bastardized by market forces. my reasoning? look at its original goal of being a multi-platform capable OS. and it succeeded, look at the alpha.

      now look at it. poor thing. god knows what other well-intentioned design goals have been abandoned for the sake of making release dates or appeasing the marketing arm of MS.

      i mean you can argue it both ways, really. oh, and that one hacker did go on to get his masters.

    17. Re:Cringly is poorly informed by Anonymous Coward · · Score: 0

      WTF does "under the gui" mean? You're talking out of your ass.

      The fact is that if the window server ('the GUI') doesn't start on NT, nothing else does either. Everything above the kernel layer is implemented 'on top of' the GUI.

    18. Re:Cringly is poorly informed by lseltzer · · Score: 1

      It's called "thunking," not chunking.

      In current versions, the 16-bit portions are basically just stubs, there's only as much Win16 code as there needs to be to support 16-bit Windows implementations, and even a Linux-based implementation would need as much 16-bit code.

    19. Re:Cringly is poorly informed by drsmithy · · Score: 1
      Yes, NT took some technology from the OS/2 collaboration (NTFS is the advancement of OS/2's HPFS) [...]

      No, it isn't. It was designed and implemented from scratch specifically for the NT project (as explained in "Inside NTFS" and presumably any other books of similar bent).

      HPFS and NTFS do not share any meangingful design features or implementation details. You are probably confused because Microsoft originally wrote HPFS for OS/2 (and still owned it right up until the end, IIRC).

    20. Re:Cringly is poorly informed by Anonymous Coward · · Score: 0

      no, chunking is good, as it describes what it blows....

      And contrary to popular belief, this was developed (and rejected) years before some numnutz in redmond thought it was a good idea....

    21. Re:Cringly is poorly informed by Some+Dumbass... · · Score: 1

      I mean, if NT were in any meaningful way based on a "separate" OS layer then he might have a case to make for changing the "separate" OS layer to something else. Of course, that's not the way things are, but then he's WRONG, not making a silly point.

      First of all, does everyone reading this understand the concept of having layers of code without each layer being a complete OS (i.e. DOS)? If nothing else, go look up NT's Hardware Abstraction Layer on Google. It is entirely possible to rip out NT's VM, disk code, network code, etc. and replace them with the equivalent code from Linux even though the NT GUI is not running "on top of" DOS like in Windows 95. Yes, this would require some rewriting, but perhaps not as much as you might think.

      MS could also port the NT Shell and API to Linux to make a system like Apple's OS X. The API has been more or less ported by Wine, and porting the Shell is the easy part. I suspect that this is what Cringely was thinking of. Even if Cringely wrongly thinks that NT/2000/XP is like Windows 95, this idea could still work.

      Of course, I've just been talking about some of the technical aspects of Cringely's suggestion. There are major licensing issues. There are "political"/PR issues. Plus there's the question of how much Windows would change if such a suggestion were implemented. The second solution (port the API/Shell) in particular would be a massive change to NT.

      Irregardless, Cringely's idea is technically possible, and that's the point. Whatever Cringely's level of technical knowledge, the suggestion he made was plausible, if unlikely. That's why it is worthwhile to discuss, and why his idea shouldn't be ignored just because he may not have as much technical knowledge as some of us.

    22. Re:Cringly is poorly informed by Moofie · · Score: 1

      Fair enough. Let's talk about the PR aspects.

      Why is it in MS's interest to do this? What on earth would possess them to reverse five years of anti-free-software rhetoric to "Wow! This is great stuff! Buy it from us!"

      --
      Why yes, I AM a rocket scientist!
  79. Wow by autopr0n · · Score: 0

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    I can't belive he's so ignorant. You can get a C prompt in XP because people want a C prompt. It isn't needed (and in fact you can't get one in Windows ME, which is more DOS-like then XP)

    --
    autopr0n is like, down and stuff.
    1. Re:Wow by keith_nt4 · · Score: 1
      Actually XP is 100% DOS-free as far as required to load and work. Me on the other hand simply has the reboot-in-msdos-mode option disabled. It can be re-enabled if so desired. I can't think of any reason for this. Either make a boot disk for your DOS adventures or use start/run to run 'command'. I actually have little experience with the innards of Me (as you can tell from my chosen knick name I have a different favorite OS).

      ----

      --
      "UNIX is very simple, it just needs a genius to understand its simplicity." -Dennis Ritchie
  80. Windows XP is descended from the IBM/MS project. by Anonymous Coward · · Score: 1, Interesting

    Aborted IBM/MS OS >> Windows NT >> Windows 2000 >> Windows XP.

    DOS >> Windows 1.0 >> Windows 2.0 >> Windows 3.1 >> Windows 95 >> Windows 98 >> Windows Millenium

    Does Cringely even know what he's talking about if can't even get this timeline straight?

  81. apt-get install windows by Anonymous Coward · · Score: 0

    apt-get install windows

    bugger it

    apt-get install kde

  82. Who? by Anonymous Coward · · Score: 0

    Who did Microsoft buy NT from? IIRC they co-developed it with IBM as OS/2 and then went seperate ways with the result being NT and OS/2.
    See http://www.jwntug.or.jp/misc/japanization/history. html

    1. Re:Who? by capnjack41 · · Score: 2, Informative

      I think that Microsoft did develop NT themselves, but with much help from some of the same guy that did VMS (basic googleing turned up this.

    2. Re:Who? by rusty+spoon · · Score: 2

      You mean "They hired smart people"?

  83. I wonder how it feels... by Anonymous Coward · · Score: 0

    Imagine how stupid this guy must feel. He writes this tabloid story hoping to suck up to some zealots . It gets posted to slashdot (home of the zealots) and even they're not dumb enough to bite on it.

    It must hurt.

  84. Now you know why they call him Cringely... by The+Gline · · Score: 3, Funny

    I cringed while reading this.

    --
    Honorary Member of Jackie Chan's Kung Fu Process Servers
  85. Cringely is an Idiot by MSTCrow5429 · · Score: 1

    Other people have already spoken on this, but I feel the need to as well. Cringely is a complete buffoon who tosses names and history around without really know what he's talking about; which is why he can only get a job on the dole. To whine about a command line in Windows while speaking about windowing systems and Linux itself is ludicrous. I guess we can't use Linux, either because it has a command line. Wait, it doesn't, because it has a pretty GUI. Oh, wait, it is, because the pretty GUI has a command line, repeat. "Linux is better, faster, stronger than whatever is living underneath XP now, right?" Apples and oranges, sometimes, stronger how? "Apple has made a virtue of doing exactly this with MacOS-X, heralding its Mach kernel and BSD roots. Couldn't Microsoft do the same?" The NT kernel is based on the Mach kernel, you idiot. "As Mike Class points out, by not having to develop its own OS, Microsoft could also save money." Um, no, because Windows is worth more than the sum of its parts. And if the Windows GUI was ported over to Linux, that means we wouldn't have DirectX and all the other goodies Windows has. Since when was breaking all the software to move over to another kernel that's just different (in construction and generation) a good idea? I would contact Cringely directly, but there's no e-mail, and the forum is down. Hmm...

    --
    Slashdot: Playing Favorites Since 1997
  86. Re:You got that right by Anonymous Coward · · Score: 0

    And, they do it once more.

  87. OS X by fussman · · Score: 0

    I think if we do have a Windows based on Linux, it will be something like the OS X setup, which would be the underlying core is open source, but the GUI (and others not in the "core" of things) would be closed source. Mark my words, it will be this way if M$ does it. However, I sincerely doubt that M$ will do it.

    --
    Support Israeli punk bands. Man Alive.
  88. No! by ucblockhead · · Score: 2, Insightful

    It's time we stopped trying to shoehorn seventies era multiuser designs (or eighties era single user designs) onto modern PCs. What we really need is an OS redesigned entirely from the ground up for the sort of tasks a modern home or business user needs on the desktop. Linux is no more that then Windows.

    All of the complaints about Linux on the desktop boil down to the fact that it is a clone of an OS designed for minicomputers with multiple users. All of the complains about Windows boild down to the fact that it is an extension of a single-user, single tasking machine.

    In both cases, the OSes have been stretched into something else. In both cases, the stretching has caused problems. Better to start from scratch.

    --
    The cake is a pie
    1. Re:No! by Sgs-Cruz · · Score: 1

      Sounds like you need... you want... EROS!. No, I'm not trying to make snide jokes about Slashdotters sexuality. Seriously, it's a system built on 'permissions' which means each piece of code is allowed only what it needs to run... it's apparently a totally different type of architechture that is effectively unhackable.

      --

      Karma: pi (Mostly due to circular reasoning in posts).

    2. Re:No! by bradams · · Score: 1

      That is why BeOS was made.

      --
      I like to build things and wire stuff together.
    3. Re:No! by yoink! · · Score: 1

      http//www.be.com

      Oh wait...

      Hmm...

      Well there's still http://www.qnx.com/

    4. Re:No! by Tim+Browse · · Score: 1

      I don't like the word 'unhackable'. It sounds too much like 'unsinkable'.

      Tim

  89. Mostly correct. by hackwrench · · Score: 1

    but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

    1. Re:Mostly correct. by miu · · Score: 1
      but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

      explorer.exe seems to be what Cringely is talking about when he says "Windows". At least that was my best guess.

      --

      [Set Cain on fire and steal his lute.]
    2. Re:Mostly correct. by Anonymous Coward · · Score: 1, Informative

      explorer.exe is just the shell, and can be replaced.

    3. Re:Mostly correct. by Anonymous Coward · · Score: 3, Insightful

      but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

      explorer.exe seems to be what Cringely is talking about when he says "Windows". At least that was my best guess.

      No, I don't think he is smart enough to even know what it is exactly he was referring to... but my guess is more along the lines of the actual Win32 API as embodied in the Csrss.exe subsystem and the core Win32 DLL's (i.e., Kernel32.dll, User32.dll, GDI32.dll, ComDlg32.dll, AdvAPI32.dll, etc.)

      Still, it's hardly even worth speculating since he is such an idiot. Listen, Linux has a lot of strong points and a good future ahead of it, but it is just lunacy to always assume that everything is better with Linux. Banana splits are great. Pepperoni pizza is great. But, that doesn't mean that I want to start putting pepperoni's, cheese, and tomato sauce on my banana splits! Both Windows and Linux will be far better off evolving on their own separate paths, and only a complete layperson would suggest otherwise.


  90. It should be built on BSD, not Linux by kakos · · Score: 1

    If Microsoft changes Windows over a Unix based OS, it will be built on a BSD, such as FreeBSD or OpenBSD or even Darwin.

    Most of the code in the NT kernel is already built from BSD code. It seems it would be a lot easier to change things over to BSD since NT seems to do a lot of things the "BSD way". Plus, since Mac OS X is BSD based, a lot of hardware developers have ported their drivers to a BSD-based system. It would be trivial to then port those drivers to MS BSD. Besides, BSD is better than Linux anyways. It just makes sense to do it with BSD.

    1. Re:It should be built on BSD, not Linux by zjbs14 · · Score: 1
      Most of the code in the NT kernel is already built from BSD code.

      Ummm, no.
      The kernel is not BSD-based. It was written with the help of DEC (who really wanted a more "mainstream" OS for the Alpha platform), and is much more VMS-like than anything.

      Now, the original TCP/IP stack and utilites were based on BSD, so in that area it's been BSD-like.

      Also, I think many Mac users would disagree with the on the availability of drivers for OS X.

      --
      No sig, sorry.
  91. cmd.exe by ucblockhead · · Score: 3, Interesting

    XP actually ships with both cmd.exe and command.com. (command.com works via emulation of the DOS calls, of course, so yes, he's an idiot.)

    --
    The cake is a pie
    1. Re:cmd.exe by Anonymous Coward · · Score: 0

      It's possible to be wrong and not be an idiot just like it's possible to be right and still be an asshole.

    2. Re:cmd.exe by orangesquid · · Score: 0

      [Rant]
      "It's possible to be wrong and not be an idiot just like it's possible to be right and still be an asshole."
      ((Sorry if I piss anybody off, but I have to agree with this AC because I see this sort of thing all the time around here...) No, sorry, not on slashdot. Here, you have to impress thousands of nerds who would never agree on anything even if they were at gunpoint. Most 15-year-olds would rather trust themselves than trust someone that proposes something "foolish," "stupid," "uncool," or "crazy." Slashdot has many closed-minded types lurking about. In a way, it's quite a bit like high school; even here, there is a "status quo" among nerds, and people are rated based on "coolness." Proposing some absurd sort of Beowulf cluster would get +5, Interesting, even if the idea was technically unthinkable, but mixing Windows and Linux would get -500, Stupid. Perhaps thinking "out-of-the-box" is stupid, but it has led us to many great scientific and engineering accomplishments in the past. Why now should it be abandoned so?)
      [/Rant]

      [OnTopic]
      Windows and Linux both have some very strong features, but strangely without overlap; they tend to contrast rather well, as Windows is easy to set up, easy to use, and difficult to kernel-program and difficult to hack and tweak, and Linux is difficult to set up, challenging to use, easy to kernel-program and simple to hack and tweak. A system that combined these things (a "committee" operating system more than a "practical" one; i.e., it sounds great on paper but it nearly impossible to implement) could very well be the next "killer app," but it would require enormous strides to be made to bring two such dissimilar systems together. However, an examination of PL/I shows that, no matter how absurdly complicated the solution is, some company is willing to throw billions at it to make it happen. I haven't been able to read the article (slashdotted, it seems), but I get the feeling it isn't as bad as the /(great-)+grandparent/ posters make it out to be.

      Also, IIRC, Cringely is not one person but a pseudo-name used by a panel of writers. One of them might be a little looney, but the rest might be very well-grounded, and perhaps we are just hearing "Spooky Mulder's" ideas?
      [/OnTopic]

      --
      --TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
    3. Re:cmd.exe by cmacb · · Score: 2, Insightful
      "Also, IIRC, Cringely is not one person but a pseudo-name used by a panel of writers. One of them might be a little looney, but the rest might be very well-grounded, and perhaps we are just hearing "Spooky Mulder's" ideas?"

      This article is by one guy, by that name. he used to write for a magazine (PC Week?) under that name and the magazine copyrited the name. That's the panel of writers you are thinking of.

      IMHO, most of the critics here did not read the article, or read it too literally. His general point was that people buy Windows for the user interface, not for its VMS underpinnings or even for DOS.

      PS: I noted the additional reasons they might want to do this in a later post. The suggestion that MS might benefit from a GUI on top of Unix approach is NOT a new prediction, and in fact there are rumors that they are already working on it.

      The reasons they might want to do this go far beyond the technical difficulty issues. They have $40 Billion dollars for petes sake, they could write the whole dang thing from the ground up in Visual Basic if they felt like it!

      (Now just watch someone comment on how ridiculous it would be to re-write Windows in Visual Basic)

    4. Re:cmd.exe by Twirlip+of+the+Mists · · Score: 4, Informative

      Also, IIRC, Cringely is not one person but a pseudo-name used by a panel of writers.

      Not exactly. Robert X. Cringely is kind of like the Dread Pirate Roberts: a serial pseudonym. The name was first used in InfoWorld magazine when Dvorak left-- and started losing his mind, if his last couple years' worth of columns are any evidence-- to replace the famous byline. The Robert X. Cringely we're all most familiar with is really Mark C. Stephens; he's the guy who wrote the books and hosted "Triumph of the Nerds" on PBS and who writes "I, Cringely." He was the third Robert X. Cringely to write for InfoWorld, and he wrote for them for 8 years. Since that Cringely's departure-- okay, firing-- from InfoWorld in '95, many others have written columns under that name for the magazine.

      The real Robert X. Cringely has been retired for 15 years, and living like a king in Patagonia. ;-)

      --

      I write in my journal
    5. Re:cmd.exe by miu · · Score: 1
      Proposing some absurd sort of Beowulf cluster would get +5, Interesting, even if the idea was technically unthinkable, but mixing Windows and Linux would get -500, Stupid. Perhaps thinking "out-of-the-box" is stupid, but it has led us to many great scientific and engineering accomplishments in the past.

      The problem with that argument is that the article is not a "thinking outside the box" "it's so crazy it just might work!" discussion starter. It is cheerleading of the worst sort.

      Since you have not been able to read the article I'll repeat a choice passage:

      Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve.

      Statements of that sort are why so many people have a problem with the article. This kind of article diminishes the Linux community and should not be taken seriously.

      --

      [Set Cain on fire and steal his lute.]
    6. Re:cmd.exe by York+the+Mysterious · · Score: 1

      Wouldn't a system that combines the ease of use of XP and the power of Unix be OS X? Well maybe not today, but that is certainly the goal. It's no simple task. I really don't think Microsoft would want to undertake the task and break compatibility while doing so. It took long enough to get people to update their apps for NT/2000/XP. This would be even worse.

      --

      Tim Smith - Ramblings from Nerd Land
    7. Re:cmd.exe by Anonymous Coward · · Score: 0

      It would be ridiculous to rewrite windows in visual basic

  92. From the column by Niten · · Score: 1

    What this would do is level the playing field just a bit.

    And that, among other things, is precisely why they will not (and from their perspective, should not) do it.

  93. My Commodore 64 had a "disk operating system" by djeaux · · Score: 1

    Admittedly, it was slower than a lawnmower, but it was a "d.o.s." nonetheless...

    --
    "Obviously, I'm not an IBM computer any more than I'm an ashtray" (Bob Dylan)
  94. cool... by typhoonius · · Score: 0

    It'll be like a combination of Lindows and Windows. We can call it Windows.

  95. BSD all the way baby! by Anonymous Coward · · Score: 0

    Lots of people are switching away from all the false promises of stability and speed that have been promised all these years, rewrite after rewrite. It's just not true. Linux is unstable and it's a piece of junk. People who hate windows and people who love Unix, both should all run FreeBSD.

  96. Re:It doesn't make sense by GombuMstr · · Score: 1

    Unlike Linux if you were to allow people to fiddle with the underbelly of Windows it would destroy the fine grained control that has taken over a decade to master.

    Actually that is called the registry. You tell Microsoft you were touching the registry and your done. Go home, reinstall and forget that you even called them.

  97. He already is... by Anonymous Coward · · Score: 0

    ...Bush/bin Laden alliance has been hot for many years.

  98. This is just silly... by glenebob · · Score: 1

    Cringely doesn't seem to know his as... well, anyway. XP is NOT based on DOS, as others have already said, it's the current version of what was called NT a couple years ago. He shows great ignorance for claiming otherwise.

    MS has one big huge overwhelming reason not to put Windows on Linux, or any other kernel for that matter. Control. Simple as that. They will not give someone else *any* control over any of they're products. That's just the way they work, and they've made billions because of it. Why do you think there is a thing called .NET? Why do you think they didn't start on a Unix kernel from the get go? If Cringely thinks there's a snowball's chance in hell of MS ever doing this, he really needs to have his head examined. He talks about what would be neat, and what would be good for the industry, and what would make /. have a happy frolic through the tulips. All in the face of reality.

    And it wouldn't even be that good an idea. Linux isn't such a wonderful kernel as good kernels go. Sure, it's stable and performs well, but it's not the only good kernel out there. More importantly, Linux the kernel is not the reason that Linux the distro rocks. The distros rock because they, like they're Unix precursors, provide huge piles of control over the system on which they run, and a nice clean interface to the hardware. It would be perfectly conceivable to build a full-featured Unix-like distro running on top of the NT kernel. MS would have to be the ones to do it of course, but that isn't the point. The point is that the NT kernel isn't the problem. The problem is MS. Slapping Linux under Windows would provide us with the same problem we have now: a monopoly exerting too much control on the industry, with a product no better than they offer now.

    I could spend the next hour picking the article to pieces, and I'm not even that good at it. I think I'll just stop now :-)

  99. Someone is becoming strange here by parkstec · · Score: 1

    Should the next version of Windows be built on Linux they ask. Does this mean no one remembers Windows 95 and all of it's problems?

    Only if you have been living in a cave in Afghanistan.

    Should the next Chevy truck be built on a Honda frame? Yeah Right! Some one close the cage, the Microsoft Evil Monkeys are loose again!

  100. platform, application... and service by Anonymous Coward · · Score: 2, Interesting

    MS could only survive in such a mythical model if they concentrated on being a service oriented organization and/or relying on applications such as Office. Why would they want to do this when their business model works perfectly well now? Sure their stuff crashes, is a crackers dream and is always about 5 years behind the *nix world with functionality (but they always have more "features"). However their marketing and legal methods have produced what their lack of engineering and innovation have not, so why change?

  101. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  102. The Pulpit by Angry+Black+Man · · Score: 1

    Judging by the name Cringley has picked out for himself, he seems to think he is of some higher breed than the rest of us. This way, he can write technical columns for PBS and get away with glaring errors and awful research. Not to mention it sounds like the article was written by a high school newspaper editor-in-chief or something.

    This isn't the first time he's been wrong. If you go back and read his columns (arrange to be checked into a mental asylum if you do decide to), you will find every article full of bs like this.

    Why would you want to buy a Microsoft product based on Linux when you can get it for free anyhow? I guess he didn't bother thinking out the reality of the situation. That's like saying maybe Xbox Next should be based on PS3 methinks.

    --
    the byproduct of years of oppression by the white man
  103. Editorial Page by LostCluster · · Score: 1

    I, Cringely has never been a source for news developments. "I, Cringely" by its name itself implies it's an opinion column...

    Cringely's most famous work has been as a historical storyteller rather than covering developments as they happen. Don't look for him expecting news, that's never been what he's had to sell you.

    So yeah, this is a rather far out idea that even he admits in the column is never gonna happen. But, hey, what a conversation starter... he's done is job.

  104. Everyone is missing the point. by Jason+Pollock · · Score: 5, Insightful

    Cringley isn't an idiot. You may not agree with what he's saying, you may think that he doesn't understand what an OS is, you may even think that Microsoft would never follow that course, but he isn't an idiot.

    He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

    Is it going to be as easy as simply porting a windowing system? No Way! Does he understand that? Most certainly.

    What he is saying is that Microsoft has demonstrated that it doesn't _need_ to control the underlying OS in order to get everyone to think that they're running the show on the desktop.

    He points out the benefits of moving to Linux or even BSD. Would replacing XP/NT/9X as the OS remove MFC .NET, C#, DirectX or any other API? Nope, it would just use the underlying OS differently. In fact, Wine has done a lot of this already...

    Would Microsoft ever do it? Doubtful, but then I would have sworn that Apple would never use BSD...

    Jason Pollock

    1. Re:Everyone is missing the point. by Osty · · Score: 1

      Cringley isn't an idiot. You may not agree with what he's saying, you may think that he doesn't understand what an OS is, you may even think that Microsoft would never follow that course, but he isn't an idiot.

      He may not be an idiot (the jury is still out on that one, though my vote goes to "idiot"), but at best he's poorly informed.


      He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

      You're correct, in that the end result would be the same. However, his basic premise as to why Microsoft would even consider doing this is flawed -- his premise being that Windows 2000 and XP are still DOS-based like their Win9x cousins, rather than NT-based. His assertion is that even today Windows is nothing more than a GUI on top of DOS, and that other versions of DOS would work just as well (let's see him try it ...). His premise is completely incorrect, as well as unfounded, and thus his arguments are worthless.


    2. Re:Everyone is missing the point. by jpmorgan · · Score: 5, Interesting
      No, Cringley is missing the point, and he's talking about something he doesn't understand: namely the Windows/NT mix.

      In some respects he's right, but accidentally (a stopped clock is right twice a day), in that Windows is built on top of another operating system, in this case, NT. But to transition to another base there are three questions that would have to be answered:

      • Is it possible?
      • Would it be better?
      • Would it be economic?

      Is it possible? Not without a lot of modification to Linux. NT is not UNIX and has a number of fundamentally different idioms; while Win32 abstracts a lot of this, it still pokes through in a few places. Even if Microsoft implemented features in the Linux kernel necessary, they'd still be forced to deprecate half the API and force developers to rewrite their applications to take full advantage of the new architecture. And if they rewrote Linux enough to make this unnecessary, it wouldn't be Linux anymore - it'd be an NT rewrite.

      Would it be better? Cringley simply assumes that Linux is faster, more stable, etc... than NT. Windows is notorious for being unstable, although most of that reputation is due to the Win9x line. Win2K/XP have been known to crash on occasion, but unless you're using some seriously broken hardware, or have fucked its internals up a lot, it doesn't crash that often, and even then the vast majority of crashes are due to the Win32 layer, not NT itself. NT has a stronger security model, is realtime and fully reentrant. In short, the problems with Windows 2000/XP are not the fault of NT, but Win32 itself. Exactly how would porting Win32 to Linux solve these problem?

      Would it be economic? The marginal benefit of porting to Linux would be minimal, and at great expense. I can't see how Microsoft would justify it.

      Cringley suggested something that is fundamentally highly technical without understanding the real issues involved, which was stupid. This is particularly ironic when you consider the section of his site saying that people should listen to him since he knows what he's talking about. Once again this simply proves that he's nothing more than a digital snake-oil salesman - under the guise of holding an expert opinion, he tells people what they want to hear in exchange for ratings.

    3. Re:Everyone is missing the point. by NeuroManson · · Score: 2, Insightful

      The difference between Apple and Microsoft, however, is this:

      Apple: Proprietary hardware and OS, though with a little effort, other operating systems can be installed.

      Microsoft: Proprietary OS, open hardware. Any variety of OS can be installed as an alternative.

      The key word here is proprietary. Apple makes whatever business they have from the proprietary hardware, not the OS. Microsoft makes whatever business they have from the proprietary OS, not the hardware.

      As Microsoft is primarily a software company, they have everything to lose by using an open source kernel which they will have no control over.

      --
      Just because you can mod me down, doesn't mean you're right. Shoes for industry!
    4. Re:Everyone is missing the point. by Sentry21 · · Score: 3, Insightful

      He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

      The difference is that Apple has always been a friendly company - not friendly to everyone, of course, they have to protect their investments, but I look at it this way: Apple may be a 'corporation', which is evil to some, and they may not GPL every line of code ever written, which is evil to others, but they're not anti-competetive (as if they have a chance), and they're not anti-user. MS, on the other hand, is very anti-competetive, and very anti-user. All their software assumes that you're a lying, cheating, thieving bastard, and spies on everything you do. Nice.

      MS makes their money by doing what's best for the company. Apple makes their money by doing what's best for the users. What MS doesn't realize is that in the short term, being a jerk is great, but in the long term, Apple's the one who's going to come out on top.

      The point I'm trying to make, I guess, is that Apple went with BSD because it was the smart thing to do, it was the clever thing to do, and it's paid off big time already. MS will never go with Linux, because then they don't control everything. They can't control Linux kernel development, they can't control apps, they can't control APIs, they can't control hardware, they can't control much of anything, because they'd always have to give the source back. Companies wouldn't want to write Linux drivers, because binary drivers generally suck, and source drivers don't leave a lot of room for trade secrets. MS requires power-control.

      Apple, on the other hand, opened the source, but still keeps a leash on it, in a small sense, and they control the hardware as well, plus the overlying APIs, but Apple's control is quality control, and no one's going to take their quality away from them just by having the source.

      --Dan

    5. Re:Everyone is missing the point. by kubrick · · Score: 1

      Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

      It would hardly have been heresy, especially as Apple's offer to buy Be (and Apple's eventual acquisition by NeXT) were big news in 1996... seven years ago.

      --
      deus does not exist but if he does
    6. Re:Everyone is missing the point. by cmacb · · Score: 1

      *Finally* someone who read (and understood) the article. I wouldn't even hold him to the Linux (as opposed to BSD) part. His point was that the underlying OS isn't now, nor was it *ever* what sold copies of Windows, and hence Office.

      The other factor that nobody has brought up is that with PCs going the comodity route of stereo equipment people are going to be paying less attention to the OS than ever before. For home users the computer is an appliance. Cheap. You don't like the color, throw it out and get a pink one!

      As Microsoft proved to IBM, what people use at home eventually finds its way into work.

      It may be doubtfull that Microsoft will make such a change gleefully, but price pressures will force them to look to other sources of revenue. I predict that they, like IBM, will move into the consulting arena more and more and gradually shed their unprofitable experiments, hanging onto the OS and Office product lines only while they continue to make money.

      Only consulting gives them the potentially high profit margins that they are used to having with the Winodows/Office monopoly. Magazines, News media, Xbox, palm devices have all been and will continue to be money losers for them.

      Anybody notice that they followed one of their best quarterly reports with a "prediction" for a downturn, and for the first time ever a dividend on their stocks? They already have the numbers that tell them what their next few quarters will look like and they know that the dividend will help prop the stock price up at that high P/E ratio. They also know they need to start looking for the follow on to their success with Windows, and it AIN'T gonna be Office 2004 or whatever.

      After a "long way 'round the barn" we have been transported back 15 years or so when there were a variety of operating systems and therfore a hope that standards-based methods would allow disparate systems to interoperate. A much healthier state of affairs than one-size-fits-all. So much for the "progress" that Microsoft is often credited with.

    7. Re:Everyone is missing the point. by EinarH · · Score: 1

      Yep, i do agree with the above, to justify a big shift from the underlying NT/Win2k technology to Linux there have to bee a significant economical upside for Microsoft. There is no such thing.
      If MS was in finacial problems or had problems with the cashflow they would have had too save money by cutting developmental cost.
      But after all their problem is that they have too much money and don't know where too use them.

      Quoted from the article:
      And for Microsoft, it offers that delectable prospect of selling Microsoft Office for Linux by inserting a bit of middleware to interface its apps with other windowing systems, again without having to adhere to the GPL.

      And why would they want that. It is the *combination* Win OS and MS Office that is their "killer app" as a company. Most companies need Word, Excel and Powerpoint, not Explorer/IE Explorer. That's why they buy Win2k. If they in the future can use MS Office an Red Hat XX Microsoft have a problem.
      Microsoft separating MS Office from MS WinOS would be like Gilette stopping selling blades.

      [Insert /. rant about my bad english]

      --

      Melius mori in libertate quam vivere in servitute.

    8. Re:Everyone is missing the point. by Anonymous Coward · · Score: 0

      Not anticompetitive my ass. They squashed the clones when they saw that they might have to *gasp* compete with other vendors for their share of the market. Just because _you_ hold Apple above god doesn't mean that's a reasonable attitude to have.

    9. Re:Everyone is missing the point. by Bastian · · Score: 1

      Apple makes their money by doing what's best for the users.

      You're saying that a company that just released an imcomplete version of their latest OS, then finished the stuff they didn't finish the first time and released it but made the users who bought the incomplete version pay for the upgrade does what's best for the users? I realize that Apple may have had to do that to cover the costs, but it's certainly not very friendly to the users.

      Similar feelings for the Color Classic, the Performa series, the insistence that function must follow form, which seems to invariably lead to shit like super-expensive circular motherboards and the like, and the first production run of PowerMacs.

    10. Re:Everyone is missing the point. by neoevans · · Score: 1

      I should note first that I am writing this from my Powerbook G4, NOT my Wintel box. Having said that, I quote thee:

      "The difference is that Apple has always been a friendly company...Apple makes their money by doing what's best for the users. What MS doesn't realize is that in the short term, being a jerk is great, but in the long term, Apple's the one who's going to come out on top..."

      How exactly is shrinkwrapping an OS that comes with everything except an Office suite freindly? Office 10.x is the only piece of software I had to purchace for my Mac. Everything else came with... The DVD player AND burning apps, Movie editing app, Multimedia app, heck... Why go and buy ANYTHING that comes in the iLife package. The only company they are being freindly to there is Microsoft! After all, what other office suite do most corporate consumers look for?

      If they wanted to be freindly, they could have left out all of the bells and whistles and just included a nice, non-MS office suite.

      PS, I love my Mac.

      --
      "You are not a beautiful and unique snowflake."...Tyler Durden
    11. Re:Everyone is missing the point. by Osty · · Score: 1

      If MS was in finacial problems or had problems with the cashflow they would have had too save money by cutting developmental cost.
      But after all their problem is that they have too much money and don't know where too use them.

      More than that, Microsoft still has a positive cash flow (ie, profit). Even with the 40bil or so cash on hand, if Microsoft stopped making profits, there would be big problems.


      And why would they want that. It is the *combination* Win OS and MS Office that is their "killer app" as a company. Most companies need Word, Excel and Powerpoint, not Explorer/IE Explorer. That's why they buy Win2k. If they in the future can use MS Office an Red Hat XX Microsoft have a problem.
      Microsoft separating MS Office from MS WinOS would be like Gilette stopping selling blades.

      You seem to be ignoring that "other" OS called Macintosh OS. I agree that on PC hardware, offering Office on anything but Windows is suicide for Microsoft. Office for Mac is less threatening because it means a much larger up-front investment, but there's still nothing stopping companies from going that route if they really must. Still, Office for Mac isn't free, so it's still cash in Microsoft's pocket (IMHO, not a bad thing).

    12. Re:Everyone is missing the point. by taweili · · Score: 1
      He is talking about Microsoft doing _exactly_ the same thing that Apple has done with OSX (use someone else's OS), except with Linux instead of BSD. Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI? Heresy!

      It was obvious that Apple is heading for the Unix based next generation when it was sallowed by NeXT and the return of Steve Jobs. The "acqusition" of NeXT happened in 1996.

      However, I agree with you about the the point of moving Windows on top of Unix (Linux, BSD or even Mach). Typical users do not care about the underlying system they are running. The UI is what interact with them.

      On the financial side, it goes by the old saying "A dollar saved is a dollar earn." Not having to maintain a large team of OS programmers would definitely save Microsoft a lot of money.

      On the marketing side, Microsoft would have no problems make the users forgot about Linux is there. It's still called Windows XP (or Windows 2004/5/6) and it's still a Microsoft products.

      The backward compatibility issues you brough up are easier for Microsoft to solve then what Apple has encounter because of existing projects like Wine. There wasn't open source effort to emulate OS 9 under Unix for Apple to reply on. Microsoft can easily leverage WINE to solve their backward compatibility problem when moving to Unix based kernel.

      Overall, there are a lot to gain for Microsoft moving to Linux and few to lose. One thing for Microsoft to lose is face and making their attack on Linux now look like idiotic. But, hey, Bill G told us "640K is enough for everything, right?" I think Microsoft's management are excellent business people. The point brought up here should be clear to them.

      Only one tatical problem I see for Microsoft to solve right now: "How to put Linux under Windows without promoting the status of our competitors." If Microsoft decided to adapt Linux as kernel, it has to do so not making market think it's putting a seal of approval of Linux, thus validate their OS competitors such as RedHat or SUSE, or in this case, GNOME or KDE.

    13. Re:Everyone is missing the point. by The+B · · Score: 1

      Apple doesnt use BSD. It uses some variant code of BSD, but it is not BSD.

    14. Re:Everyone is missing the point. by Tailhook · · Score: 1

      MS doesn't realize is that in the short term, being a jerk is great, but in the long term, Apple's the one who's going to come out on top.

      Microsoft has been kicking Apple's ass for going on 20 years. What sort of timeframe did you have in mind?

      --
      Maw! Fire up the karma burner!
    15. Re:Everyone is missing the point. by mangu · · Score: 2, Informative
      I was agreeing with everything you mention, until I got to "...is realtime and fully reentrant."


      The reason I migrated completely from NT to Linux is that a few years ago I was writing a software that did realtime data acquisition from the sound card. It never worked correctly in NT, because, as I found out after much debugging, NT disables interrupts for as long as 100 milliseconds at a time. If you want to do any extensive data processing on an audio stream without gaps in NT, you have three alternatives: (1) write a realtime thread handler that duplicates a lot of the scheduling task, (2) write a new device driver, or (3) do it offline. Strange thing is, Linux is *not* realtime, but my program works fine in it, just goes to show how important a good task scheduler is.

    16. Re:Everyone is missing the point. by IamTheRealMike · · Score: 1
      MS makes their money by doing what's best for the company. Apple makes their money by doing what's best for the users. What MS doesn't realize is that in the short term, being a jerk is great, but in the long term, Apple's the one who's going to come out on top.

      Bwahaha. I think you need a history lesson. Microsoft IS on top because Apple WERE jerks. Hell, when Jobs asked Gates what he should do to increase the Mac marketshare, Gates told him "license clones". Gates realised that the fact the hardware came from only one company was holding them back. They tried it, and when they realised the clones were seriously cutting into their own marketshare, they killed them rather than actually become competitive. Oops.

      I dunno what kind of short term you're thinking about either, Microsoft has been on top for a long time. Apple by the way don't stand a chance - they have exactly the same business models as Microsoft except with proprietary hardware, and history showed that this doesn't work.

      Finally, the idea that Apple is a cuddly fluffy bunny that has a giant great big heart and loves its customers to bits is simply laughable. The number of cases where Apple has made seriously unpopular decisions that pissed off ALL their customers at once is so long I won't write it all down here, I'm sure you can think of some. Apple are sometimes just as much a nasty piece of work as Microsoft are, so to pretend that if they had absolute power they wouldn't abuse it like Gates did is ridiculous.

      Apple, on the other hand, opened the source, but still keeps a leash on it, in a small sense, and they control the hardware as well, plus the overlying APIs, but Apple's control is quality control, and no one's going to take their quality away from them just by having the source.

      Repeat after me. MacOS is NOT open source. I don't understand why people repeat this myth. The small percentage that is open sourced is based on BSD which was already available. Most importantly, the API implementations are not open sourced, and they are the things that give an OS its lockin value. Linux has a fine kernel, but we can't run Windows apps well yet because the implementations of the Windows APIs aren't complete.

    17. Re:Everyone is missing the point. by Alomex · · Score: 1

      NT disables interrupts for as long as 100 milliseconds at a time.

      Until very recently, Linux disabled interrupts for the entire duration of the interrupt call, rather than doing so only during the critical sections of the interrupt call.

    18. Re:Everyone is missing the point. by esarjeant · · Score: 1

      NT (W2K) also seems to handle serial ports by sending sporadic streams of gunk to them, which could be related to this virtual interrupt handling scheme? We had a headless Sparc connected via serial cable to a W2K box, and for some reason -- every so often -- the Sparc would become unavailable.

      It turned out the Windows dumb-terminal wasn't so dumb after all! It would occasionally send garbage characters to the tty and force the Sparc to a PROM prompt. Since the box was headless, we went through a lot of trouble to borrow a monitor and connect it to the Sparc.

      Afterwards, we simply dropped the serial cable into a Linux box and accessed the dumb terminal from there. Evidently Windows wasn't up to the task of serving as a dumb terminal.

      --

      Eric Sarjeant
      eric[@]sarjeant.com

    19. Re:Everyone is missing the point. by swillden · · Score: 1

      Any device driver whose interrupt handler runs for 100ms should be shot. In an open source kernel, any such driver would quickly be removed or rewritten, so it's not surprising that Linux is much less problematic in this respect.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    20. Re:Everyone is missing the point. by p00ya · · Score: 1
      Microsoft: ... open hardware.

      Im sure that will all change with palladium.

  105. Way to show some balls mods! by Anonymous Coward · · Score: 0
    w00t -1, Troll! I was afraid I'd just see a bunch of overrated mods.

    You may be an emasculated loser, but at least you are willing to take it up the ass in metamod.

  106. Re:"Back when Unix meant typing on a command line. by damiam · · Score: 1

    Using Unix doesn't necessarily mean recompiling Apache. And, if you really felt the urge, there's probably some GUI program out there that will automatically run ./configure && make && make install for you. If there isn't, it'd be trivial to write one. The command line is an important and useful part of Unix, but it's certainly not a necessary one.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  107. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  108. BSD, not Linux by pvera · · Score: 1

    The only thing that stops Microsoft from using Linux as the baseline is the GPL. MS would love the public relations coup of jumping into a unix-like platform, but they are scared to death of GPL. The BSD family, on the other hand, is more aligned with the way Microsoft wants to run their business.

    --
    Pedro
    ----
    The Insomniac Coder
  109. The Truth... by Anonvmous+Coward · · Score: 4, Funny

    "Should The Next Windows Be Built On Linux?"

    No because I hate Microsoft and I refuse to see any good that could come from it.

    1. Re:The Truth... by NanoGator · · Score: 2, Funny

      "No because I hate Microsoft and I refuse to see any good that could come from it."

      Heh. If you posted that sooner a bunch of other posts would have been modded as redundant.

      Too bad I don't think anybody'll see the humor in it.

      --
      "Derp de derp."
  110. You're wrong. VMS != UNIX by jpmorgan · · Score: 4, Interesting
    Correct me if I'm wrong, but isn't VMS based off of Unix as well?

    You're wrong. VMS and UNIX appeared at about the same time, but are very different beasts. Arguably, VMS was better than UNIX, but UNIX became dominant as a result of BSD.

    1. Re:You're wrong. VMS != UNIX by drinkypoo · · Score: 1
      I'll take a second to argue why VMS was not better; It lacked portability in its early days and ran only on a limited set of proprietary hardware.

      Say what you want about Unix, there's a flavor of it for just about everything.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:You're wrong. VMS != UNIX by ucblockhead · · Score: 1

      No...Unix became dominant over VMS on the PC because it was ported (more than once) to PC class machines while VMS was not.

      --
      The cake is a pie
    3. Re:You're wrong. VMS != UNIX by John_Sauter · · Score: 3, Informative
      Actually, it was TOPS-10 that appeared at about the same time as UNIX. VMS didn't appear until 1978, but TOPS-10 was one of its ancestors. Descendents of TOPS-10 use the DIR command; descendents of UNIX use the ls command.


      John Sauter (J_Sauter@Empire.Net)

    4. Re:You're wrong. VMS != UNIX by Jahf · · Score: 1

      PC-VMS existed to run VMS on PC machines since at -least- 1986, when I can remember seeing it sitting in my father's desk drawer next to our 8088 PC.

      It may never have gotten popular, but it did exist. And the versions of Unix for the PC that got popular didn't do so until the 80286 with it's enhanced memory modes.

      Personally, I hate VMS from a usability point of view, I never got the hang of it very well whereas Unix seemed to just make sense to me. However, I know plenty of folk (including a couple of relatives) who would strongly argue in VMS' favor.

      Unix getting popular in the 80's and 90's had very little to do with PCs until Linux kernel 2.0 came out. Unix getting popular had to do with it being relatively easy to learn to navigate combined with being on nearly every (non-PC) server/workstation of the day.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    5. Re:You're wrong. VMS != UNIX by Senjutsu · · Score: 1

      In its early days, Unix was written in nothing but assembly, and was every bit as unportable as VMS was. It was untill Unix was reimplemented in C that it became portable.

    6. Re:You're wrong. VMS != UNIX by Anonymous Coward · · Score: 0

      That singularity of hardware was the REASON that VMS was so good. Much like Apple having only limited hadrware to work against, but with the added advantage that they made the hardware too.

      OpenVMS was portable (mostly), but
      1) Too late
      2) Lost some of the advantages VMS had had.

    7. Re:You're wrong. VMS != UNIX by Anonymous Coward · · Score: 0

      Digital (the creator of VMS) sold hardware. Portability isn't very interesting to Hardware vendors.

      When hardware was a whole lot slower, the ability to tightly tie features of the OS to features of the hardware was really important.

      Nowadays, who really cares about portability? Most of the CPU's that run OS's just care about x86 compatibility.

  111. IE 7 for Linux by Anonymous Coward · · Score: 0

    Dx9 and up support.
    Use of proprietary extensions.
    Media Player.... v6.4
    etc.etc.etc.

    Your 4 year linense for 49.99

    Ends one argument, begins four more.

    If they kept who in mind who they're making this for they'd have less problems.

  112. Re:"Back when Unix meant typing on a command line. by Anonymous Coward · · Score: 0

    The command line is an important and useful part of Unix, but it's certainly not a necessary one

    What would X sit on top of if there was on command line? Itself? That makes for some weird Mc Escher picture.

  113. MS used to sell UNIX by karlm · · Score: 4, Insightful
    Did they sell exclusive rights to Xenix to SCO, or could they still migrate everything over to the Xenix kernel without having to pay SCO?

    This will NOT happen.

    It's a shame to see MS take things it definately knows about and reinvent them poorly. They knew about UNIX crypt passwords, but went ahead and made the LM hash for passwords but neglected the salt value used in UNIX crypt to prevent parallel cracking of the entire password file. They later saw some of thier problems and came up with the NT hash based on UNIX md5 passwords (but using the md4 hash), again neglecting the UNIX salt. I'm a security systems guy, so maybe it just happens that MS only reinvented poorly the stuff I'm knowledgable about. Using off-the-shelf MIT-liscenced (similar to X11 liscence) Kerberos instead of making up their own networking authentication protocols and having to revise them when they realize they designed them poorly.

    It was a good idea for them to try and make NT a microkernel OS, but it didn't end up working out. It's a shame they didn't reinvent the filesystem as a unified virtual filesystem with C:, D:, etc. being symbolic links for legacy purposes. Oh well.

    --
    Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
    1. Re:MS used to sell UNIX by JanusFury · · Score: 1

      Dunno about the rest, but the nt filesystem IS virtual like you describe. Drive letters are not required for partitions in nt; half the partitions on my xp box are mounted in folders.

      --
      using namespace slashdot;
      troll::post();
    2. Re:MS used to sell UNIX by hbackert · · Score: 1

      Out of curiousity: how do you get rid of the system drive letter (C: usually)?

    3. Re:MS used to sell UNIX by swillden · · Score: 1

      Dunno about the rest, but the nt filesystem IS virtual like you describe.

      Sort of. It's at a higher level -- it's an NTFS feature, not an NT feature. This means that you can't mount partitions under a folder on a FAT partition. Also, you can only handle hard drive partitions this way. You can't mount a floppy, Zip disk, CD-ROM, network share, etc., on a folder. Oh, and you still can't get rid of drive C:.

      In fact, I think this is yet another good example of how MS takes a good idea and reinvents it poorly.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  114. Ya know... by Squidgee · · Score: 1
    I kind of feel bad for Cringely; I'm sure he actually thought he was right when he was typing it.

    Heh, well, I guess that's what you get for penning something a ridiculous/obiously-overly-attention-grabbing/horr ibly researched as this.

  115. Probably redundant.... by frozencesium · · Score: 1

    yes the article is inacurate. what does that matter? this is like telling apple 5 years ago that they should move to a kernel that is unix based and open source (bsd anyone?). of course, they would have laughed in your face.

    microsoft is like any capitalist entity...they are there to make $$$. apple has gone the way of an open and stable kernel. they decided to forgo the waste of money that is kernel development and use a system that is currently open, supported, and doesn't have to be bought. apple figured that they shouldn't have to spend money on something they clould have for free. why not M$? apple doesn't make their money based upon the kernel. they make their money because their proprietary interface (and hardware...yada, yada, yada...). same is true with windows. if the the NT kernel changes to an open source kernel, the interface is what will matter. instead of useing X11 they use their own GUI server...

    on another note...if M$ becomes more compatible with open source software (on a kernel level), then one of 2 things are going to happen. either 1.) M$ will expand because they will have the ability to run and develop software that will work on open systems (even if the binaries are closed), or 2.) they will open the door for open source os's to penitrate the market.

    --
    I'm not always the brightest pixel in the stream
  116. Dumb idea... by Alomex · · Score: 1, Flamebait


    This pressumes that the Linux kernel is in anyway superior to the WinNT kernel, which it isn't.

    There are many reasons to be enthusiastic about Linux and the accomplishment of a group of volunteers assembling a Unix clone is remarkable.

    However in our enthusiasm for OSS we should not lose sight that linux is a reimplementation of a 30 year old operating system (although admittedly a very good one, that has seem some updates along the way).

    In other words, Linux is the open source implementation of a VW bug. The state of the art is way ahead of this (both in car and OS design).

    Mach, the NT kernel, BeOS, AtheOS are examples of where an OS can be. The Apple UI shows what a decent toolkit and window manager ought to look like.

    There is still much work to be done before linux is a state-of-the-art OS worth replacing the NT kernel.

    1. Re:Dumb idea... by evilviper · · Score: 1
      linux is a reimplementation of a 30 year old operating system

      And all cars today are just reimplimentations of the Fort Model-T.

      Let's here it for gross oversimplification!
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:Dumb idea... by Alomex · · Score: 1


      And here I was thinking that the goal of linux was to reimplement Unix on a PC as indicated by Linus from day one...

    3. Re:Dumb idea... by evilviper · · Score: 2, Informative

      Linux is a Unix-like system. However, the fact that it is partially based on a 30 year old design does not make it any less advanced.

      Saying: ``The state of the art is way ahead of this" about Linux is like saying the same thing about a recent BMW. Just because it has roughly the same design as something that is very old, does not mean that the modern implimentation is less advanced by any means.

      You could say the state-of-the-art desktop computers of today are obsoltele because they are all based on the Apple II. Sure, technically true, but it's such a gross oversimplification that it doesn't hold up.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    4. Re:Dumb idea... by Anonymous Coward · · Score: 0

      nah, it was to reimplement Minux, which was a UNIX like OS.
      So it's to reimplement a unix like OS, based on a UNIX like os, LINUX is not UNIX like,

    5. Re:Dumb idea... by Alomex · · Score: 1

      Saying: ``The state of the art is way ahead of this" about Linux is like saying the same thing about a recent BMW.

      If Linux is so advanced, please list fifteen advanced features present in standard Linux in 2000 that were not already present in Unix/minix fifteen years ago.

    6. Re:Dumb idea... by Alomex · · Score: 1

      Look this is from another posting rated +5 Informative:

      On the other hand, Linux is a very straightforward, unexceptional reimplementation of a standard, monolithic Unix kernel, which has become very popular more or less because it works, it is free, and it was there when people needed it. Its novelty is that it allowed for the first complete Free Unix-like system (while *BSD was still in legal limbo). Microsoft could take that kernel, and modify it to run Windows, and neither they, nor we (Linux users), would gain anything...Microsoft would get an operating system more or less like what they have now, except with a pesky kernel under a free-software license, and we would get another version of Windows, which might, with the installation of an X11 server and a raft of libraries, be able to run Linux software, not that anyone would want to.

    7. Re:Dumb idea... by the+eric+conspiracy · · Score: 1

      please list fifteen advanced features present in standard Linux in 2000 that were not already present in Unix/minix fifteen years ago.

      You are joking, right? Tennenbaum was just graduating about then, The first X11 was just being released. NFS didn't exist..gcc had just started. This is just about the time Minix 1.0 was released. The GNU project just started in 1987. Sun didn't release an SMP tuned version of Solaris until 1991. Hell, this is even before TCP/IP was firmly standardized in it's Tahoe incarnation.

      There has been a huge change in the feature set of whatever 'UNIX' is today vs. 15 years ago.

    8. Re:Dumb idea... by Zorikin · · Score: 1

      Here are some more acronyms which demonstrate the point:

      DRI, RAID, LVM, PnP, IPX, SMB, AFS, QoS, JFS, XFS

    9. Re:Dumb idea... by evilviper · · Score: 1

      I don't see your your point there.

      I agree that Microsoft and the Linux community have nothing to gain by being tied togther. So what?

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:Dumb idea... by josh+crawley · · Score: 1

      The fanboys?

    11. Re:Dumb idea... by Alomex · · Score: 1

      I don't see your your point there.

      Here goes again :

      "On the other hand, Linux is a very straightforward, unexceptional reimplementation of a standard, monolithic Unix kernel,"

      which is what I've been claiming all along.

    12. Re:Dumb idea... by evilviper · · Score: 1

      And the fact that someone besides you said it makes it true?

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    13. Re:Dumb idea... by Alomex · · Score: 1


      And the fact that someone besides you said it makes it true?

      I'll let you chew on it. As you learn more about OSes you will come to realize how true it is.

      Beginners like you are bedazled by the sheer magnitude of the porting task accomplished by Linux and fail to see the quirks.

    14. Re:Dumb idea... by evilviper · · Score: 1

      Beginner? No.

      Of course namecalling is is always a popular arguement tactic here on slashdot.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  117. slashdot's new slogan by larry+bagina · · Score: 1

    Slashdot: news for nerds. Stuff that you saw on osnews.com two days ago.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  118. Cringley is channeling Abian. by ktakki · · Score: 1
    With apologies to the late Professor Alexander Abian:
    WINDOWS must be REORBITED into a NEAR-LINUX ORBIT to become a BORN AGAIN OS X


    k.
    --
    "In spite of everything, I still believe that people are really good at heart." - Anne Frank
  119. DOS emulation by jpmorgan · · Score: 1

    NT understands both the concepts of DOS programs and console mode Windows programs. cmd.exe, the command shell, is a console mode Windows program. NT is able to run real DOS programs in an emulated environment, however.

  120. What was /. thinking? by Anonymous Coward · · Score: 0
    Why the heck bother to post this story in the first place? Is it newsworthy whenever any idiot has a binary fart online and it smells vaguely like Linux?

    Sorry for the sarcasm, but this reall pisses me off. This is either the /. editors trolling for hits by mentioning something bizarre, or their posting about articles without even reading them.

    Deciding which one of those is a bigger problem is left as an exercise for the reader...

  121. They could... by dancingmad · · Score: 2, Funny

    MS could just buy Mandrake and not miss a beat...say hello to the new clippy.

    --
    "There is no time, sir, at which ties do not matter," Jeeves, (Jeeves and the Impending Doom)
  122. Maybe this is simplifying it too much but... by techstar25 · · Score: 2, Informative

    Maybe this is simplifying it too much but . . . if Apple put a nice GUI on top of UNIX and called it OS X then why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows? If the GUI is nice looking enough, most people won't know the difference, so they'd still be able to sell "Windows 2003" for $100 per copy. Now that Apple has done it, MS could probably get away with the same thing.

    1. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 4, Insightful
      why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows?

      Because Apple was willing to almost completely drop backwards compatibility. Microsoft's entire monopoly is based on backwards compatibility. If they were to say that the next version of Windows wouldn't be able to run most current programs, you would see their share of the desktop market instantly drop like a rock.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:Maybe this is simplifying it too much but... by m1chael · · Score: 0

      because microsoft doesnt build good graphical interfaces?

      --
      I know you are psychotic, but please make an effort.
    3. Re:Maybe this is simplifying it too much but... by wayne606 · · Score: 1

      > why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows

      Because there is no technical reason to do it, and it would cost a huge amount of $$$?

    4. Re:Maybe this is simplifying it too much but... by Anonymous Coward · · Score: 0
      Hmmm. I've met several people who buy a new
      computer every couple years just like they
      might buy a new car--one guy bought all new
      hardware, software and peripherals so that
      everything would have the vital DESIGNED FOR WINDOWS XP
      logo. I picked up his old system and life goes on,
      but surely there are millions like him who
      take their conclusions from others, just like

      Scientists Don't Read the Papers they Cite: Study in New Scientist. Certainly
      millions, probably billions of marketing dollars
      go into convincing us to go with the herd into
      the greener pastures and rugged SUV tamed landscapes.
      So the idea that having to get all new software
      is abhorrent to consumers is incorrect: every year
      they are prodded, exhorted, probably even extorted
      to upgrade. Many SIPRs (suits in positions of responsibility) also say "Windows
      is our lifeblood, We must upgrade!" and
      in fact its the guys who maintain the systems
      who would prefer a lower slope of treadmill.

    5. Re:Maybe this is simplifying it too much but... by Anonymous Coward · · Score: 0

      " . . . if Apple put a nice GUI on top of UNIX and called it OS X then why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows?"

      If Apple ever does that, let me know, k?

    6. Re:Maybe this is simplifying it too much but... by roskakori · · Score: 1
      Because Apple was willing to almost completely drop backwards compatibility.
      yeah, right. in particular, apple didn't include something like a classic environment. and even if they would, i'm sure i couldn't run my old 68k applications in it. worst of all, they never provided an upgrade path for developers, so everybody was forced to jump to cocoa from one day to the other! oh, wait...
    7. Re:Maybe this is simplifying it too much but... by IamTheRealMike · · Score: 1
      That's why we're lucky Wine is now under the LGPL instead of the X11 license.

      If that wasn't the case, Microsoft could come in, fill in the gaps in Wine (it's like 80% of the way there already) and presto: a version of Linux that can run Windows apps. No problemo. Fortunately they can't do that any longer, without giving it away to us all, which would of course break their monopoly.

    8. Re:Maybe this is simplifying it too much but... by ammulder · · Score: 1

      So Microsoft would need to drop backward compatibility...

      All programs would need to recompiled to take advantage of the new features...

      Right about the time Intel is ready to move their consumer CPUs to IA-64?

    9. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 1

      Well, you are forgetting cause and effect. Why are people upgrading? They upgrade because the next version of Windows promises not to be as screwed up as the current version... People are happy to upgrade because of the fact that they can keep all the current programs, and believe they will run better/faster.

      If you were to tell someone that they had to get rid of all the programs they currently use, you'd see mass migration away from Windows.

      Now, Microsoft's ability to bundle the software with the hardware would help to force adoptation, but I have to doubt that it would be nearly enough.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 1

      That's why I said they almost dropped compatibility.

      For one thing, Apple users are very unhappy that certain applications (*cough* *cough* quark *cough*) need to be run under the classic environment. Since Windows has such a huge library of third-party software, they would need to have an effecient compatibility layer (just as good as native) and keep it around for the next decade to allow everything to catch-up.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    11. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 1

      I don't consider it lucky. Microsoft has used GPL'd software in the past, and without violating the GPL. They are able to make it useless unless you have their propritary parts.

      If you think the GPL will stop Microsoft from extending open source projects, you are sorely mistaken. Not to mention that they will have an even easier time doing so with the LGPL.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    12. Re:Maybe this is simplifying it too much but... by evilviper · · Score: 1

      Despite the switch to ia64, I seriously doubt that Microsoft would leave users without decent backwards compatibility.

      Besides, it's not up to Microsoft to force users to switch to ia64. The ia64 may very well only be used for servers, and regular consumers may stick with x86 or AMD's Hammer (which does provide compatibility).

      If users wanted to switch to a 64-bit platform, they had the option to do that ever since Windows NT 3.51 was available for the Alpha (and Sparc IIRC).

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  123. Test for dos using debug. by Anonymous Coward · · Score: 0

    Windows 9x depended on dos as well.
    A simple way to see this is at a dos prompt run
    debug
    Then at the
    -
    prompt run
    -f 0:0 ffff 0
    And hit enter.
    IF it's based on dos, then it will crash as you just overwrote the interupt vector table.
    Windows all the way up til windows 98 depended on this... :D

    -Ober

  124. I agree by Anonymous Coward · · Score: 1, Interesting

    Why would microsoft LIMIT themselves by using a kernal that has licensing LIMITATIONS, which BSD doesnt. Much less the fact that BSD has a far superiour kernal than linux.

  125. Re:Erm no. More like bankruptcy. by NoMoreNicksLeft · · Score: 1

    Actually I would be upset about it. I would worry to no end, that they would be up to any number of shenanigans.

  126. Re:That's why the BSD license is superior. by Anonymous Coward · · Score: 0

    Assuming you're refering to Linus, he's a Finn (there's a not-inconsequential Swedish-speaking minority in Finnland).

    Besides, Linus isn't pimply-faced; he's HOT! I think he's married, but if he wasn't I'd fuck his hot geeky Finnish brains out.

  127. Re:I don't know about 95%.... by VoidEngineer · · Score: 1

    No, I wouldn't call you a troll. I think you've made a very good point.

    I actually hope that 95% is an inaccurate number, as I support freeware and GPL. (I run RedHat 8.0, Gnome, and Enlightenment on my homebox).

  128. Comercial free software & why it won't work fo by grantb · · Score: 1

    We have already seen with Apple that a company can sell an operating system on top of a open source base, but is it really worth it. Apple's has imposed many restriction on it's Darwin projects which have kept many in the free software community out of joining the project. The beauty of OS X is that it brings Unix to the masses and does have a solid foundation. But at what cost would this be implemented through Microsoft, their sole reason for such a move would be to convince people to stop using other implementations of Linux. What would be the advantage in having Linux running as a base for Windows, just the same as BSD/Darwin is the base for Aqua. Unless companies fully agree to the open source mind set there is little to no point. Running X11 on top of Darwin can be done yet people still opt for the Linux alternative despite the fact that a lot of open source app's will run on X11/Darwin machines it's still not the same. Also Microsoft is more than likely aware that selling a windowing system in it's self would not work and what possible reason would they have to give up such a revenue generator as Windows which allows them to fight in other market spaces. They have already used windows to support the destruction of Netscape and now it is more than likely funding the push into game console markets and everything else that is being slapped with a Microsoft sticker. If they were to build Windows on top of Linux they would then have to stop campaigning against it, and if they tell people to now embrace Linux, people will opt for the cheaper alternative and slowly the Windows and Office empire would fall and they would have to rely on the quality of their product and the ability to generate revenue in other key markets which they are currently driving into, which could be hard given that [I believe] many are currently running at a loss (xbox).

  129. It would work by Slime-dogg · · Score: 2, Informative

    The same way that MacOS works. You can distribute the binaries that sit on top of the OS. Just make sure you don't link any of the OS code into your binaries, and you'll be ok.

    --
    You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
  130. and this would help by Anonymous Coward · · Score: 0

    my stock price how?

    Splits and dividends, whoo hooo!

  131. Hey! Turn that thing off! by Bobzibub · · Score: 1

    You're just wasting power.
    Or crack some keys or something!
    -b

  132. Not aborted! by ucblockhead · · Score: 3, Informative

    That IBM/OS project wasn't aborted! It released OS/2 1.0, which was a fully multitasking OS with no GUI. I believe Microsoft was still involved when OS/2 1.1 was released. This release included Presentation Manager, the first GUI for OS/2.

    Also, your progression for DOS isn't really correct. DOS and Windows were concurrent things for years. All 16-bit versions of Windows required you to actually go out and buy DOS. They weren't just two different things from a technical standpoint. They were two different things from a marketting standpoint. It was really more like:

    DOS 3.0 >> DOS 4.0 >> DOS 5.0 >> DOS 6.0 >> Windows 95
    Windows 1.0 >> Windows 2.0 >> Windows 3.1 >> Windows 95

    --
    The cake is a pie
    1. Re:Not aborted! by mentin · · Score: 0

      I think according to the article's author, OS/2 is also based on MS DOS, may be even more than Windows - really, I could reboot OS/2 by clicking Ctrl-Alt-Del. Is not it the sign that it is just DOS?

      --
      MSDOS: 20+ years without remote hole in the default install
    2. Re:Not aborted! by quantum+bit · · Score: 2, Funny

      really, I could reboot OS/2 by clicking Ctrl-Alt-Del. Is not it the sign that it is just DOS?

      I can reboot Linux by pressing Ctrl+Alt+Del, that means it must be based on DOS...

    3. Re:Not aborted! by kasperd · · Score: 1

      I could reboot OS/2 by clicking Ctrl-Alt-Del. Is not it the sign that it is just DOS?

      I can reboot a PC without any OS by pressing C-A-D. In fact the C-A-D combination was originally implemented by the BIOS. It only worked in DOS because DOS was built on top of the BIOS. Later DOS got an optional keyboard driver of it's own with support for different keymaps but otherwise fully compatible with the BIOS driver. This driver did in fact reimplement the C-A-D combination. And most later OS running on the PC platform has some similar function bound to C-A-D.

      --

      Do you care about the security of your wireless mouse?
    4. Re:Not aborted! by Chainsaw · · Score: 1

      Think about what you just wrote for a second. Then try to imagine bolting on a 32-bit, multithreading, memory protected, virtual memory capable system onto DOS which is a 16-bit, one-task, 640kb system with no access restrictions at all. Add to that the concept of standardized drivers for everything including file systems, DLLs and all of the modern stuff that we take for granted today.

      Using the word "impossible" would be appropriate here.

      --
      War is one of the most horrible things a human can be exposed to. And one of the worlds largest industries.
    5. Re:Not aborted! by Anonymous Coward · · Score: 0

      "Then try to imagine bolting on a 32-bit, multithreading, memory protected, virtual memory capable system onto DOS ... Using the word "impossible" would be appropriate here."

      Heh -- rather than bitching about Win9x's inherit suckyness, we should all be in awe of MS's wizkids doing the "impossible".

      (Likewise, props to OS/2 2.x for doing the "impossible" of having 98% DOS/Win compatibilty on top of a modern protected mode design.)

    6. Re:Not aborted! by ReverendRyan · · Score: 1

      I can reboot while in the BIOS by pressing Ctrl-Alt-Del, therefore it also must be based on MS-DOS.

  133. 0wn0r3d! by Anonymous Coward · · Score: 0

    If I ever want MS to get root on my machine, I'll just install IIS.

    Otherwise, no thanks.

  134. Someone is already trying to do this...sorta by angryrobot · · Score: 2, Interesting

    A bunch of folks have already started working on xpde. It aims to be a "transitional" window manager to give people an easier time moving to Linux from from Windows. It's basically a Windows look-alike, but instead of being the end-all like the Microsoft idea, it's meant to give people something that simply looks like windows, so they can get past desktop-shock.

  135. New motto by abe+ferlman · · Score: 2, Funny

    Slashdot
    News for Nerds. Stuff that's never gonna happen.

    --
    microsoftword.mp3 - it doesn't care that they're not words...
  136. Their new business plan.. by jpt.d · · Score: 1

    1. Port Windows XP over to MSFT/Linux 2. Talk about evils of GPL 3. ??? 4. Profit!!

    --
    What we see depends on mainly what we look for. -- John Lubbock Now search for that bug slave!
  137. No... by hackwrench · · Score: 1

    He's referring to the X-window like portion.

  138. People have been saying this for over a year! by Anonymous Coward · · Score: 0

    I think it's nice in concept, but I'd rather have MS Office for Linux than the XP shell for Linux.

  139. Re:"Back when Unix meant typing on a command line. by su007 · · Score: 1

    I realize that using unix doesn't necessarily mean recompiling Apache, it's just an example. Unix usually implies a certain amount of efficency.. if there was a gui that could be used to compile apache I know of noone (personally)that would use it aside from new users. Why waste space and memory on a gui when you can use config.nice to recompile? Otherwise it would be called Windows. Command line not necessary on *nix? I will have to politely disagee here.

  140. Shit on ice cream by Jebediah21 · · Score: 1

    Windows needs to run on *nix just as much as we need shit on our ice cream.

    --

    Everytime you look at porn a devil gets their horns.
  141. And it was like that... by motox · · Score: 1

    And it was like that that the big mean giant became good and open sourced all it's stuff...
    and mr cringely finally got a life...

    c'mon...

  142. Actualy by autopr0n · · Score: 1

    Win9x didn't really run 'on-top' of dos, but rather 'next' to it. Their relationship was complicated.

    --
    autopr0n is like, down and stuff.
    1. Re:Actualy by zephc · · Score: 1

      hmm, much like guests on Jerry Springer.

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
  143. Don't forget 32-bit DOS as well! by CreateWindowEx · · Score: 1
    Win95 and later can also run 32-bit DOS programs (built for DOS4GW and friends), which was a really nice environement for full-screen games--use more than 640K without crapping around, 32-bit registers, etc, but still have complete control of the machine. Mmm... VGA, mode-X, writing your own joystick routines; those were the days...

    This is not a .sig--it's just something I typed at the end of my message.

  144. greece and turkey by agurkan · · Score: 1

    I had once proposed Greece and Turkey should unite to solve their problems with each other, in a discussion list. I still don't know how I thought it was possible, but Window uniting with Linux sure surpasses the craziness of my idea.

    --
    ato
  145. Re:I don't know about 95%.... by gilroy · · Score: 1

    You're not trolling and I hope I'm not, either, but what matters here is the weighted average. That is, there may be a lot more people in, say, India than the US -- but are there more people using computers?

  146. Windows Kernels, and Environments by einhverfr · · Score: 5, Informative

    but explorer.exe is not the windowing layer/api, just like Gnome is not X-Window

    Quick and dirty architectural comparisons:

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    Note these are just quick approximations. My point is that both OS's are reasonably mature and stable (baring spyware, etc.) and there are a lot of areas where both could improve, but porting Windows onto Linux doesn;t make sense for Microsoft today and is a lot more work than Cringly seems to think.

    But then this guy has never seemed to know what he is talking about

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:Windows Kernels, and Environments by SirSlud · · Score: 4, Funny

      you're bang on, man

      again, we think, who combines the awesomeness of *nix with the gui wikedness of XP? Oh yeah, apple! ;)

      --
      "Old man yells at systemd"
    2. Re:Windows Kernels, and Environments by Osty · · Score: 1, Redundant

      X server -> GDI.exe

      First off, I hope you really meant gdi32.dll and not gdi.exe, as the various system files ending in .exe like gdi.exe and krnl386.exe and so on are only around for compatibility reasons for WOW (Windows on Windows, or the Win16 subsystem). Look at the file information on gdi.exe, for example. The version is not 5.1.2600.1106 (XP sp1), but 3.10.0.103 (ack! Win3.1!). Second, GDI is more like X's programming interface rather than the X server. It gives you all of the drawing primitives, and little more. In XP and later Windows operating systems, one could consider Terminal Services to be like X, since it's been integrated to handle all logins (even those while sitting directly in front of the computer).


    3. Re:Windows Kernels, and Environments by apweiler · · Score: 3, Informative

      Window Manager -> Explorer.exe

      I disagree here. I don't know much about Windows internals (and I've *never* used WinXP...), but Explorer.exe is probably more equivalent to something like Konqueror (or even KDE as a whole) - integrated Browser/file manager/desktop environment. The window manager would probably be integrated in GDI or something. Hell, I've had (on Win98 though) Explorer.exe crashed and killed, but the system was still sort-of-running, with some windows open (well, the 'end task' box you get when you press Ctrl-alt-del).

    4. Re:Windows Kernels, and Environments by Mars+Hill · · Score: 1

      Cringley has fabulous idea here. Similar to the Mac OS X on top of Mach/BSD thing. The x86 architecture is the same, endieness is the same, system calls are different, but abstractions and wrappers could be written to compensate. Sure there would have to be a crossover API (analogous to Carbon), but in the end a closed source (and a large one at that) on top of the stable extendable 2.4 kernel would be the bomb.

    5. Re:Windows Kernels, and Environments by Anonymous Coward · · Score: 0

      They could just extend WINE, then setup binfmt_misc to run "legacy" EXEs with it...

    6. Re:Windows Kernels, and Environments by Genom · · Score: 1

      The idea itself is fairly sound - but his approach to it needs a bit of thought.

      Linux isn't where MS would go if they decided to base an OS on a *nix backend - there are simply too many licensing issues with GPL'd code and MS's Proprietary nature. That having been said, they'd most likely take the same route Apple did with OS X - build on top of one of the BSDs. Under the BSD license, they could take the core code, modify it to their heart's content, and realease it under their same, existing business model.

      What this would ammount to is a Windows API on top of BSD - similar to what the WINE project is trying to do under Linux, except (most likely) not open-source. They could even follow Apple's lead, and release the code to the BSD "core", while keeping the layers above that closed off.

      It's not a bad concept, really. It would more than likely add some stability and security over WIn2K and XP (both of which, I will admit, are far more stable than their predecessors). Opening the "core" would be good PR, in much the same way Apple opening Darwin up was good PR.

      The total stability/security of the system would, as always, depend on what is installed and enabled by default. MS doesn't have a very good track record here, but it's not out of the question for them to get better.

      It could be a VERY good move for them, long-term. But they would need to weigh the benefits versus the drawbacks of leaving their NT core (which, if nothing else, has an immense ammount of driver support, both from MS, as well as 3rd parties).

      I doubt it'll ever happen - but nothing's entirely impossible =)

    7. Re:Windows Kernels, and Environments by Oculus+Habent · · Score: 1

      While the concept of putting Windows on Linux (BSD is more likely, as you mentioned) is a great thought, I agree that it would be a huge undertaking. The changeover would essentially need to happen in the same manner as the Mac OS X conversion - with the previous operating system running as well to manage old apps.

      The large problem is that Windows relies of a huge assortment of components at various levels of the OS, which would all need either a further layer of abstraction to change, or to be re-written for a new OS.

      The change could be a good thing as well. Moving to another OS might require Microsoft to fix some of their outstanding issues with security, but ultimately the project would involve a huge time investment for Microsoft and every hardware and software vendor who wants to survive in the plan.

      The financial strain on Microsoft could be handled - the initial expense of converting the Windowing System would offset the reduced expense of the OS for years, most likely. It's the vendors who would suffer - thousands of them collapsing under the sudden burden of a complete re-design of software and drivers that have been built upon Microsoft quirks and hacks for years.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  147. Multiuser OSs are usefull by autopr0n · · Score: 1

    If you don't need the features, don't use 'em. A good multi-user OS is helpfull for families so that diffrent members can have their own book-marks, files, desktop backgrounds, etc. Sure, you don't need a multi-user OS to do that, but it makes it a lot cleaner.

    It's also nice to be able to throw an OS you're used to up on a server, or whatnot.

    --
    autopr0n is like, down and stuff.
    1. Re:Multiuser OSs are usefull by mystran · · Score: 1
      This is where XP is clearly ahead of Linux with it's fast user switching. Telling my girl-friend to switch to console, start another X at first available screen is quite a lot harder than just hitting windows-L and having your processes thrown to background.

      Disclaimer: I'm a Linux user since '95 and still trying to resist the temptation to switch to Windows XP. Mainly staying because I like to develop on Linux, and I like having the source. Pretty much everything else on Linux sucks, if you don't spend ours to configure it (once though, but still).

      --
      Software should be free as in speech, but if we also get some free beer, all the better.
    2. Re:Multiuser OSs are usefull by SkunkPussy · · Score: 1

      "multi-user OS" means that the OS is able to support tasks running as different users, without them interfering with each other. It is more concerned with the security (ie I can't read memory that your task is running in and e.g. find out the password to your mail account). The phrase "multi-user OS" is less concerned with the fact that different people could use the computer at different times, yet it will keep their settings for them.

      Any modern OS will be multi-user, simply because it is more secure to restrict system services to the minimum privileges required to carry out their task. This is for the same reason that you should't run your {linux,windows} box as {root,Administrator}.

      hope this helps

      frankie

      george bush is a joker

      --
      SURELY NOT!!!!!
  148. Re:That's why the BSD license is superior. by Anonymous Coward · · Score: 0
    (there's a not-inconsequential Swedish-speaking minority in Finnland)

    according to the finns i've met, the only consequence that the swedish-speaking finns have is that they force everyone to learn swedish b/c of them; otherwise they are of no consequence.

  149. Won't happen by sfe_software · · Score: 1

    Windows has far too many kernel dependancies (if that's the right term) for this to happen. Think about this: how do you implement DirectX (as an example) in Linux without serious kernel hacking? I doubt something this low-level -- something that requires cooperation of all sound/video/input drivers and many internel kernel hooks -- could be done with a module.

    Someone else pointed out that all hardware drivers would have to be rewritten. Filename/path conventions (backslash != forward slash), not to mention the underlying filesystem, has to change. Filesystem attributes (ACLs, etc) have to be implemented.

    Then you have the multi-thread capabilities. I don't know where Linux is at on that currently, but I don't honestly think it's up there with Windows, or at minimum we're talking serious differences in implementation.

    And what of applications? The strong-hold Microsoft has on the PC market lies primarily in a) hardware/driver availability, and b) software availability.

    Even if you s/Linux/BSD/, the above all still applies.

    And seriously -- is the Windows 2000/XP core bad enough to warrant replacement? I don't think it is, personally. The vast majority of the problems I have with Windows is the applications on top of it (IIS, MSIE, Outlook, etc). The OS itself is pretty solid, honestly, as long as you have decent hardware (and drivers). Yes, there is TONS of room for improvement, but that doesn't warrant dumping the entire core and starting with something new...

    So no, won't ever happen, and not because of pride or anything else -- it won't happen because it's not necessary, and would be a very bad decision, both technically and from a business point of view.

    Apple was a completely different situation. For one, they control the hardware, so compatibility and drivers weren't an issue. I don't know much about the previous Mac-OS versions, so I really don't know if it was technically necessary or not, but in the end it seemed to have been a good decision (it sure made me suddenly crave a Mac, something I thought would never happen).

    In my opinion the article (and author) is a bit uninformed. He had some of the tech terms right, and sounds reasonably intelligent, sure, but I don't feel he understands the underlying issues. Sounds more like an attempt to jump on the "MS sucks, Linux Rocks" bandwagon, by pointing out some far-fetched "wouldn't it be ironic?" scenerio...

    --
    NGWave - Fast Sound Editor for Windows
    1. Re:Won't happen by Anonymous Coward · · Score: 0

      "Someone else pointed out that all hardware drivers would have to be rewritten. Filename/path conventions (backslash != forward slash), not to mention the underlying filesystem, has to change. Filesystem attributes (ACLs, etc) have to be implemented."

      No problem there. The OS kernel doesn't care about how a command shell takes its input from the user. And Linux has several filesystems to choose from, some of which do support ACLs. Conversely, NT-XP does run on FAT filesystems if you so choose, so ACLs etc. isn't a show-stopper.

      "And seriously -- is the Windows 2000/XP core bad enough to warrant replacement?"

      This is the real issue. Technical matters can be worked out, but why bother? There's nothing really wrong with the OS part of XP that can't be fixed; no need to throw the baby out with the bathwater. In that respect, Linux is hardly a panacea for Windows' ills.

      Right now the biggest problem that I have with Windows (security issues and bloatware aside) is that the UI becomes unresponsive way too often. With Win9x the problem was MPREXE.EXE and 16-bit non-reentrant code. So why does all-32-bit NT-based Windows XP still become unresponsive so often? I suspect that replacing the NT kernel will not fix this problem.

    2. Re:Won't happen by glenstar · · Score: 1
      I suspect that replacing the NT kernel will not fix this problem

      In the mid-90's. when I had a short contract out at the MS campus, I got to meet a couple of the NT 4.0 kernel guys (it's funny, the only smokers at MS tend to be the kernel and VC++ teams). There were rumors, completely unsubstantiated mind you, of the possibility of the next version of Windows supporting "Plug and Play Kernels". While the mechanics of this were never made clear to me, the possibility to boot Windows with the stock kernel, then turn around and boot it with say a *BSD kernel are pretty neat. Possible? Maybe, but not without a fuckload of work.

  150. Riiiiiiight..... by Tsali · · Score: 1

    Okay....

    Bill Gates is going to throw out twenty years of R&D on his own server (now home) operating system and is going to adopt some GPL style OS underneath it. Then again, if Mono ever makes critical mass, you could probably pull such a feat, ironically, in Linux.

    I also predict Saddam Hussain will be a born again Christian by year's end. And pigs do fly.

    J.

    --
    This space for rent.
    1. Re:Riiiiiiight..... by Anonymous Coward · · Score: 0

      > I also predict Saddam Hussain will be a born
      > again Christian by year's end

      Wow, he'll become as pig headed and war-mongering as Bush!
      Eak, we are in shit!

  151. Re:Erm no. More like bankruptcy. by Anonymous Coward · · Score: 0

    Sure, maybe the average joe's might sell their stock. so that leaves what, 98.5% still in the hands of the MS board of directors? bankrupty with $40 billion of non-stock cash in the bank? ya, maybe if they made no profit for 150 years, hired on 8000 more people every year... you get the picture.

  152. yes, he is. by autopr0n · · Score: 1

    Well, actually he's not an idiot in general but this time he's talking about something he does not understand.

    (btw, Apple didn't port anything, they wrote their own version of UNIX and then wrote a compatibility layer for their old stuff. )

    Anyway, The entire basis of the article relies on a false premise, that Windows XP is still based on DOS. He offers cmd.exe as evidence. But the thing is, M$ already did what apple did, years BEFORE apple when they wrote NT. NT does most of what Unix can do, and it doesn't need to be replaced by Linux for any reason.

    --
    autopr0n is like, down and stuff.
  153. Two reasons by autopr0n · · Score: 1

    Apple put a nice GUI on top of UNIX and called it OS X then why can't Microsoft develop a nice GUI to go on top of Linux and just call it Windows?

    1) Linux is GPL'd and Microsoft would have to release a lot of their secret sauce, which they loath to do.

    2) It would be retarded.

    --
    autopr0n is like, down and stuff.
  154. Huh? by Anonymous Coward · · Score: 0

    WTF kind of crack are you on, dude?


    Windows 95 was not an OS because it sat atop a 16-bit protected mode bootloader


    Utter nonsense. You obviously don't know what the heck you're talking about. Here're the steps taken during Win9x/ME initialization:

    - Real-mode DOS is loaded, as usual.
    - win.com is executed.
    - win.com loads the vmm32.vxd image into RAM, and executes it. vmm32.vxd is essentially an EXE.
    - vmm32.vxd creates the GDT, IDT and the necessary paging structures, and switches the system to protected mode -- DOS ends right here, its subroutines are no longer called. They simply CANNOT be called from protected mode, unless called via a V86 task rerouting the calls to DOS itself. Want proof? Create an empty Win32 project in, say, VC++, and try executing any "harmless" DOS (or BIOS -- doesn't matter) interrupts. See what happens. The system will fuck up.

    (the rest is besides my point, but anyway, here)
    - vmm32.vxd loads the vxd's necessary to revive the devices present in the system.
    - explorer.exe is loaded, and you see the system shell.
    (I didn't bother to list the numerous DLL's which are loaded in the process, since it's got nothing to do with what I have to say)

    That's it. From here and on, the vmm32.vxd's subroutines are as deep as a system call can go, and you cannot access DOS at all -- it is not touched until you kill Windows and return to DOS from the shutdown menu. One exception to that is if you've loaded any real mode device drivers during bootup (not likely, but possible) -- this touches real mode code, but not DOS itself. So any claims that Windows somehow "sits atop" of DOS don't make sense at all. DOS is needed to *load* it, yes, but it's something that's done only once.

    That "16-bit PROTECTED MODE _BOOTLOADER_" part makes no sense to me, either. In the case of DOS, the *final* bootloader is the SYSINIT subroutine of io.sys, which is executed in REAL mode. In NT, the bootloader specifically responsible for NT's boot process is ntldr.com, and it also starts out in real mode. The only difference from Win9x/ME here is, that NT does not offer a 16-bit operating environment in-between the bootloader and NT itself.
    Your comments do partially apply to Windows 3.x, but you haven't even mentioned that system.

    Get your facts straight, or your next remark will be just as lame.

    1. Re:Huh? by The+Bungi · · Score: 1
      I said I could nitpick that, and you just did. Thanks for your trouble.

      WTF kind of crack are you on, dude?

      Next time, log in or FOAD.

  155. NT and VMS by mattdm · · Score: 1

    The NT core didn't come from VMS. One of the key developers was an import VMS person, and so there's some shared concepts, but it's a whole new beast.

    1. Re:NT and VMS by Anonymous Coward · · Score: 0

      Oh, do you know, as a fact, code wasn't brought in from DEC? Unless you are this 'import [sic] VMS person' himself, I doubt you can make this claim.

      (just someone who worked for a company which got nailed with a code audit after hiring talent from a competing company).

    2. Re:NT and VMS by vistas · · Score: 1

      Microsoft hiring Dave Cutler (and eventually some members of his group at DEC) was a pretty high profile event. You can be sure there were lawyers on both sides watching how everything was going

  156. Your sig? by autopr0n · · Score: 0, Flamebait

    Well, slashdot wasn't an apple zealot orgy when first started using the site (like 99 or 98). The apple crap only started up about a year so ago.

    --
    autopr0n is like, down and stuff.
  157. Re:Err make that X -bbp 32 :1 by Anonymous Coward · · Score: 0

    Err make that 'X -bpp 32 :1'
    need the 32 bpp for the dual slot sbus
    framebuffer. getting sleepy
    But seriously I'm always amazed at the
    cool shit that you can do with X that if
    you were raised on mac, os/2 or microsoft
    you wouldn't even think possible.

  158. I'm not sure which is funnier... by Anonymous Coward · · Score: 0

    this guy's post or that he scored "2 interesting"...

  159. Re:I don't know about 95%.... by n3m6 · · Score: 1

    good point..
    also .. in many countries that can't afford to pay windows licenses have pirated copies of it to run. ;)

    making the 95% a very realistic figure.

  160. But what about the balance?! by Cyb3rt3k · · Score: 2, Interesting

    If for some mysterious, magical reason Windows would be built on Linux, I think it'd be a Bad Thing, not for any technological reason though, but for economical reason.

    A healthy capitalist system requires a diverse eco-system, in this case, various technologies to compete, something like this would just tip the balance too much on one side. The ideal situation is that you have multiple operating systems with roughly equal market share, so they compete against each other to gain more market shares, but ideally, they only temporarily gain a lead.

    I'm pretty certain the open-source movement generally agrees that different approaches to one problem, is a good thing, like KDE, Gnome, Window Maker, BlackBox, etc. No window manager should ever completely dominate the others, because then it stifles improvement.

    *puts on an absestos suit* I wonder how much I'll be flamed this time for posting...

  161. Apple by Morthaur · · Score: 1

    Microsoft should have followed Apple's lead and ditched the Windows codebase in favour of an abstraction layer. Maintaining backward compatibility over ~20 years worth of products, and building on a codebase that, while admittedly supperior to 9x, is still more than 10 years old is never going to result in real power and stability. There's just too much bad work in there that everything else depends on; if they fixed all the errors, half the applications written to run on it would probably break!

    --

    +++++++
    "Look, dear, it's a crazy hairy scary man!"
    1. Re:Apple by drsmithy · · Score: 1
      Microsoft should have followed Apple's lead and ditched the Windows codebase in favour of an abstraction layer.

      They did - ten years ago with Windows NT 3.1.

      [...]and building on a codebase that, while admittedly supperior to 9x, is still more than 10 years old [...]

      The code*bases* of most OSes around today (in common use) would be around this age (give or take a couple of years). BeOS is probably the youngest, and even it started circa 1992, IIRC.

      There's just too much bad work in there that everything else depends on; if they fixed all the errors, half the applications written to run on it would probably break!

      This is precisely what did happen when they made NT, which is why they had to write Win95 (and then drag it out through 98 and Me). Practically Win95's sole reason for existence is backward compatibility (the only other one being performance).

  162. NeXT. by Anonymous Coward · · Score: 0

    Five years ago, would anyone have thought that Apple would use someone else's OS to run their UI?

    Yes. NeXT. Based on Mach. The difference between the Open-Source kernel (Mach) and the Open-Source OS (BSD) is fairly unimportant, especially since the important stuff (NeXTStep/Carbon/Cocoa) is still proprietary. And it was well known that Apple had completely fucked up their own Next-Gen OS and needed to get something to rescue their hopelessly obsolete system.

    Anyway...

    His "benefits" of moving to Linux or even BSD are wrong. BSD was orders of magnitude better than OS9; the NT kernel, on the other hand, is one of the most advanced systems out there - it's the stuff that's build on top of it that Microsoft fucks up. Moving to a new underlying OS would just make things worse in pretty much every conceivable way.

    He's doesn't know what he's talking about, and he drones on like he's an expert - that's makes him an idiot in my books. Sure, he's right, the user wouldn't care what the underlying OS is, if it worked perfectly - which it would never, ever do. Just ask anyone who runs OS9 apps on OSX.

    If, five years from now, Microsoft's OS is hopelessly behind every other operating system out there (a rather unlikely scenario), it might be possible. Right now, it doesn't make sense in any possible way except maybe on Bizarro World.

  163. Windoze based on a unix micro-kernel by Anonymous Coward · · Score: 0

    AFAIK windows has a POSIX compatible micro-kernel underneath it

    1. Re:Windoze based on a unix micro-kernel by Anonymous Coward · · Score: 0

      "AFAIK windows has a POSIX compatible micro-kernel underneath it"

      That's either the most clever bit of satire in this thread, or it's every bit as dense as Cringely's piece.

      For those who don't get the joke, a microkernel and API elements like POSIX are mutually exclusive items.

  164. Apple had a good reason by Imoen1337 · · Score: 1
    Apple had a much more compelling reason to adopt Mach for OSX: They desperately needed to get a modern OS out to replace the very outdated OS 9.x kernel. After their Copeland vaporware debacle, they had little choice if they wanted to remain at all competitive but to look for some other premade kernel to build from.

    Cringely states that Microsoft should, for no apparent reason but PR, scrap the NT kernel and move everything onto linux - which, in technical terms is not as modern as the NT kernel. Why would any company want to invent a huge amount in change for change's sake? Microsoft may be a bunch of lamers, but they aren't stupid.

  165. UNIX was already dominant by Trepidity · · Score: 1

    By the time anybody cared at all about UNIX on the PC, UNIX was already quite dominant on "enterprise-level" hardware (at least compared to VMS).

    1. Re:UNIX was already dominant by Anonymous Coward · · Score: 0

      Actually, UNIX was a big joke for "enterprise-level" applications in ~1990.

      It was popular on workstations, and the difference between a "workstation" and a "PC" is just one of semantics and price tags.

    2. Re:UNIX was already dominant by Alien+Being · · Score: 1

      Actually, UNIX was a big joke for "enterprise-level" applications in ~1990.

      Snake oil?

  166. cringely crap, typical of slashdot tabloid (tm) by vvikram · · Score: 1


    really this guy is talking rot. imho i always feel people who say things like `i am smart, i have contacts` [see about cringely portion] blah blah...suck. overrated sensationalist crap. the true folks keep quiet and allow their work to talk instead.

    can i say i have noticed that slashdot is becoming like a news rag hyping up people and technology [ooh...its MS bashing time]. similar to cringely, personally, i think lessig is overrated, i am right now in stanford and have seen his works and heard him speak. but then again i guess this site is full of such dual confused philosophies ? [we hate blizzard, i cant wait for next release, we hate m$ but this problem has nothing to do with it, free software rulez, lets beg for the money, linux rulez but how can redhat change a theme *gasp*, we develop software for passion not money , how can someone make money out of it *so bad*]

    it was nice initially . now its quite painful to read most of the stuff. news.google + bottomquark + ars technica + cnn makes a good alternative seriously

    sorry for the long mail. my $.02 . no offence

    vv

  167. Hrm... by autopr0n · · Score: 1

    D:\WINNT>DEL TREE /Y C:/ Invalid switch - "Y".

    --
    autopr0n is like, down and stuff.
  168. yeah... by panic911 · · Score: 1

    Ultimately this is what all you linux geeks really want - but if it happened, would you really be happy with Microsoft? I have a feeling everyone would still find reasons to bag on microsoft...

  169. no. by knowledgepeacewi · · Score: 1

    No.

  170. Wine by Anonymous Coward · · Score: 0

    How is this different than what WINE could become? WINE could eventually run everything. What is the point of Windows anyway cnsidering there are alternitives. And running Windows on Linux is Linux running an API layer. I guess this would be like Mac OS X.

  171. Mike Class is the fall guy by cygnusx · · Score: 1
    Note how well Cringely has set him up: from the article:
    And if it ever happens (the ring-kissing, I mean), don't forget Mike Class in Milwaukee, who came up with the idea in the first place. I don't know if Jesuit friars are allowed to accept big checks from corporations, but I'm sure Marquette University could always use the money.
    I think Cringely was molested by Jesuit Priests or something when he was a kid, he's getting his jollies by seeing this poor man being turned into a laughing stock. Or maybe he hates Marquette U., where this poor sap teaches.

  172. Cringly is right by gregm · · Score: 1

    but for the wrong reasons. As has been pointed out here quite a few times a c:\ does not indicate dos is the underlying operating system. I've got a c:\ prompt on my linux dos and I doubt anyone (well no one intelligent) would try to claim my Linux box is running on top of dos. There is an operating system down there somewhere though and it doesn't require clicking to make it go.

    All those flashy clicking things in Windows are not part of the operating system. They're not built into the kernel, nor do they talk to the hardware directly. They are part of a windows manager running on top of an operating system. In this, I agree with Cringly's conclusion. Windows is not only a winodws manager, it's also a giant visual basic interpreter that is designed to let even the most clueless vb weenies crank out shitware. This is why windows has done so well financially and so poorly in the areas of security and stability.

    Microsoft's biggest problem is backward compatibility. They cannot afford to break the cycle of backward compatibility like Apple did. Sure some things break here and there but it's pretty amazing to me that I can fire up some old program from the early 90's and it usually runs. This is their downfall. All this old cruft has to be dragged on and on to each new version of windows.

    It would not be a simple task to make the clicky flashy thing called windows run on top of Linux and keep all those old 16 bit apps working. In order to pull this off they'd have to translate windows system calls to linux systems calls. In other words, they'd have to write Wine. Now they could certainly have an easier time of it than our current wine team since they have that source code and could legally use it.

    Should they do it? Hell yeah they should... they're losing the battle and it will get worse and worse for them unless they can take over even more of the government and make the GPL illegal. If they fail to get the mindless sheep of the world to sign up for the Digital rights crap they'll need a plan B. They could roll out their own version of wine, support only the most modern 32bit or even 64 bit apps with a smaller, cleaner API and start doing it right. They could continue to milk their dos/windows until it runs out. This could get them out of the lukewarm water they're in with the DOJ and give them a real product that might even be worth buying.

    Of course they won't do this since the GPL "should" put a stop on their embrace and extend tactics. Plus I doubt they'd let themselves be at the mercy of the Linux kernel guys.... imagine Microsoft having to play catch-up with changes in the underlying APIs.... not likely. Now how about BSD though? The BSD license would give them the control that they would require but BSD (The os) doesn't have the name that Linux does. By name, I mean name recognition. I don't wish to start a BSD/Linux flame war. A BSD/GPL flame war on the other hand might be worth another look.

    G

  173. Recent experience by Anonymous Coward · · Score: 0

    Recently I've been playing with .NET to see what all the hype is about and I have to say, I am not impressed. For example, lets take threading as it is done in .NET.
    The default limit for System.Threading.ThreadPool is 25. Now the limit in and of itself is a clue as to .NET scalability. If your application doesn't have a lot of concurrent use, it's not a problem. But if on the other hand you are building a heavy weight application that needs to do lots of things in parallel or distributed, 25 threads probably won't be enough. For applications like websites that are stateless, no big deal. For a company that aggregates products from dozens of other companies, it's a huge problem. Say you're a travel agent that specializes in package deals that include hotel, airlines, dining and rentals. If any one of the items are no longer available, the package can't be sold. This means your application has to maintain state about a lot of data. Not only that, it has to have a way of resolving conflicts and/or recommending other pacakges or offering additional options.
    It's obvious in an application like this, you will easily use a dozen or more threads if the data has to be retrieved at transaction time, since that kind of information changes frequently. Now if your server has to serve every state in the pacific time zone, that could be thousands of requests per second. With a thread limit of 25 per threadpool would mean multiple threadpools. But at what point can you have threadpool of threadpool of threadpools without killing the server every minute. In a scenario where your system has to support high concurrency, .NET simply won't scale because the underlying COM/COM+, Win32 DLL's are flawed.
    Should windows use linux? In many cases I would say yes, but over all no. The problems in windows API and DLL's are not well suited to server environments, so it's not a light task. I'm no expert with windows API, so I could be wrong and over generalizing. Hopefully if I am wrong, someone will correct me and provide the correct information.

    1. Re:Recent experience by glenstar · · Score: 1
      Hm... I am running RC1 of .NET Server on a lowly P200/256MB RAM. It works (nearly) flawlessly. From this lowly machine I am hosting a prototype web site that is pretty resource intensive. I tend to eat up the upstream bandwidth (384Kbps) before my machine maxes out.

      I am actually disturbed by how solid .NET Server is (as well as the entire .NET platform). I installed it originally just so I would have ammunition *against* it. Now I am actually using it for something productive.

      While I haven't installed it on any bigger iron, I would imagine that it screams. I think that MS finally did something right with .NET Server. It feels like a turbocharged Win2k with lots of extra perks on the backend.

  174. PET PEEVE by Anonymous Coward · · Score: 0

    hey... it's spelled:

    K E R N E L

    though its constant misuse has no doubt rendered this point moot. still, i'm full of a deep, burning hatred for you.

  175. Moderators? Hello, where are the moderators? by Anonymous Coward · · Score: 0

    Out to lunch I suppose.

    This troll, captainclever, is just here to slander. Speculate on Microsoft venturing into its bloodbath of openGL, GTK, Motif, Linux; it's speculation. This troll begins by saying the X Window Sysems is slow: It is obvious captainclever has no merit, because no evidence is provided on any such claims and no resolutions are provided that define the purpose of such software.

    The moderators are supposed to moderate these posts accordingly into Troll heaven; c'mon, the post was supposed to be -1, but +3 is rediculous for mis-leading everyone and blithering information no different that what can be found in a recipe book for chocolate-chip cookies. Moderators, you have failed slashdot and knowing your disgust in everyone's eyes; will probably moderate this verry post down instead of the troll I am responding to.

    Such a sad event to see slashdot slowly drift into a sad state of depression in its journalism...

  176. Separation of operating system and windowing by Animats · · Score: 4, Interesting
    There are arguments for a strong separation between the operating system and the windowing system. NT 3.51 really did have a strong separation between the two. In NT 4/2000/XP, the graphics subsystem moved into the kernel, over the objections of Dave Cutler, the primary architect of NT. This wasn't done to improve performance; it was done so that Windows 95 code could be reused in NT 4, giving NT and Win95 closer graphics semantics.

    More and more junk has been going into the kernel ever since. The multimedia codecs have moved into the Win2000/XP kernel, for example. Start coding your viruses now.

    1. Re:Separation of operating system and windowing by Anonymous Coward · · Score: 0

      "In NT 4/2000/XP, the graphics subsystem moved into the kernel, over the objections of Dave Cutler, the primary architect of NT. This wasn't done to improve performance; it was done so that Windows 95 code could be reused in NT 4, giving NT and Win95 closer graphics semantics."

      Interesting. I'd like to know more about it not being a performance issue. Linkies?

      Whatever the rationale behind the move, having a single user be able to crash a multiuser WTS box by doing something as basic as printing a document is totally unacceptable. I'll take X over RDP (or even ICA) any day!

    2. Re:Separation of operating system and windowing by Animats · · Score: 1
      I'd like to know more about it not being a performance issue. Linkies?

      Not any more. Microsoft leaned on the guy behind NTinternals.com to stop publishing stuff like that. NTinternals.com also had the famous "NTcrash.exe", which made random system calls while recording what it had tried. You'd run it for a few hours, and, a few autoreboots later, it would have a list of exploits ready for you. Microsoft leaned on Mark Russinovich to take that down, too.

      There's a general feeling that interprocess communication is expensive, but that's because UNIX does it badly. It was an afterthought in UNIX, as were threads and locking. Those are really the most fundamental operating system operations, and to get them right, the kernel has to be designed and optimized for interprocess communication.

      Take a look at QNX, which can do a million or more interprocess communication operations a second. That's how it should work.

      QNX is something of a specialist operating system, mostly used for industrial real-time control. But if you can use Linux at the command line, you'll find QNX easy to use. It's Posix-compliant, and all the GNU command line tools have been ported. There's a GUI, called Photon, and it's all in user space.

      If you want to play with QNX, download their free version as a CD image. This makes a bootable CD workable on most x86 machines. You can boot it and run without touching the hard disk, which makes your machine an "Internet appliance" - you can connect via dialup or LAN and browse. It's just like the i-Opener, which was powered by QNX. Except that it runs both Voyager, their little browser, and Mozilla. (If you see slow graphics, it's probably because QNX doesn't have a driver for your graphics card, and defaults to VGA or VESA mode. Check the supported hardware list.)

      But you only do that to see that it works. Then you install it into a disk partition or on a bare machine. This gets you a QNX system with all the development tools. All the important stuff is there, but there's far less cruft than in the Windows, UNIX, or Linux world. QNX got the basic design decisions right back in the 1980s, and it shows. All the growth is outside the kernel. The kernel itself is tiny. Only about 60K of code runs in kernel mode, and that code changes very seldom and is well debugged. Drivers are outside the kernel. You can do driver development on a running system, without rebooting. I'm working on a QNX driver for FireWire cameras now, and I haven't had to reboot yet.

  177. Read the Microsoft press release... by SlowMovingTarget · · Score: 1

    Microsoft Corporation announced today the impending release of Microsoft WindowsTUX. Major features include:

    OpenDRM: Digital Rights Management software under GPL

    MDE: The new M Desktop Environment includes spinning flashing buttons you can skin!

    NoIm: NotepadImproved will automatically add ^M characters after every carriage return!

    Outlook Evolution: Use it to load test your system.

    Expel: Hyperfast CD ejection

    BSOKP: Blue Screen of Kernel Panic

    JFS: Journalist File System - automatically publishes all your files to the entire Internet so there's no need for security.

    Send Microsoft your firstborn child to reserve your copy today!

  178. They don't have to make a profit. by Anonymous Coward · · Score: 0

    Microsoft has $43 BILLION (US) in the bank.

    Even if they're incompetent at investing, they could probably still get 2% interest. That's $860,000,000 (close to $1 billon) a year. In interest alone.

    Considering that a smart investor (ie: not me) can achieve 12% returns in a good year - they're probably making a lot more than 2%. The rich get richer.

    They could give away every single product they ever make so long as they're allowed to invest - and they'd _still_ be profitable.

  179. I want what hes on! by Chexsum · · Score: 0

    Its crazy to think a proprietary systems maker would consider GNU/Linux - hahaha!!!

    That said it would be nice for Microsoft to release a POSIX/UNIX system because these systems have proven to work excellently and GNU/Linux needs some real competition. NT is OK but its not as easy to fix when things go horribly wrong, isnt as easy to develop and the GNU/Linux system will soon be as simple to administer *if it isnt already* as NT.

    Perhaps MS would buy Mandrake as they both give the exact same experience to the user? Theyd probably have a lot of work to do making it proprietary though *or maybe they could just slip MS Office into MS Office Linux*. ;)

    --
    Pixels keep you awake!
  180. When non-techies try to fake it... by Eric+Damron · · Score: 2, Insightful

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    This is pretty much total crap. Yes, you can bring up a C prompt. Does that mean that XP sits on top of DOS? No. What you are doing is running a type of "DOS emulator." It's not really DOS at all.

    "Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux."

    Nope... Total crap here.

    Windows, Windows 95, 98 and I believe ME are one branch. Windows NT is a completely different code base. NT, 2000 and I believe XP are all from the same code base.

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:When non-techies try to fake it... by demon · · Score: 1

      That's almost as bad as saying that because there's a command shell that you can install on classic MacOS, that it's basically DOS or UNIX underneath, while classic MacOS (9.x and before) was most assuredly neither. And here I thought Cringely actually knew something about computers. What's next, we'll find out that George W. Bush doesn't actually know anything about being President? :)

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  181. There may be some truth to this already... by neoevans · · Score: 2, Interesting

    I always had a suspision that underneath it all, Windows (NT especially) was running atop of some bastardized form of Unix. Think about it.
    What was there 30+ years ago but Unix? Isn't it the grandfather of all anyways? Try this:

    -Open the management console in Windows 2000 (the one called "Manage" when you right-click My Computer).
    -Select "System Information", expand the "Software Environment" folder and select "Loaded Modules".

    In pre-SP1 builds of Win2K the dates on some of the DLLs in this folder were in the 1970's. How can that be? Windows wasn't even around in the 70's! Isn't it possible the kernel is already based on Unix and 'Windows' is just another abstraction layer? It sure would account for the mediocre performance (added overhead).
    And some of the hardware names in the registry are Unix-like. Check:

    \HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\H ivelist
    You can see the OS locates volumes the same way Unix does. For example, the location of Registry file \REGISTRY\MACHINE\SAM is:

    \Device\HarddiskVolume1\WINNT\System32\Config\SA M

    So what if the '/' is a '\'? It's the same thing right?
    After all...

    "...The greatest trick the devil ever made was convincing the world he didn't exist..."

    I know, corny one...;)

    --
    "You are not a beautiful and unique snowflake."...Tyler Durden
    1. Re:There may be some truth to this already... by cant_get_a_good_nick · · Score: 1

      Not UNIX, try VAX. It was designed with a lot of the old DEC boys, though over the years as it has grown it has added more and more and put the VAX stuff farther and farther away in the deep recesses.

    2. Re:There may be some truth to this already... by neoevans · · Score: 1

      But didn't Microsoft own a version of Unix at some point? I seem to recall the vendor name on a Unix box that used to run the call managment server at my work was Microsoft.

      Can't recall what version it was though...

      --
      "You are not a beautiful and unique snowflake."...Tyler Durden
    3. Re:There may be some truth to this already... by ilikehardhouse · · Score: 1
      But didn't Microsoft own a version of Unix at some point? I seem to recall the vendor name on a Unix box that used to run the call managment server at my work was Microsoft.

      Xenix. M$ used to be a *nix vendor. They own some copyrights/patents on it as well - so SCO had to pay royalties to M$, as I recall.

      I found a copy of SCO Xenix in a surplus electronics store. For 15 bucks (NZ). The TCP/IP drivers (yes, sold seperately) cost $1300!

    4. Re:There may be some truth to this already... by spitzak · · Score: 1
      That was Xenix.

      The VMS guys from Dec HATED Unix, because BSD had completely wiped out their beloved VMS. The expensive new hires had enough clout to either fire or bury all the Unix supporters at MicroSoft. Their hatred is the real reason NT is so hostile to Unix.

      If MicroSoft had any business sense they would have made NT very Unix-like so that porting software to it was a no-brainer. If they had done that there would probably not be any Linux or any other Unix variant today and EVERYTHING would run NT. But emotions were stronger than sense...

    5. Re:There may be some truth to this already... by Anonymous Coward · · Score: 0

      That kind of inductive reasoning can make you the perfect dupe on April Fool's Day, but has no utility outside that. Consider this:

      The product that Microsoft is currently marketing as Windows is more like 10 years old, not 30. IBM's MVS and DEC's VMS also provided advanced OS features before Windows did. In fact, Microsoft hired David Cutler away from DEC, where he had worked on VMS, to develop Windows. On the GUI front, Microsoft helped Apple bring the Macintosh to market, and acquired certain IP from that deal.

      I regularly get e-mail from 1969, according to the date field. I could believe that people from the past are trying to communicate with me, using technology that didn't even exist back then. But maybe, just maybe the date was wrong. I once zapped the CMOS clock on a computer, then ran Norton Utilities, which "corrected invalid file dates and times" to match the CMOS time, which was 10 years before the motherboard had been manufactured. That proves exactly nothing about Windows and UNIX, same as your story.

      Early versions of MS-DOS used the forward slash "/" and backslash "\" interchangeably. Does that make MS-DOS 1.0 UNIX? Is Grampa's ancient Underwood typewriter really a UNIX computer that was magically built before UNIX was invented, just because it has a "/" key?

      I don't mean to say that speculation that requires the laws of nature to stop working to come true can't possibly be right. It's just that the likliehood of that being the case are just about nil.

    6. Re:There may be some truth to this already... by Anonymous Coward · · Score: 0

      > \Device\HarddiskVolume1\WINNT\System32\Config\SA M

      > So what if the '/' is a '\'? It's the same thing > right?
      > After all...

      POSIX dear boy, POSIX. NT is (mostly) posix compilent, this (as with hardware being accessed by a file, \Device\Sound etc) is all part of that.

    7. Re:There may be some truth to this already... by Anonymous Coward · · Score: 0

      "POSIX dear boy, POSIX. NT is (mostly) posix compilent, this (as with hardware being accessed by a file, \Device\Sound etc) is all part of that."

      One problem -- the Windows Registry is not a filesystem.

  182. Re: Apple Propaganda by Anonymous Coward · · Score: 0

    "When I grew up, I realized how stupid I'd been and acknowledged that I didn't really hate Macs, but their users. Today I might even consider buying one because of OSX, but my earlier feelings show just how much a platform can be hurt by bigoted users."

    You must understand that those "users" were reciting propaganda that came directly from Apple Computer, Inc. It's hard to know exactly how many were actually Apple employees, but it is clear that propaganda like the "Windows is DOS" confusion originated from the office of one Guy Kawasaki. With a job title of "Evangelist", Kawasaki was officially responsible for telling the Apple shills what lies to spread.

    Apple's EvangeList network, as it was known, employed such "high-tech" technology as fax machines at a time when most businesses were using _computers_ to communicate (e-mail, www, etc.). Ironic, no?

    Today the names and job titles may have changed, but Apple is still up to the same old tricks. Now they're trying to ride the coattails of UNIX fame. Now the propaganda is trying to equate BSD to UNIX, although the U of C's BSD never was UNIX, and the "baby BSDs" (OSX is a mishmash of these various incompatible distributions) are not UNIX either. And then there's the "MHz myth" myth...

  183. Lets take this one step further by JudgeFurious · · Score: 1

    Just to raise the bar some and because there isn't a doubt in my mind that some geek somewhere would give it a try (in the fantasy world where this man apparently wrote this article) lets make the very next version of Linux based on Windows.

    Come on, you know you want to do it.

    --
    Appended to the end of comments you post. 120 chars.
  184. Re:wait..... (fixed post) by JW+Troll · · Score: 1

    I think you meant to say, "so don't run Mozilla or KDE or GNOME or BlackBox or Enlightenment (especially Enlightenment!) or Nautilus or Konqueror or the GIMP then.. sheesh!"

    --
    just like the humble blood clot... turboporsche@telus.net
  185. Wanted to? by Ancil · · Score: 2, Insightful

    Microsoft has $40 billion dollars in cash tucked away.

    If they wanted to, the could be the world's biggest just-about-anything.

  186. dang.... that kinda hurts by Anonymous Coward · · Score: 0

    Windows is comprable to gnome or KDE? ouch. But KDE and gnome don't exactly sit atop Linux... or even the linux kernel. they are part of a GNU/Linux backage in some cases -- or KDE can even be run on Mac, Win32, or BSD. God this guy is ignorant...

  187. Should The Next Windows Be Built On Linux? by Anonymous Coward · · Score: 1, Funny

    no...

    i love easy questions :)

  188. PARENT POST IS +5 INSIGHTFUL by Anonymous Coward · · Score: 0

    mod accordingly.

  189. Re:"Back when Unix meant typing on a command line. by Anonymous Coward · · Score: 0

    Because GUI is easier to learn. I Know I wont be migrating untill there's a distro that locks bash out to prove that it can be used without it.

  190. f*ck linux, 8-bit atari os by Anonymous Coward · · Score: 0

    why bother with linux - go for the heart of gold of communal knowledge contained within atari 8-bit o.s.; de re atari++.

    Purchase the technical reference manuals and you've got the keys to the crystal castle along w/ Bentley the Bear, h0lmz.

    Watch out for the king bees though, whirlwinds of sting is all they are about.

  191. Explain this by Anonymous Coward · · Score: 0

    If what you are saying is true then explain why Apple was able to pull it off with OSX?

  192. Is that correct? by Anonymous Coward · · Score: 0

    Correct me if I'm wrong, but I thought Ken Thompson came up with C (from B) and unix together, and used the new C language to make the first unix?

    1. Re:Is that correct? by Anonymous Coward · · Score: 0

      You're wrong.

  193. Copy Apple? by Anonymous Coward · · Score: 0

    Actually, MS could just do what Apple did: build their OS on top of *nix and only give the source to the underlying *nix core. I think one of the appealing aspects of OS X is its pleasing looks while have a robust *nix core.

  194. drivers and drivers and more drivers.. by tewmten · · Score: 0

    all the windows drivers for hardware would have to be ported to Linux.. would be nice for me cos my soundcard isnt really supported :)

  195. Re:Erm no. More like bankruptcy. by timmyf2371 · · Score: 1
    There's the whole matter of how you make free software profitable.

    If Microsoft were to base Windows on GNU/Linux, why would they need to give Windows away, or indeed release the entire source code to a Windows release? If they built their own closed X Windowing system and a GUI similar to what they have right now, this wouldn't necessarily need to be GPL'd - similar to how OS X is based on Darwin, although Quartzextreme and Aqua are still proprietary.

    Tim

    --

    Backup not found: (A)bort (R)etry (P)anic
  196. Re: Xenix & VMS by Anonymous Coward · · Score: 0

    No, Xenix was not UNIX. It was a feeble attempt to copy UNIX, marketed at a time when AT&T was the only UNIX vendor.

    I don't know if any "VMS guys from Dec HATED Unix, because BSD had completely wiped out their beloved VMS". But since VMS is still around, and BSD is not UNIX, that would be a very illogical sentiment. I really doubt that an OS has the capacity to be "hostile", as you describe. Perhaps there is a more realistic explanation.

    "If MicroSoft had any business sense they would have made NT very Unix-like so that porting software to it was a no-brainer."

    I'm not sure why this is stated rhetorically, since MS (with $40B in cash, but never paid a dividend) obviously does have business sense, and the NT POSIX DLL is there to aid exactly such porting. But what you thought was probable didn't happen, so...

  197. Perhaps we should let windows be windows geez! by The+B · · Score: 2, Interesting

    This is ridiculous. MS persists to achieve its goals, achieve them amidst years of laughter and jokes from Mr Big Iron. Its a bit late Linux. I'm sure you'll mature, but you need the apps. Then again perhaps this article just proves what I've said before. Linux just turns more into windows with every so called improvement. Why build what already exists.

  198. it WAS done for performance! by Otis_INF · · Score: 1

    Because when the graphical subsystem should be placed outside the kernel, you would have a lot of CPU statechanges (which costed a lot of cycles) in gui applications, including a lot of messaging going on between kernel and userland. Now this is optimized and does not take place. It's however a myth that the total graphical subsystem is in the kernel, still a lot of drawing is going on outside the kernel, however the logic that controls the gui is inside the kernel and I think that was a wise decision.

    --
    Never underestimate the relief of true separation of Religion and State.
  199. Back it with facts please by The+B · · Score: 0, Flamebait

    Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve. As Mike Class points out, by not having to develop its own OS, Microsoft could also save money. They wouldn't need however many people are presently devoted to maintaining the underlying OS that isn't supposed to be there. And what actual data do you have to prove this? Our win200 advanced server smokes our Caldera server both running on the same hardware config, but then again Im comparing SQL server on win 2000 VS MySQL on Linux. Oh..thats right...I'm sorry Linux pundits..I guess this isnt a fair comparison because SQL server is optimized on windows.....Please.

    1. Re:Back it with facts please by Anonymous Coward · · Score: 0

      I don't see any facts included with your story. Would you care to explain that?

    2. Re:Back it with facts please by the+eric+conspiracy · · Score: 0, Offtopic

      And what actual data do you have to prove this? Our win200 advanced server smokes our Caldera server

      I don't szee any of your actual data.

      Places that I do see actual data, like the SPECWeb results, show that IIS is a smoking hole in the ground.

      http://www.specbench.org/web99/results/web99.htm l

  200. MS. LInux by Anonymous Coward · · Score: 0

    Hey, what are you talking about?

    Microsoft has already started developing its own version of Linux (MS. Linux)

    For details, please visit MS Linux

  201. Yes and no by lvdrproject · · Score: 1
    I've often thought about the fans Microsoft could win over if they decided somewhere along the line to build their next version of Windows on UNIX... after some thought, i've decided that while this might be a good thing, it doesn't automatically come with any benefits just "because it's UNIX". Before i proceed, a disclaimer: Linux and Windows are fairly equal in my mind; each has its own use, and they're both (in my opinion) great operating systems. I'm somewhat biased towards Windows, however (one, because of the "what i'm used to" factor, and two, because Linux is missing some major features that i look for in a desktop OS (i.e. a GUI :p)), but i can't say i dislike Linux. Just wanted to be clear, i'm not a Microsoft fanboy or anything; i can certainly see some of the reasons people dislike Microsoft and their products. With that in mind....

    Building Windows on UNIX, presumably Linux, doesn't mean anything. Define "build". Microsoft can take Linux, and taint it in any way they see fit. They would no doubt use "non-standard" calls, APIs, etc. (i'm no programming expert, heh), even if they did build Windows on UNIX. The prospect of a universal standards system is one of the things that gets UNIX guys so hot. Everything pretty much runs the same way on UNIX, no matter what distribution you have, what "form" you have (Linux/BSD/commercial UNIX/whatever), mostly not even what processor you have. UNIX is UNIX. Microsoft would certainly change that if UNIX was a factor in Windows. Microsoft wants you to buy Microsoft UNIX, and buy products made for Microsoft UNIX; they don't want to be compliant with other operating systems. As such, you've lost a high proportion of UNIX guys already.

    Assuming, however, that Microsoft did manage to make a good OS built on UNIX, and even a lot of the UNIX guys liked it, you still have the "monopoly" argument. Microsoft likes their income. They like the fact that their products are used all around the world. They're still going to employ the "monopoly" tactics. High prices, less-than-satisfying licences, FUD, Palladium-type stuff, etc.. Microsoft will never just one day turn around and start playing ball with everyone that hates them.

    Also, what the fuck is Cringely talking about? XP is a windowing system? What the Hell. Firstly, KDE and GNOME don't just "sit atop Linux"; they sit atop X, which sits atop Linux. Secondly, the ability to get a C:\ prompt in XP does not mean that MS-DOS is hiding underneath. I mean, don't they call "the C:\ prompt" in Linux a terminal emulator? Windows emulates MS-DOS.

    Anyway, really the point of that article shouldn't have been the whole thing about DOS, the point should've been building the OS itself on the Linux kernel. Either way, not going to happen. :p

  202. why?? by smash · · Score: 2, Interesting
    Why would they use Linux, when FreeBSD is available under a less restrictive license.

    Now before the Linux purists get started up and start modding me as flamebait - I use both Linux and FreeBSD (Linux since 96, BSD since 2000) and although I'm partial to FreeBSD myself, I have nothing serious against either one...

    Parts of Windows have used BSD derived code in the past, such as the TCP/IP stack (which may have since been rewritten), and MS is a lot friendlier to FreeBSD than linux (C# anyone?).

    Barring legalities, the whole FreeBSD vs Linux argument is a matter of personal preference at the moment for most people. So Linux does better SMP at the moment? How many desktop users have SMP desktop machines out there? Amongst the *geeks* maybe 10%. I've run both extensively and as far as performance goes, there's not enough in it to bicker about.

    Again, the BSD license is a lot more compatible with MS - they can base Windows 2008 on xBSD and not have to open the source up at all if they like!

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    1. Re:why?? by Anonymous Coward · · Score: 0

      "Why would they use Linux, when FreeBSD is available under a less restrictive license."

      Why didn't Apple simply use FreeBSD?

      "Parts of Windows have used BSD derived code in the past, such as the TCP/IP stack (which may have since been rewritten), and MS is a lot friendlier to FreeBSD than linux (C# anyone?)."

      BSD != FreeBSD, and I haven't ever seen any proof that Windows actually uses/used BSD code. All in all, that's a very shaky foundation.

      Rumors aside, you're saying that Microsoft should choose FreeBSD over Linux because they could easily make FreeBSD proprietary and closed. That might be true, but is it better?

    2. Re:why?? by smash · · Score: 1
      "Why would they use Linux, when FreeBSD is available under a less restrictive license."

      Why didn't Apple simply use FreeBSD?

      As far as I'm aware, they did use most of the FreeBSD userland. They used mach as the underlying kernel for reasons I don't know - possibly something to do with having another seperate virtual machine running on it to run legacy MacOS apps with? I don't know the specifics, I'm not a MacHead ;P
      "Parts of Windows have used BSD derived code in the past, such as the TCP/IP stack (which may have since been rewritten), and MS is a lot friendlier to FreeBSD than linux (C# anyone?)."

      BSD != FreeBSD, and I haven't ever seen any proof that Windows actually uses/used BSD code. All in all, that's a very shaky foundation.

      I never said BSD==FreeBSD. I merely used FreeBSD as an example of a BSD licensed codebase, as thats the most polished IMHO for i386. I never meant to imply they used FreeBSD code, but I've read credits on MS packaging before (NT 4 I believe) giving credit to Berkley university or such. Forget the exact wording, but I recall specifically thinking "hey thats BSD code" when I read it (this was 1997 or so).
      Rumors aside, you're saying that Microsoft should choose FreeBSD over Linux because they could easily make FreeBSD proprietary and closed. That might be true, but is it better?
      I never intented to imply it was better for the end user. From Microsoft's point of view, however (and they are the ones who would make the decision in the end) it makes more business sense.

      Personally, I don't care if they were to take some BSD code and put it into Windows and close it, so long as they credit it as per the BSD license (and this is likely the opinion shared by the BSD developers). Maybe Windows might actually start being functional ;P

      My point was, that there is other code out there, equivalent to Linux, with a less restrictive license. Using Linux as the basis for the next version of Windows would simply make no business sense.

      Hope that clarifies things a bit...

      smash

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  203. Short answer by inode_buddha · · Score: 1

    Hell, no!

    Long answer: Let M$ have what they've earned. Personally, I wouldn't tolerate a Windows UI on Linux, BSD, or anything else for that matter.

    Simple reason for this: I prefer a combination of Gnome/Enlightenment. That's all it is, just personal preferences. When M$ offers this combination without their spyware (ya, right!) please get back to me.

    Heck, at least with Open Source/Free Software I at least *have* choices like that.

    --
    C|N>K
  204. Been there, done that! by Anonymous Coward · · Score: 0

    It's called XPde and it's been discussed before right here on /. ;-)

  205. mslinux...shipping in November 2003 :) by Anonymous Coward · · Score: 0

    mslinux.org

    *grin*

  206. XP better than Linux (flamebait?) by forged · · Score: 2, Insightful

    From the article:

    • Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve.

    I actually have a positive experience after having -finally- moved from 98SE and ME to XP, and despite my very low expectations about XP, I have to admit that it's not working too badly after all, to say the least.

    Don't get me wrong, I'm also a happy Linux user since 1994. But with XP I can actually see Microsoft catching up with Linux regarding stability, performance and features....

    1. Re:XP better than Linux (flamebait?) by ajole · · Score: 1

      Good point. I too used linux because it _was_ more stable than 95 and 98, but even then it wasn't more stable than NT. 95 and 98 aren't Ms's biggest operating systems anymore.

      --
      -P ...and the boy pulled open his bleary eyes an discovered the python he always knew he was.
  207. No basis by ajole · · Score: 2, Interesting

    This article has almost no validity. When you use windows, you get a feeling of reliability and an *speed*. I'm writing an audio application that has very tight time-performance constraints, and I'm finding MFC's threads and gui widgets to be by far the quickest over qt. Why? its native. Don't flame me about qt not being linux. if you do you've missed the point.
    The point IS that MFC is native. N-A-T-I-V-E. In the windows sense that means its going to deal with the K-E-R-N-E-L better, and anything else that has to do with the windows platform.
    Windows XP is not just a windowing system. It is more complete than linux. I don't like XP for various reasons, but that doesn't change how a business makes decisions. point is, if this all this was true windows WOULD be, how was that? "kissing the ring of linux?"

    --
    -P ...and the boy pulled open his bleary eyes an discovered the python he always knew he was.
    1. Re:No basis by Anonymous Coward · · Score: 0

      ??? reliability and an *speed*? You are talking about Windows? MFC? the Macros? no.

    2. Re:No basis by Anonymous Coward · · Score: 0

      Reliability, Speed and Windows all dont go in a single sentance. That just makes me suspicious about the rest of your post.

  208. windows on linux by colinleroy · · Score: 1

    That would be useless - FVWM95 already exists :)

    --
    blah
  209. Need $25bn and 10 years to pull it off by Anonymous Coward · · Score: 0
    Microsoft won't be around long enough to pull it off. Microsoft loses scads on everything except Windows and Office and then only because of monopoly prices. The price will drop in geometric proportion to their market share and quickly put those two into a loss.

    On top of it Chairman Bill has put up a distress flare to the Bush regime asking for a corporate hand out. The Apollo program took over $25 billion dollars and more than ten years to acheive it's goal of catching up to and passing the competition. Is Bill telling us that this is what it would take? Just upgrade to a non-Microsoft product.

  210. device interface by lseltzer · · Score: 1

    If one accepts that most of Windows could be implemented on Linux through an official WINE, one must also accept that huge code investments would have to be thrown away. One of the great advantages of Windows is that anyone who creates a hardware device of any kind writes Windows drivers for it, but they would have to ditch their device driver model. Go look at Microsoft's device driver development facilities, they're extensive and represent a huge investment.

    I hope nobody gets the impression that I take Cringely's stupid idea seriously just because I posted to this thread. They guy is an interesting writer, but his writing often betrays a serious ignorance of how computers work. Plus he stole the Cringely name from Infoworld.

  211. Missing obvious: NT kernel is better than linux by Anonymous Coward · · Score: 0

    Stupid things said by stupid (made up) people. The fact is, the NT kernel is way better than linux, and has always been so demonstrated.

  212. What REALLY Lies Beneath: by jsherring · · Score: 2, Funny

    What Lies Beneath: Why Cringley Should Write His Next Article on Toilet Paper

    I was discussing this article with a friend, and he suggested that Cringley should write his next article on toilet paper. And you know, it actually makes some sense!

    1. Re:What REALLY Lies Beneath: by Anonymous Coward · · Score: 0

      Wasnt that what he was writing about anyway? I'm completely lost now.

  213. The FAT32 part by lseltzer · · Score: 1

    Here's another technical nonsensity he got from who-the-hell-knows where:

    >>DOS 7.0 was under Windows 95 and DOS 7.1 brought the FAT32 file system to Win95, not the other way around.

    All versions of WIndows 95 had FAT32. I'm not sure what DOS 7.1 was, but 7.0 had it. And the DOS implementation in those versions was not the implementation of FAT32; Windows never used DOS for file calls. In fact, even Windows for Workgroups 3.11, where a lot of Win95 core parts were first implemented, also had a fully 32-bit file system driver (vfat), although no FAT32.

    The DOS in Win95 was sort-of compatible with FAT32, in that it could read the directories and files, but it was not the file system implementation used by Windows.

    1. Re:The FAT32 part by Arthur+Dent+75 · · Score: 1
      All versions of WIndows 95 had FAT32.

      Nope. FAT32 was introduced with the OSR2 version of Windows 95 (Windows 95b) that was only sold to OEMs, neither availabe as an update nor as a retail product.

      In fact, even Windows for Workgroups 3.11, where a lot of Win95 core parts were first implemented, also had a fully 32-bit file system driver (vfat), although no FAT32.

      Nope again. VFAT is a driver for providing long filename support to FAT16 and was provided with Windows 95 and Windows NT. WFW 3.11 did not allow long filenames.

      --
      michael at slashdot.org: The real answer is that a couple of the slashdot authors are sick.
    2. Re:The FAT32 part by lseltzer · · Score: 1

      Duh. I was wrong about FAT32, I was confusing it with the fact that Windows95 always had a 32-bit protected mode file system, but the format was FAT16, and also that it always supported long file names on FAT16 volumes.

      But I was right about Windows For Workgroups 3.11 and its 32-bit prot-mode VFAT. See this Jon Udell piece in Byte for confirmation:

      "...Why not take DOS out of the loop as well? That's what WFW 3.11's 32-bit file access feature does, using a pair of new VxDs. VFAT.386 delivers protected-mode INT 21h services..."

    3. Re:The FAT32 part by Arthur+Dent+75 · · Score: 1
      Not to be nitpicking... but VFAT was only partially implemented in WfW 3.11. E.g. it did not support long file names.

      See this bit of information.

      --
      michael at slashdot.org: The real answer is that a couple of the slashdot authors are sick.
  214. MS with ca$h on hand... by Lord+Prox · · Score: 1

    This is kinda off-topic but I have to ask....

    I have been hearing rumor that MS is looking in buying or becoming a controlling intrest in Pepsi. Presumably for the marketing/brand recognition and market demographics of Pepsi in conjunction with the Xbox and related MS projects in the works.

    Has anyone heard anything like this? Any truth to this or is it just BS

  215. Backwards Compatibility by Biggs+Driut · · Score: 1

    Disregarding all the other comments: If what the article say IS true (I'm not saying it is), wouldn't there also be some backwards compatibility issues with Windows on top of Linux? Regarding all the comments: No matter what, I will never consider Windows an operating system. It may be a system, but it cannot operate.

    1. Re:Backwards Compatibility by Anonymous Coward · · Score: 0

      Yes, like some one said a while back about why its hard to do a windows clone, "You have to be bug for bug compatible"

  216. What is Wine but Windows on Linux? by thaig · · Score: 1

    I am amazed that no-one has mentioned Wine yet which is essentially what Cringely is proposing.

    If Wine was being developed by a company with the resources and inside knowledge of Microsoft, I wouldn't be surprised if it could be an almost complete replacement for XP within about 2 years.

    Windows is just one API sitting on another from a program's perspective. If programs depend only on the upper levels then it becomes a lot easier to port them to other operating systems.

    So yes, underneath the pretty GUI is just another operating system - a sort of VMS revisited.

    Regards,

    Tim

    --
    This is all just my personal opinion.
  217. Re:You got that right by SavingPrivateNawak · · Score: 1

    First, it's highly probable that these moderations were made by editors
    Second, moderations were right, the first comment was flamebait, and the second offtopic. (Like this one, alas)

    The discussion is not specifically about which free distribution should windows be based on, but it's about whether it is a good idea or not and what would be the implications...

  218. Pure Capitalism by valisk · · Score: 0, Offtopic
    Pure Capitalism would also see the removal of all aide-monopoly laws and statutes including copyright and Patents which are used by corporations in a mercantilistic manner to exclude competitors from markets.
    Pure capitalism would result in the lowest price to the consumer every time as all companies would price to the 'margin'
    The GPL seems to offer a pure capitalist opportunity for anybody who wants to take it, I can download Debian images and compete with the largest of Linux vendors like Redhat, just like Lindows is doing. My sales and standing in the market would be based soley on my reputation and speed to market of new innovations.
    The main argument against this market is that companies would hold 'trade secrets' which would possibly thwart the progress of science and learning in society so we have a patent system.
    However patents and copyrights allow companies to force competitors to enter the market on their terms or not enter at all. Rather like the old Navigation and Corn Laws of England these are Mercantilist protections of existing interests. I think it could fairly be called Neo Mercantilism or Corporate Mercantilism. This does not truly benefit the consumer except arguably in some circumstances.
    I think patents on drugs, whilst devisive do have a purpose, the research nessasary to produce a working 'safe' drug can easily reach billions of dollars, and there would be no incentive to invest that money if there was no chance of a return on it.
    There are examples of other industries where patent protection is arguably justifiable to encourage investment. In most industries patents are used as bargaining tools to get access to the latest technologies and remain competitive.
    Serious problems arise when non-innovative companies buy up existing patents and use them to extract money from industries, which harms innovation in every way as money will almost always be cut from R & D operations first as any potential gain they will make is always a) uncertain and b) years away.
    This problem strikes in every patent protected industy following a recession and always results in higher costs being passed onto consumers.
    It does in fact represent a private tax extracted from companies by groups who's interests represent no common good.
    These private tax collection agencies are almost universally made up of Lawyers and see a removal of useful capital from industy to benefit an already wealthy few.

    > Pure capitalism would be NO government aid. No major tax cuts, no negative net taxes paid back to corporations.

    I would also argue that pure capitalism can exist with Govenment aid and tax cuts/rises as long as such are applied equally throughout the industries concerned.

    >No corporations being handed publically funded projects (aka the phone lines, the railways etc).
    >Today's capitalist system thrives because of the socialist controls imposed on it...

    I would certainly say that a section of todays capitalism thrives based on government contracts, I would even say that the companies involved are worse than the the Patent Hoover companies as they are stealing money directly from taxpayers pockets.
    In the UK we had a recent example where a government directive to purchase Generic medicines in place of Brand names, a contract was given to a major Labour party contributor and friend of the Prime Minister. At this point generic medicines averaged at 10-15% the cost of Brand name products. It should have been a huge saving for the NHS and tax payer. Instead the cost of Generic drugs sourced exclusively through this one agent rose month on month until they represented a cost 90% of the brand name products.
    This problem wasn't noticed for over 2 years and refered to as an 'oversight' by the chancellors office.
    This isn't the only example by any stretch of the imagination.

    John H.

    Redistribution and use of this comment in text and opinion form, with or without modification, are permitted provided that the following conditions are met: 1.Redistributions of comment must retain the above copyright notice, this list of conditions and the following disclaimer. 2.Redistributions in opinion form must reproduce the above copyright notice :P this list of conditions and the following disclaimer in the documentation and/or other materials provided with the opinion. 3.All advertising materials mentioning features or use of this comment must display the following acknowledgement: This comment includes braingivings developed by John Holroyd of Manchester, England and his pet cat Simpkin. 4.Neither the name John Holroyd nor the name Simpkin may be used to endorse or promote comments or opinions derived from this comment without specific prior written permission.

    --

    Economic Left/Right: -0.62
    Social Libertarian/Authoritarian: -3.69
  219. Article makes me cringe by thasmudyan · · Score: 4, Informative

    It's been a long time that I read such completely bogus. I don't want to flame but I have to. Here it goes:

    Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.

    What a bunch of crap! So there is still a "disk operating system" under Linux because I can open a shell window, too? Man, what are you talking about?

    DOS 7.1 brought the FAT32 file system to Win95, not the other way around

    So what, FAT32 is a file system, and now - ? What does that say about the operating system? Nothing? Right.

    Windows XP is not an operating system. It is a windowing system that sits atop an operating system much as KDE or Gnome sit atop Linux.

    What's this guy's definition of an operating system? First, Windows has its OWN KERNEL (microkernel, btw). Second, it has its OWN DEVICE DRIVER and SOFTWARE ARCHITECTURE. While I can agree that KDE/Gnome do a fairly large and important part of the work that non-Linux OSes provide as a whole package, Windows is doing ALL THE STUFF an OS does with *no* underlying foreign kernel or architecture.

    The history of DR-DOS is especially interesting because it went through so many hands. [....]

    Blah, blah, blah... where's all that DOS talk supposed to get us? Does it really make sense to talk about legacy crap like that? And if so, should we really begin to talk about text-mode-only Linux, from back in the days, also? What about legacy mainframe interfaces? Why? To prove the point that DOS is underlying of Windows just as Linux is the underlying architecture to KDE? WTF???

    Now back to Microsoft putting Windows on top of Linux. Linux is better, faster, stronger than whatever is living underneath XP now, right? Performance would improve.

    Give me a break here! Driver support for Windows often leads to much better performance (because PC manufacturers really cater to the Windows monopoly).

    Apple has made a virtue of doing exactly this with MacOS-X, heralding its Mach kernel and BSD roots. Couldn't Microsoft do the same?

    MacOS-X is a completely new system, it has a legacy-app compatibility layer (like Wine is for Linux) but otherwise it's a complete new system. And, they HAD to do it, because OS 9 and below where such utter crap (from a purely technical point of view, mind you). If MS where to switch (for whatever stupid reasons) to a *nix kernel like BSD or Linux they would have to provide a complete legacy Windows version inside the new system just to provide backwards-compatibility. And boy would *that* be slow! And, again, why??? It would mean to develop *LOADS* of new device drivers and APIs - for what?

    I could go on like this forever. Articles like that make me want to puke. It would be suicide for MS if they did something like that, especially now, the first time they have a workable OS with Win2000/XP. Why oh why?

    OK, I asked for it. Bomb me, I don't really care. Cringely articles I actually liked them in the past, but what the fuck is this load of crap supposed to be?

    1. Re:Article makes me cringe by Anonymous Coward · · Score: 0

      Despite all your explanation, Windows still SUCKS!

      Dont want to program in Visual C++, want real C++ without hideous MFC.

      Dont want to program in Visual Basic, want that silly language dead.

      Dont want Visual C#, the M$ centric Java. Use REAL Java instead.

      Dont want anything vith Visual, non visual is very fine.

    2. Re:Article makes me cringe by thasmudyan · · Score: 1

      Despite all your explanation, Windows still SUCKS!
      I don't aim to make Windows attractive to you, son. As for programming languages, this has nothing to do with the discussion, but:

      Dont want to program in Visual C++, want real C++ without hideous MFC.
      MFC is basically just an API-thing, otherwise Visual C++ is pretty much like standard C++.

      Dont want to program in Visual Basic, want that silly language dead.
      Yeah, I hate that one too. But hey, nobody forces you to use it, right? Except maybe your employer? Oops. OK.

      Dont want Visual C#, the M$ centric Java. Use REAL Java instead.
      C# IS NOT MS centric Java! When will people EVER learn? The language is quite different from Java. Have a look at the C# spec and then come back to make some informed comments about it. Personally, having to program in Java from time to time, I hate it, because so much code is required to produce so little results (well, depends on your type of project I presume). C# is more terse to code, much like Delphi for example.

      Dont want anything vith Visual, non visual is very fine.
      GUIs *are* a reality, you know. Unless you code kernel or underlying architecture, you won't get around GUI programming in today's market. And, by the way, I don't like Visual products from MS too.

  220. Re:You got that right by Anonymous Coward · · Score: 0
    The discussion is not specifically about which free distribution should windows be based on, but it's about whether it is a good idea or not and what would be the implications...

    But it would be a very limited discussion about "whether it is a good idea or not" and "the implications" if you can't consider the alternatives. If MS decided to build Windows on top of UNIX similar to the way Apple did, it would make sense to look at the different options. One can't discuss the validity of doing this with Linux without considering the BSDs.

    On the other hand, the whole discussion has limited use because most comments won't be technical in nature (e.g. this one isn't) and unless MS has people considering this, this discussion will be largely (if not completely) ignored by them. However, that's no reason not to have the discussion...

  221. He was just emphasising the parrallels by DABANSHEE · · Score: 1

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    As someone above mentioned

  222. The parrallels are there by DABANSHEE · · Score: 1

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    1. Re:The parrallels are there by Anonymous Coward · · Score: 0

      parrallels????? pull your head outa' your ass, dimwit.

      yes, mr. moderator, you may classify this as a troll, but please mod the parent as idiotic.

  223. Hah! by Anonymous Coward · · Score: 0

    Elitist as Apple may be, MS must be biting its lips in anger... because Apple let it eating dust... again!

    Someone has its ears hot up there in MS: "Why didn't you think of it first?"

    Heh. Ingenuity will always be ahead of money.

  224. WinNT Mach Kernel? by perdelucena · · Score: 0

    What about WinNT Mach Kernel?

    I think in MSDN CDs you still can install a Unix comapbillity layer which allows Windows 2000, XP to suport unix calls. Somewhat related to mach kernel structure. Does anyone knows more about it?

    ---
    There's always more than meets the eye.

  225. The best combination ever! by ExCEPTION · · Score: 0

    Linux and Bob.
    Now we have Linux for Dummy

  226. Heheh, how about... by Klowner · · Score: 1

    ..tell the guy it's already been done.

    Install a reasonable linux distro, get wine running, and then drop XPde on top of it, Set his wallpaper to a picture of green grass and blue skys.

    There, problem solved,

    Klowner

  227. Wrong by DABANSHEE · · Score: 1

    He was just dumbing things down for the masses.

    Fact is, if he thought XP was ontop of DOS he would simply had said so.

    All he was stating was that there are parrallels.

    Look at his background as a journo & a TV doco maker. Fact is American television networks tradition dumb down everything as they're designed for adults with a mental age of 10. Great production values yes, but script wise American television is really dumbed down - just compare Columbo to Morse. It's piss easy to work out who the killer is in Columbo (It's always the really helpful person who Columbo keeps annoying till the point that he/she get the shits), in Morse you actually have to follow the nuinces of the script right to the end.

    Cringly just dumbed his blurb down to the same 'adult with a mental age of 10' standard.

    Because, fact is the parrallels are there:

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    Just as people are building a BeOS API & GUI layer onto the Linux kernal, the same can be done with Windows.

    But for what, there's really nothing that great about the Linux kernal. Sure a non X linux GUI OS could potentialy (but not necassarily) be a vast improvement over the graphical enviroment/window manager/X/Linux-GNU mess we have now, but what does MS gain? XP & its NT kernal's fine.

  228. If he meant DOS he would've said DOS by DABANSHEE · · Score: 1

    He was just dumbing things down for the masses.

    Fact is, if he thought XP was ontop of DOS he would simply had said so.

    All he was basically stating was that there are parrallels.

    Look at his background as a journo & a TV doco maker. Fact is American television networks tradition dumb down everything to the adult with a mental age of 10 level. Great production values yes, but script wise American television is really dumbed down - just compare Columbo to Morse. It's piss easy to work out who the killer is in Columbo (It's always the really helpful person who Columbo keeps annoying till the point that he/she get the shits), in Morse you actually have to follow the nuances of the script right to the end.

    Cringly just dumbed his blurb down to the same 'adult with a mental age of 10' standard.

    Because, fact is the parrallels are there:

    Linux Kernal -> Windows Kernel
    sh -> cmd.exe
    X server -> GDI.exe
    Window Manager -> Explorer.exe
    CORBA -> (D)COM

    Just as people are building a BeOS API & GUI layer onto the Linux kernal, the same can be done with Windows.

    But for what, there's really nothing that great about the Linux kernal. Sure a non X linux GUI OS could potentialy (but not necassarily) be a vast improvement over the graphical enviroment/window manager/X/Linux-GNU mess we have now, but what does MS gain? XP & its NT kernal's fine

  229. And even then it's impossible... by SiMac · · Score: 1

    Because people can't run Windows! Only computers! I would be very suprised to find a single person running Windows...he or she would probably be pretty slow...

  230. W95 OSR2 introed FAT32 by DABANSHEE · · Score: 1

    W95 used FAT16

  231. XFree86 not stable by yerricde · · Score: 1

    stability is a plus that windows has over linux. well, at least where xfree86 is concerned.

    Your implication: "The version of XFree86 included with popular distributions of the Linux operating environment is not very stable."

    What makes you think XFree86 isn't stable in general?

    If you're having specific problems with your system that you can't solve by reading HOWTOs (or if you don't understand the terse language in which HOWTOs are written), then buy a copy of a distro such as Red Hat Linux that includes a few months of tech support and have the distro publisher's tech support department help you fix your problem.

    --
    Will I retire or break 10K?
  232. Re:You got that right by Anonymous Coward · · Score: 0

    Statements of fact are not flamebait. Anyone who believes they are is in denial.

  233. twm-gl by Anonymous Coward · · Score: 0

    apparently you're not using twm-gl like the rest of us.

  234. then what... by floydman · · Score: 1

    then release Windows XP under the GPL...:) and license Linux.....

    --
    The lunatic is in my head
  235. In the Real World by tarawa · · Score: 2, Insightful

    First, the idea of porting the Windows into Linux has been around for a long long long long time. It's always had it's supporters and dissenters, so far nothing in this string of posts have contributed anything new to the argument.

    It comes down to getting decent apps on the Linux platform, and I know I'm probably gonna get flamed for this, but 95% of the software honestly sucks. At least Windows apps generally conform to a standard and typically very polished. Yes, I know that Linux apps are getting better, but they aren't there yet and why we all argue about every little thing, Microsoft moves on to the their next version, happy to throw something at the Linux community to get it all rialled up.

    So far, the only version of Linux that I see as promising is Xandros and that's because they are in control rather than 5 million whiney geeks, hackers, cracker, dweebs, or whatever we call ourselves today.

    Second, every OS out there sucks. They all do. Windows X.X, MacOS X.X, Linux and every other OS that is out there sucks.

    I would love nothing better than to see a free, open source OS dominate the market because it is fast, stable, and actually easy to use. Linux is 2 out of 3. Windows XP is generally fast, stable, and a lot easier to use than Linux. MacOS X is fast, stable, and easy to use to a certain group of people while the rest think it is either moronic or insulting to use. In my book that puts Linux at 2 out of 3 while XP and MacOS are at 2.5. Perhaps Linux, in it current form, isn't the answer for the desktop. Maybe the GNU community needs to develope an OS from the ground up that is geared towards the Desktop, and let Linux handle the server and workstation market (where it is competeing extremely well). That way we aren't wasting are time trying to make the Swiss Army Knife of the OS world.

    Oh, BTW, DOS under NT, 2000, and XP is an emulator, just like DOSEMU in Linux. It provides enough of DOS so that many, but not all, old DOS programs will run. The great part is that since those DOS apps run inside a Windows app, if the DOS program pukes, it doesn't take the OS with it like what used to happen under Win 3.x and Win 9.x.

    Finally, here is a link to a funny song that helps make my point on OSes sucking. :) It should make at least some of giggle. :)

    Cya L8r
    Lee

    1. Re:In the Real World by Anonymous Coward · · Score: 0

      You can take that attitude that all OSes suck... but show us your alternative. Talk is cheap, do something rather than complaining.

      "sucks" is a relative term, and yes Windows, really, really, really.... sucks, but it works where Linux fails. I can install windows on 100% of the pcs, but i cant say the same about Linux. The worst part is that you have to find out what video card its using. Who the hell cares. When i want to install the OS, I dont have to dig in and find out what video card it uses. An the GUIs really, really, really... suck for Linux (yes, even the Blue Curve), and this is where Windows shines through.

      As for Mac OS-X, they have a done a pretty good job of getting a Unix to do a real nice GUI. At least some one is considering the GUI an important part.

  236. Worlds larges vendor of free software... by meowmonster · · Score: 1

    What do you mean? This isn't a new concept. Noone but corporations is actually dumb enough to pay for their stuff do they?

  237. Not to split hairs... by thatguywhoiam · · Score: 1
    But you haven't said why.

    I agree - you're probably right, but you haven't given reasons. CMD.EXE != Windows is not a cogent argument by itself.

    --
    If Jesus wants me it knows where to find me.
    1. Re:Not to split hairs... by miu · · Score: 1
      But you haven't said why.

      I agree - you're probably right, but you haven't given reasons. CMD.EXE != Windows is not a cogent argument by itself.

      My argument is that Cringely keeps saying "DOS" and "Windows", without any understanding or explanation of what he means by those terms. Beyond confusion about basic terms he also misses the distinction between abstraction levels.

      I understand that a popular science article is no place for an intro to CS, but he should make at least an effort to understand the basics of the subject he is writing about.

      --

      [Set Cain on fire and steal his lute.]
  238. Instead of building it on Linux by sielwolf · · Score: 2, Interesting

    How about on the GNU/Hurd? They could make some Win32, OS/2 modules and work it in over an architecture that's going to try and be compatible with a horde of *nixes.

    But then the question is: if a company makes a proprietary component on the Hurd, would they have to release the source as per the GPL?

    --
    What is music when you despise all sound?
  239. Modules and modprobe anyone? by Henk+Poley · · Score: 1

    You could just (re)compile a module and insert (modprobe) that into the kernel, IMHO.

  240. You're both wrong. VMS != UNIX by MobyTurbo · · Score: 1
    I'm not sure how this got modded up to 4!
    You're wrong. VMS and UNIX appeared at about the same time, but are very different beasts. Arguably, VMS was better than UNIX, but UNIX became dominant as a result of BSD.
    This is so bizzare that I don't know where to start. VMS appeared near the end of the 70s, when the DEC VAX was introduced. Unix began in 1969, and was first written in C in 1973, though it wasn't widespread until 1976; when the 6th edition of Unix was released. The 7th edition is probably what cemented it as an operating system for accademia. It orignally ran on the PDP-11, which was the most popular mini DEC made before the VAX.

    When the VAX was introduced, BSD had already existed for a couple of years, basically as a collection of utilities that required an AT&T source code license to install, (which later versions up to Net/2 required as well) but BSD really took off when they made a BSD (3BSD) for the VAX that included virtual memory, a feature AT&T was not yet offering and a key feature of the VAX hardware. (V=virtual in both "VAX" and "VMS") 4BSD, thanks to ARPA asking Berkeley to add a networking stack for ARPAnet protocols (TCP/IP) to Unix, was the first version to include TCP/IP. This version of BSD did indeed take off, but later on AT&T's System V became more popular.

  241. linux based windows, ISNT THAT LINDOWS? by Anonymous Coward · · Score: 0

    wasnt that the Point of LINDOWS?
    linux with a similat GUI to windows?

  242. The only way to win Linux by axxackall · · Score: 1
    The only way for Microsoft to win in the buttle with Linux is to stop the buttle and to begin cooperation. If you cannot win - live with it and use it for your own benefit.

    There is no such company as Linux - there are dozen of vendors, handreds of support centers and thousands of independent developers. You cannot buy ALL of them. You cannot force ALL of them out of business. This is the new life, new objective reality. You cannot compete with the life itself.

    Microsoft is not a church or any religion organization. Instead, Microsoft is the most successful software-related business. When Microsoft is using some propaganda - it's to make new money, nothing else. If (or when) strategic planners in the giant discover that Windows on a top of Linux is a good idea - they will command to do it without any hesitation.

    Linux community won't be really hurt - more drivers etc etc. The life won't be the same as we know it, but that won't be the death for the Linux community. I am positive.

    There won't be the war between OSes. Instead, there will be wars between architecture and design ideas. Users won't choose between Windows and Linux. They will be choosing between diffirent implementations and distros.

    I guess, Microsoft will shift their main profit source from OS licensing to application licensing and even more - to support.

    If (actually - when) Microsoft will build new Windows on a top of Linux, the users will win. That's for sure.
    Now, why linux and why not BSD? If Microsoft will adopt BSD then it will play well for its strong potential competitor - Apple. If Apple will deliver MacOSX for x86 - Microsoft market share will collapse and it would happen rapidly - MSFT stock may collapse.

    How Linux may help? It's very simple. Just count how many Linux users are out there. Add how many corps have already considered Linux (just not migrated yet). If Microsoft will declare that new Windows will be on the top of Linux then Apple can forget about x86 forever.

    Speaking about GPL, it's a matter of time that Microsoft will agree with logic of IBM: GPL is compatible with profitable business models. There is nothing wrong of including GPL kernel and uilities into your OS. And that there are much more good GPL software out there than BSDL.

    Besides, if you agree to include GPL into your product, its more likely you agree with BSDL as well. If don't - then you are limited only to BSDL subset of OSS. So, your agreement to include GPL gives you all OSS instead of just small portion of it. Just make sure your lawers are OK with GPL and your business model is OK with GPL. And that what's gonna happen to Microsoft soon, I believe.

    --

    Less is more !
    1. Re:The only way to win Linux by Anonymous Coward · · Score: 0

      Of course, then M$ can fire a lot more developers and add to the unemployment pool that Free Software helped create, pocketting the money they would have had to pay some one to get a product done. Thanks Free Software.

      Then those developers who got fired will think of gaining some recognition by writing some free software with the hope of getting employed again, and in the process, get whole bunch of other developers fired... and the cycle continues.

      Yeah, Free Software works... for the big greedy companies who dosent want to pay anything for a product.

  243. And it would be called... by Zebra_X · · Score: 1

    OS X!

  244. HAL, IBM by Anonymous Coward · · Score: 0

    WNT = VMS + 1

  245. No by Hard_Code · · Score: 2, Insightful

    "Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe."

    WRONG. From NT onward, Windows has been an entirely new OS, not a windowing system "running on" DOS. Yes, NT/2000/XP etc have a command processor that LOOKS like DOS, and in fact they have DOS emulation SUPPORT (including the familiar "command.com" binary), but that does not mean they run on it, any more than it means Lindows runs on DOS because of Wine, or that any machine is running on Amiga just because it has an Amiga emulator.

    _Showstopper_ is a good read.

    --

    It's 10 PM. Do you know if you're un-American?
  246. vendor of free ... by Anonymous Coward · · Score: 0

    quote:
    vendor of Free software (...)
    end quote.

    That's a joke certenely ... :\

  247. Didn't Bill Gates say DOS was finally dead? by rapidweather · · Score: 1

    When XP was brought out, didn't Bill Gates say the underlying DOS was not there anymore? I doubt he would say that if it was not true. I have seen stories about certain Governments getting the Windows source code. If that happens, it'll leak out, and we'll then know if DOS is required or not to run windows. Nice thought, that Windows is just another wm. Makes me want to run icewm, and save some processing power. I do that now with RHL 7.1. I have some more RAM ordered, but for now, I run icewm to lighten the load as compared to KDE. Very clever, really, of Cringley to present us with the "Windows XP = a wm" idea.

    1. Re:Didn't Bill Gates say DOS was finally dead? by neuroticia · · Score: 1

      You can save memory by running an alternate window manager under WinXP. It's just called a "Shell". When you use a different Shell, memory usage drops because the GUI can be made more simple/more efficient.

      While 'Windows is just a WM' is un-true, 'there are alternate WM's for Windows" is not un-true, and those WM's save a lot of system resources (As does shutting off most of the 'services' that run by default under XP, disabling any devices that aren't on the system even though XP insists that they are, etc.)

      Just be sure to back up your registry before you muck around with changing WM's. The first time I did that I ended up nearly b0rking my WinXP install, and had a fun time playing around for 30 minutes to get it to run properly again.

      -Sara

    2. Re:Didn't Bill Gates say DOS was finally dead? by Anonymous Coward · · Score: 0

      I did find an XP-like wm for linux, at XPde.com. I don't have
      XP itself, due to the cost ( can buy a new pc with linux already on it for about $250.00) and the fact that I cannot put it on more than one machine. I'm sure anyone viewing this thread would like more information on the alternate window managers available for XP. As I said before, I like to run something like icewm to save resources, and perhaps the XP crowd would also like to do something along that line.

  248. No, it isn't by ucblockhead · · Score: 1

    OS/2 couldn't run DOS programs until Version 2.0. That's a pretty good sign that it wasn't "just DOS".

    --
    The cake is a pie
  249. Re:No, it should be built on FreeBSD by uncoveror · · Score: 1

    According to insiders, It indeed will be based on BSD. Check it out!

    --
    The Uncoveror: It's the real news.
  250. Why? by NineNine · · Score: 2

    What's the point, exactly? Why would MS bother? The NT kernel is stable, fast, and secure if you want it secure. Why would the re-invent the wheel? They've *finally* come out with a good product for the consumers (businesses have been using NT for a long time). After all of these years, and all of this work, why in the *hell* would they suddenly decide to start back at the drawing board again? That was one of the stupidest, for lack of a better word, article that I've read in a *long* time.

  251. I hate these idiots by failedlogic · · Score: 1

    There's a funny thing editorial and opinion based articles on the Net about anything hi-tech - no references. He clearly does not know what he's talking about. He has not done any research on how this would be accomplised. This is a daunting task. To me, this is like a cardiac surgeron simply stating "Heart transplants always work because I did my first transplant today." This idiot's reasoning is the same thing. Linux works and X has a Windows like interface. Gimp works in Windows so its easy to port Linux apps to Windows. Liunx is stable, Windows isn't. Let's port Linux to Windows. No research, credentials, references are used to back up his claim. Yet he's being /.'ed and getting media attention. Hope Darwin's theory works soon rather than later.

    1. Re:I hate these idiots by Anonymous Coward · · Score: 0

      Hes a priest... Gods's will be done ;-)

    2. Re:I hate these idiots by jimmy_dean · · Score: 1

      He does know what he's talking about actually. Though it would be an enormous programming task, it could be done in much of the same way as Apple porting their system to BSD. With the right amount of money and semi-knowledgable programmers, anything is possible. But that doesn't mean this will happen. The day this happens is the day Bill Gates becomes the world's poorest man instead of the world's richest man.

      --
      -> Sometimes, you just gotta break free from the shackles of proprietary code.
  252. Gee I wonder why Microsoft hasn't jumped at this? by thehunger · · Score: 2, Funny

    > If Microsoft wanted to, they could be the world's largest vendor of Free software .. couldn't they?

    Gee what where they THINKING?!

    "Wow! We could become the world's largest vendor of Free software!"
    -Or-
    "we continue to be the world's largest vendor of software that people PAY for.."

    Is it still mindboggling? Why is this even a thread?

  253. for D in seq 0 1000000; do echo "c: != DOS" done by MadFarmAnimalz · · Score: 3, Interesting

    WTF? Slashdot was never this lame... I've been forced to browse at +5 and I've seen a bazillion posts explaining how smart the poster is that he knows that cmd.exe is not DOS, and how Cringely is by comparison.

    If an explanation of why cmd.exe is not DOS +5 interesting gets modded +5, then there's too many mod points floating around. That's what you get when you mod karma whores +5.

    This is NOT meant to be a troll. Slashdot used to be better than this.

    --
    Blearf. Blearf, I say.
  254. Re:Erm no. More like bankruptcy. by Anonymous Coward · · Score: 0

    Hey, genius, if people who own MS's stock all sell it, MS doesn't go bankrupt. Bankrupcy means that the company isn't making enough income to pay their expenses. What the value of the stock price is has nothing to do with this.[*]

    I tried to type slowly so that you might understand this.

    [*] A low stock price can be problematic for the company in that it makes it harder for them to raise additional capital by selling more stock. However, with $40+Bn in the bank, MS doesn't need to issue any new stock any time soon.

  255. Re:You got that right by BarrettAnderson · · Score: 0

    you are one of the stupidest people i know. not a single one of those moderations was a good moderation. flamebait=trying to attract flames. this person was stating the truth in his/her opinion. the 2nd one was not offtopic - he/she was replying to an on-topic post. discussions go on tangents sometimes - but as long as there is a link to the original topic, it is still ONtopic. but no, you won't get modded offtopic because you are going against people who are going against linux. the only possible way you'll get modded offtopic is if a person with any common sense gets moderatorship, which doesn't happen very often.

  256. Worst of all worlds! by Anonymous Coward · · Score: 1, Insightful

    Knowing Microsoft, they will probably settle for the Windows OS, and Linux GUI.

    A better world already exists, called MAc OS-X. Got the best of all worlds with a great Unix OS, and a really cool GUI.

  257. Re:Gee I wonder why Microsoft hasn't jumped at thi by Anonymous Coward · · Score: 0

    He's just a hippie, waking up from a high... please be kind.

  258. Linux? Give me a break! by incripshin · · Score: 2, Insightful
    First off, Microsoft despises Linux. If they were to turn around and give the penguin a big ol' hug, they'd look like hypocrites. Nobody likes being thought of as a hypocrite.

    But that doesn't mean M$ would give up on basing their OS on other existing OSes. There's always BSD. If you had any memory at all, you'd remember the /. story Why Unix is better than Windows... By Microsoft. M$ goes on and on about all the things BSD does better than Windows. And who could forget that Hotmail used to be run on BSD.

    Don't expect Windows 2004 to be based on Linux. It'd be BSD if anything (and if they give a rat's behind about security, they should go with OpenBSD ... but that's just me).

    And you KNOW this.

    1. Re:Linux? Give me a break! by janda · · Score: 1

      Microsoft has never been concerned about being seen as a hypocrite. For examples, see the DOJ documents, the fact that Windows is a copy of the Apple windowing system (which is based on the Xerox PARC system), the DR-DOS lawsuits, the recent DOJ stuff, and the rest, the rest, the rest.

      --
      Karma: Food Fight (Mostly affected by Date Plate).
  259. Re:You got that right by SavingPrivateNawak · · Score: 1

    I'm sorry but a 'FreeBSD r0x0rs so mUch tHan L1nux' post without any other 'proof' than 'If you are in the l33t BSD users circle, you already know this' IS flamebait!!! It's not even an argument, it's just there to begin a 'BSD vs linux' flamewar, which is, I'm sorry to say, offtopic.

    You could argue than the first post was an opinion and that everybody's free to express his opinions, yada, yada, but this kind of opinion fall into the same category as the 'BSD is dead' opinions, that is 'troll/flamebait'...

    Now you're right that sometimes stories bring interessant 'tangent' discussions, but I do not feel that would have been the case...

  260. Just port explorer.exe to be the GUI for distros by charnov · · Score: 1

    What I would pay big money for is the XP GUI on top of linux/unix. As I sit here, I have a machine which is running the Lycoris distro and it comes close to the ease of use.

    I have said it many times before, but I'll post it again: the world will be a much better place if everyone DUMPS X. X has no future on the average desktop which is where the OS battle is fought. Linux/Unix in the server world is fine, but there are few (Xandros, Lycoris, Ximian, etc) that are good enugh to be called desktop distros.

    Now when Fresco, Chandler, Phoenix (which rocks), etc. all fully mature, I'll be a happy boy.

    Or maybe Apple will get off their ass (aka Steve Jobs), and port MacOS X to x86. ah...to be a dreamer...

    --
    [RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
  261. Mascot? by NeuroMorphus · · Score: 2, Funny

    I wonder which mascot they will use...Personally, I'd prefer tux rather than some dancing orangutang. ;)

    --

    python >>>
    reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
  262. Mission ciritical my ASS by Mr.+Fred+Smoothie · · Score: 1
    Agreed. As an MCSE (Windows NT), I've supported all the flavors of Windows around (and some that were never officially released, via the TechNet program). NT works like Unix. In fact, the Chicago Board of Trade, nuclear power plants, and airports often use NT for mission critical systems.
    And I've had moving a window on the screen of a heavily loaded NT 4 box bring the server down (BSOD). Mission critical only if your mission tolerates frequent catastrophical failure, or the load on the box is negligible, maybe.
    --

    1. Re:Mission ciritical my ASS by VoidEngineer · · Score: 1

      And I've had moving a window on the screen of a heavily loaded NT 4 box bring the server down (BSOD). Mission critical only if your mission tolerates frequent catastrophical failure, or the load on the box is negligible, maybe.

      Agreed. I have also had NT machines crash into a BSOD by moving a window.

      I've also has the same thing happen to me with FVWM running on a Solaris 8 machine (dumps you into the PROM screen, much like the BSOD). My coworkers didn't know what to say... they'd never seen such a crash (granted, I was messing around with non-standard device drivers, wacky equipment, and unsupported libraries...) Nontheless, it can happen to all platforms.

      If you want to get NT to run mission critical stuff, you typically has to remove all the extranious sub-systems. (Ever see a Harley-Davidson 'chopper, where they take everything off that isn't needed to make a real light bike?)

      Interesting process that. It can definately be done.

  263. I always thought... by fred666 · · Score: 1

    ... that NT meaned "Neanderthal Technology"

  264. +5 Insightful my foot by mav[LAG] · · Score: 1

    I also don't give a fsck what you'll say about "but the GPL!!

    OK, at least we know where you stand but let me try and present the facts anyway.

    If MS were to do this they would withouth question weasal around the GPL or hire an army of lawyers to get it thrown out or watered down to the point it wouldn't matter.

    That's an amazing amount of crap squeezed into one sentence. You can't just "weasel around the GPL": it's a license that happens to be applied to someone else's copyrighted code. Should your theoretical army of Microsoft-sponsored lawyers get the GPL chucked out of court, then an even worse fate awaits the company: illegal use of copyrighted code - an offence they know and understand very well (since they have been found guilty and fined for doing so more than once). Your other suggestion is equally laughable. Microsoft's lawyers can't water down the GPL any more than I can sign a piece of paper giving you carte blanche to sell unauthorised copies of Windows XP. There are a good five million lines of GPLed code in the Linux kernel and tens of thousands of contributors. Microsoft knows only too well they can't even look at GPL projects let alone use their code.

    Meanwhile, they would either not give any code back to the kernel, or more likely would inject code specifically designed to slowly build up an IP claim over the entire kernel.

    Um, yeah right. Microsoft forks the kernel and builds in its own proprietary extensions, starts distributing them illegally and attempts to sabotage the remaining official branches. Apart from wrapping the whole of Seattle in huge plastic letters that spell out the words "WE LOST" I can't think of a better way to admit defeat.

    Linus once said, and it's a telling quote: "if Microsoft ever port Office to Linux, I've won." You can be really sure that quote is well known (and understood) by management in Redmond - who are people that like to win more than they like to make money.

    --
    --- Hot Shot City is particularly good.
  265. wishful thinking by ScubaS · · Score: 1

    this would never happen, at least anytime in the forseeable future.

  266. Cringley's Smokin Dat Crack Pipe by PleaseDontBeTaken · · Score: 1

    Damn glass gets hot, don't it!

    --
    --
  267. Microsoftlinux websight by Anonymous Coward · · Score: 0

    Have a look at the www.microsoftlinux.com

  268. Solaris OE != SunOS by fwr · · Score: 1

    Solaris refers to the complete "Operating Environment" which includes SunOS (5.9 at it's latest version). What he is suggesting would be more akin to Sun replacing SunOS with Linux, not Solaris. In fact, there is no reason that I know this could not be done.

    I think it is quite clear to anyone who knows both Windows and Linux history that when he says Windows he means the GUI front end, non-kernel space programs, and DOS refers to the kernel. Similarly, Linux means just Linux, the kernel.

    So would that be plausible then? Replace the Windows NT/XP kernel with the Linux kernel? THey would have to do some things, like take the GUI display driver out of the kernel and make it a user process. Then users could load up either a XDM process to launch X 11, or a Microsoft process to launch "Windows."

    I believe there would also be some process and thread control issues, but then there's no reason they can't run everything in user-space or contribute (gasp!) to the Linux kernel. Could you imagine Linus having to approve any Microsoft patches to the kernel? That would be hillarious.

  269. Portability? by heatmzr · · Score: 1

    OK, I don't except this to every happen, but MS could adopt NetBSD as thier underlying kernel and run Windows on it.

    Windows running on everything from big iron servers to toasters?! One step closer to world domination!

  270. Re:You got that right by BarrettAnderson · · Score: 0

    ok, read all the comments on this board right here. if you believe 100% of the ones that do not present evidence are "flamebait", then i think you're an idiot. just because he doesn't like linux doesn't mean it's freeking flamebait. we get modded down for stating our opinions, but you freeks get away with "M$ sucks" (as the body of the entire commment) comments - and get modded up insightfull for those.

  271. Re: if you don't let it go, we'll make another by johnrpenner · · Score: 1


    microsoft will never do it -- they'll never let go of control of the lowest common denominator (the OS is the last layer between software and the hardware) - they don't want to lose that control, and never will.

    because they kept that hood so tightly welded shut -- open source had to arise, because people like to be able to tinker. so -- thank you microsoft! :)

    cheers,
    john

  272. Re:apple has GREAT backwards compatibility by johnrpenner · · Score: 1


    when apple put 'classic' compatibility in a box -- the os9 'classic' compatibility ran better than most windows 'upgrades' that were supposed to be compatible.

    i can still run software from macOS 6.0.4 in the OS-X 'classic' mode -- macwrite II v1.5, photoshop 3.0 (from 1994 - mac OS 7.6 era), and macpaint 2.0 (from 1988) still runs fine -- mac compatibility is really quite good.

    john

  273. This will never happen. by janda · · Score: 1

    Why? Because if Microsoft doesn't control the OS, they can't very well force the hardware vendors to include certain things (e.g. network cards) as part fo their "standard" platform, could they?

    M$ is way to anal about the money, and nowhere near enough anal about the innovation.

    --
    Karma: Food Fight (Mostly affected by Date Plate).
  274. Re:apple has GREAT backwards compatibility by evilviper · · Score: 1

    Yeah, and I can run DOS programs on my Alpha (using Bochs)... It may work, but it will really have to work incredibly well. Besides, I would believe that Windows' API is an order of magnitude more complicated.

    In any case, I'm sure I can find any number of OS X compatibility horror stories on the net. I've already seen a few, although I don't even look for them.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  275. Embarrasing by Anonymous Coward · · Score: 0

    This Cringely article is so technically ridiculous that it's embarrasing for the Linux community. I wonder if the article was sponsored by M$ in order to discredit Linux.

  276. Win32 on Linux isn't a techinical issue....... by Anonymous Coward · · Score: 0

    It's a commercial issue. Microsoft would see their revenues fall if they built their core OS on Linux.

    Licensing issues would also be an obstacle, I'm sure many court cases would follow too. There are already some patent issues with Linux and Microsoft would be the target of some legal action if they released a commercial OS based on such code.

  277. DRDOS Rejected By Windows by tgrigsby · · Score: 1

    Ok, I think the /. crowd has certainly expounded justifiably on Mr. Cringely's ignorance. To add fuel to the fire:

    Up through Windows 3.11 both these products worked as well or better under Windows than MS-DOS, and some people have claimed to have made them work under later Windows versions, too.

    That's actually not true. Windows 3.1 (3.11? it's been a while) was made to generate an error if you attempted to start it up on DRDOS. It's my understanding that there was no technical reason for this except that Gates didn't like competition.

    In hindsight, I think a trend could have been detected even then...

    --
    *** *** You're just jealous 'cause the voices talk to me... ***
  278. why this won't happen... by jeske · · Score: 1

    Microsoft has been really good about one thing from the outset of Windows, and that is third party support. Applications and drivers can be released independently by third parties and stay compatible for a reasonable period of time.

    Linux, on the other hand, seems designed to prevent third party developers. It's not possible for third parties to ship applications which will run on all the different distributions available for a given version of Linux, let alone different versions. Newer kernels constantly break the kernel driver interface layers. The philosophy is that it just dosn't matter, because as long as the source is there in the kernel, someone will update the interface.

    The trouble is that the world is not open source. Linux has terrible third party application support in part because it's impossible to be a third party for Linux. If Microsoft based their next operating system on "Linux" it would be in name only. They would tear the innards appart to mature the driver interface, stabilize the binary format, and stop letting people make incompatible changes to the MS fork of the OS. They wouldn't do these things to "own" Linux, they would do them because this is the only way you can have a hugely popular operating system installed on 96% of desktops, performing millions of different types of operations for different people.

    However, the biggest reason they won't do this is that they just don't need to. The balkanazation of UNIX has merely been replaced with the balkanazation of Linux.

  279. A minor, big difference by Decimal · · Score: 1

    Directory structure. Windows users use the backslash \. *nix users use the (fore)slash /. (Call me petty, but I prefer the backslash over the slash. It makes more sense -- in fraction form, the bigger directory goes under the smaller one) Microsoft will demand the use of the backslash. Microsoft may adapt easy to software that tries to use the wrong slash, but the biggest headaches this will cause is trying to use all of the Linux software that is specifically programmed to use the foreslash. A whole bunch of code will have to be changed and recompiled, which isn't a problem, but I think it would cause a huge flamefest from the Linux side.

    It will be called the holy war of slash. :p

    --

    Remember "Bring 'em on"? *sigh
  280. Good thinking. by jrwillis · · Score: 1

    It's quite possible that they have...

    --
    Keep Austin Weird!
  281. Oh...My...God! by cyberdog6 · · Score: 1

    This may have flown if XP was not based on NT, which I believe was based on the old VAX systems and never had anything to do with DOS. I think there may be some OS/2 code in there, but Cringely obviously doesn't know the difference between Win95/98/ME ilk and the NT derivatives.

    XP IS an OS and IS integrated with the code that talks to the hardware. It is not a windowing system that sits on DOS.

    How can a technology writer have missed this rather obvious and very important development?

    --
    Evil is the money of all root....
  282. Re: Xenix & VMS by spitzak · · Score: 1
    No, the "POSIX subsystem" is absolutely useless. It cannot read/write files that the Win32 system could read/write, and it cannot make any Win32 calls. It is strictly there to fullfill a checkmark on government requirement forms and is purposely designed so that it is impossible to write useful software under it.

    I still say they were stupid. There would be no Linux today if they had just based NT on Unix. It could have been even as bad a copy as Xenix. They realized their mistake and that is why the now say "embrace and extend" is the way to go.

    The VMS guys saw all the Vaxen sold to education instutions wiped and replaced with BSD Unix and felt quite defeated by this. It did not matter what banks left on the Vaxes, for the average new student is CS a VAX ran BSD Unix. The students were also exposed to a great deal of FUD that VMS sucked and Unix was a win. I think they had a lot of hatred of Unix.

  283. If they want return on investment... by jotaeleemeese · · Score: 1

    ... why are they not whining for their dividends?

    As things stand now they will be slightly less better of in a casino.

    --
    IANAL but write like a drunk one.
  284. Re:You got that right by Anonymous Coward · · Score: 0

    Barrett Anderson, I hereby wish to express my desire for you to end your life. Please. Now. Go kill yourself.

  285. Last Post! by alpg · · Score: 0

    I do not seek the ignorant; the ignorant seek me -- I will instruct them.
    I ask nothing but sincerity. If they come out of habit, they become tiresome.
    -- I Ching

    - this post brought to you by the Automated Last Post Generator...