From: chet.ramey@case.edu (Chet Ramey)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 12:06:20 -0500 [thread overview]
Message-ID: <8c534c33-349d-3c3c-ebaf-eccf49928784@case.edu> (raw)
In-Reply-To: <CAC20D2N74KiRfBzmiGmvyHTgaaMQfPd9QBYc_iUt6nCz7wdA3A@mail.gmail.com>
On 2/22/17 12:00 PM, Clem Cole wrote:
> But you are right .. no one was really sure what was going to happen. So
> the BSD/386 iso's were hidden, so at least officially they could say the
> only people that we supposed to have access were the BSD licensees. But
> as I say it was a well known "secret."
This has very much the aura of a private club. If you were in the club,
the secret was well known, but most of the people who went to Linux and
supported its growth were not.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet at case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2017-02-22 17:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 3:38 Clem Cole
2017-02-22 4:28 ` Dan Cross
2017-02-22 15:36 ` Clem Cole
2017-02-22 16:11 ` Larry McVoy
2017-02-22 17:00 ` Clem Cole
2017-02-22 17:06 ` Chet Ramey [this message]
2017-02-22 18:24 ` Larry McVoy
2017-02-22 19:35 ` Clem Cole
2017-02-22 20:18 ` arnold
2017-02-22 22:11 ` Clem Cole
2017-02-22 21:34 ` Larry McVoy
2017-02-22 22:56 ` Clem Cole
2017-02-22 23:13 ` Larry McVoy
2017-02-22 23:51 ` Clem Cole
2017-02-22 23:51 ` Paul Ruizendaal
2017-02-23 19:15 ` Clem Cole
2017-02-23 20:31 ` Random832
2017-02-23 22:48 ` Joerg Schilling
2017-02-24 2:07 ` Jason Stevens
2017-02-23 23:06 ` Wesley Parish
2017-02-22 17:41 ` Arthur Krewat
2017-02-22 21:00 ` Michael Kerpan
2017-02-22 22:03 ` Arno Griffioen
2017-02-22 22:51 ` Larry McVoy
2017-02-22 23:29 ` Clem Cole
2017-02-23 4:53 ` Gregg Levine
2017-02-22 22:18 ` Clem Cole
2017-02-24 3:53 ` Dan Cross
2017-02-22 5:56 ` Steve Nickolas
2017-02-24 5:31 ` John Labovitz
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=8c534c33-349d-3c3c-ebaf-eccf49928784@case.edu \
--to=chet.ramey@case.edu \
/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).