From: don@DonHopkins.com (Don Hopkins)
Subject: Favorite UNIX
Date: Mon, 2 Oct 2017 01:28:09 +0200 [thread overview]
Message-ID: <F01BFED4-3E46-4FCB-B1FF-057A836E60AA@gmail.com> (raw)
In-Reply-To: <201710012121.v91LLKHK004998@darkstar.fourwinds.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
The term I heard to describe Unix USL was “Turkey Farm”. And there was something about “Stewing in their own juices for too long”. Sounds delicious!
-Don
> On 1 Oct 2017, at 23:21, Jon Steinhart <jon at fourwinds.com> wrote:
>
> Steve Mynott writes:
>> On 1 October 2017 at 18:51, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
>>
>>> Why was Solaris so much worse than SunOS?
>>
>> Probably because it was so much more buggy on release and people were
>> more used to BSD and didn't like change and the fact that greedy Sun
>> had removed the compiler. Solaris 2.3 had core dumps from base
>> binaries everywhere where SunOS 4.1.3 seemed quite stable.
>
> I think that the root cause is AT&T USL. When UNIX went from research
> to "product" different people worked on it. And those people seemed to
> lack the artistry, vision, and craftsmanship of the original developers.
> AT&T pushed their SVR4 crud hard onto the rest of the world. Meanwhile,
> the folks at Berkeley produced code more in the original tradition
> possibly because of Ken taking a sabbatical year to teach there. SunOS
> was the result of the pipeline between Berkeley and Sun.
>
> Solaris was the result of Sun abandoning the Berkeley branch for the USL
> branch.
next prev parent reply other threads:[~2017-10-01 23:28 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
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 [this message]
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=F01BFED4-3E46-4FCB-B1FF-057A836E60AA@gmail.com \
--to=don@donhopkins.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).