Microsoft's Ancient History w/ Unix 403
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.
Unix is the future. (Score:4, Interesting)
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.
Re:Unix is the future. (Score:2, Interesting)
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
Re:Unix is the future. (Score:2, Informative)
Re:Unix is the future. (Score:2, Informative)
Re:Unix is the future. (Score:3, Informative)
Unfortunately, my memory fails as to whether this was still IBM PCDOS or MSDOS. I'm thinking by that time it was MSDOS.
Re:Unix is the future. (Score:2, Informative)
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.
Re:The Microsoft Borg analogy (Score:2, Funny)
Re:Unix is the future. (Score:2)
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.
Unix was the future (was: Re:Unix is the future.) (Score:2, Insightful)
Mac OS X. The "10" stands for "about 10 years to late".
Re:Unix is the future. (Score:3, Informative)
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.
This isn't surprising. (Score:5, Interesting)
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
Re:This isn't surprising. (Score:2)
No need. He can use vi for windows [winvi.de].
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.
Re:This isn't surprising. (Score:2)
Re:Cut N Paste? (Score:2)
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 [amazon.com]. Where else was I supposed to learn about it?
Re:Cut N Paste? (Score:4, Informative)
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.
Re:This isn't surprising. (Score:5, Funny)
Maybe this will become the single most powerful argument in the emacs vs. vi religious war.
Re:This isn't surprising. (Score:2)
Re:This isn't surprising. (Score:5, Funny)
** Use of Hitler in Arguement Detected: AUTOMATIC LOSS **
Ok, I lose.
Re:This isn't surprising. (Score:3, Insightful)
See http://www.faqs.org/faqs/usenet/legends/godwin/ [faqs.org].
Re:This isn't surprising. (Score:2, Interesting)
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.
Computer Lib / Dream Machines (Score:2, Interesting)
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.
Re:This isn't surprising. (Score:3, Interesting)
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.
Microsoft ported vi to windows...... (Score:2, Interesting)
Vi's longevity. (Score:2)
(-5, Troll)
--saint
Re:This isn't surprising. (Score:2, Funny)
Pico does not like escapes much.
Re:This isn't surprising. (Score:2)
Wrong Way (Score:2, Funny)
Re:This isn't surprising. (Score:4, Insightful)
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
Re:This isn't surprising. (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. :)
Re:This isn't surprising. (Score:3, Insightful)
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/tucker0
Re:This isn't surprising. (Score:3, Interesting)
I would be suprised if he hadn't. Melinda is a LISP weenie.
Ever wonder who was in charge of Microsoft 'Bob' ?
Re:This isn't surprising. (Score:3, Funny)
+10 Funny!
It's a weak form of Unix (Score:5, Funny)
Windows NT == VMS (Score:5, Informative)
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
Re:Windows NT == VMS (Score:2)
Re:Windows NT == VMS (Score:4, Interesting)
Re:Windows NT == VMS (Score:3, Funny)
I'll bet you get to be employee of the month a lot, too.
Re:Windows NT == VMS (Score:5, 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. Even with Alpha, DEC never got more than 1% of the Unix market.
Re:Windows NT == VMS (Score:3, Informative)
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.
Re:Windows NT == VMS (Score:5, Informative)
IBM/HAL, Santa/Saten, its all part of a biiig plot...
Re:Windows NT != VMS (Score:2, Interesting)
Re:Windows NT != VMS (Score:2, Informative)
Hint - it will be the most stable thing you've seen on PC (at that time)..
Re:Windows NT != VMS (Score:2)
Sometimes moderators just suck! Yes, I am very well aware that this will give me a Karma hit. Go fire!
Mod parent up (Score:2)
Re:Windows NT == VMS (Score:2, Informative)
Re:Windows NT == VMS (Score:3, Informative)
NT actually started life as OS/2 3.0, not Windows.
Re:Windows NT == VMS (Score:2)
Re:Windows NT == VMS (Score:2, Informative)
all in all, not a bad idea: on paper
enjoy!
So Scientology has Xenu... (Score:2, Funny)
...and Microsoft has Xenix.
Coincidence? I think not.
Re:Xenix has returned (Score:2)
>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
The closest thing to a remaining relative would be Openserver 5.0.6, which is still marketed by Caldera.
Matt
a glorified email terminal (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.
Re:a glorified email terminal (Score:4, Informative)
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.
Re:a glorified email terminal (Score:2, Insightful)
The only other use for Xenix was to check your email.
Re:a glorified email terminal (Score:2, Interesting)
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.
A lot of flannel there (Score:2, Informative)
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.
Gates as a closet Linux user (Score:4, Funny)
Xenix was for email and little else (Score:5, Informative)
I joined Microsoft in 1988 and after working on QNX I was stunned at how primitive their development environment was. I would have been only too happy to develop on Unix
Instead, all development was done on PCs running DOS.
I don't know who the unnamed "former grunt" quoted in the article is but he's full of it.
what developers at Microsoft ran (Score:5, Informative)
There was a push to self-host on NT which I recall became feasible in early 1992. Eventually more and more of the group switched over to it. I think the rest of the company probably didn't switch until after the first version of NT shipped in July 1993.
But it is indeed true that the standard email terminal in 1990 was connected to a Xenix machine, and there was a card handed out "how to use vi to edit email" or somesuch.
Actually I used vi for writing code for a while...someone inside Microsoft had hacked up a version that supported multiple windows...but eventually I switched to slick like most of the NT team. BAsically the incremental search in slick was cooler than the . command in vi.
- adam
Microsoft and UNIX (Score:5, Informative)
Re:Microsoft and UNIX (Score:5, Informative)
With NT, Cutler finally designed and helped implement an operating system explicitly meant to run on multiple hardware platforms, about 20 years after the second implementation of Unix in C made its debut.
Cutler's spent most of his life trying to snuff Unix, poor boy. The booming popularity of Linux in the server world running on those PCs must be incredibly frustrating to the NT hackers at MS who thought they were going to finally drive the last nails into the Unix coffin
Re:Microsoft and UNIX (Score:5, Interesting)
I'm no expert on PDP11 operating systems, having only used RSX-11M and Unix V7m (the DEC distribution of AT&T Unix for PDP11s, I believe almost entirely used by Universities), but I think this is revisionist history.
I do believe that RSX-11M was the OS of choice for small systems or Real Time programming. RSX-11S, an offshoot of M for very small systems, was a dream to work with for very small footprint embedded systems, as I recall.
It's unfortunate that RSX-11M(+) supplanted IAS and RSTS/E, which were good time sharing systems, but I knew quite a few people who appreciated 11M for what it was good for.
Now this is definitely revisionist history. DEC provided device driver support and made releases of Unix V7 on PDP-11s as far back as 1978, IIRC. They were doing the same thing with BSD Unix on VAXs shortly thereafter (a little fuzzy on this).
Cutler's spent most of his life trying to snuff Unix, poor boy. The booming popularity of Linux in the server world running on those PCs must be incredibly frustrating to the NT hackers at MS who thought they were going to finally drive the last nails into the Unix coffin ...
Now, this sounds right. From what I've heard, Cutler does hate Unix and I'm certain that the ex-DECies at MS were on a mission.
Funny how NT was designed to run on multiple hardware platforms, I believe it first ran on MIPS in fact, but now you can get it on Intel only.
Re:Microsoft and UNIX (Score:2)
Not true. NT4, still a viable OS and used in many companies (i just upgraded the pcs to 2k at work) shipped RISC, DEC, and i86 versions. Win2k and XP only work on the i86 platform, but, that is mostly because DEC is dead (Thanks Compaq!) and because they are focusing on 64 bit market, where they save a lot of R+D time (considering the market) by sticking w/ the established big boys. There is almost not reason for them to work on MIPS or RISC processors since the market for them is so incredibly tiny. If you were to buy Sun or SGI proprietary systems, would you really want to slap WinXP on there? No, because all the programs you could possibly now use are compiled for the i86 architecture, and there is already software out there that is prepared for the specific app you are using that processor for.
NT on Alpha, MIPS, x86, PPC, & Itanium (Score:3, Informative)
PPC made it to NT 4.0, Service Pack 2. The last to go was the Alpha in 9/99 which was suprising to many as it was in line to be the first 64bit Win NT implemention. There are still sites like AlphaNT [alphant.com] out there providing resources for the last holdouts.
Re:Microsoft and UNIX (Score:2, Interesting)
The Architects: First, Get the Spec Right [microsoft.com]
"Once upon a time
"Every month, Nadine Kano prowls the halls of Redmond to profile the real folks behind Windows 2000 development. This month: David Cutler and Mark Lucovsky, who helped guide the operating system from its infancy."
Comment removed (Score:4, Insightful)
Re:Brighten up everyone!!! (Score:3, Informative)
Re:Brighten up everyone!!! (Score:3, Informative)
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.
ATT's "failure" to properly manage UNIX (Score:5, Informative)
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!
msdos ...? (Score:5, Funny)
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
Spin is not correct (Score:3, Interesting)
-russ
Re: (Score:2, Informative)
There is no contradiction in MS philosophy here (Score:2, Interesting)
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.
What's really being said? (Score:2)
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.
M$ used Xenix until 96-97 (Score:2, Informative)
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
Re:M$ used Xenix until 96-97 (Score:4, Funny)
Simple--use SourceSafe as your source code control system.
Some history notes on NT's development: (Score:5, Informative)
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.
Microsoft Confidential source (Score:4, Interesting)
#!/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"
# 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
Re:Microsoft Confidential source (Score:2)
Microsoft's early plans for XENIX (Score:5, Interesting)
"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
Xenix in 1989 (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:
The advantages of using this:
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.
EPuzzled with the Cronology (Score:3, Interesting)
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.
Xenix XP (Score:3, Funny)
You might find this funny:
Xenix XP [wubda.com]
MD
Two interesting points (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!
First Unix/Xenix (Score:5, Interesting)
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
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.
Stuff to read (Score:2)
I'd bet my left nut that "stuff-to-read" has to be the most common department by a longshot.
Apple also had Unix on the desktop in years past (Score:3, Informative)
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.
NT, Xenix. (Score:3, Insightful)
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.
(yet another) My Xenix story (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.
Xenix or dogfood? (Score:3, Funny)
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.
Re:Yet more proof microsoft is actually... (Score:4, Funny)
Re:Xenix? That's SCO's distro, isn't it? (Score:4, Informative)
>
>You might want to lay off that crack you
>mention...
Actually, he's not on any more crack than you.
Microsoft didn't sell Xenix directly - they licenced it to various companies, including SCO. They are the ones who actually sold Xenix for Intel processors, starting with SCO Xenix System V way back in 1983.
This is the eventually became the basis for SCO UNIX in 1989. When they released version 3.2v4.2 of this product, they also started selling it under the named Openserver and Opendesktop around 1991. Around 1995 they dropped the SCO Unix and SCO Opendesktop brandings, and sold exclusively under the name Openserver (in Host, Enterprise and Desktop configurations).
Unixware, far from being SCO's baby, was originally put out directly by AT&T's Unix System Labs back in 1992. They divested themselves rather quickly of this product by selling it to Novell in 1993, who themselves sold it to SCO in 1995.
Finally, in 2001, Caldera aquired the entire Unix division of SCO, to become the controller of the Xenix grandchild Openserver and the Unixware product lines.
Mind you, over the years SCO has stripped out virtually all of the Microsoft code in their product line, but had to go into litigation to remove some DOS compatibility code they by contract included in their software.
In any case, back to the point - SCO had 16 years of experience with Microsoft Xenix products before it even touched Unixware, and Unixware had 4 years of existence before SCO got their hands on it.
So both you and the person you responded to didn't have it quite right.
Matt
Re:Xenix? That's SCO's distro, isn't it? (Score:2)
>product which SCO aquired in 95
Actually, I did address that:
Unixware, far from being SCO's baby, was
originally put out directly by AT&T's Unix
System Labs back in 1992. They divested
themselves rather quickly of this product by
selling it to Novell in 1993, who themselves
sold it to SCO in 1995.
It came to SCO via Novell, but before that it was a USL project.
(I am so glad that my years selling and supporting SCO have come in handy... even if it is just for Slashdot posts
Matt
You're thinking MacOSX (Score:2)
Re:No, he's not. (Score:2)
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
Re:No, he's not. (Score:2)
Re:If Bill didn't abandon Xenix... (Score:5, Funny)
graspee
Re:If Bill didn't abandon Xenix... (Score:2)
And who the hell modded me informative? Someone with a sense of humour, or an extremely gullible person?
graspee
Re:If Bill didn't abandon Xenix... (Score:2)
/Brian
Re:If Bill didn't abandon Xenix... (Score:2, Funny)
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!!!!!!!!!
Re:Vi is the tool of Satan (Score:4, Funny)