The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: Favorite UNIX
Date: Sun, 1 Oct 2017 11:05:00 -0700	[thread overview]
Message-ID: <20171001180500.GD16755@mcvoy.com> (raw)
In-Reply-To: <20171001175106.5FE3318C0A6@mercury.lcs.mit.edu>

On Sun, Oct 01, 2017 at 01:51:06PM -0400, Noel Chiappa wrote:
>     > From: Don Hopkins
>     
>     > Solaris: so bad I left the company.
> 
> Why was Solaris so much worse than SunOS?

Because SunOS had years of polish.  It was a nicer starting point (BSD
had all the fun stuff, AT&T was sort of a stuffed shirt's Unix, BSD was
Unix for hackers) and the engineers who polished it did so because they
loved it.  Lots of us stayed late into the night working on that OS and
it showed.  It was fun times, McNealy knew we were working on it and he'd
come over to the kernel team's building and egg us on.  He'd get up on
the conference table and preach to us how it was going to rule the world.

> I guess the Sun management didn't understand that was the case? Or were they
> so hot for the AT+T linkup that they were willing to live with it?

No, the deal was that Sun needed money and AT&T bought $200M of Sun stock
at 35% over market.  In exchange, Sun agreed to take SVR4 and make it
popular.   At&T wanted SVR4 to be the next SunOS.

But that was a kick in the nuts to us engineers.  The sytem v source base
was crap compared to sunos, a huge step backwards.

So my crowd pretty much all left in disgust.  There was a lot of heartache
over it.  None of us knew about the business deal at the time, in fact I
think a lot of management didn't know.

I pushed for a free version of SunOS 4.x.  I removed the STREAMS code and
the drivers because that wasn't free; put back the BSD tty drivers and
I had an unencumbered source base.  I demo-ed it.  My boss, Ken Okin,
VP of server hardware, paid me to argue for that for 6 months (which is
why I say I don't think management knew about the deal; Ken was a senior
dude, he wouldn't have sent me off if he knew for sure I was going to 
fail).

I wrote a paper arguing for this:

http://www.mcvoy.com/lm/bitmover/lm/papers/freeos.pdf

but it never happened.  We'd all be running SunOS today if they had done
that.

Instead, they repeated the SunOS journey.  Bryan and crew polished that
turd for years and got it sort of reasonable.  Some people grew to like
it, I never did.  Too system v-ish for my tastes.  You have to install
the GNU tools to have a reasonable tool chain, they never fixed the
default tools.  That's crazy, why ship them and maintain them if you
aren't using them?  Solaris has always felt weird to me, but they went
for it and got it better.  Only to have it tossed away again.  Yuck.


  reply	other threads:[~2017-10-01 18:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 17:51 Noel Chiappa
2017-10-01 18:05 ` Larry McVoy [this message]
2017-10-01 18:39   ` Don Hopkins
2017-10-02  8:44   ` jason-tuhs
2017-10-02 11:52     ` Kevin Bowling
2017-10-02 14:17     ` Warner Losh
2017-10-01 18:13 ` Don Hopkins
2017-10-01 20:15 ` Steve Mynott
2017-10-01 21:21   ` Jon Steinhart
2017-10-01 23:28     ` Don Hopkins
2017-10-02  0:36     ` Larry McVoy
     [not found] <mailman.1424.1506881102.3779.tuhs@minnie.tuhs.org>
2017-10-01 19:09 ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2017-09-29  2:58 [TUHS] " Kevin Bowling
2017-09-30 15:40 ` Michael Parson
2017-09-30 17:53   ` Ian Zimmerman
2017-09-30 18:34     ` Michael Parson
2017-09-30 18:45       ` Arthur Krewat
2017-10-01  0:36       ` Larry McVoy
2017-10-01  0:51         ` Dave Horsfall
2017-10-01  1:10           ` Larry McVoy
2017-10-01  1:13             ` Cory Smelosky
2017-10-01  3:43             ` Arthur Krewat
2017-10-01 14:07             ` Don Hopkins
2017-10-01  3:05       ` Michael Parson
2017-10-01  3:15         ` Kevin Bowling
     [not found]       ` <201710011513.v91FDSMB011831@freefriends.org>
2017-10-01 19:35         ` Michael Parson

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=20171001180500.GD16755@mcvoy.com \
    --to=lm@mcvoy.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).