The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] What UNIX Artifacts Are Still Missing?
Date: Wed, 6 Dec 2017 12:13:36 -0500	[thread overview]
Message-ID: <CAC20D2Mt42f0P7XYvsNSAJm76T=wvaNsc4Rd7LTxRby6WGfn0A@mail.gmail.com> (raw)
In-Reply-To: <CDB2E063-28F2-4E7E-A3C9-114EF0FB90C5@planet.nl>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3160 bytes --]

On Wed, Dec 6, 2017 at 9:33 AM, Paul Ruizendaal <pnr at planet.nl> wrote:
>
> ​A​
> lthough Xenix predates Venix, I'm not sure it predates it on PC hardware.

​It really depends how you count.   I was there at time when AT&T was
negotiating the replacement for the V7 license with 10 of us (the 10 firms
included Microsoft - the only time I can say I was in the room with Willy
G. - but that's another story)​.  This work would become the System III
license.

​Xenix, which was V7 based originally, was target for the generic 8086
systems (as well as PDP-11, 68K and Z8000) but the Intel support was
generic so it included the PC.   The bigger problem is that it really
wanted a hard disk, which made its target a 'high end' computer in those
days.  Running on a floppy was sort of possible (besides slow, it tended to
wear out the oxide in the center of the disk where the superblock and
i-list was storied from all r/w - I used to have an 8" floppy sans case
hanging in my office).

But that said, the V7 based license was terrible for a 'small value system'
and I'm not sure Microsoft shipped much against it.   That was the primary
reason they wanted to a new license [Gate's line at the time: 'You guys
don't get it.  The only thing that matters is volume.'].   So until the
System III license, which is what Xenix 2.0 and later shipped, I don't
think Microsoft really had much presence.  But at that time, Microsoft [via
Bob Greenburg a founder and the only one of Gates roommates at Harvard to
graduate btw] was trying to a UNIX porting house, similar to HCR.   That
had been the original vision of Xenix, they would OEM the SW to other firms
that build HW, just like they did for BASIC and were beginning to do for
FORTRAN and COBOL.

As you point out, other firms such as ISC, HCR and Locus appeared on the
scene as more UNIX knowledgeable.   I also think IBM already had placed big
bets on Microsoft for DOS and BASIC, so they wanted to spread the risk a
little which is why ISC got the original UNIX for the PC HW deal.   Once
Microsoft had Xenix stable, IBM was already their customer so selling Xenix
on IBM was a secondary issue.

For a little more on the history front; my former boss, Phill Shevrin, who
would later switch from ISC to Locus where I worked for him, pulled what I
always thought was one of the great tricks of salesmanship in the UNIX
business.  When he was at ISC, he sold for $1.5M a 'port' to the 386 of
System III to each of IBM, AT&T and Intel.   He got paid three times for
same work and got to sell the result as their own product when they were
done.

Also, from a historical standpoint, I hope we do have the ISC 386 code base
- that was the first of the 32-bit linear UNIX ports for the x86 systems.
The other thing that we should try to find is the Phoenix Tech VP/IX code
base and the Locus Merge Code base.   These were the first VM/hypervisors.
They ran in PC/IX 386 and allowed Windows to run under it, long before
VMware existed.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171206/8a5d8fb6/attachment.html>


  reply	other threads:[~2017-12-06 17:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.400.1512518427.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:25 ` Paul Ruizendaal
2017-12-06 12:58   ` Mutiny 
2017-12-06 14:33     ` Paul Ruizendaal
2017-12-06 17:13       ` Clem Cole [this message]
2017-12-06 19:27         ` Paul Ruizendaal
2017-12-07  6:14         ` Jason Stevens
2017-12-06 22:32       ` Dave Horsfall
2017-12-07  5:05         ` Jason Stevens
2017-12-07  5:46           ` Dave Horsfall
2017-12-07  5:40         ` Andy Kosela
2017-12-07  5:56         ` Robert Brockway
2017-12-07  6:07           ` Warner Losh
2017-12-07 17:47             ` Grant Taylor
2017-12-09  6:03               ` Nigel Williams
2017-12-07  6:14           ` Jon Steinhart
2017-12-07  7:02             ` Robert Brockway
2017-12-07 16:22               ` Jon Steinhart
2017-12-07 14:59             ` Larry McVoy
2017-12-07 15:40               ` Steve Simon
2017-12-07 15:42               ` Chet Ramey
2017-12-07 16:28             ` Clem Cole
2017-12-07 16:30               ` Clem Cole
2017-12-06 17:55   ` Warner Losh
2017-12-07 15:14 Noel Chiappa
2017-12-07 15:36 ` Nevin Liber
  -- strict thread matches above, loose matches on Subject: below --
2017-12-06 17:59 Rudi Blom
     [not found] <mailman.398.1512513526.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:22 ` Paul Ruizendaal
2017-12-05 22:45 Nelson H. F. Beebe
2017-12-05 22:21 Warren Toomey
2017-12-05 22:38 ` Robert Swierczek
2017-12-05 22:55 ` Angelo Papenhoff
2017-12-05 23:06   ` Warner Losh
2017-12-05 23:03 ` Dave Horsfall
2017-12-06  0:00 ` Robert Swierczek
2017-12-06  0:08   ` Grant Taylor
2017-12-06 15:23   ` Clem Cole
2017-12-06  5:54 ` arnold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC20D2Mt42f0P7XYvsNSAJm76T=wvaNsc4Rd7LTxRby6WGfn0A@mail.gmail.com' \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).