Slashdot Mirror


Microsoft's Ancient History w/ Unix

NutscrapeSucks writes "The Register is running a article which discusses Microsoft's experience running their own version of UNIX, called Xenix, as their standard desktop operating system. Before they got involved with OS/2 and later NT, Microsoft considered UNIX to be the PC operating system of the future. Talks about Bill Gates running vi, difficulties with AT&T, and other interesting tidbits." There's a lot of stuff everyone knows, and a lot of stuff you probably didn't know. Worth a read.

357 comments

  1. Unix is the future. by Anonymous Coward · · Score: 4, Interesting

    Kerberos..
    Shortcuts.. Symbolic links.
    Multitasking..
    How many others?

    Not to troll, but a lot of Microsoft's innovations are actually recycled ideas that've been around for years. No, really, not to troll - I'm glad they've taken certain ideas from Unix. It wouldn't make sense for them to have not done so. There's a lot of good stuff in the various Unices out there.

    1. Re:Unix is the future. by fredrik70 · · Score: 2, Interesting

      Well, multitasking isn't really a Unix specific feature, more of a fairly standard general OS function.
      The others though are probably inspired from Unix, don't know of any other OS that unix might have been inspired of (well, except multics), anyone know?
      Win NT was designed by the same people who designed VMS IIRC, so I suppose they got lots if inspiration from there as well

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    2. Re:Unix is the future. by The+Wookie · · Score: 3, Informative

      DOS 2.0 included Unixy features like file descriptors (instead of the old FCB file control blocks), directories, and devices as files (COM1:, LPT0:, etc) that weren't present in DOS 1.0.

      Unfortunately, my memory fails as to whether this was still IBM PCDOS or MSDOS. I'm thinking by that time it was MSDOS.

    3. Re:Unix is the future. by thogard · · Score: 2, Informative

      but those had already found their way into CPM. You could do many unixy things in CPM on machines with at least a few 64k pages.

      DOS 1.0 was PCDOS unless you ran it on a DEC rainbow or a few other very rare boxes. MSDOS was later.

      Of course the 1.0 and 2.0 syscals are still in win 2002 or whatever its called.

    4. Re:Unix is the future. by Anonymous Coward · · Score: 1, Insightful
      Win NT was designed by the same people who designed VMS IIRC
      Yup. Easy way to remember: what are the next letters in the alphabet after V, M and S? I think HAL must have been the project leader ;)
    5. Re:Unix is the future. by thogard · · Score: 1

      Multitasking predates Gates. Most OS's at the time (including the ones MS used to build their cross compilers) all did multitasking. It was assumed any "real" os would do that.

    6. Re:Unix is the future. by fredrik70 · · Score: 1

      indeed. the teachers at my Uni used to think of dos a application launcher rather than as an OS. Mind you was still fun to program for dos, TSRs anyone??? THe smaller the better!

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    7. Re:Unix is the future. by Anonymous Coward · · Score: 2, Informative
    8. Re:Unix is the future. by swb · · Score: 2

      Not to troll, but a lot of Microsoft's innovations are actually recycled ideas that've been around for years. No, really, not to troll - I'm glad they've taken certain ideas from Unix. It wouldn't make sense for them to have not done so. There's a lot of good stuff in the various Unices out there.

      All of the features you've mentioned were not invented by UNIX operating system, they're features of many operating systems (multitasking) or filesystems (symlinks) that have been implemented within the UNIX environment. (I may be wrong about symlinks -- I don't remember them as a feature in my Cyber or limited VMS experience, although the idea I'm sure was thought of in those days).

      Kerberos is an application that was implemented on UNIX -- it doesn't have anything to do with the UNIX operating system.

      A better question may be asking why new features are so often implemented on UNIX instead of other operating systems.

    9. Re:Unix is the future. by Deid · · Score: 2, Informative

      IBM TSX and MPX Late 60's Ran on an IBM 1800 mainframe and was designed as multi-tasking O/S for process control. It ran many of the various chemical plants etc. in the US and Canada for years.

    10. Re:Unix is the future. by cvd6262 · · Score: 1

      I saw an iMac on display at my university's bookstore last year running a 'demo' of OSX. It was a self-guided tour with 5 main sections explaining the new features of OSX. The only one which Unix has not had for years was Aqua. (The others were stuff like SMP and Memory Management.)

      --

      I'd rather have someone respond than be modded up.

    11. Re:Unix is the future. by Corporate+Troll · · Score: 1
      And this comes as a surprise to you? Mac OS X is a Unix. It's that simple. Actually I have currently 3 terminals open, one of which is used to ssh to my OpenBSD box. I use vi daily on my Apple (I love vi, don't flame me for that). A Mac with Mac OS X is everything a unix-geek can dream of!

      Here little proof fo you:

      Welcome to Darwin!
      [hathi:~] jorg% uptime
      8:16PM up 3 days, 1:53, 4 users, load averages: 2.28, 2.17, 2.02
      [hathi:~] jorg% uname -a
      Darwin Hathi 5.3 Darwin Kernel Version 5.3: Thu Jan 24 22:06:02 PST 2002; root:xnu/xnu-201.19.obj~1/RELEASE_PPC Power Macintosh powerpc
      [hathi:~] jorg%

      Unixy enough for ya?
    12. Re:Unix is the future. by Zeinfeld · · Score: 3, Informative
      Not to troll, but a lot of Microsoft's innovations are actually recycled ideas that've been around for years. No, really, not to troll - I'm glad they've taken certain ideas from Unix.

      But none of the 'innovations' you cite came out of UNIX. The closest one would be Kerberos, but even that was conceived from day one as being independent of the O/S. MIT has developed enough O/S to know that there is more than one.

      UNIX was not an O/S with lots of innovative features, the main innovation was the idea that most of the O/S could be written in a high level language. Most of the advances in UNIX consisted of removing unnecessary junk from Multics or ITS.

      UNIX was not the first O/S with symbolic links, it was however the first where the feature was widely used. There is even a way to create symlinks in VMS, although you have to go through an API to do it.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    13. Re:Unix is the future. by mini+me · · Score: 1

      I think HAL must have been the project leader

      You mean IBM!

    14. Re:Unix is the future. by Anonymous Coward · · Score: 0

      > UNIX was not an O/S with lots of innovative
      > features, the main innovation was the idea
      > that most of the O/S could be written in a
      > high level language.

      i guess they picked up that idea from multics, which was written in a fialect of PL1. afaik, they also picked up the language at MIT (BCPL, which was brought there by its inventor when he spent a sabbatical(?) at there)

    15. Re:Unix is the future. by csbruce · · Score: 1

      [hathi:~] jorg% uptime
      8:16PM up 3 days, 1:53, 4 users, load averages: 2.28, 2.17, 2.02


      That evidence is inconclusive. A real Unix system would look like this:

      [hathi:~] jorg% uptime
      8:16PM up 374 days, 1:53, 4 users, load averages: 2.28, 2.17, 2.02

    16. Re:Unix is the future. by Anonymous Coward · · Score: 0

      hooking the timer interrupt to implement background ymodem file transfers (in 9k of resident cod ei might add)... finding that microsoft had gone out of their way to screw with the serial port, as well as the timer interrupt chain, just so you couldn't do that in their latest version... Those were the days.

    17. Re:Unix is the future. by ickyfreak · · Score: 0

      hehe its only 3 days because his unix runs office and ie :)

      --

      ---------------
      100% Australian

    18. Re:Unix is the future. by Corporate+Troll · · Score: 1

      Give me a break! Unlike a server, a desktop machine (okay, laptop) doesn't need to stay on the whole day. I tend to turn it off from time to time. I sure get pissed when my BSD box in the basement goes out due to power failure (today again..thanx dad...sniff), but on a desktop machine it's just irrelevant!
      I wanted to show the uptime for the multi-using (which is new for Mac systems) and the uname was to show it is really a Unix system. I don't brag with uptimes, it's a childisch as comparing "lengths" if you see what I mean!

    19. Re:Unix is the future. by Corporate+Troll · · Score: 1
      I have to admit that I run IE on it, yes. And IE for Mac crashes occasionally, but doesn't take the system down as on a Windows machine.
      I tried Opera, but it doesn't cut it because the proxies are defined within the application and not within the OS. When I change network location (work to home), this stuff changes and I'd need to type it in each time.

      As for office: I have Apple Works because it came with the machine...No I rarely use it. Applications most used are probably Terminal, IE, ICQ, Mail, Apache, FTP, Project Builder and Samba. I touch office applications about once a month. I still hope for a Mac OS X port of openoffice :-)

    20. Re:Unix is the future. by rusty+spoon · · Score: 1

      It's not important where ideas come from, what's important is that we do indeed build on them. (*)

      "If I have seen further, it is by standing on the shoulders of giants" - Sir Isaac Newton

      * - Patents aside I guess

  2. This isn't surprising. by saintlupus · · Score: 5, Interesting

    Bill Gates running vi

    I don't know why this in particular would stick out as something surprising. People on this site seem to forget that Gates is a serious geek - he's not some MBA who got lucky. I wouldn't be surprised if he _still_ uses vi, maybe even under Cygwin, on his own machines.

    --saint

    1. Re:This isn't surprising. by Marcus+Brody · · Score: 2

      I wouldn't be surprised if he [Bill Gates] _still_ uses vi, maybe even under Cygwin

      No need. He can use vi for windows.

      ANd yes, I wouldnt be suprised if he did use it. I have heard that quite a few senior MS employees use windows ports of classic UNIX apps. After all, most UNIX apps take some getting used to - but once you do get to know them, they are unbeatable. As the reg article illustrates, many MS people come from a UNIX background, and it is not really suprising they have taken some of this with them.

    2. Re:This isn't surprising. by O2n · · Score: 5, Funny

      I wouldn't be surprised if he _still_ uses vi

      Maybe this will become the single most powerful argument in the emacs vs. vi religious war. :)

    3. Re:This isn't surprising. by Luke+Marsden · · Score: 0, Redundant

      "Use emacs, because Billy Gates uses vi."

    4. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      "he's not some MBA who got lucky"

      What have you been smoking ?

      Next you'll be tell us he is a visionary that has a good understanding of technology.

      Hes just another meglamainiac

    5. Re:This isn't surprising. by dzym · · Score: 2

      Yeah, but for which side? "Bill Gates uses vi! Emacs is god!" ? :)

    6. Re:This isn't surprising. by billy_troll · · Score: 0

      noits not surprising as vi is for losers.
      you want the mighty emacs
      it kicks your butt anytime

      --
      -----im billy troll----- im better than you at everything you do.
    7. Re:This isn't surprising. by O2n · · Score: 1

      obviously... (for me at least).

    8. Re:This isn't surprising. by fredrik70 · · Score: 1

      Does coding in your head straight to x86 binary code make you a geek?
      um yes, I would say that makes you a quite hardcore geek...
      seriously though, you might think vi is and old and hard-to-use editor, but it is popular for a reason, it's not only a 'religious' thing. once you have get used to a tool like vi it seems you're stuck for pretty much life. Got a guy at work who does everything in vi and it's not that he haven't used other editors, he's not even a unix person, pretty much pragmatic over his OS.

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    9. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      My heart is really with emacs, but vi also does out-of-memory editing by default (i.e. don't load the whole damn file into RAM), so you can just vi an ISO or a massive text file without breaking a sweat.

      Does anyone know of an out-of-memory editing mode for emacs? Right now I'm using vi for very-large-file work and emacs for all my day-to-day work.

    10. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      M E G A L O M A N I A C

      see it, repeat it, write it down, retain it.

      megalomaniac: a pathological egotist.

    11. Re:This isn't surprising. by fredrik70 · · Score: 1

      He might not use the nicest of business methods, but that doesn't stop him from being a geek. BG dropped out of Uni. and yes he could code

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    12. Re:This isn't surprising. by Kircle · · Score: 1

      Even though the article implies that Microsoft is being a hypocrite, I don't think that is this case here. Microsoft is saying that their business model is superior. I guess the best product does not always perform the best in the marketplace.

      --

      -- Kircle

    13. Re:This isn't surprising. by PlaysWithMatches · · Score: 2

      Perhaps vim for Windows would be a better choice. I haven't tried "WinVi" but when I'm forced to suffer in a Windows environment from time to time, it's nice to just use vim. It's consistent with what I run on my home machines after all. :)

      --

      Mozilla's a nice operating system, but it needs a better browser.
    14. Re:This isn't surprising. by saintlupus · · Score: 4, Insightful

      I guess the best product does not always perform the best in the marketplace.

      Well, shit, you just blew all my fourth grade course material on economics right out the window.

      Of course it doesn't. Ever heard of BeOS, or OS/2? How about car companies like DeLorean or Tucker, or hell, even AMC?

      --saint

    15. Re:This isn't surprising. by thogard · · Score: 1

      If I had enough money, I could get people to swear I can code too.

      I've meet someone that I think is clued in who has been dealing with MS since 1974. The story goes that there was an op code in an assember that didn't work right. Clued in geek calls MS and talks bill into making a patch. The patch is sent out and the new opcode works if you type it in call CAPS and not will most aruments since it wasn't added to the op code table but hard coded.

      So far none of the "Bill gates could code" pages ever show any code he did him self but talk about code he might have managed. Come up with some more details and maybe you'll have a point.

    16. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      no bill gates uses microsoft word's voice recognition features to type all his documents now.

    17. Re:This isn't surprising. by Hank+Kingsley · · Score: 1

      I have heard that quite a few senior MS employees use windows ports of classic UNIX apps.

      And quite a few of the current "grunts" at MS also use vi & emacs.

    18. Re:This isn't surprising. by calumr · · Score: 1

      Do you think Gates has ever tried emacs? I'd love to be a fly on the wall at that moment.

    19. Re:This isn't surprising. by Anonymous Coward · · Score: 2, Interesting

      Personnally (sp?), I am wondering if this "Gates is really a geek" is not some sort of personality cult, like that of Chairman Mao's or Joseph Stalin's. How soon before we hear about is superhuman feats?

      Cookies to doughnuts that Gates is just a competent programmer, no more, who was just a very good student of the Ancient Ways of IBM (remember, Big Blue was one the Evil Empire -- read "BIG BLUE: IBM's use and abuse of power", an account of the darker side of our "favorite" Linux company...) and who has this incredible drive to crush anything that might smell like competition.

      Not to troll, but I will more readily accept accounts of Woz', Gary Killdall's or even Doug Enghelbart's (sp?) geekyness than those of billg's.

    20. Re:This isn't surprising. by Chan · · Score: 2, Funny

      Whenever I try to use other editors, I keep ending up with llll or jjjj inserted in my text.
      Pico does not like escapes much.

      --
      (nil)
    21. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Bill Gates running vi, difficulties with

      for the dyslexic among us, i thought the above read as "Bill Gates running vi with difficulties"

    22. Re:This isn't surprising. by Yarn · · Score: 5, Funny

      Oh crap. Erm... Hitler used emacs?

      ** Use of Hitler in Arguement Detected: AUTOMATIC LOSS **

      Ok, I lose.

      --
      -Yarn - Rio Karma: Excellent
    23. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      vim is, indeed, widely used among us MS grunts. Lots of us even read /.

    24. Re:This isn't surprising. by JamesOfTheDesert · · Score: 1
      Come up with some more details and maybe you'll have a point.

      Go dig up the bok Programmers at Work, Microsoft Press, 1986, ISBN 0-914845-71-3, and look at the interview with Bill Gates. It includes some source listings, plus there are more listings in the appendix.

      It's a pretty good book, too.

      --

      Java is the blue pill
      Choose the red pill
    25. Re:This isn't surprising. by Komodo · · Score: 3, Interesting

      Now, I don't know Bill personally, but I did read 'Hackers', and I've seen his mug shot for the Albequerque PD. He may be a serious geek, but if we judge by competence, he's also a LOSING serious geek.

      According to 'Hackers', Bill's BASIC program for the MITS Altair was big, slow, bloated, late, didn't work well, and (here's the kicker) required an expensive 4k memory expansion board from MITS that basically didn't work.

      Compare to today, where we have Windows , which is... essentially the same, right down to the excessive hardware upgrade treadmill.

      The point? Bill's spirit rules the place. Bill hasn't changed. I don't think he's learned ANYTHING in the technology arena except how to muscle it around with money. That's not the same as being a 'serious geek'. Essentially, he IS an MBA who got lucky.

      It must be really sad. He's got all the money in the world, but it can't buy him cool points. So he sits there in his billion-dollar house, crying himself to sleep because he's still no closer to the nirvana of technical competence than he was back in 1977.

      Software will flourish if Bill learns to accept his inadequacies and stop trying to take over the world.

    26. Re:This isn't surprising. by bwulf · · Score: 3, Insightful

      Sorry, doesn't work that way.

      See http://www.faqs.org/faqs/usenet/legends/godwin/.

    27. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Well he hasn't written a line of code in 15 years. He is obviously not a geek.

    28. Re:This isn't surprising. by Hank+Kingsley · · Score: 1

      I am aware of which vi port most MSers use. Excuse the hell out of me.

    29. Re:This isn't surprising. by Art+Tatum · · Score: 1
      Ever heard of BeOS, or OS/2?

      Screw those. What about NeXTSTEP?

    30. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Oh gee, a book printed by MS hailing Mr. Bill as being a good programmer. BULLSHIT. Say no more. He is a cult of personality for all those that really wish they posessed the brains enough write code, and nothing more. Bunch of MBA students who feel left out!

    31. Re:This isn't surprising. by Zeinfeld · · Score: 3, Interesting
      Do you think Gates has ever tried emacs? I'd love to be a fly on the wall at that moment.

      I would be suprised if he hadn't. Melinda is a LISP weenie.

      Ever wonder who was in charge of Microsoft 'Bob' ?

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    32. Re:This isn't surprising. by nickynicky9doors · · Score: 2

      AMC?

      *Gremlin, are we talk'n Gremlin here?

      Only a mother could love a geek; and only a geek could love a Gremlin

      It's a fact live with it. :)

      --

      heuristic algorithm seeks stochastic relationship
    33. Re:This isn't surprising. by snake_dad · · Score: 2

      A word of comfort, Chan: You Are Not Alone. :-)

      --
      karma capped .sig seeking available Slashdot poster for long-term relationship.
    34. Re:This isn't surprising. by leandrod · · Score: 2

      Only that he's not really a MBA. He got at least a honoris causa title from Holland, in a move by a business school-mistakenly-turned-University that is regretted by Edsger Wybe Dijkstra at his convocation speech for the graduates of the College of Natural Sciences of the University of Texas at Austin in December 1.996.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    35. Re:This isn't surprising. by leandrod · · Score: 2

      > Melinda is a LISP weenie.

      I’d love to see some proof of, some reference for this. Looks like a simple joke

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    36. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Isn't OS X a decendent of NeXTSTEP?

    37. Re:This isn't surprising. by twalk · · Score: 3, Funny

      "Fall 2001 Ken Lay needs to provide something he wholly owns as loan collatoral, Cheney disappears, Coincidence?"

      +10 Funny!

    38. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Very cool. I'd forgotten about this little bit of comedy. But it is still funny. I use to love use net.

      Dave Rosser Jr.

    39. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      Yeah, this begs the question: what did Gates *REALLY* write, what great hacks did he pull off? Did he really write Altair BASIC or did he rip it off (wouldn't surprise me)?

      Who'se the guy who said he's the one who wrote most of the code that Bill's apologists claim he wrote? I do remember reading this in a book sometime ago, but I lent it to someone who never gave it back.

    40. Re:This isn't surprising. by SoftwareJanitor · · Score: 2

      Many people have suggested that the design for Altair BASIC was largely cribbed from the DEC BASIC that Gates had worked with while interning with DEC when he was still a Harvard student. And many others also say that most of the important coding on Altair BASIC was actually done by Paul Allen, who certainly has more unassailable geek credentials than Gates.

    41. Re:This isn't surprising. by zulux · · Score: 1, Troll

      People on this site seem to forget that Gates is a serious geek - he's not some MBA who got lucky.

      No. He's a spoiled brat, born with a silver spoon in his mouth. Do you think he would have gotten the traff-o-data gig, if it wasen't for his mommy pulling strings, or started Microsoft without Daddys seed money.

      Daddy Gates is a true rags to riches stroy - Baby Bill just stood on his shoulders.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    42. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      The Big Cheese at IBM was known to remark "Oh, isn't the Melinda Gates' boy?" when Bill was in the building. Yup, no connections or funny handshakes there!

    43. Re:This isn't surprising. by sheldon · · Score: 3, Insightful

      BeOS, OS/2, etc only add further proof to the claim that the best product always wins in the marketplace.

      The problem with your 4th grade education is that you have to understand that the definition of "Best" is not defined by you, but rather by consumers.

      As far as Tucker... That story is frequently exagerrated. Here's part of the story from someone who worked for Tucker:

      http://www.dispatch.com/wheels/autonews/tucker06 30 .html

    44. Re:This isn't surprising. by Anonymous Coward · · Score: 0

      I have photos of her and RMS fondling a Symbolics machine.

    45. Re:This isn't surprising. by Art+Tatum · · Score: 1
      Isn't OS X a decendent of NeXTSTEP?

      Yep. But since Apple included a compatibility environment, no one is using the incredibly sexy OPENSTEP API. Instead, everyone just uses the kludgy old Mac OS APIs. Like Adobe. And Microsoft. Otherwise, it would be pretty easy to build these applications with GNUstep (which would then run on FreeBSD, Solaris, Linux, whatever). Objective C blows C++ away (and you can learn it in an afternoon, if you already have OO experience) but it will never reach critical mass because of inertia. (How's that for mixed metaphors?)

    46. Re:This isn't surprising. by madenosine · · Score: 1

      Bill Gates might not be rags to riches, but how many other people can you name who created a Fortune 500 company in their lifetime?

      I mean seriously, what else would he have to do to get your respect?

    47. Re:This isn't surprising. by Drazi100 · · Score: 0

      Yeah right, ask any marketing guy if consumers buy the best products. They will say consumers are frickin retards that succumb easily to basic principles of psychology. Unless of course they are selling you something.
      Salespeople must love you.

    48. Re:This isn't surprising. by Datafage · · Score: 1
      I mean seriously, what else would he have to do to get your respect?

      Do it legally.

      --

      Nicotine free Amish .sig.

    49. Re:This isn't surprising. by leandrod · · Score: 2

      Well mr AC, perhaps that’s some kind of joke that makes sense to people with a better command of the English language than mine but I’ll run the risk of asking you to post this photos somewhere.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  3. It's a weak form of Unix by MBCook · · Score: 5, Funny

    NT is a weak form of unix like a donught is a weak form of a particle accelerator.

    --
    Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    1. Re:It's a weak form of Unix by p3d0 · · Score: 0, Offtopic

      Check your sig. It's "repetitive".

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    2. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      It really pisses me off that IBM didn't take UNIX back then. We could have had UNIX everywhere now. None of that painful command.com stuff. Course, it'd probably be csh instead of bash, but nothing's perfect.

      Of course, from what I've heard of SCO, we might be using a pretty awful UNIX...

    3. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      Put a magnet in the hole and put it next to the local MSCE's monitor.

    4. Re:It's a weak form of Unix by fredrik70 · · Score: 1

      do not underestimate the power of a doughnut

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    5. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      If PacMan did, we'd all be eating pills and listening to repeditive music...

      Sounds like a pretty accurate description of a raver to me..

    6. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      Well shit Einstein, you sure got him! You must be like one of them there comedy telling people, ain't ya?

    7. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      Microsoft, in the shape of Gates and Paul Allen, kicked off with Basic, and followed up in 1978 with Fortran.

      This sentence implies that they came up with
      fortran, which I believe was developed in the
      late 1950's. I wish that these types of
      sentences would be more explicit, like
      "these two guys had other people port fortran
      to DOS". Man that must have been a serious
      number crunching machine.

    8. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      Yeah. But your sig kicks arse though.

    9. Re:It's a weak form of Unix by Rotten168 · · Score: 1

      Horseshit, I used SCO at work running on a Zenith server, it's fine. The only time it crashed was 'cause my last company used cheap, crappy hardware that failed.

    10. Re:It's a weak form of Unix by csbruce · · Score: 1

      This sentence implies that they came up with
      fortran, which I believe was developed in the
      late 1950's.


      So? They didn't exactly invent BASIC either.

    11. Re:It's a weak form of Unix by Anonymous Coward · · Score: 0

      yeah but basic sucks and is in my
      opinion inconsequential to computing.
      Fortran however is still going strong
      and is still the best mathematical
      modeling language.

    12. Re:It's a weak form of Unix by troff · · Score: 1

      Mmm... weak particle accelerators... is there anything they can't do?

      :-)

    13. Re:It's a weak form of Unix by rark · · Score: 2

      Try feeding a doughnut to a hyperactive four year old and get back to me.

  4. Windows NT == VMS by quark2universe · · Score: 5, Informative

    "And through Windows NT, you can see it throughout the design. In a weak sense, it is a form of Unix."

    Actually, Windows NT was built very much like VMS, the operating system for the VAX built by DEC. David Cutler, one of the main architects for VMS, was hired by Microsoft to build Windows NT. The name Windows NT itself is one of those HAL like play on letters where each letter is the VMS letter plus 1. WNT VMS

    --

    Believe in things of which no person has ever learned
    1. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      I've read in several books about Microsoft that NT stands for "new technology." A great book called Showstopper! has a detailed account of how NT was built.

    2. Re:Windows NT == VMS by s20451 · · Score: 2

      In the novel 2001, the joke about HAL was that H, A, L are one letter before I, B, M, so HAL was one step ahead of IBM. (There was also an expansion of the acronym: Heuristic ALgorithmetric, I think.) Applying the same logic, are we saying that WNT is one step behind VMS?

      --
      Toronto-area transit rider? Rate your ride.
    3. Re:Windows NT == VMS by O2n · · Score: 1

      A great book called Showstopper! has a detailed account of how NT was built.

      Well,this seems to me as the most inspired title a book about the origins of NT could get. Mmmm... unbeatable. Thanks, Anonymous Coward! :)

    4. Re:Windows NT == VMS by Michael+Winser · · Score: 3, Informative
      NT stands for n10 which was the intel codename for the i960 risc processor. The n10 was the first platform to run Windows NT.

      NT actually started life as OS/2 3.0, not Windows.

    5. Re:Windows NT == VMS by AtrN · · Score: 2

      The N10 was the i860. Very different beast to the i960s.

    6. Re:Windows NT == VMS by quark2universe · · Score: 4, Interesting

      NT is one or more steps behind VMS. Some people who were only users of VMS didn't like it because it had a clunky command line interface. BUT, under the hood, VMS was an awesome operating system. I know because I took many internals classes, and worked with it for many years as an operator, system manager, DBA, and programmer. A large reason for it not being more successful was that DEC had no marketing intelligence whatsoever. Their engineers, on the other hand, were the best. Did you know that VMS had clustering in the 1980's? Everyone else is still struggling to get that right.

      --

      Believe in things of which no person has ever learned
    7. Re:Windows NT == VMS by Paradise+Pete · · Score: 3, Funny
      Since I'm self employed, my comments DO reflect those of management.

      I'll bet you get to be employee of the month a lot, too.

    8. Re:Windows NT == VMS by maggard · · Score: 5, Informative
      In the novel 2001, the joke about HAL was that H, A, L are one letter before I, B, M, so HAL was one step ahead of IBM.
      Actually Arthur C. Clarke has denied this repeatedly, loudly, and at this point irritably. He even wrote Byte Magazine a few years ago correcting their reference to this geek lore. He claims this is just one of those accidents that happens and indeed in his book "The Worlds of 2001" goes into a bit on how HAL's name actually did come about: Pretty much happenstance, it was "Athena" through most of drafts.

      IBM/HAL, Santa/Saten, its all part of a biiig plot...

      --
      I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
    9. Re:Windows NT == VMS by accessdeniednsp · · Score: 2, Informative

      actually NT stands for New Technology. in the sense of full 32bit memory management and address space, concept of "rings" to pull apps away from the core kernel and into what we call "userland". NT was a detraction from the norm at the time (os/2 and win3.1). os/2 had good stuff. it's now part of NT (3.51 at the time). NTFS == HPFS (in 3.51, improved upon in 4.0). also gives us various permissions, multi-user, true multitasking, networking, extendable networking model (ipx, ip, netbeui, dlc, whatever else u wanna write).

      all in all, not a bad idea: on paper :) we all know how the real-life implementation turned out. but they were/are still learning.

      enjoy!

    10. Re:Windows NT == VMS by SlimySlimy · · Score: 1

      I always thought "NT" stood for "Northern Telecom".

      Look on the side of a Windows NT or Windows 2000 retail box. It says right on the side, "NT is a trademark of Northern Telecom Limited."

      hmmmm

      --
      This sig provides no comical value.
    11. Re:Windows NT == VMS by DigiBoi · · Score: 0, Offtopic

      IBM/HAL, Santa/Saten, its all part of a biiig plot...


      it's ingrates like you that make satan smile!

      --
      I put on my robe and wizard hat.
    12. Re:Windows NT == VMS by VAXman · · Score: 5, Informative

      VMS was hugely successful. It was the most successful minicomputer OS of all time, and made DEC filthy rich in the 80's.

      What killed VMS was not DEC, but Unix - mostly Sun. Their stuff was 10x as fast at 1/10 the price, so people bought Sun instead. DEC was never really able to adapt from the closed proprietary business model to the open commodity business model. Even with Alpha, DEC never got more than 1% of the Unix market.

    13. Re:Windows NT == VMS by kermit6306 · · Score: 2, Informative

      You're right, Microsft's Windows NT was designed by the same group of people that created VMS. NT is very similar is DEC's (now Compaq) VMS. So similar, in fact, that DEC thought that the situation warranted litigation. DEC filed a complaint against Microsoft. Apparently, even Microsoft's legal department thought DEC had a case. The parties eventually settled out of court for a rather large amount of cash.

    14. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      And of course HAL is 1+ more than IBM

    15. Re:Windows NT == VMS by Speed+Racer · · Score: 1

      Mmmm... unbeatable

      CLONE! That's my favorite sound bite.

      --
      Free Mac Mini. Yes, I'm
    16. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      Since I'm self employed, my comments DO reflect those of management.

      I'll bet you get to be employee of the month a lot, too.


      Funny.

    17. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      Since you are the VAXman, do you know the relative popularity of UNIX versus VMS on VAX hardware? At least when I was in University, it was all UNIX, but I suspect the corporate markets were VMS.

      While VMS is still a nice revenue stream for Compaq, it's too bad they stopped the marketing push. Look at IBM AS/400 -- still making them filthy rich.

    18. Re:Windows NT == VMS by Slashamatic · · Score: 2, Informative
      Cutler was Mr RSX-11M but Andy Goldstein was also part of the team for VMS. Both names are on as architects on the Starlet report (the arch document for VAX/VMS). Cutler is very good but he isn't perfect. Andy did a lot of the later VMS security stuff and he was responsible for the file system.

      Th VMS file system was awesome, it worked transparently across a cluster in the early eighties and it supported ISAM out of the box. If you paid extra, you even got transaction journalling, on straight files. Anyway, Andy G stayed with Digital so you only got part of the time working on NT.

      Another point is that Cutler is a legendary coder, he added paged support to 11M over a weekend, but I guess that he wasn't much of a team worker.

      I agree about the market/sales droids - they were considered legendary in their awfulness even within the company.

    19. Re:Windows NT == VMS by csbruce · · Score: 2

      "The Worlds of 2001" goes into a bit on how HAL's name actually did come about: Pretty much happenstance, it was "Athena" through most of drafts.

      But they couldn't get Majel Barrett to do the voice work?

    20. Re:Windows NT == VMS by Big+Jason · · Score: 1

      (VMS)++ == WNT

    21. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      concept of "rings"

      I'm sure you know this, but just in case anyone else gets any ideas, this was originally implemented as part of MULTICS

      MULTICS & Algol 60. You all own these two bits of history big!

    22. Re:Windows NT == VMS by Zeinfeld · · Score: 3, Informative
      What killed VMS was not DEC, but Unix - mostly Sun. Their stuff was 10x as fast at 1/10 the price, so people bought Sun instead. DEC was never really able to adapt from the closed proprietary business model to the open commodity business model

      The price performance was never quite that extreme, SPARC was about double to tripple the price performance of the equivalent VAX workstation when it first appeared.

      The thing that killed VMS was not UNIX, it was RISC. People moved to Sun in spite of UNIX, and for that matter in spite of Sun's quality control. In those days, interms of reliability SunOS was to VMS what Windows 3.1 was to AIX.

      Incidentally, DEC was a very early member of the UNIX club. The first virtual memory UNIX was developed on a VAX. It is a pity that Thomson et. al. were so determined to learn as little as possible from the design of VMS.

      In the very early years Sun attempted to license VMS. DEC refused, claiming that it could not be ported because of the dependency of VMS on a couple of fairly specialized processor instructions, like remove from head interlocked and the security ring instructions.

      The reason DEC was so far behind Sun in the first place was that their bean counters axed the PRISM project that was meant to built the successor to VAX and VMS. Dave Cutler left DEC for MSFT and vowed to force DEC to buy the O/S they could have had for free - whats more he did exactly that. When the Alpha chip appeared much later than SPARC it was named AXP or Almost Exactly Prism as insiders call it.

      WNT is not VMS but it has most of the best features of VMS and is the type of thing you might build if you were designing a sucessor to VMS but did not need to have backwards compatibility.

      There are a bunch of late VMS features that WNT is noticably lacking, in particular the transactional file system. Hopefully we may see some of that appear in OFS. What is disappointing about WNT is that many of the interesting O/S features are sumberged in low level APIs. It is possible to do VMS tricks like ASTs but you have to really know the layout of the O/S.

      Unfortunately there is no guide that compares with the Digital VMS architecture manual.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    23. Re:Windows NT == VMS by Anonymous Coward · · Score: 0
      Well, since I have a copy of "2001" on DVD, and have refreshed my memory several times (since seeing it in first run back in the 60's), I find the "removal of product placement" story to be the most likely.

      In this version of the legend, the IBM labeling was removed/not used after it was determined that most of the movie's plot line in the second half revolved around an AI that has gone crazy as well as homocidal (e.g., not very good from a marketing standpoint). I like this story, because so much of the hardware used (in terms of consoles/keyboards, displays, and even HAL's various "eyes" - which had heavy chrome bezels around a black background) was very IBM-like.

      Even more ironic, IBM has been using two guys in replicas of the space suits from the movie (although they are usually blue in color, not yellow or white) for 2001 and 2002 advertising campaigns. So, maybe HAL was not IBM hardware, but certainly Dave must have been IBM "wetware"! This might put a whole other spin on Dave's turning off HAL in the the major scene in the computer core ("Dave ---- my mind is going; are you from a competitor?").

      --AC--

    24. Re:Windows NT == VMS by cpeterso · · Score: 1


      Windows NT was built very much like VMS, the operating system for the VAX built by DEC

      According to the book "Showstopper", Cutler was working on a DEC project called Prism. Prism was a new DEC computer which would run a new operating system called Mica. Mica was an "object-oriented" follow-on operating system to VMS and would have backward compatibility support for Vax applications.

      DEC canned the Prism/Mica project, Cutler was pissed and joined Microsoft. Windows NT is much more influenced by Mica than VMS.

    25. Re:Windows NT == VMS by Anonymous Coward · · Score: 0

      In the novel 2001, the joke about HAL was that H, A, L are one letter before I, B, M, so HAL was one step ahead of IBM. (There was also an expansion of the acronym: Heuristic ALgorithmetric, I think.) Applying the same logic, are we saying that WNT is one step behind VMS?

      Why wasn't this modded up +1 Funny? LOL.

    26. Re:Windows NT == VMS by gorilla · · Score: 2
      Incidentally, DEC was a very early member of the UNIX club. The first virtual memory UNIX was developed on a VAX. It is a pity that Thomson et. al. were so determined to learn as little as possible from the design of VMS.

      Unix was first introduced in 1970, and had all the features we'd recognize by 1975 or so. VMS was first introduced in 1978, but still required RSX until 1980. It's hard to learn from stuff which hasn't been done yet.

    27. Re:Windows NT == VMS by egoots · · Score: 1

      As I understand it, the concept of "rings" for different privilege levels in a processor was introduced by Data General. Please refer to "Soul of a New Machine" by Tracy Kidder for details.

  5. Huh? by joshjs · · Score: 1

    Doesn't windows run on top of UNIX? ;p

    1. Re:Huh? by Anonymous Coward · · Score: 0

      Um, NO

    2. Re:Huh? by SuperCal · · Score: 1

      I remeber reading... a long time ago... that NT was going to be(is?) built on a Mach-like kernel, which, from my limited understanding is used by several UNIX OSs. This may be where the misunderstanding came from...

      --
      Business News and Resources: www.usasource.net
    3. Re:Huh? by archen · · Score: 1

      if by UNIX you mean the Internet, then yeah, sorta.

    4. Re:Huh? by Anonymous Coward · · Score: 0

      To be accurate, it runs on top of Linux - at least if you count wine (the least buggy Windows version ever).

    5. Re:Huh? by jimfrost · · Score: 2
      You're likely confusing NT with OSF's operating system. The two were developed more or less concurrently. OSF was Mach based. NT was highly derivative of Prism, which was a next-generation portable VMS (which got cancelled, and that has a lot to do with how Cutler and clan ended up at Microsoft).

      The other possibility is that you're confusing NT with NeXT, but I really hope not :-).

      --
      jim frost
      jimf@frostbytes.com
  6. So Scientology has Xenu... by dukethug · · Score: 2, Funny

    ...and Microsoft has Xenix.

    Coincidence? I think not.

    1. Re:So Scientology has Xenu... by WWWWolf · · Score: 1

      Oh, yeah. definitely not a coincidence.

      Xenix was that Evil Overlord who v-bombed the PCs in planet Iibee-em (the Earth), was vanquished by the Loyal Officers and is now trapped somewhere and will return some day.

      Or something like that =)

  7. ms agreed to never again produce a version of unix by Anonymous Coward · · Score: 1

    I heard that to settle a legal dispute MS agreed to NEVER produce a version of UNIX.

    I dont have any more detail than that, can anyone back me up with details ?

  8. a glorified email terminal by Speare · · Score: 4, Informative

    When I worked at Microsoft in the early 90s, the role of Xenix was pretty much relegated to a glorified email terminal. A few old-timer people on the teams I worked with used it, and few of those people did anything but read their email remotely on the Xenix email servers. I don't recall anyone actually running Xenix on any box within their own office.

    At no time did I get the impression that a developer at Microsoft felt that Xenix/UNIX was the future of the desktop. It was big, it was bloated, it couldn't run on then-current PCs well, nevermind the smaller machines of the mid-80s.

    Sure, maybe there were some hold-outs in groups I didn't interact with, and I was only there long past Xenix heyday, but Xenix had no chance at the desktop, really.

    --
    [ .sig file not found ]
    1. Re:a glorified email terminal by Chas2K · · Score: 1

      Yeah Xenix was bloated. I had the WHOLE enchilada on a 30 meg drive sharing space with DOS. Later SCO UNIX came along with X Windows and an emulator that ran MS Windows 3.x. It ran like a scalded dog on 4 meg of RAM and a shared 40 meg drive also running DOS and Windows 3.1. 20 developers and a communication app. The Xenix box cored one day, was rebooted and never went down again. The SCO UNIX box never stopped. If it didn't run well on your box it might be a personal problem.

    2. Re:a glorified email terminal by Anne+Thwacks · · Score: 2, Interesting
      SCO was the Santa Cruz Operation (Of Microsoft). They produced Xenix.

      Xenix was a not very good Unix. It was not expecially bloated. It was not especially reliable, and not especially expensive. In fact, it was average.

      However, it was promoted by MS, until they got bored with it, and sold it. I think it was a management buy-out, which involved MS agreeing never to make a competitive Unix - obviously, otherwise the management would have been shafted in weeks, when MS would have launched ZooNix or something and stolen the market, using a copy of the user base which they had "forgotten about" on a server somewhere. The Xenix name was later used for a version which could run on machines with little or no memory management - eg a 286. (Like Minix and Idris) This was a lame idea from the start, and did not survive the introduction of the 386 commercially.

      --
      Sent from my ASR33 using ASCII
    3. Re:a glorified email terminal by Lumpy · · Score: 4, Informative

      you are so full of Shit you stink.

      Xenix ran fine on a 386DX-35 platform supporting 10 users off of that ONE computer using Wyse 75 terminals. It supported several businesses helping with Multiple tasks in that company using that ONE computer. Excalibur was the best Business accounting/inventory/Point of Sale software on the market at that time (1992) It ran faster than anything that microsoft offered it gave you more productivity than anything that Microsoft offere'd then and NOW from your equipment and coince it was really written by a group that were outside Microsoft at the beginning, bought by them and then re-sold (SantaCruz Operation) it was never tainted with the Microsoft Style. The Only thing that sucked about Xenix was that the Xwindows system was horrible and required specalized hardware, Compiling X11 on it solved that problem. ..

      SCO Xenix was a awesome thing at the time, and I still have the origional disks and Manuals from that 386 version.

      --
      Do not look at laser with remaining good eye.
    4. Re:a glorified email terminal by YetAnotherName · · Score: 2, Insightful

      I can corroborate that. I worked at Microsoft in the early 90's, too, as a tech writer. Sure enough, there was troff for the users' manual for Microsoft C Compiler. Most of the other writers edited on their desktops and then uploaded to a Xenix box for formatting.

      The only other use for Xenix was to check your email.

    5. Re:a glorified email terminal by Anonymous Coward · · Score: 0

      ...the role of Xenix was pretty much relegated to a glorified email terminal

      Oh! So it's exactly the same as it is today with Linux then? it's amazing how little things change in the unix world...

    6. Re:a glorified email terminal by Stuart+Park · · Score: 1

      Yes Xenix on a 386 ran quite well.. but the earlier versions of Xenix were basically garbage. Many years ago I worked for a company writing unix/xenix applications, and the xenix 286 machine was the one we all dreaded using the most - with all the other unix machines being far superior (although I admit that was a combination of hardware and operating system).

      Also, Xenix had the WORST version of UUCP I had ever seen.. I very quickly replaced it with Taylor UUCP.

    7. Re:a glorified email terminal by Anonymous Coward · · Score: 0

      Xenix was my first experience with Unix, I believe it was an Altos 386 system no bigger than a pc tower, it can boot with 5" diskette and use green terminals. At that time we have about 10-15 people working on it at all times but no internet connection though (small comp school).

      We used to complain about its speed and we work out to not start a compilation at the same time or it will drag along.

    8. Re:a glorified email terminal by Lumpy · · Score: 2

      the 10 user mark is the MAX suggested. It would do more than that but the reccomended number of users per machine was 6 (including one at the machine it's self.) Most of the speed problems you saw was of overloading the system with too many users. yes compiles were slow AND slowed the machine (It's a 386 for poop-sake! what do you expect?) when you had multiple users, the C compiler ran by default with almost 0 nice level and would consume most of the cycles for it's self. for regular business, printing invoices, packing slips, accounting, inventory management, shipping and recieving, plus offering 3 dial in lines for salesmen on the road to call and place invoices. (giving XT laptops to sales people with hothing more than a VT-100 emulator on it was great!
      bn

      --
      Do not look at laser with remaining good eye.
  9. Gates as a closet Linux user by Anonymous Coward · · Score: 4, Funny

    I can see that being revealed in the future. By day CEO of Microsoft, by night coding for 10 different free sofware projects under psuedonyms, like B1ll G4t3s.

    1. Re:Gates as a closet Linux user by Ivan+Raikov · · Score: 1

      Oh, THAT's why KDE and Gnome look more and more like Windows. Thanks for straightening it out... :-)

    2. Re:Gates as a closet Linux user by Anonymous Coward · · Score: 0

      no, B1FF G8z...

      and he's porting viruses to UNIX!

  10. NHS by Anonymous Coward · · Score: 1, Informative

    If I remember correctly my Dad's GP surgery (England) used to use Xenix

    1. Re:NHS by hmallett · · Score: 1

      If it was Meditel System 5 (later acquired by Torex) then it was probably migrated to SCO Unix quite some time ago.

  11. Re:FR15T P@5T by Anonymous Coward · · Score: 0

    heh, what's the world coming to when we have to correct 31337 speak?

  12. Vi's longevity. by saintlupus · · Score: 2

    Since when does running "vi" make you a geek? Vi is just yet another antiquated shitty text editor that should die off.

    (-5, Troll)

    --saint

  13. Re:The Microsoft Borg analogy by 56ker · · Score: 2, Funny

    The phrase "Your technological distinctiveness will be added to our own" springs to mind.

  14. Wrong Way by Aglassis · · Score: 2, Funny

    Yeah vi is for losers. Any true geek uses ed.

    --
    Suddenly, the hairy finger of a familiar monkey tapped me on the shoulder. It was time.--G. T.
    1. Re:Wrong Way by birder · · Score: 1

      I use copy con [filename]

      I have to rewrite my files everytime I need to make a change. Just makes me do it right the first time...

    2. Re:Wrong Way by halfnerd · · Score: 1

      actually in unix it would be: cat > file (write your stuff and press Ctrl-C)

    3. Re:Wrong Way by Anonymous Coward · · Score: 0

      Haven't you heard about the editor upgrade? You
      can use COPY CON >> file and add to an existing
      file. To cool! What will Bill Gates innovate
      next?! ;)

    4. Re:Wrong Way by hawk · · Score: 2
      >Yeah vi is for losers. Any true geek uses ed.


      Come on, man. Show a little self respect!


      If you're not good enough to manipulate core planes directly with a magnet, you can at least use cat & sed to do your editing . . .


      hawk

  15. Cut N Paste? by Anonymous Coward · · Score: 0

    How do you cut n paste in vi ?

    beyond the basics of vi ( insert, escape, :q :w :q! :wq! / // etc etc... most people don't how to do moderately complicated stuff that's easy in almost any other editor

    I've asked several people, and none of them know how to cut n paste in vi. Most of them recommended opening up a Samba share in the /etc/smb.conf or using FTP to transfer files to Windows to cut n paste in the file, and then transfer the files back. This doesn't indicate a good editor. Perhaps if the vi guys actually provided readable documentation, it'd gain market share. For now, it doesn't have my vote.

    1. Re:Cut N Paste? by Anonymous Coward · · Score: 1, Informative

      yy dd p

    2. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      Use vim, not vi. And try :help

      Additionally, you can use the mouse to cut and paste to any application in X, using the middle mouse button, or a chord of the left/right.

      If using the console, make sure you're running gpm, and the mouse cut/paste features will be available there.

      Or, you can learn a little sed, and edit the file without even knowing where it is:

      for i in `find ./|grep bla`;do cat $i|sed s/cut/paste/g >$itemp;mv $itemp $i;done

    3. Re:Cut N Paste? by thogard · · Score: 1

      If your using :wq you do not understand so give it up.
      :wq was replaced by :x in a very early version of bsd. I still don't know where these young whipersnapers learn about the :wq as it was made obsolete in 1978 and I don't think there are too many /. people let alone Unix users that predate that.

    4. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      dd p
      No need for a yy

    5. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      open up another xterm with the text of what ever file you want, put vi into insert mode, and insert the text with the center mouse button. just don't try to insert text in command mode. sheesh.

    6. Re:Cut N Paste? by Chan · · Score: 1

      You can always do ZZ as well. I'm guessing that we (and I'd never learned about :x either) have simply learned all we know about vi from professors and mentors who do predate that.

      BTW: if you do a :x! what does that do? (:w! :q, or :q! ?)

      --
      (nil)
    7. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      If you look at the old code,
      the lexer defines these symbols,
      WRITE,
      QUITE
      and
      DAMNIT

      the "new" (about '78)changes added
      EXIT
      so:
      WRITE+QUIT+DAMNIT
      called the same function as:
      EXIT+DAMNIT

      this all predates your professors and mentors unless you went to UCB and were in the proper department. Keep in mind that some of this stuff predates Unix .

    8. Re:Cut N Paste? by Rumble · · Score: 1

      It could be because :w and :q are in the manpage but :x is not. This holds for the Solaris box I Checked as well as FreeBSD. So get off your high horse.

    9. Re:Cut N Paste? by Mikesch · · Score: 1

      Muscle memory.

      Every reference to vi I've ever seen has used :wq to write and quit. People eventually learn this, probably because it is more descriptive e.g. x, meaning....whatever, wq having an actual meaning in write+quit. At a certain point, even when you learn :x, you are so used to typing wq, often with the !, which is just one key and a shift away from the w and q, rather than the considerable leap for x, that it simply rolls out. Given the !, it likely takes less time to type than making the jump from the x all the way up to the top of the keyboard, those thousands of seconds add up over the course of a sysadmin's life.

      Man, I really need to finish studying for that final. Posting this reply is the definition of procrastination.

    10. Re:Cut N Paste? by Pinball+Wizard · · Score: 2

      I am one of those people who knows the bare minimum to move around in vi, type things in, and quit and nothing else. My total knowledge of vi is i to turn on insert mode, esc to go back to command mode, x to delete characters, dd to delete a line, the arrow keys to move around, :q! to quit without writing, and :wq to write the file and quit.

      I learned vi because it is the one editor that is on every single system, and also because its small enough to fit on a boot disk. However, once I learned the bare minimum I needed I quit learning about it because its simply not productive to use such a rudimentary editor when there are so many better tools available.

      :wq might be obsolete, but I picked it up from the O'Reilly book, Learning The Vi Editor. Where else was I supposed to learn about it?

      --

      No, Thursday's out. How about never - is never good for you?

    11. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      yy is copy.
      dd is cut.

      You can also do 3dd for 3 lines, etc...

    12. Re:Cut N Paste? by WindowsTroll · · Score: 1

      The question is not 'how do you cut and paste in vi?', but rather how do you cut and paste a single line and how do you cut and paste multiple lines.

      For a single line
      to cut: dd
      to paste p

      For multiple lines (easiest to do this do a named buffer)
      1.mark first line of buffer (buffer a)
      ma
      2.mark the end of buffer a
      "a
      3.delete buffer a
      d'a
      4.paste buffer a
      "ap

      --
      "Microsoft has made computing accessible to a population who would otherwise not be able to use computers" - B. Kernigha
    13. Re:Cut N Paste? by NotoriousQ · · Score: 1

      if you have gpm running cutting and pasting is easy....highlight what you want to copy, make sure the cursor is where you want paste and in insert mode, and then just middle click, and voila -- the text magically appears -- props to the gpm crew

      --
      badness 10000
    14. Re:Cut N Paste? by he-sk · · Score: 1
      For multiple lines (easiest to do this do a named buffer) ... [rest skipped]


      Yes, this works. And it's useful to remember, when you have to use the original vi.

      But for all VIM users (note to vi users: you should really try VIM), try:

      - Shift-V to go into visual line mode
      - mark text with cursor keys
      - hit d to delete the marked section
      - use p to paste

      Much better.
      --
      Free Manning, jail Obama.
    15. Re:Cut N Paste? by sketerpot · · Score: 1

      The people you asked sound like idiots. They could simply find some documentation (and yes, it's out there in abundance) and read it, rather than doing some completely idiotic "FTP to Windows box" thing just to copy and paste.

    16. Re:Cut N Paste? by rot26 · · Score: 1

      count me as another "idiot" who still uses :wq

      --



      To ensure perfect aim, shoot first and call whatever you hit the target
    17. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      the arrow keys to move around

      You mean h, j, k, and l to move around!

    18. Re:Cut N Paste? by Roxy · · Score: 1

      I learned vi in the beginning of the eighties, what I learned was ZZ to write and quit. :x and :wq is in fact ed syntax. I never bothered to learn much of that...

      For the young whipersnapers, ed is the equivalent to MS-DOG edlin (but much more powerful and an ancestor to sed, [am I the only one using it yet?]) :-)

      Roland B.

      Off-topic, I know ....

      --
      -- Roland Buresund MBA, MCMI, CISSP
    19. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      Additionally, you can use the mouse to cut and paste to any application in X, using the middle mouse button, or a chord of the left/right.

      Just be sure you are in insert mode when you do this, or the string you paste will be executed as a command.

    20. Re:Cut N Paste? by Anonymous Coward · · Score: 0

      1.mark first line of buffer (buffer a)
      ma
      2.mark the end of buffer a
      "a
      3.delete buffer a
      d'a
      4.paste buffer a
      "ap


      Actually, your interpretation of the commands is incorrect.

      ma = mark text position with the label a
      "a = specify buffer a
      d`a = delete everything between label a and the current position. Since this was preceded by "a, the deleted stuff ends up in buffer a
      "ap = paste the contents of buffer a after the
      current line

      To see that this is so, note that if you replace this sequence with

      (move to start of section to be cut)
      mb
      (move to end of section to be cut)
      "cd`b
      (move to line after which section is to be pasted)
      "cp

      then it works just as well.

      What's more, there's an unnamed buffer for cut text so as long as you don't do any other deletions before you use it, and aren't cutting/pasting between different files, you don't need to use a named buffer at all:

      (move to start of section to be cut)
      ma
      (move to end of section to be cut)
      d`a
      (move to line after which section is to be pasted)
      p

    21. Re:Cut N Paste? by MAXOMENOS · · Score: 4, Informative
      I've always found these handy:
      • dd and yy to cut and copy, respectively
      • p to paste
      • J (note caps) to append the next line to the end of the present line
      • U (note caps) to undo the last command.
      • :1,$ sub /oldphrase/newphrase/ to replace oldphrase with newphrase throughout a document
      • :syntax on with VIM, for syntax highlighting
      • :cd to change current working directory
      • :e! file to edit file file
      • CTRL-W n to create a split window...sometimes useful if you're writing code and want to have the header file right in front of you.
      • CTRL-W w to switch from one split window to another
      • :set sw=num and :set softtabstop=num to set how far your tab key indents (in spaces). I use four spaces, and this is set automatically by putting these lines in my .vimrc and .gvimrc files.
      • /phrase to search forward for phrase phrase; / alone to search again for that same phrase. ? searches backwards.

      That's just off the top of my head. Things beside these I can usually find in New Riders' book Vi IMproved -- Vim

      Good luck. I use VIM almost exclusively for my editing needs; over the last ten years it has been my constant companion through thick and thin. I wouldn't work without it.

    22. Re:Cut N Paste? by binner1 · · Score: 1

      I actually popped back into this thread to post a very similar comment. I first learned vi for my first CS class at university. We had an older (almost retired) prof that preferred old-school tools. I'm still saddened by the fact that the prof that now teaches the course has students use pico (good for pine, not general purpose editting)...

      Anyway, this prof was old-school enough that he didn't even use pine. He preferred command-line mail instead.

      I bet that there are lots of people in this same situation, not that it's bad!

      -Ben

    23. Re:Cut N Paste? by koogydelbbog · · Score: 1

      :1,$ sub /oldphrase/newphrase/ to replace oldphrase with newphrase throughout a document

      you can use % instead of 1,$. and s is enough to do a sub:

      :%s/oldphrase/newphrase/

      vim is good, use it on solaris and win2000 all the time. have been using it for years and am still learning new things.

      in response to 'how do i cut and paste' there's always visual mode:

      v to start visual mode (or V for complete lines)
      move to end of selection
      y to 'yank' into copy buffer
      move to where you want text to go
      p to 'put'

      vim for win32 also allows you to define selection with the mouse and cut and paste using icons or menu entries.

      andy

  16. If Bill didn't abandon Xenix... by Hank+Kingsley · · Score: 1


    Or if Microsoft had stuck with Xenix rather than throwing it back into the pot... But enough of that.

    That was actually the most interesting speculation. What if MS kept Xenix and was successful with it? Considering its history co-opting & corrupting good technology, and its propensity toward monopolization through its proprietary property, perhaps Xenix would be the only widely implemented form of *nix around today. And if we still had a Linux, it might be a whole different OS.

    1. Re:If Bill didn't abandon Xenix... by Graspee_Leemoor · · Score: 5, Funny

      Bill Gates got sued by the CoC for using the copyrighted entity "Xenix"; he hasn't abandoned plans to make Xenix the #1 OS- what he is doing right now is trying to make enough money to become OTIII so the CoC will let him use the name...

      graspee

    2. Re:If Bill didn't abandon Xenix... by Treeluvinhippy · · Score: 2, Funny

      Imagine being transported to another dimension somehow. A Dimension not of sight or sound but of mind.

      Your standing in your bedroom/gaage/server closet/basement/dens/etc. and everything appears to be the same. You fire up your linux box. Everything seems normal, all is as it was in your original plane of exsistance.

      The login prompt appears, your username/password in this counterpart universe and yours is identical, but.....

      Instead of your default shell you see...

      C:\

      N000000000000000000000000000!!!!!!!!!

      --
      >
    3. Re:If Bill didn't abandon Xenix... by Graspee_Leemoor · · Score: 2

      oops - that should have been CoS- CoC is "Call of Cthulhu" (yeah I could never spell it- hence the acronym).

      And who the hell modded me informative? Someone with a sense of humour, or an extremely gullible person?

      graspee

    4. Re:If Bill didn't abandon Xenix... by connorbd · · Score: 2

      You know, I'm just about ready to start on EGIII (Elder God III) -- isn't that the one with the snaps and the thing with the big squid head comes out, then has everybody crammed into a small New England town with the help of tax auditors and shrinks and eats everybody?

      /Brian

    5. Re:If Bill didn't abandon Xenix... by El+Kevbo · · Score: 1

      oops - that should have been CoS

      I was wondering why the metal band Corrosion of Conformity was suing Gates... :)

      Kevin

  17. UNIX! by qslack · · Score: 0, Troll

    Ha-ha. Microsoft had a product named "UNIX." That's such a stupid name, obviously no one there ever said it out loud.

    M$ sucks!

    </sarcasm> :)

  18. Brighten up everyone!!! by JFMulder · · Score: 4, Insightful

    There are so many post I'd like to respond to that instead I'll post my replys in this one big message.
    First of all, to the moderator who moderated to 0 the comment about NT meaning "New Technology", go read a little and you'll find out that it's true.
    Second of all, Microsoft didn't rip off Unix. No sir they didn't. They just applied concepts that everyone has been incorporating for years in their OSes. It's like saying that the Saturn cars are ripping the 1900's Fords because Ford has been here for almost a century (I think, maybe it's some other company).
    Third, if you've programmed a lot in Windows, you'll notice that the API is very different then it's Unix conterpart, and by that I don,t mean only different names for same methods. Ever noticed that everything in Windows is centralized around handles, objects and the WaitForSingleObject/WaitForMultipleObject that are used everywhere in the OS to wait for something to complete/release/signal/join? That's pretty elegant, and it enables a user to lock a lot of different resources (mutexes, event, thread, semaphores, sockets) all in once, helping to avoid some pretty nasty deadlocks sometimes. Unix and Linux doesn't have these. Go through the API, you'll say that it's very rich and not that much borrowed from Unix.
    There are a lot of other Microsoft myths out there, and I guess that's because a lot of people just think they know stuff because they know how to recompile their kernel, when in fact they know "shit" about OS infrastructure and concepts.

    1. Re:Brighten up everyone!!! by pauljlucas · · Score: 1
      Ever noticed that ... Windows is centralized around ... WaitForSingleObject/WaitForMultipleObject that are used everywhere ... Unix and Linux doesn't have these.

      Obviously you've never bothered to read the pthread standard.

      --
      If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
    2. Re:Brighten up everyone!!! by Anonymous Coward · · Score: 0

      You don't know what a mutex is, do you? :P

    3. Re:Brighten up everyone!!! by Wonko42 · · Score: 3, Informative

      Actually "NT" has a double meaning. Its primary meaning was "N-Ten", because Windows NT was being developed initially only for the Intel i860 chipset, which was code-named "N10". Later, when it was decided NT would run on other platforms, the term "New Technology" was used. At least, this is what I've read.

    4. Re:Brighten up everyone!!! by Anonymous Coward · · Score: 0

      Also obviously you nevar read abou the unix "select" system call.

      For instance, with X11 on a unix system you can use a single "select" to wait for a mouse/keyboard event and wait for data coming from the nextwork socket.

    5. Re:Brighten up everyone!!! by Anonymous Coward · · Score: 0
      ...and I guess that's because a lot of people just think they know stuff because they know how to recompile their kernel, when in fact they know "shit" about OS infrastructure and concepts.

      you mean like making a web browser central to the structure of an operating system?

    6. Re:Brighten up everyone!!! by Umanity · · Score: 3, Informative
      This is a brilliant programmer speaking...

      He speaks before he knows... People like this give software engineers bad names. It is so obvious he hasn't looked at the Unix API... The wait() call is a central part of Unixes, since day one. Signals, semaphores, mutexes, they are used abundantly in Unixes. Whoever posted this should be tarred and feathered..

      I program both Windows and Unix, and have written OS Wrappers which allow me to port my applications between OS's. Everything you can do in Windows OS's can be done in Unix. Threads, Processes, Semaphores, Mutexes, Spin-Locks, Signals, memory maps, pipes, timers, etc. To make assertions that Windows uses WaitForObject, etc. is a ridiculous one. I would use semaphores or mutexes to co-ordinate two threads.

      Personally I find the Unix OS much more straight forward and easier to design for. Microsoft keeps on making programming more and more esoteric, more difficult to understand. I use COM all over the place, and have started to port COM to Linux. It is nice, but it is not anything new, it is basically dynamic libraries with a known exported interface which exports class factories. I write low-level, often device drivers, or interfaces to video capture devices for DVD burning software. I use DirectShow which is a layer on COM. I find COM beneficial for some things and think Linux needs a similar framework.

      --

      Michael A. Uman
      Sr Software Engineer
      softwaremagic.net

    7. Re:Brighten up everyone!!! by Anonymous Coward · · Score: 0
      I find COM beneficial for some things and think Linux needs a similar framework.

      XPCOM

    8. Re:Brighten up everyone!!! by Anonymous Coward · · Score: 0

      >>>I find COM beneficial for some things and think Linux needs a similar framework.

      Linux does have a similar framework it is called Corba...I'm just getting into COM/+/DCOM/WinDNA/MTS coding and that was the first thing they told me about COM that it has a widely accepted counterpart called Corba. I'm sure your reason for trying to port over COM objects to Linux have to do with the proprietary objects you may be dealing with but I just thought it was important to point out.

      Just one question...if you are converting COM objects over to Linux what are you using for the "SCUM" dll/server/client loader? Please don't tell me you rewrote that too!

      I however wasn't sure if that guy was correct about Unix supporting WaitForSignel but I knew Unix supported mutex/semaphores/ect....thanks for the info on that as I'm not a Unix coder yet!

      Please note the yet part.

      happy trails...

    9. Re:Brighten up everyone!!! by JFMulder · · Score: 1

      The blurb about WaitForSingleObject has been a little unclear I admit. Here's what I meant : what I intended to put emphasis on was the WaitForMULTIPLEObject, which ISN'T part of the pthread standard. This solves some nasty deadlocks problem as I stated earlier.
      I was sure not going to give a thourough analysis of both APIs, and this is the first example that poped in my mind, since this is probably the first thing you notice when you start toying around with pthread and "WinThreads". The synchronization possibilities are much wider with Windows than with Unix.
      But what you said is true, what you can do in Unix, you can generally do it in Windows, and vice-versa.

  19. Re:Windows NT & acronyms by 56ker · · Score: 1

    If people start using more than two acronyms per a sentence I start getting a H.E.A.D.A.C.H.E. trying to work out what it is they mean.

  20. ATT's "failure" to properly manage UNIX by mikewas · · Score: 5, Informative

    ATT had no reason to "properly manage" UNIX. ATT's forays into areas that the FCC deemed outside of the realm of telecommunications (i.e. computer HW & SW) resulted in a a choice for ATT:
    1. retain the telecommunications monopoly but refrain from any money-making ventures outside of the telecom area
    2. become a real business, make money on anything you want, and open up competition in telecommunications.

    ATT chose choice #1 -- retain the monopoly. This was for them a sure thing. They had always managed to retain the monopoly in the past and it provided a steady source of income. Computers were new, and internally were not percieved as a consumer item.

    So at the time Bill was talking about ATT, the UNIX development/administration/lisencing was, by legal necesity, not a money-making area for ATT. UNIX was a tool to develop telecom products, the real business of ATT. Giving the technology away and managing the process "for the public good" was a means to demonstrate that it was not a money-making venture as well as a way to trumpet Bell Labs. It didn't recieve the best support from management, though, as they were focused on the money-making areas of the business.

    On the other hand, the statement that ATT didn't know what they had, was that ever true! Once they did figure it out it was too late, they were legally barred from that market untl after deregulation (nothing is forever!) -- too late!

    --

    "Glory is fleeting, but obscurity is forever." --Napoleon Bonaparte
    1. Re:ATT's "failure" to properly manage UNIX by Anonymous Coward · · Score: 0

      When I worked in ATT, "ATT Unix System V" books stood on the bookshelf over every desk, while all desktop PCs were running Windows NT. When I asked my boss can use Linux or Unix instead I've been answered "No. Its a company policy". When I asked "why do we keep all those "ATT Unix System V" books, I've got the same answer. It seems like ATT created their idol and forgot why they did it :)

    2. Re:ATT's "failure" to properly manage UNIX by Anonymous Coward · · Score: 1, Informative

      While it might have been true early on that AT&T was sort of the clueless master of UNIX, their actions late in the game caused all the trouble.

      + They introduced their own line of workstations running UNIX. This would be like Microsoft coming out with a PC line today.
      + They stedily raised the price of a UNIX licence from near-0 to high enough that UNIX was effectivly excluded from the low-end (PC) markets.
      + They forbid their licencees from referring to their products as "UNIX", thus causing much branding confusion and ye olde *nix jokes.
      + They got into bed with Sun and started the "Unix Wars" of the early 90s.

      True none of that directly affected MSoft, except allowing them to sell into all sorts of markets abandoned or scared off by the UNIX masters.

  21. msdos ...? by rkoot · · Score: 5, Funny
    Wasn't QDOS short for Quick 'n Dirty Operating System ? Must have been....
    And that way MS-DOS isn't Microsoft Disk Operating System but Microsoft's Dirty Operating System.
    First they took out the Quick Bits and kept the dirty bits....

    roger

    1. Re:msdos ...? by Arker · · Score: 2

      Yes, QDOS was "Quick and Dirty Operating System." It was written in 1979 by Tim Patterson of the Seattle Computer Company, as a personal stopgap while Gary Killdall at Digital Research was busy doing a proper CP/M port for the i8086. Since CP/M source was available under a license somewhat like todays "shared source" agreements, it wasn't all that difficult to hack up a functional CP/M, even if it was a little rough. Gates managed to buy this hack for a pittance and build an empire on it... the rest, as they say, is history.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    2. Re:msdos ...? by hound3000 · · Score: 1

      I thought MS-DOS stood for Microsoft Seeks Dominion Over Society.

  22. Spin is not correct by Russ+Nelson · · Score: 3, Interesting

    Bill Gates was the keynote speaker at the Trenton Computer Festival in the early 90's. He spoke about His Vision, which included a processor per person, or even more. He said "There are more people running DOS than anything else". Later, when he took questions, I asked him about Unix: "But each Unix machine serves multiple people at the same time". He countered that with "Unix isn't the future."
    -russ

    --
    Don't piss off The Angry Economist
  23. Sinix by motox · · Score: 2, Informative

    I also worked on Siemens SINIX and most of the kernel includes were (C) Microsoft Corporation :)

    1. Re:Sinix by minus9 · · Score: 1

      Wow I'm the other guy that has used SINIX!

  24. *nix a pile a' dogcrap by Anonymous Coward · · Score: 0

    Unix? The future?? *nix is a sloppy pile a' dogcrap SPLAT run over by a truck-tire. SPLAT ... that's also the sound of 6-finger webtoed weenies reaching under a truck-tire ... hehe

    1. Re:*nix a pile a' dogcrap by Anonymous Coward · · Score: 0

      Whats the future then, genius? Windows NT? Bzzzzt, NT is basically VMS with bells on.

    2. Re:*nix a pile a' dogcrap by larry+bagina · · Score: 1

      I work with OpenVMS and NT all day long. NT is influenced by VMS, but it is absolutely not "VMS with bells on."

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

  25. Road Ahead by desierto · · Score: 1

    So what your saying is that to get started out on the Road Ahead, Mr. Gates needed a jumpstart from a unix beater or a vax cadillac, and his driving manual was written in vi?

  26. There is no contradiction in MS philosophy here by Anonymous Coward · · Score: 2, Interesting

    I don't see how Microsoft incorporating UNIX pirinciples into NT demonstrates any hypocrisy on their part. When they said they wanted a different business model and direction than UNIX, yet expounded UNIX for its technical elegance and power, how can this be rectified?

    Well, they incorporated UNIX principles as desired into a new system that they felt could gain wider desktop acceptance.

    If the author is indignant that MS rejected the precious UN*X philosophy (whose design goals could arguably be mutually exclusive with widespread desktop acceptance), he should just say it. If he really doesn't understand, his reasoning faculties should be brought into question.

  27. Re:a glorified email terminal-TRS80 by Anonymous Coward · · Score: 0

    "The Xenix name was later used for a version which could run on machines with little or no memory management - eg a 286. (Like Minix and Idris) This was a lame idea from the start, and did not survive the introduction of the 386 commercially."

    Would that happen to be the version that ran on a TRS80 model 16 Business computer?

  28. Re:Windows NT != VMS by eap · · Score: 2, Interesting

    As one who uses both VMS and NT on a daily basis, I can attest that the similarities between the two platforms are nonexistent as far as stability and robustness are concerned. VMS is one of the most stable OS's ever to gain widespread deployment. NT is somewhat lacking in this respect, to say the least.

  29. Xenix lives! by RFC959 · · Score: 1
    Get this:

    yoyodyne:~$ uname -a
    SunOS yoyodyne 5.8 Generic_108528-13 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
    yoyodyne:~$ grep Microsoft /usr/bin/clear
    # Copyright (c) 1987, 1988 Microsoft Corporation
    # This Module contains Proprietary Information of Microsoft

    So remember, kiddies, don't make unauthorized copies of /usr/bin/clear, or MS will come after you.
    1. Re:Xenix lives! by Anonymous Coward · · Score: 0

      oh yeah? oh yeah??

      % uname -a
      Darwin --.--.--.--.net 5.3 Darwin Kernel Version 5.3: Thu Jan 24 22:06:02 PST 2002; root:xnu/xnu-201.19.obj~1/RELEASE_PPC Power Macintosh powerpc
      % grep Microsoft /usr/bin/clear
      %

    2. Re:Xenix lives! by Anonymous Coward · · Score: 0

      Oh yeah, that makes sense!

      I always wondered why 'clear' was the only
      Unix command which wasn't abbreviated.

      Then of course, when M$ had to name the same
      command in M$DOS, they had to name it differently
      and thus had to go with the non-intuitive 'cls'.

      Mystery resolved.

    3. Re:Xenix lives! by Arandir · · Score: 2

      So I decided to look at my "clear" script. It has one line with "#!/bin/sh -", 35 lines with the BSD license and warranty disclaimer, and one line with "exec tput clear".

      95% of this script is copyright. Geez! I'm so glad this isn't under the GPL...

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  30. What's really being said? by 3seas · · Score: 2

    Seems to me that the message is more like "*inx flavors aren't the future due to it's lack of leadership."

    The sort of thing that is an indirect attack on GNU/GPL commons, which is both a flavor of Unix and by nature
    having an absence of overall leadership.

    And thgis isn't the first time I've seen such faulty insinuations being made towards GNU/GPL.

  31. I am a geek! by Anonymous Coward · · Score: 0

    what are you? dork.

  32. You're thinking MacOSX by DABANSHEE · · Score: 2

    It runs on the mach kernal, BSD & all that.

  33. M$ used Xenix until 96-97 by maggotbrain_777 · · Score: 2, Informative

    "If it is indeed true that Microsoft was running on Xenix up until Windows 3.1, it casts an interesting light on how flexible Bill's vision of the future was right up until the early 90s."

    If I recall correctly, the last Xenix server on the MS corporate backbone was removed in late 96- early 1997. Primarily, they were used as Internet gateways, running Sendmail. Also , they functioned as internal gateways between MSMail and Exchange while the company converted everyone over to having personal mailboxes on an Exchange server.
    While we tried to get some improvements made to applications running on the Xenix boxes, rumour had it that no one could develop these apps, since the source code had been lost somewhere on campus. Also, this is why they couldn't sell the OS to another company.....c'est la vie

    1. Re:M$ used Xenix until 96-97 by nikkatsu · · Score: 1

      lost the source code? how the hell does that happen?

    2. Re:M$ used Xenix until 96-97 by Dahan · · Score: 4, Funny
      lost the source code? how the hell does that happen?

      Simple--use SourceSafe as your source code control system.

    3. Re:M$ used Xenix until 96-97 by rusty+spoon · · Score: 1

      I worked at MS, and where I worked we didn't use Source Safe. Instead it was some nasty commandline junk (called "slime" ) that was easy to break (lock everyone out). Looked like a Unix tool ;)

      dog food? Nah.

    4. Re:M$ used Xenix until 96-97 by Anonymous Coward · · Score: 0

      I will send Microsoft a copy of cvs right away. They need it.

  34. Vi is the tool of Satan by Hieronymus+Howard · · Score: 1

    Look all ye unbelievers. The article states:

    "Mac Word and Mac Excel, Windows Excel and Windows Word were written in vi"
    and also says that Bill Gates himself used Vi.

    This just goes to prove what us Emacs users have known for a long time - Vi is the tool of Satan. Well, a tool of Satan. I expect that the tool of Satan is long, pointed and greasy with sharp hairs and spurts sulphuric acid. Sorry, got a bit carried away there. Vi users - repent of your evil ways. The only path to true salvation is though Emacs.

    HH

    1. Re:Vi is the tool of Satan by pauljlucas · · Score: 4, Funny
      Vi users - repent of your evil ways.
      I have: I use vim.
      --
      If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
    2. Re:Vi is the tool of Satan by distributed.karma · · Score: 1
      The number of the beast is VI VI VI. Guess that explains it all.

      OK, actually that is wrong and the number of the Gates^W Beast is six hundred sixty-six. You can get it from the phrase VICARIVS FILII DEI (Vicar of the Son of God) and using I=1, V=5, L=50, C=100, D=500.

      --

      --
      If you moderate this, then your children will be next.

  35. Some history notes on NT's development: by Otis_INF · · Score: 5, Informative

    Slideshow: http://www.usenix.org/events/usenix-win2000/invite dtalks/lucovsky_html/.

    In there, you'll learn 'NT' was related to the first proc it was targeted to, the 860 of intel, codenamed 'N10', plus some juicy stuff about the development of NT3.1 and win2k, and some related notes to Unix and NT.

    --
    Never underestimate the relief of true separation of Religion and State.
  36. Microsoft Confidential source by brer_rabbit · · Score: 4, Interesting

    I was hunting around on my Solaris machine at the office yesterday. For amusement, I looked at the shell script it's got for /usr/bin/clear. In addition to containing the standard AT&T copyright, it also contains a Microsoft Copyright:

    #!/usr/bin/sh
    # Copyright (c) 1984, 1986, 1987, 1988, 1989 AT&T
    # All Rights Reserved

    # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T
    # The copyright notice above does not evidence any
    # actual or intended publication of such source code.

    #ident "@(#)clear.sh 1.8 96/10/14 SMI" /* SVr4.0 1.3 */
    # Copyright (c) 1987, 1988 Microsoft Corporation
    # All Rights Reserved

    # This Module contains Proprietary Information of Microsoft
    # Corporation and should be treated as Confidential.

    # clear the screen with terminfo.
    #

    It thought it rather amusing to see a Microsoft copyright there of all places. And the source is only two lines of code, one of them being exit. It's left as an exercise to the reader which line (first or second) is exit.

    The other line is /usr/bin/tput ${1:+-T$1} clear 2> /dev/null, but you didn't hear that from me.

    1. Re:Microsoft Confidential source by harlows_monkeys · · Score: 2

      The amazing thing is that it is version 1.8. It took the combined intellects of Sun, Microsoft, and AT&T 8 tries to get two lines right?

    2. Re:Microsoft Confidential source by Otterley · · Score: 1

      Changes in the comments would have resulted in an SCCS delta. It could have been correct the first time.

    3. Re:Microsoft Confidential source by gorilla · · Score: 2

      More amusing is /bin/true. On solaris 8, it's version 1.6, and the entire file, excluding the comments, is "". Yup, version 1.6 of an empty file.

  37. Microsoft's early plans for XENIX by AdamBa · · Score: 5, Interesting
    Here is a quote from the 3rd issue of PC Magazine, June/July 1982 (which also features a review of PC-FORTH by some dude named Eric Raymond)...this is from Paul Allen, Microsoft co-founder:

    "It's important to realize that MS-DOS is part of a family of operating systems....Providing the user with a family of operating system capabilities means a clear migration path from MS-DOS to XENIX. That means compatibility for both the terminal end user and the systems programmer.

    A standard library for XENIX-86 C will allow compilation of a program on XENIX system and then execution on MS-DOS....XENIX systems will be able to function as network file servers."

    So as you can see, Microsoft had big plans for XENIX back then. As it turned out, XENIX's place in the Microsoft family was first taken by OS/2, and then by NT.

    - adam

  38. Xenix in 1989 by ciurana · · Score: 3, Insightful

    I deployed a number of Xenix installations in the mid- to late 1980's, the last one in either 1989 or 1990. We were competing against Novell Netware networks (back when TeleVideo made that hideous Novell dedicated hardware with the 286 and the Z-80 and all the way to the IBM PS/2 model 80 days) and usually beat them hands down for an inventory and POS application. Our customers were medium-size enterprises (up to 200 employees, up to five physical locations). The configuration:

    • HP Vectra 286 with 1 MB RAM (!!!) and 60 MB HD
    • 12 RS-232C port expansion (for terminals)
    • Up to 12 TTY
    • App developed by my company
    • SCO Xenix (can't remember the version)

    The advantages of using this:

    • Cost
    • Ease of maintenance
    • Rich tool set for the sys admins
    • High ROI (return on investment) for our customers
    • Higher profits for my company

    NCR *nix, Xenix, Minix, and AIX 3.0 were the first *nix OSs I was involved with, back in 1985 and forward. I went from Apple's Applesoft/ProDOS/MacOS/UCSD Pascal to *nix, then to Microsoft's world.

    All in all, I remember Xenix being one of the most complete *nix environments I played with. Only AIX running on RS/6000 (I was working on them prior to the announcement in March 1990) was more complete in its blend of SV and BSD tools. SCO occasionally facilitated SCO Unix to us but it was a PIA to install and configure, and lacked *lots* of driver support.

    The interesting thing to us was that, while Xenix was an MS product, MS had a very hands off approach towards it. All customer relationships were handled by SCO. The only time I ever remember Bill G. saying something about it was when he was asked about branching NT away from OS/2 and whether he was afraid of losing market share to *nix. His reply (I'm paraphrasing): We have DOS, Windows, OS/2, Xenix, and NT. It's Microsoft against Microsoft against Microsoft against Microsoft.

    OK, time to stop reminiscing. Have a great Saturday.

    E
    --
    http://eugeneciurana.com | http://ciurana.eu
  39. Re:Windows NT != VMS by HeUnique · · Score: 2, Informative

    Take the GUI off, take the crappy drivers that are binding to the kernel off - and see if NT is stable or not..

    Hint - it will be the most stable thing you've seen on PC (at that time)..

    --
    Hetz (Heunique)
  40. Puzzled with the Cronology by akc · · Score: 3, Interesting

    Our company (Logica) licenced Xenix from Microsoft for distribution on the UK in the early '80s (and later sold out to SCO). I purchased a copy from our internal product department in about '83 in order to create a configuration management system (using SCCS) for my team for our own (SCADA) software which ran under RSX-11M. Except that my copy of Xenix ran on a PDP-11/34 not on an IBM PC.

    This was perhaps one of the first client server implementations of Configuration Management, very similar to what CVS is today. The server was this Xenix based 11/34 and the clients were PDP 11's running RSX-11M and the networking was homegrown protocols over serial links.

    After I had been running this software for at least 18 months I remember being given a demonstration of a new version that our internal Xenix group had just received running on an early IBM PC (don't know the model, probably an AT - it was pre PS/2). This was because we were trying to decide on a platform for the client end a new version of our SCADA software that was to become client server and we were comparing XENIX (multitasking but no GUI interface - but at the time we were only replacing a system which used block graphic character based colour terminals), GEM (anyone remember that!) and Windows 2.0. We chose Windows for reasons I can't remember - but were able to dominate UK Water Company SCADA systems for most of the '80s

    I was just after this that I was able to justify the purchase of a MiniVAX and a version of Unix System V for our Configuration Management server on the savings in maintenance costs over the PDP-11 and Xenix was ditched.

  41. Xenix has returned by yerricde · · Score: 1

    Xenix ... is now trapped somewhere and will return some day.

    Some day is now. Xenix became SCO UnixWare became Open UNIX 8.

    Funny quote on that page from Unisys: "Through it, our customers can jointly run Open UNIX 8 and Windows applications, giving them the flexibility of multiple platforms handling diverse responsibilities." Guess they left out the part about "such as using tools that support GIF for all your bitmap image processing needs."

    --
    Will I retire or break 10K?
    1. Re:Xenix has returned by Wdomburg · · Score: 2

      >Some day is now. Xenix became SCO UnixWare became
      >Open UNIX 8 [caldera.com].

      Not quite.. As I pointed out in an earlier post Xenix became SCO UNIX which became SCO Openserver. It was originally based on V7, and later SVR2 and SVR3.2, with features from SVR4 either backported or reimplemented when it became Openserver.

      Unixware was an SVR4.2 implementation SCO aquired from then owner Novell. It was sold pretty much unchanged as Unixware 2.x for several years.

      In 1998 they released Unixware 7, which was touted as being the first SVR5 implementation. Since SCO now controlled the Unix codebase, they could bump the version number :). This release did include some features designed to ease transition from Openserver 5, but it was an evolution of the SVR4.2 codebase of Unixware, NOT the SVR3.2 codebase of Xenix.

      The closest thing to a remaining relative would be Openserver 5.0.6, which is still marketed by Caldera.

      Matt

  42. Northern Telecom by Anonymous Coward · · Score: 0

    Then how come Northern Telecom holds some copyrights for Windows NT?

    1. Re:Northern Telecom by Dahan · · Score: 2

      Don't worry, Northern Telecom doesn't hold any copyrights for Windows NT.

    2. Re:Northern Telecom by cpeterso · · Score: 1


      Why do you think Microsoft changed the name from Windows NT to Windows 2000? Microsoft's lawyers were getting nervous about keeping Northern Telecom happy.

  43. A lot of flannel there by /dev/zero · · Score: 2, Informative

    I ran Xenix for years, on the 386, 486, and Pentium. It wasn't bloated, it was rock-solid reliable. Xenix not only survived the introduction of the 386, it thrived. Many vertical applications (doctors' offices, etc) are still running these systems. By my lights, it was a very good Unix (though not fully SVID-compliant). I learned a lot and made a lot of money with Xenix.

    SCO's move from Xenix to Unix coincided with their less developer-friendly, more grab-the-cash mentality (adding RAM to your box? That's an additional license fee, please.) as Doug Micheals took over from his dad (Larry), and played a large role in SCO's decline and eventual purchase by Caldera.

    I'll always have fond memories of my years with Xenix, though. Even though my video card has more RAM than any of my Xenix boxes ever had -- hell my Palm IIIxe as as much.

    --

    He that breaks a thing to find out what it is has left the path of wisdom.
    -- J.R.R. Tolkien
  44. Xenix XP by api · · Score: 3, Funny


    You might find this funny:

    Xenix XP

    MD

  45. GET A MAC! by Anonymous Coward · · Score: 0

    The article left out the part where Gates & CO. realized that all the mac users were actually HAPPY when they were using thier computers. Which is why 10 YEARS after MacOS was on the market, they produced their own cheap knock-off and somehow managed to make everyone think it was new.

  46. Microsoft ported vi to windows...... by amemily · · Score: 2, Interesting

    Bill probably does still use vi, there's a binary for vi in the NT resource kit in the posix folder along with the source code to a couple of other commands.

  47. Gates is a closet MAC user!!!! by Anonymous Coward · · Score: 0

    I had a dream where I was taunting Bill Gates about how much I loved my Mac and I was saying "HA HA I have a mac I have a mac" and Bill Gates looked me straight in the eye and said, "But Microsoft makes TONS of software for the Mac" They even gave Apple a bunch of money! And what do you know... OSX is like all Unixy and stuff...

  48. Xenix was the bomb... by xtermz · · Score: 1

    ...Well at least in my mind it was. Xenix was my first introduction to that "YOU NUCKS" thing I kept hearing about. I was a pimply faced teenager who was friends with a real live "hacker". Imagine that. But anyway, he did some wardialing and found a open Xenix box, and gave me the info. I remember calling him up going 'dude, whats the command to do DIR ? '. Little did I know at the time, but because of that one experience, i would fall in love with unix for the rest of my life... I sit here typing on my linux box, remembering thinking how it would be cool to run a unix clone on my pc in circa 1994 and have something similiar to that first box i encountered. aww..the memories..

    --


    I lost my concept of community when my community lost all concept of me.
  49. that's 7uck1n funny by Anonymous Coward · · Score: 0

    Bull5h17. Another example of the U.S. Government (not the democracy) as a form of Church.

  50. What if? by Anonymous Coward · · Score: 0
    If ACE had worked we might all today be running machines using MIPS and Unix derivatives. Or alternatively, if Microsoft had agreed with IBM about OS/2 2.0, rather than spiking it with Win 3.1, we might all be running OS/2. Or if Microsoft had stuck with Xenix rather than throwing it back into the pot... But enough of that.


    ... and we'd be praising the virtues of an open source NT.
  51. Two interesting points by kubla2000 · · Score: 3, Interesting

    Two interesting points which jumped out at me when I was reading Billy G's Unix Expo Remarks remembering that they were from October 9, 1996 were:

    One of the exciting things we're announcing today is that our commitment to the Internet and to building a state-of-the-art browser extends not only to Windows 95 and Windows NT, but also to 16-bit Windows and the Macintosh and to Unix.

    Explorer for Unix!

    And this:

    And the reason we do that -- it's not purely a magnanimous thing on our part. (Laughter.) We're doing that to promote the Active X technology, and by having the browser be out there very, very broadly...

    Clearly an early vision of .Net!

    1. Re:Two interesting points by kaphka · · Score: 2, Informative
      Explorer for Unix!
      Gosh, imagine that.
      --

      MSK

    2. Re:Two interesting points by Anonymous Coward · · Score: 0

      you can get IE for Solaris, you know.

    3. Re:Two interesting points by demon · · Score: 1

      Yes, a couple old-ass builds of IE for Unix (aka the Windows IE codebase, built against Win32 compatibility libs for UNIX). We're all very impressed. I just remember a friend telling me about running it on a Sun box, and then having to power the box off, it locked it up so badly (ate all mem and swap).

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
    4. Re:Two interesting points by Bert64 · · Score: 1

      Yes, an OLD version of IE, which is far less stable and slower than it`s windows counterpart, consumes more ram, doesn`t use standard X11 cut+paste features, doesn`t have any plugins available (java, swf etc).. infact it`s pretty much useless.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  52. No, he's not. by Anonymous Coward · · Score: 0

    He's thinking microkernel, not Mach. NT originally was going to be a microkernel, like Mach is. But they canned that idea for a more monolithic architecture for performance reasons.

    BTW: Mac OS X is closer to NeXT than anything else. It's Mach, with a BSD layer, with some BSD userland stuff, and some NeXTSTEP userland things...

    1. Re:No, he's not. by connorbd · · Score: 2

      Actually, I think the NT architecture is even weirder than that. As far as I can remember from what I've heard, NT is indeed microkernel-based (can't remember if the proper name for the original mk was Mica or Prism; I've heard both names), but they've blown so many holes in the design over the years (particularly where NT 4 moved GDI into user space) that it may as well be monolithic. (Funniest damn thing; NT was designed to be portable originally, but I seriously doubt they could go back and put XP on all the hardware NT was originally designed for; I think even WinCE was rebuilt from the ground up, wasn't it?)

      And you've got OS X inside out; you're essentially correct, but the userland is specifically FreeBSD, and "some NeXTSTEP userland things" is way off the mark. OS X is NeXTSTEP/PPC with Mac compatibility and a nice coat of Bondi Blue paint.

      /Brian

    2. Re:No, he's not. by spike+hay · · Score: 2

      I have always wondered if sometime microsoft is just going ditch the NT kernal, and maybe with their next version, use Mach or VMS or something for their kernal. Just like Apple did. Then finally they could claim that their product is stable.

      --
      If you don't understand any of my sayings, come to me in private and I shall take you in my German mouth.
    3. Re:No, he's not. by leandrod · · Score: 2

      > can't remember if the proper name for the original mk was Mica or Prism

      Microsoft oriented press usually have little regard for jornalistic quality standards, but as far as I remember this article is correct: Prism was the hardware, Mica the OS for Digital’s ‘future system’ that failed, prompting Cutler to go work at Microsoft. Interesting that these ‘future systems’ have a tendency of going seriously wrong: IBM’s gave us SQL instead of relational, and that is worse than Windows!.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:No, he's not. by jimfrost · · Score: 2
      I think even WinCE was rebuilt from the ground up, wasn't it?

      No, WinCE is an NT derivative. That's not so clear now, but it was really clear in 1.0.

      --
      jim frost
      jimf@frostbytes.com
  53. First Unix/Xenix by presearch · · Score: 5, Interesting

    In 1979 all that existed of Xenix was a silver brochure from Microsoft
    but there was no distribution. I wanted it to run it/sell it, seeing that
    you could do the timesharing thing just like back at college, except
    without a giant machine behind glass. I contacted the then tiny
    Microsoft, asked, begged, pleaded but they had nothing to sell.

    After multiple inquiries, they finally told me that they didn't have
    Xenix yet, but they expected it to arrive shortly. Arrive? From where?
    I was told, from Human Computing Resources (HCR) in Toronto.
    Ahh, interesting. So I called HCR somehow got them to commit
    to an early delivery. After a few weeks, and several dollars, the
    day came. MS wanted a PDP-11 and 68000 version and was
    only after the PDP-11 distro, I was 1 week ahead in the queue
    from Microsoft. So, as I was told from HCR, I had the first Xenix
    distribution in the US, ahead of Microsoft. I ran it on a LSI-11/23
    with insanely expensive 256Kb of memory and a giant 20Mb
    drive from Charles River Data Systems. It also had 2 eight inch
    floppies (errrtt, clunk, clunk, errrrttt), and 2 four port serial cards
    that each ran a VT100. The distro came on a 9-track tape (which
    I still have) and the take drive was this weird, front loading thing
    where you loaded the tape in the front like a big floppy and it
    auto threaded the tape (sometimes). As I remember, it seemed
    pretty fast, I'd start up stuff on all of the terminals, just to do it.
    Of course, it wasn't that fast but at the time....

    The Unix itself was a more or less pure Unix v7. The only thing,
    as I remember that made is Xenix, was the boot message and
    the captions on the man pages. There was no vi at that time,
    the editor of choice was "ed". It did have a nice /usr/games
    and I got a Zork for it from a friend.

    We ended up selling a few of the boxes. The company was
    called MSD. The only record of such is in a 1981 (Jan?) issue
    of Byte with our little ad in the back. And that's the story of the
    first commercial Unix sold in the US.

    1. Re:First Unix/Xenix by Anonymous Coward · · Score: 0

      Any relation to the MSD (Micro Systems Development) that sold Commodore drives and peripherals up into at least the mid-'90s?

    2. Re:First Unix/Xenix by Anonynnous+Coward · · Score: 1

      I was wondering the exact same thing-ah, MSD. The SD-2 ruled!

    3. Re:First Unix/Xenix by Dr+Looney · · Score: 1

      Hi, I run the Unix Archive at www.tuhs.org. Would you care to let us read the tape and add it to the collection? It certainly is a historical release of Unix. Warren wkt@tuhs.org

    4. Re:First Unix/Xenix by minus9 · · Score: 1

      Not only is this interesting, it's also an uncannily accurate impression of an 8 inch floppy drive.

  54. Saddest part of XENIX Story by Anonymous Coward · · Score: 0

    When I came to Microsoft in 1980 I was pitching my real-time kernel that had almost the same API as UNIX but some real-time mojo and a somewhat different FS. My NOTNIX ran on the 68000, so porting UNIX, marketing called it XENIX, to the 68k was easy for me.

    Second say part ofthe story: later I was doing a demo of my client-server windows system (1983) and MS decided it liked an all-in-one-address-space approach better. Some of you were todlers back theni, I guess.

  55. Unix was the future (was: Re:Unix is the future.) by kermit6306 · · Score: 2, Insightful

    It's not that Unix fell off, it's just that it didn't grow into new markets: PC's, low end workstations, embedded systems, etc. AT&T and all the other big Unix vendors had no interest in "toys", (Hubis, it'll get you every time). They sat around and *watched* Microsoft eat up entire markets.
    Mac OS X. The "10" stands for "about 10 years to late".

  56. Stuff to read by andy@petdance.com · · Score: 2
    I'd like to see a summary of all the various "departments" under which the stories are posted.

    I'd bet my left nut that "stuff-to-read" has to be the most common department by a longshot.

  57. Computer Lib / Dream Machines by Anonymous Coward · · Score: 2, Interesting

    You are =so= close to the truth.

    Consider Ted Nelson's revolutionary book _Computer Lib / Dream Machines_. This book changed my life. I ceased being a drug-crazed radical hippy and became a drug-crazed radical computer geek.

    The first edition contained great tirades over IBM.

    Then Microsoft Press bought the book, castrated it, and released the second edition. All of the heart and soul was gone from it. All of the anti-monopolistic material was removed.

    The original edition is nearly impossible to find now. I haven't seen a single one since the second edition came out, about 1985.

    I would treasure even a photocopy of the original.

    1. Re:Computer Lib / Dream Machines by Anonymous Coward · · Score: 2, Interesting

      Amazon say's $467 for one in 'good' condition.

      For a packerback book not even thirty years old, this must be some kind of record!

  58. Microsoft's UNIX by Fembot · · Score: 1

    Where can I get it from? I have an old 8086 lying around to play with it on :-)

    1. Re:Microsoft's UNIX by Anonymous Coward · · Score: 0

      I'm not sure about 8086 Xenix, but if you want to emulate a really Ancient Unix environment, look at The Unix Heritage Society's web site (http://www.tuhs.org/). Caldera (the current owner of the copyrights) has made PDP/11 versions available under a BSD style license. You can download them and a PDP/11 emulator from the TUHS site. Given the speed of modern PCs, the emulation actually runs faster than the old hardware did! Have fun!

  59. Cut'n paste revisited. by Corporate+Troll · · Score: 1

    "dd p" would be enough. dd copies the deleted line into the buffer so, you don't need to yy before doing dd.
    Anyway, I'm a novice vi user. Strange thing: at College the only thing they teached us was "Esc:q" to quit from vi...in case we accidentally typed vi. Emacs was our editor, strangely enough I woudn't even be able to use emacs anymore: all I remember is how to quit it ;-) Ctrl-X Ctrl-C...I think :-)

  60. Re: Linux is a copycat OS by Anonymous Coward · · Score: 0

    Not a troll, but Linux is really nothing new.
    In fact, FreeBSD does everything it does, better
    and years ago and is more stable.

  61. Re:Windows NT != VMS by Corporate+Troll · · Score: 2
    This guy is not a troll. He is very right: NT is stable, and most trouble I had were with crappy graphics drivers. I'm pretty sure a command-line-only NT would be great. Besides, he says "at that time", so he means back in the NT 3.51 days were most OSes were DOS or DOS/Windows 3.0 on PC.

    Sometimes moderators just suck! Yes, I am very well aware that this will give me a Karma hit. Go fire!

  62. Hedge Gates by Tablizer · · Score: 1
    The only time I ever remember Bill G. saying something about it was when he was asked about branching NT away from OS/2 and whether he was afraid of losing market share to *nix. His reply (I'm paraphrasing): "We have DOS, Windows, OS/2, Xenix, and NT. It's Microsoft against Microsoft against Microsoft against Microsoft."

    That is pretty much how MS got big. They keep enough different things alive that whatever new fad or trend comes along, they have something similar already in a corner.

    Windows was a poor seller in the mid and late 80's, but MS still kept it alive "just in case". Most other software companies dump loosing products after a few years, because they are not big enuf to carry them all.

    I bet they are playing with Word for Linux in a dark corner somewhere, just in case.

  63. IExplorer for Unix has been here for a while by Anonymous Coward · · Score: 0
  64. Re:a glorified email terminal-TRS80 by rot26 · · Score: 1

    Same vintage, different binaries, of course. The model 16 was a 68000 machine.

    --



    To ensure perfect aim, shoot first and call whatever you hit the target
  65. Links? by MoogMan · · Score: 1

    Ok, so has anyone got a download link to 'Xenix'. Im sure it'd be a good laugh getting it running on an old pc. (Laugh being to laugh at not laugh for enjoyment of)

  66. Mod parent up by DarkEdgeX · · Score: 2

    This guy is absolutely correct-- just about any problems you can find with older versions of NT stems from drivers/resources/applications written by *SOMEONE ELSE*.

    --
    All I know about Bush is I had a good job when Clinton was president.
    1. Re:Mod parent up by phaze3000 · · Score: 2
      Absolutely.

      It's a perfect demonstration why having everything closed-source and binary only and then trying to get it all to interoperate is a very bad idea indeed.

      --
      Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
    2. Re:Mod parent up by DarkEdgeX · · Score: 2

      Nice trolling, I'm not going to bite, merely refute why you're wrong (and why anyone who believes this shit is wrong too)--

      It's really rather easy to write to closed-source, binary only OS's; it's called writing code that's not broken itself and using the API correctly. Sure, there's bound to be bugs inside an OS' kernel, but if your code still won't work when the bug is fixed, then it's something with YOUR code. Driver writers are notorious for being sloppy and having all variety of problems under NT/2000/XP. Epson is my favorite example-- their printer driver for the Stylus COLOR 440 has a memory leak (specifically, the 'Status Monitor' portion of the software). Leave it run for a few weeks and watch it easily chew up 300-400 MB of memory. Is this a problem with the NT kernel? Should it be Microsoft's responsibility to make sure OTHER people write good code?

      Open source is great, I love it, it gives me and others an opportunity to learn about pieces of software we'd otherwise never be exposed to, but trolling the idea that closed-source/binary is the root cause of poor system stability is weak at best, and wrong on it's face.

      --
      All I know about Bush is I had a good job when Clinton was president.
    3. Re:Mod parent up by cyber-vandal · · Score: 2

      It's always someone else's fault isn't it. Microsoft never do anything wrong ever do they.


      Of course the fact that drivers are much harder to write and debug on NT has nothing to do with it no, no it's these incompetent ISVs.


    4. Re:Mod parent up by demon · · Score: 1

      Are you actually saying that printer drivers on NT/2K/XP reside IN THE KERNEL? Is this true? If so, IMO that's pretty damn dumb. I can think of precisely zero decent reasons for putting printing functionality directly into kernel space. But then MS did move the NT graphics subsystem into kernel space as of NT 4, because having it in user space made it "too slow", even though having it in the kernel reduced system stability overall...

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  67. Apple also had Unix on the desktop in years past by MacBoy · · Score: 3, Informative

    A/UX or Apple UNIX was Apple computer's entry into the desktop UNIX world. It ran on their 68030 and '040 based systems, but was never ported to the PowerPC when they made the move to that CPU architechture in the early 90's.

    A/UX had a nice GUI (it was from Apple after all!) which was very similar to the Macintosh GUI of the time (System 7). It had all the greatness of UNIX, including pre-emptive multitasking and protected memory, and it was even able to run most Macintosh applications without modification. Yes, you could bring up a terminal window and much around with a command line if you so pleased, but like today's Mac OS X, you never needed to. Sadly Apple only marketted it to corporate and higher-education users, so it never caught on and was forgotten.

  68. Lee Data by Anonymous Coward · · Score: 0

    My unclde use to work for Lee Data Inc before they were sold off to some Isaraeli company. We had a few of their machines for awhile. They were 286's that ran MS Xenix. The machines had support for 8 terminals and an card for another 8. The motherboard was huge though, at around 24" x 18". They ran on MFMs and were mainly used with Informix.

    I also have a copy of MS Word for SCO/Xenix. Its on two floppies.

  69. So true, so true by Arker · · Score: 0, Troll

    According to 'Hackers', Bill's BASIC program for the MITS Altair was big, slow, bloated, late, didn't work well, and (here's the kicker) required an expensive 4k memory expansion board from MITS that basically didn't work.

    Never used Altair basic, so I won't diss it, but since the versions that MS has produced since then (GW Basic, Qbasic, VBasic) are pretty incredibly shoddy compared to implementations that predated DOS I am guessing the criticism is probably fair.


    Everytime someone claims Bill Gates is a "geek" let alone implying he's some sort of superlative geek, I must say I take that as a personal attack on all true geeks. In a sense it's true. I mean, well, look at him - obviously that was his social assignment in high school, yes. But he's about the worst example of a geek ever. He's simply never shown competence at anything except management and marketing.


    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:So true, so true by Anonymous Coward · · Score: 1, Interesting

      I mean, well, look at him - obviously that was his social assignment in high school, yes.

      At some point you guys have to define "geek" rather than playing it both ways. Most of the scrawny, greasy AV Room social misfits in my high school never showed any particular competence at anything at all. (That's not to say that they aren't screwing together PCs or installing Linux nowdays, just that's nothing to write home about.)

      On the other hand you've got Paul Allen, Bill Joy, Linus Torvalds -- none of which seem like the kid who got swirlies from the football team.

      If anything Gates is interesting because he defies his stereotypical looks and spaz-attack personality. (and for the kids out there, Gates actually washing his hair before going out in public is a recent phenomonon, much like the suits)

  70. lol by Billly+Gates · · Score: 2

    I quivered at the thought of this possible alternative universe when I went to the website. If BIll never agreed to do os/2 then all of that might of happened. We might of all been using MS Xenix right now. Funny as hell. Mod the parent up.

  71. NT, VMS, Northern Telecom... by Arker · · Score: 1, Offtopic

    NT stands for Northern Telecom (Nortel) who originally developed it. However, after MS acquired it, they also referred to it as "New Technology." It's not in any sense a unix implementation, although it is in some senses a VMS implementation. Digital Equipment sued over that and got paid off several years ago.


    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:NT, VMS, Northern Telecom... by Anonymous Coward · · Score: 0
      you mean that NT was yet another MS 'innovation' that was bought and not developed?

      NT kernel and architecte was the one thing that I actually gave them some respect for.

    2. Re:NT, VMS, Northern Telecom... by caspper69 · · Score: 1

      NT stands for Northern Telecom (Nortel) who originally developed it. However, after MS acquired it, they also referred to it as "New Technology." It's not in any sense a unix implementation, although it is in some senses a VMS implementation. Digital Equipment sued over that and got paid off several years ago.

      Stop smoking crack. NT was trademarked because that was their name. It has NOTHING to do with them developing Windows. They are a telecom equipment provider. I wonder how many people read your message and actually believed Nortel (Northern Telecom) actually developed Windows NT. You really should check your facts. It was nothing more than a naming conflict. Hence the name change to Windows 2000...

    3. Re:NT, VMS, Northern Telecom... by Arker · · Score: 2

      you mean that NT was yet another MS 'innovation' that was bought and not developed?

      Doh!


      NT kernel and architecte was the one thing that I actually gave them some respect for.

      Well, this is not to say they didn't do a lot of work on it themselves - the original components weren't even a working OS after all. Microsoft hired away key parts of Digital Equipments VMS team to work on it, IBM programmers worked on it for a bit too, before IBM and MS parted ways. But yeah, in essence, has MS ever innovated anything? Of course not. They buy things that have promise, polish them, and market them.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:NT, VMS, Northern Telecom... by rusty+spoon · · Score: 1

      if it was "New Technology" then the Win2K startup, oddly, says "built on New Technology technology" ;)

  72. Poor Article by Anonymous Coward · · Score: 0

    This is one of the poorest articles I have ever read. The author jumps all over the place and makes vague quotes coming from nowhere..kinda like this comment

  73. Re:Workstations by Slashamatic · · Score: 1

    Actually it was the workstations that did it. Digital's were relatively slow and expensive and could be delivered - eventually. Sun's were relatively cheap and you didn't have to stretch a salesman over a rack to get an allocation.

  74. Also used as route to Internet way before Epiphany by rufusdufus · · Score: 2

    Hey, back in the day at MS I used Xenix to get to Usenet and other internet resources. I was one of the last to give it up, when they pried it out of my fingers. [wasnt willing to die for that one]

  75. What I've gleaned from various sources... by leandrod · · Score: 2

    including the Web, Byte and others, I’ve written down in Portuguese. I’ve already got a very bad translation into English, am looking for confirmation about the exact relationship between Mach and NT before I do a proper revision of the English version.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  76. Re:ms agreed to never again produce a version of u by The+Creator · · Score: 1

    >I heard that to settle a legal dispute MS agreed to NEVER produce a version of UNIX.

    So if UNIX really is the future then MS is doomed to die? Vhuppii... only good news this weekend. :)

    --

    FRA: STFU GTFO
  77. Slashdot Spelling Rools! by uptownguy · · Score: 1

    IBM/HAL, Santa/Saten, its all part of a biiig plot...

    Come -on-!!! Its an anagram, for goodness sake. How hard is it to reuse the same letters!?

    I might get modded down for caring... apparently many geeks still don't realize that style really is substance. But the correct spelling is "SATAN" not "saten".

    --


    I would have to say that explosives are the most abused technology in all of history.
  78. Re:First Unix/Xenix MOD PARENT UP by Anonymous Coward · · Score: 0

    intresting!

  79. Re:ms agreed to never again produce a version of u by gabrieltss · · Score: 2, Informative

    >I heard that to settle a legal dispute MS agreed to NEVER produce a version of UNIX.

    This is true. M$ sold Xenix to SCO SCO Unix is Xenix or was Xenix. But part of the condition of the sale was the M$ could NEVER produce a version of Unix again. That is why NT was touted as an OS like Unix but better. .

    --
    The Truth is a Virus!!!
  80. NT, Xenix. by mindstrm · · Score: 3, Insightful

    Did MS actually *write* xenix, or just license it?

    Regarding NT...

    First, NT stands for "New Technology". It is a coincidence that "WNT" is offset by one from "VMS".

    NT had some of the same designers as VMS.

    NT was new. It is not based on unix.

    NT *is* cool, and has done some cool things since day one. Do not confuse the NT kernel with the abortion of an operating environment Microsoft chose to build with it. As a kernel, it's very cool in many ways.
    Yes, I mean cooler than unix.

    1. Re:NT, Xenix. by demon · · Score: 1

      The Santa Cruz Operation (aka SCO) developed what we know as Xenix, and provided it under the name Xenix for Microsoft under license.

      Windows NT is hardly "new technology" - if you look hard at it, it's just an amalgamation of things which existed. Its GUI is right out of Windows. Its filesystem started as HPFS (OS/2's High Performance Filesystem) - in NT 3.1, you could use HPFS and NTFS partitions 100% interchangeably. Its kernelspace borrows from UNIX and VMS (its head architect, David Cutler, was a member of the original VMS dev team, hired away from DEC). Its userspace API is, of course, based loosely on the 16-bit Windows APIs (known collectively as Win16).

      Remind me. What exactly was "new" about it? Oh yeah, ground-up rewrite. I forgot.

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
    2. Re:NT, Xenix. by mindstrm · · Score: 2

      And none of those things are the Kernel.

      I'm talking about NT, the kernel, not NT, the product.

      IF it's a ground-up rewrite, what is it a ground-up rewrite of? By your criteria, every OS is a rewrite.

  81. For those interested in whats in the posix folder by amemily · · Score: 1

    I dug out my copy of the 2K resource kit cd, and located in the posix folder is the following:

    cat.exe, chmod.exe, chown.exe, cp.exe, find.exe, grep.exe, ln.exe, ls.exe, mkdir.exe, mv.exe, rm.exe, rmdir.exe, sh.exe, touch.exe, vi.exe, wc.exe

    and in the source folder, you can find:

    ar, bsdpsx, cat, cc, chmod, chown, devsrv, elvis, find, grep, include, ld, ln, ls, lstlib, make, man, makedir, mk-rules, mv, pax, rm, rmdir, sh, term, touch and wc.

  82. NT a kind of UNIX? Not bloody likely by jimfrost · · Score: 2

    NT isn't in any way derivative of MS's UNIX experience. It's a clear derivative of VMS, and a direct derivative of Prism.

    --
    jim frost
    jimf@frostbytes.com
  83. hateful cramped little place by drinkypoo · · Score: 2

    "Anyway, when I worked there back in the mid 80's every poor sod in the company from Bill down to the mail clerks had a Xenix terminal on their desk and used it daily for email at least. Meaning every poor sod had to master vi before they could request vacation time (and everyone wonders why Microsoft is such a hateful cramped little place.)

    I'm sorry, do I understand this correctly? Microsoft's problems are being blamed on having to learn vi? The editor that thousand of script kiddies have managed to learn well enough to sabotage Unix systems worldwide?

    To understand my disbelief, take a look at the old MS-DOS editor edlin if you want to see a learning curve. It's essentially the same as "ed", which for those who don't know (I'm sure it's a very small group around here -- Or so I hope) is vi without being full screen. That's right, a line-editor, which you can use on teletypes.

    edlin's learning curve is dramatically worse than vi's because you have to learn how to think non-linearly. You have to know how to visualize a file that you can't see all at once, or you end up displaying blocks of lines repeatedly - On a teletype, that wastes a lot of paper. On a CRT, it just wastes a lot of time.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:hateful cramped little place by Anonymous Coward · · Score: 0

      Isn't edlin *still* MS' editor of choice when working at a terminal console?

  84. What Windows got from Unix by drinkypoo · · Score: 2

    DOS is a (bad) Unix clone: Pipes, redirection, devices which act like files. (/dev/null becomes NUL:, /dev/console is CON:, etc.) Of course, DOS isn't multitasking (though you can fake it with TSRs) so pipes dump their contents into a temp file and then feed the data to another program.

    Windows is basically a clone of Motif, as far as the widgets go; It looks pretty bad, even compared to Motif, but it behaves in pretty much the same way. Minimize to icon, the drop-down menu in the upper-left of the window that you can double-click to close... Most of this stuff has been carried into the windows we know (and usually love or hate, with very little in between, like any other OS) today.

    As for Xenix: I'm minimally annuated as far as Unix geeks go, and so my first experience with it was when SCO was the only company putting it out. I ran Xenix 2.3.2 on a 286-6MHz with 1MB of ram and a 40MB RLL disk. I mostly used vi, uucp, and cu. This was enough to call BBSes and get mail and news delivered to my PC. Clearly it was superior in basically every way when compared to MS-DOS, except for ease of use.

    If Microsoft had created an unencumbered version of "Xenix" at the time, we could have had a very different experience. As it is, we got stuck with DOS and all that that has put us through until the modern day. Instead of simply changing binary formats and having a new kernel with a good compatibility layer for older versions of the binaries, like Unix, we got a rock.

    And it's not even shiny.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:What Windows got from Unix by paul.dunne · · Score: 2

      > Windows is basically a clone of Motif

      This is backwards. Motif copied Windows. Credit where credit
      is due. Did you know that one of the stated design goals of Motif
      was to give X "the visual elegance of Microsoft Windows"? If Unix
      GUIs are still so goddamn awful today, it's in large part because
      of the years spent resolutely refusing to do independent thinking,
      and instead copying already-existing crud.

    2. Re:What Windows got from Unix by drinkypoo · · Score: 1

      As I understand it, Microsoft was one of the original members of the committee to create Motif, but Windows using the motif look came later.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:What Windows got from Unix by paul.dunne · · Score: 2

      You understand wrongly. The Motif docs themselves state:

      "On December 30, 1988, OSF announced that the user environment
      component offering will be based on several leading technologies:
      Digital Equipment Corporation's toolkit technology (widgets)
      and the joint Hewlett-Packard/Microsoft submission of H-P's 3-D
      appearance and Microsoft's Presentation Manager-compatible behavior
      (window manager)."

      Or, to paraphrase: we copied Windows. If you want to be picky,
      you can say instead: they copied a joint IBM/Windows standard (CUA,
      isn't it?), but it amounts to the same thing.

    4. Re:What Windows got from Unix by spitzak · · Score: 2
      But the Motif appearance is from the "HP 3-D appearance", not from Windows.

      Explain how Motif can have copied windows when it has a button and scrollbar appearance that is totally different from every version of Windows.

    5. Re:What Windows got from Unix by paul.dunne · · Score: 2

      > Explain how Motif can have copied windows when it has a button and
      > scrollbar appearance that is totally different from every version of
      > Windows.

      I suggest (re)taking Logic 101.

  85. (yet another) My Xenix story by mihalis · · Score: 3, Interesting

    The National Exhibition Centre ("NEC") in Birmingham, England had an inventory system running on Xenix in 1988. There were 5-10 terminals across the site, mostly Wyse VT terminals plus the console (VGA graphics).

    I think the system was called "Impact" but I'm not sure. It had some problems in the UI with a large data set (all character-based graphics of course).

    I got a job there as a student in my second year at University doing data entry. We would read an entry from a Kalamazoo paper based inventory book like "Rubber grommet, 1/16 cubit, 12.50/100, 12.5% discount, Acme Grommets" and convert it to a price each (yes, we had to throw away information) and enter it into the new system by hand.

    I worked on the console of the server which was a 10MHz AT-clone which ran "like shit off a shovel" according to the vendor rep.

    Every night I would back up the whole system to tape. I think it was a 250MB QIC cartridge, but I'm not sure. I know they had that distinctive metal plate on one side (a Travan NS20 is quite similar, but smaller, and 10GB).

    In my lunch-hours I would read about strange things like "Bourne Shell" and "echo".

    It was the first multi-user system I ever used so we all had fun looking at each others files.

    I seem to remember making a directory called personal, which contained another called private, and in there a file called readme.txt, which contained only the words "aren't you nosy". Someone asked me about that within a week.

    The Word processor was quite nice for the day and called "Lyrix". Unix systems in those days had real printed manuals which is good for beginners who don't know their way around. All the messages that Lyrix used could be overriden in a text file, so again we had a lot of fun with that.

    I seem to remember I was being paid 100 pounds a week in total for a full-time job, and paying rent and running a car out of that. I lost quite a bit of weight that summer.

    1. Re:(yet another) My Xenix story by Anonymous Coward · · Score: 0
      I lost quite a bit of weight that summer.
      If you were a student there in 1988, PLUS earning 100 quid a week, you would certainly not be badly off. Low CoL, no tuition fees, and didn't you even have living grants then? Or had Thatcher already killed 'em off?
    2. Re:(yet another) My Xenix story by mihalis · · Score: 2

      My "living grant" was from my Dad and was long gone before the end of the summer term, so I was living on 100 pounds/week total for 12 weeks. I'm not saying it was penury, but there wasn't much left over for beer (my downfall!).

    3. Re:(yet another) My Xenix story by Anonymous Coward · · Score: 0

      Summer love...
      sniff sniff

      How romantic!

  86. False Myth by sheldon · · Score: 2

    This is a myth which was started by R.E. Ballard in the comp.os.linux.advocacy group back in around 1995. It's not been corroborated by anybody else, and Mr. Ballard refuses to provide any evidence to substantiate it, although he did once claim that it was so important to SCO that they reported it as an Asset in their annual reports.

    Given Mr. Ballard's propensity for exagerration and lying, I really would not lend any credence to this story. It may very well be true, but if it is, the consequences of it would surely not be nearly as far reaching as Mr. Ballard's claim.

  87. False Myth? by Decimal · · Score: 2

    "False" Myth? As opposed to one of those "True" Myths?

    Oh, I get it. It's one of those oxymoron jokes, like "Microsoft Works."

    --

    Remember "Bring 'em on"? *sigh
    1. Re:False Myth? by gorilla · · Score: 2

      To anthropologists, there is such a thing as a true myth. A myth is basically a story that has been passed along an oral tradition. Some of those stories are based upon actual events.

  88. Re:Unix is the future. A question... by lewkor · · Score: 1

    Sorry for being off topic. You will have to excuse me I have (blissfully) not had to use Windows for several years - I have made my living since I graduated from university in 1992 using Linux/UNIX. I wasn't aware that MS had something equivilent to symbolic links. What do they call them? Are they just as flexible as under unix?

  89. greed kills new platforms by mmusn · · Score: 2, Informative
    Yes, Microsoft did sell Xenix. As I recall, it was very expensive and deviated from AT&T's system in unleasant ways.

    Most likely, what killed Xenix was AT&T's licensing fees--it's hard to see how such a premium priced system could have caught on with normal users, in particular at a time where people expected their OS to just "come" with the computer for free and nobody else was offering something as nice and expensive as UNIX. Many other great software systems have been killed by the desire of their creators to milk the market early and often with "breakthrough platforms". Smalltalk80, CommonLisp, and NeXTStep all priced themselves out of the market. Gates has the right business idea: make it cheap and simple and tighten the screws once you have a monopoly and people can't jump ship anymore.

    I find this particular report rather dubious, however:

    "Anyway, when I worked there back in the mid 80's every poor sod in the company from Bill down to the mail clerks had a Xenix terminal on their desk and used it daily for email at least. Meaning every poor sod had to master vi before they could request vacation time (and everyone wonders why Microsoft is such a hateful cramped little place.)

    As opposed to what? The text editor that came with DOS? It seems to me they should have been so lucky as to get "vi". If Microsoft didn't like it, they could have developed whatever you think they did was so much better for DOS. And where did "vi" even come from? Xenix derives from 7th Edition UNIX, and I don't remember "vi" coming standard with 7th edition UNIX. If Xenix had "vi", someone must have decided that it was a good idea to backport it.

  90. Vi, VBA, Viva! by fm6 · · Score: 2
    I wouldn't be surprised if he _still_ uses vi, maybe even under Cygwin, on his own machines.
    Cygwin has its uses, but running vi isn't one of them. Easier to run vim, which is profoundly vi-compatible, and runs on just about everything.

    There are lots of reasons to like vim over vi, but for me the big one is GUI integration. Running vi under X-Windows is a nightmare, unless you're better than I am at remembering to go into insert mode before pasting. Vim, by contrast, talks directly to clipboard. And using vim under Windows and X-Windows is pretty much the same.

    But given Mister Bill's fondness for gee-whiz technology (is it true that the famous mansion needs 50 NT servers to keep from falling down?) I suspect he does everything in MS office -- and spends a good chunk of each day hacking VBA macros!

  91. Xenix or dogfood? by xeno · · Score: 3, Funny

    If it is indeed true that Microsoft was running on Xenix up until Windows 3.1, it casts an interesting light on how flexible Bill's vision of the future was right up until the early 90s.

    Funny, that. When I was at MS from 94 to 95 or so, there were still quite a few Xenix systems around in the "Business Systems" group or whatever the hell they were calling it then. I found it particularly humorous because I was working on the MS Exchange Server project, and here my co-workers were using Xenix mail. Some folks apparently wanted to *read* their email, not just to "eat dogfood"

    When I think what MS *could* have done with the amount of development effort that went into MSExchange v. 1.0^H^H^H 4.0, if they had applied it to Xenix mail... We'd have rock-solid secure email that'd be delivered before it was sent, managed by a system running on a 486 with 16mb ram, hosting 10,000 accounts. Instead, we have memory leaks, a GUI designed by Smurfs, and secure coding philosophies that led to inclusion of auto-executing-content as message body (= by-design vehicle for viruses, which we reported internally in the company in '95). What a waste.

    The hell with it, I'm buying a Mac.

    --
    I think not...(*poof*)
  92. bah by ceethree · · Score: 1

    Bah ! i dont think MS had the right to run a distro of nix they wanna wipe them out .. well i believe *nix is wiping the floor with MS . heh anyways peace

    --
    Yours Truly, Wes -- Owner ... http://www.geekish.net
  93. Did the Register author complete Grade 2 english? by Anonymous Coward · · Score: 0

    Their writing style sucks! It hurts to read this crap.

  94. Hey, we USED Xenix by rs79 · · Score: 1

    And ran mail and news in the mid 80's. Brian Reid got us a UUCP feed from a real TCP/IP connected site - JPL, and put gryphon.com on the usenet backbone, no doubt helping to lead to it's demise .

    Xenix worked perfectly well; we fed news and mail to over a hundred downstream sites with UUCP and had a doezen news peers.

    If you look at old usenet postings in Google, anything that was gryphon.com or gryphon.cts.com came from that lowly i286 development system running Xenix administered by Greg Laskin (who died in 1990). Gryphon.com posters were constantly in the top 25 bandwidth wasters postings that K*net Paul Dolan annoyed everybody with.

    Whether it had a chance on the desktop depends on whose desk it was on.

    --
    Need Mercedes parts ?
  95. I worked with Xenix..... by cyberkahn · · Score: 1

    And I didn't like it all. I would take Linux or FreeBSD any day over Xenix.

    1. Re:I worked with Xenix..... by ASyndicate · · Score: 2

      Remeber the dates.

      I dont think you would have wanted to use any machine back then...

      --
      This page left intentionally blank.
    2. Re:I worked with Xenix..... by cyberkahn · · Score: 1

      I know. I was just making a comparison if Linux/FreeBSD were available back then. You took me too literal.

    3. Re:I worked with Xenix..... by ASyndicate · · Score: 2

      Ahh, Ok Sorry :-)

      --
      This page left intentionally blank.
    4. Re:I worked with Xenix..... by b4r4bb4s · · Score: 1

      I don't know why almost nobody remembers this OS. It shipped preloaded on the original IBM PC-AT. It was a good version of unix for the power of the PC back then in '85. It was completely compatible with PC-DOS and could live on the same computer while running at the same time (try that with Linux and Windows). Xenix was based on AT&T's System III and back in that day and age it actually supported 3 megs of ram and a 20 meg hard drive! I'm not defending Xenix as the best *nix version but it was the very first and so far worked the best on the pc (as in being completely integrated). Don't knock Gates just because of what he became...remember he tried to make Unix for the desktop but just gave up...why? Apple. Yes. Apple. They are the ones who ruined it for us all...they almost ran Gates out of business so he ported windows (originally an alternate to the X server) to the PC and made it the standard. Thats why Windows has always run as an application rather than an OS...because it never was an OS it was an application...only now is it becoming a real OS with Win2000 and (shudder) XP. So don't blame Gates he at least tried to do it first...but the urge to make money and be popular overcame him.

  96. MS actually has some pretty cool version control.. by mjfgates · · Score: 1

    Their older system, SLM, was about equivalent to cvs, and perhaps slightly better. Its main trouble was ease of use; the first time I ever had to use SLM, it took me a week to get it set up because the documentation was wrong and I was in a remote location.

    Their newer version control is called "Source Depot", and it's got a really cool trick: transactional checkins. Add two files, change three others, and delete one, all in a single operation. Once again, ease of use, poor documentation, and lack of training are real killers, which is a shame because the system is SO DAMNED COOL if you only understand it.

  97. Rudimentary? by crucini · · Score: 2
    Yes, you need to know vi if you're going to work on a lot of different machines. That's aside from the fact that it's a good editor.
    However, once I learned the bare minimum I needed I quit learning about it because its simply not productive to use such a rudimentary editor when there are so many better tools available.

    Why exactly do you call vi rudimentary? By your account you have learned only the bare minimum about vi - the functionality it shares with DOS EDIT.COM or Pico. Your grasp of vi is rudimentary, but if you increase your understanding you may come to understand that vi is very productive. I wonder what you consider 'non-rudimentary'. If it's EMACS, I won't try to argue because that's a religion. But if it's some GUI thing, you're probably fooling yourself. I've watched a lot of people using a lot of tools, and nobody using a GUI is as fast as a fast vi user. Crawling is easier than walking but once you learn to walk you generally don't go back.

    Vi isn't 'rudimentary' - it is possibly sailing right over your head. It encourages more abstract commands like 'delete 3 words' or 'go to line 2511' or 'change everything up to the period to "this year"' rather than the too-low-level commands of a GUI editor: "move down one line. again. again ...". Vi assumes that the human will specify the work and the computer will do the work. What's really rudimentary is a shiny expensive interface that forces a human to do a machine's work.

    On a more positive note, I hope you continue to learn vi. Perhaps your 'Eureka' experience is still in the future.
  98. Everything worked out for the best by crucini · · Score: 2
    It really pisses me off that IBM didn't take UNIX back then. We could have had UNIX everywhere now. None of that painful command.com stuff. Course, it'd probably be csh instead of bash, but nothing's perfect. Of course, from what I've heard of SCO, we might be using a pretty awful UNIX..

    I disagree, just as I disagree with the people who wish IBM had pushed OS/2 better. I'm really glad to have Linux, and there's no way a corporation would have created something like that. By fumbling so badly, the corporations created a vacuum into which Linux stepped. Corporations have an incredible gift for ruining software - even something like Unix that's good at the core was being ruined by the commercial Unix vendors.

    Likewise, I am incredibly grateful to Bill Gates for helping to create a world of standardized cheap hardware which made Linux possible. Can you imagine how it would suck if there were 25 popular computer architectures, all proprietary, closed, shitty, with their own proprietary OS's that were bastardized versions of DOS or SCO? And I'm grateful to him for making his software so unattractive to smart people that we swarmed to Linux.

    When I look at the modern history of computing I almost believe in God. It's as if everything were arranged perfectly to create the wonderful situation we have today.
    1. Re:Everything worked out for the best by Bert64 · · Score: 1

      Multiple computer architectures would infact HELP linux and open source software in general. Afterall, if you could run a cross platform os and apps on all of the popular architectures, it would atleast be a simple matter of recompiling software to run under linux on any of the popular arch`s, whereas it would require heavy duty porting to run on a propriatory os.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    2. Re:Everything worked out for the best by crucini · · Score: 2

      I disagree. Look at the current situation with game consoles. Nobody has a usable distro for any game console. The manufacturers have put up too many obstacles. Similarly, in a world of fragmented proprietary computing, the effects of business and marketing decisions could be very harmful. Companies might sell their computers below cost (as game consoler makers do) and make it up on licensing software. In that case they would fight aggressively against any attempt to reverse engineer the platform or write an alternate OS. Instead of accepting the internet, each computer company would probably have tried to create their own. Some would work out OK, some would die, and lots of hobbyists would build bridges. Of course a guy bridging the Commodore network to the Apple network would probably get sued by both companies.

      Remember, Linux was not initially a cross-platform OS. It gained momentum because it ran on the most popular and generic platform. The first real port of Linux was a major traumatic experience. If a large pool of generic hardware had not existed, I don't think Linux would have acquired momentum.

      Proprietary computing tends to be integrated and seamless and therefore unfriendly to modification and reverse engineering. The Wintel world, however, has lots of public interfaces like the disk booting capability that allows any OS to boot.

  99. godwin's law has been superceded by ahde · · Score: 2

    the probability of godwin's law being invoked has exceeded that of Hitler or Nazi's being mentioned.

    We need a new law.

  100. dbdebunk.com by crucini · · Score: 2
    Interesting site. However Mr. Pascal seems to be floating on his own clowd, high above the real world. He writes that relational databases do not exist. I looked (in the first article) for some support for this startling idea and found only:
    1. Date, a relational database pioneer, has written a manifesto saying that SQL databases are not relational. I think it's a bit late for even such an influential writer to kick all the players off the field and repaint the lines.
    2. Today's databases link a conceptual entity-instance to a physical row in a table. This violates set theory because members of a set have no "order" while rows in a table do. I totally fail to see why this matters. Any good database appication programmer knows not to rely on the natural order of rows. If you're selecting more than one row, use an ORDER BY clause.

    However I do agree with the author that the current buzz around "xml databases" is an attempt to revive a failed technology (hierarchical db) under a new coat of paint. I don't mean to condemn such things completely - I recently implemented such a database at work as a very minor adjunct to our relational databases - but they can only be used within their niche, which assumes that a record is always retrieved by its key. Such structures lack the reporting flexibility of the relational database.

    Anyhow, Mr. Pascal goes on to criticize data warehousing:
    By ignoring sound logical design principles such as normalization, data warehouses take us back to application-biased files and incorporate analytical presentation functions, which belong at the application level, into the DBMS.
    He seems to ignore the real-world considerations that drive data warehousing. If you're going to run tons of queries on a static set of data (no more inserts or updates) it's faster to denormalize the data first. Why should companies have to buy beefier hardware to keep their data warehouse "truly relational"? Second, the reporting programmers might not feel like wrapping their minds around a four-table outer join on unfamiliar tables just to get the most basic report. Letting the data model be the king is great when there's only one data model. Since the data warehouse works with every data model in the enterprise, it's more logical to flatten the data on intake.
    1. Re:dbdebunk.com by leandrod · · Score: 2

      > He writes that relational databases do not exist. I looked (in the first article) for some support for this startling idea and found only:

      You can hardly want to get the whole truth from a single article in a web site while its authors have written several other articles in that web site, and indeed several books about the issue.

      If I were to summarize the articles and books that you didn’t care to read, I’d say that SQL never intended to use more than a few basic relational ideas, without ever caring about being faithful to the whole theoretical model. As an analogy you could say that it would be like trying to implement OO without encapsulation: if a model is completely subverted by a product claiming to support it, the claim can’t be considered valid.

      > He seems to ignore the real-world considerations that drive data warehousing.

      You seem to be reaching conclusions without enough reading. The whole point of relational is that a single database would be able to perform adequately for different applications. That’s impossible with SQL precisely because by subverting the relational model SQL looses many of the advantages the relational model was created to provide. If current databases were relational they would require neither such a beefy hardware to start with, nor such costly programming and conversion procedures.

      Also, you fail to distinguish the different meanings of data model, and indeed the goal of data modelling: to make data understandable, logic and accessible. If there are ‘different data models’ in a company, that means already a failure either in the DBMS, or in the data modelling, or both.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    2. Re:dbdebunk.com by crucini · · Score: 2
      You can hardly want to get the whole truth from a single article in a web site while its authors have written several other articles in that web site, and indeed several books about the issue.

      A valid point, and I may read some more of the articles on the site. But I'm not likely to buy books merely to understand an argument which appears dubious and impractical.

      It seems that the core issue is the authors' demand to define 'relational database' in a sense that predates SQL and ignores all recent evolution.
      Karl Marx wrote about 'communism', and communists insist that true communism never existed. Ayn Rand wrote about 'capitalism' and objectivists insist that true capitalism never existed. It's pointless to compare these platonic ideals to real-world political systems practiced in the US and USSR. Naturally the real world is inferior to the dream world. But the real world does take on labels 'communism' and 'captitalism' that originate in the dream world.

      If current databases were relational they would require neither such a beefy hardware to start with, nor such costly programming and conversion procedures.

      Has anyone written a true relational database? If not, what are they waiting for? Is such a database vastly harder to write than the pseudo-relational databases being used today?
      If there are `different data models' in a company, that means already a failure either in the DBMS, or in the data modelling, or both.

      Sounds like another collision between reality and ideal. In an ideal world, the structure and business model of a company would be known in advance and someone would create a unified data model for the company. In practice, large companies purchase many different software packages that come with their own database schema. The packages are purchased over decades and represent different trends in programming. A company could have Siebel defect tracking, Clarify CRM, Oracle ERP, and some smaller packages specific to the industry. Add to this a few in-house projects - remember that the designers of these projects do not have time to learn the data model of any of the existing systems, which are large. Now we have a collection of independent systems that work pretty well in their own domains, but no way to aggregate the data. That's where data warehousing comes in. Data warehousing adapts the fragmented world of corporate IT to a unified reporting architecture.
    3. Re:dbdebunk.com by leandrod · · Score: 2

      > A valid point, and I may read some more of the articles on the site.

      Please do. You may also be interested in some stuff at DMoz Relational Implementations and Model listings... I created these, they have been taken over with no explanations and I could never get back into DMoz, again with now explanations as to why.

      > But I'm not likely to buy books merely to understand an argument which appears dubious and impractical.

      ‘Dubious and impractical’ in which grounds? In fact, it’s hardly dubious because they are the authors and maintainers of the relational model; and it’s not impractical at all because there were already at least two faithful implementations of the relational model already, one currently in beta and other in production usage for twenty years already, not to mention other implementations, partial or not that aren’t perfect but are still more faithful to the model.

      > It seems that the core issue is the authors' demand to define 'relational database' in a sense that predates SQL and ignores all recent evolution.

      The whole point is that SQL is an involution.

      > Has anyone written a true relational database? If not, what are they waiting for? Is such a database vastly harder to write than the pseudo-relational databases being used today?

      Yes, as I pointed above. The issue here is that the market has in the eighties taken the ‘safe’ option (IBM SQL/DS) and fell in love with it over the better alternatives, just as it did with MS Windows over Unix and OS/2 in the nineties.

      > Sounds like another collision between reality and ideal. In an ideal world, the structure and business model of a company would be known in advance and someone would create a unified data model for the company. In practice, large companies purchase many different software packages that come with their own database schema.

      Again that’s a failure in the tools and processes. Even if SQL is fundamentally flawed, if it was really standard integrating all these databases wouldn't be so hard; if it was really distributed it would be a given; if on top of this all these products were properly documented, this job would be almost done already.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  101. Better be careful... by Canar · · Score: 1

    ...you might give Taco a reason to start censoring /.

    Not that I care.

  102. It shouldn't be. by Anonymous Coward · · Score: 1, Interesting

    Actually, there are many people at MS who use vi or vim. My boss prefers emacs to Visual Studio. I prefer VS.NET, but I've used vi, and it gets installed with my team's dev tools, along with a whole bunch of old familiar Unix-like tools.

    This really shouldn't surprise anyone. Coming from a CS background (Linux and Solaris), and growing up using DOS, I'm used to both sets of command-line tools. I'm sure BillG is, too. He wrote some of them.

    Just because I work at Microsoft doesn't mean I don't understand what is important to geeks like the kind here at Slashdot. I just want to use my skills to improve the software that the most people use. More people use MS software, so that's why I'm here. I've been here less than a year, but if you look around MS, you'll find a lot of others here for the same reason.

  103. Re:Unix was the future (was: Re:Unix is the future by Anonymous Coward · · Score: 0

    Regarding your sig:

    Please review your second grade English class notes, specifically the section under the heading "To vs. Too vs. Two". Thanks.

  104. MSDOS & PCDOS by Hugonz · · Score: 1
    This was both MSDOS & PCDOS at that time, only the versions shipped with IBM PCs were called PCDOS, and MS could market it under the name MSDOS.

    Still, I don't think there were lots of clones (yet) by the time MSDOS 2.0 came around, so it's probably more accurate to talk about PCDOS

  105. Re:For those interested in whats in the posix fold by mirabilos · · Score: 1

    Pax actually is in the WINNT\SYSTEM32 folder, too.
    Rename it to tar.exe or posix.exe and you see it
    works as intended, too.
    It even has ancient BSD RCSID strings in it.

    But heck, where can I download that CD?

    --
    My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  106. Re:Unix was the future (was: Re:Unix is the future by kermit6306 · · Score: 1

    What sig might this be?

  107. MS Philosophy? by Razzak · · Score: 1

    Now, i'm not trying to troll either but...

    if I recall an article I read on /. a few weeks ago, an engineer on IE was talking about why NS "lost" the browser war.

    He was talking about how they started from scratch, and how you're always better off keeping your code, bloated as it is, and letting hardware catch up (Word just seems to scream this).

    I think he makes some good points in favor of his argument, but, this does seem to be the general philosophy of MS (And that probably came down directly from Gates).

    The thing is, he's got the market share to backup this software philosophy. I don't agree with it, but it doesn't always matter if you bribed the refs. In the end, all that matters is what's on the scoreboard.

  108. MS-DOS Directories From Unix by Anonymous Coward · · Score: 0

    The MS-DOS directories (rather than having the disk have one directory) did come from Unix. There was a trade paper article at the time where Gates stated it was from Unix and they intended in the future to add many more of the abilities of Unix to MS-DOS.

  109. you're all wrong. by hawk · · Score: 2
    NT is short for "No Thanks", the Thinking Man's (TM) repsonse to windows . . .


    hawk, who understands that if windows is the answer, you asked the wrong question

  110. Re:ms agreed to never again produce a version of u by Anonymous Coward · · Score: 0

    Last I heard (this was true years ago) MS held a 20% stake in SCO.

  111. Re:Apple also had Unix on the desktop in years pas by Anonymous Coward · · Score: 0

    The A/UX thing always mystified me.

    Here, they had a real Unix, with a decent filesystem and the nicest GUI around, and they just walked away from it, telling their clients with Appleshare Pro (Appleshare on A/UX) to replace their machines with a non-preemptively scheduled OS and an extremely fragile file system and a horribly unstable architecture for loading third party system extensions. Of course for file service the new PPC machines were not very much faster than the A/UX machines despite having much, much faster hardware -- because of the inferior OS.

    In the mean time, NT really began to steamroller Novell around the same time,mainly based on its suitability for hosting applications (it still can't hold a candle to Novell for file service). Yet A/UX would have been far superior to NT for hosting applications. Of course, then the Internet exploded, and Apple could have been right there with an admin friendly Unix ready to take advantage of all the free software that makes the Internet run.

  112. radio shack and xenix by zonker · · Score: 0

    i used to work for radio shack back in '95-96 and the backoffice machine in each company owned store was xenix based. the individual pc's that stood for pos stations were dec machines, and they were apparently just running as dumb terminals to the host machine. just wondering if anyone else knew anything about their old system...