The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck')
Date: Mon, 2 Jun 2014 10:25:58 -0400	[thread overview]
Message-ID: <CAC20D2OpxV611CAuXtkZg_cxJX5o5yCq=PXh72mL_QVk+EGOWQ@mail.gmail.com> (raw)
In-Reply-To: <59D01DBF-EF49-45B8-8F80-FA03E644A528@tfeb.org>

Tim - cart and horse reversed.. ;-)

Linus did not like the fact the when Andy wrote Minux, he and his students
did not use the 386 MMU HW.   It was made to run on a 8086/8088 -- straight
PC/XT  because Andy wanted the lowest cost of entry for his students.
Also at the time, Andy's compiler tool kit was not as easy to get the
source.

My memory on this part is hazy, but I think you had to purchase the
compiler sources.   So  Linus started with MINUX and started to add more
and more support.   He eventually tossed out the ukernel nature of Minux
and went the more traditional kernel architecture.    He and Andy would
famously fight about that choice on usenet.

Linus this would eventually need a compiler and pulled rms' suite.


The funny part is that his University has 386BSD (aka 4.2 for the 386) at
the time which did use the MMU, had networking and even the first step at
X11.  At the time I had helped the guys get the AT disk driver working as I
had access to all the Western Digital documentation.   But to get the code
from CRSG, you needed at BSD license, which required an AT&T license.
Linus' university had one, but he did know know the magic ftp site to
download or have access.

I've often wondered what would have happened if he had known about it.

And again, fast forward about 18-24 months and folks like me were worried
when the BSDi case came out that we were going to lose access to a UNIX for
the Intel processor.   So we started to help him, even though at the time
is a huge step backwards.

Clearly, the "powers" at AT&T really did not know they were awaking a
sleeping animal in the hacker community.

Clem


On Mon, Jun 2, 2014 at 10:11 AM, Tim Bradshaw <tfb at tfeb.org> wrote:

>
> On 2 Jun 2014, at 14:28, Clem Cole <clemc at ccc.com> wrote:
>
> [About gcc]
>
> But the command suite was able to grow and lots of people besides rms
> contribute to it, because the basic development tools were there.   As
> strange and difficult a person he is, I suspect we do all own rms a certain
> level of thanks for the basic dev tools.
>
>
> In particular I think the existence of GCC was critical to the existence
> of Linux: there is some complicated history involving a GCC port to
> ?Minix?, which I think was done because Minix's compiler was rudimentary,
> and that port enabling some Finnish guy (using Minix I guess) to bring up a
> kernel.  I suspect there are people on this list who remember this better
> than I do though.
>
> --tim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140602/1d034672/attachment.html>


  reply	other threads:[~2014-06-02 14:25 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  2:09 Doug McIlroy
2014-06-02  2:24 ` John Cowan
2014-06-02  2:59 ` Warner Losh
2014-06-02  3:17   ` Greg 'groggy' Lehey
2014-06-02  3:37     ` John Cowan
2014-06-02  4:08       ` scj
2014-06-02  5:03       ` Greg 'groggy' Lehey
2014-06-02 12:31         ` Ronald Natalie
2014-06-02  4:04     ` Nick Downing
2014-06-02  4:43       ` John Cowan
2014-06-02  6:23         ` arnold
2014-06-02 17:35           ` John Cowan
2014-06-02 18:44             ` Warner Losh
2014-06-02 18:52               ` John Cowan
2014-06-02  3:18   ` John Cowan
2014-06-02  6:08   ` Steve Nickolas
2014-06-02 12:04 ` Clem Cole
2014-06-02 12:27   ` Ronald Natalie
2014-06-02 13:28     ` Clem Cole
2014-06-02 14:11       ` Tim Bradshaw
2014-06-02 14:25         ` Clem Cole [this message]
2014-06-02 14:41           ` John Cowan
2014-06-02 14:50             ` Armando Stettner
2014-06-02 18:27               ` Brantley Coile
2014-06-02 18:52                 ` Dan Cross
2014-06-02 19:10                   ` arnold
2014-06-03  1:45                     ` Brantley Coile
2014-06-02 19:30                   ` John Cowan
2014-06-02 19:54                     ` Dan Cross
2014-06-02 23:37                       ` John Cowan
2014-06-03  1:24                         ` Dan Cross
2014-06-03  2:16                           ` John Cowan
2014-06-03  2:18                             ` Dan Cross
2014-06-02 19:47                   ` Chris Nehren
2014-06-02 20:23                     ` Dan Cross
2014-06-03 18:48                       ` [TUHS] Evolutionary Paths (was Gnu/Stallman (was Bugs in V6 'dcheck')) scj
2014-06-04  1:10                         ` Larry McVoy
2014-06-04  3:42                           ` Greg Chesson
2014-06-05  0:43                             ` Larry McVoy
2014-06-02 21:08                   ` [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck') Charlie Kester
2014-06-03  0:37                   ` Tim Newsham
2014-06-02 20:06           ` Jacob Goense
2014-06-02 14:26         ` arnold
2014-06-02 14:30       ` John Cowan
2014-06-02 14:24     ` John Cowan
2014-06-02 14:29       ` Ronald Natalie
2014-06-02 14:37       ` Clem Cole
2014-06-05  7:31       ` Arno Griffioen
2014-06-05  8:24         ` emu
2014-06-05  9:17         ` Wesley Parish
2014-06-05 11:26           ` Brantley Coile
2014-06-05 13:34             ` Jesus Cea
2014-06-11 12:10           ` Michael Parson
2014-06-12  1:20             ` Wesley Parish
2014-06-05 15:07         ` Clem Cole
2014-06-05 18:26           ` Ronald Natalie

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='CAC20D2OpxV611CAuXtkZg_cxJX5o5yCq=PXh72mL_QVk+EGOWQ@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).