From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Greg 'groggy' Lehey <grog@lemis.com>, Larry McVoy <lm@mcvoy.com>
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Early Linux and BSD (was: On the origins of Linux - "an academic question")
Date: Sat, 18 Jan 2020 15:35:40 +0000 (UTC) [thread overview]
Message-ID: <25E62EB5E090E7CB.0e52e059-5d83-4d31-98f4-bb2d82ede4f8@mail.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
I would imagine that the user land changes made its way into 386 Mach. Although I haven't seen anything I can recall off the top of my head about 386 commits in user land until much later.
Maybe one day more of that Mt Xinu stuff will surface, although I'm still amazed I got the kernel to build.
Internet legend is that the rift was massive.
From: TUHS <tuhs-bounces@minnie.tuhs.org> on behalf of Larry McVoy <lm@mcvoy.com>
Sent: Sunday, January 19, 2020, 12:26 a.m.
To: Greg 'groggy' Lehey
Cc: UNIX Heritage Society
Subject: Re: [TUHS] Early Linux and BSD (was: On the origins of Linux - "an academic question")
On Sat, Jan 18, 2020 at 03:19:13PM +1100, Greg 'groggy' Lehey wrote:
> On Friday, 17 January 2020 at 22:50:51 -0500, Theodore Y. Ts'o wrote:
> >
> > In the super-early days (late 1991, early 1992), those of us who
> > worked on it just wanted a "something Unix-like" that we could run at
> > home (my first computer was a 40 MHz 386 with 16 MB of memory). This
> > was before the AT&T/BSD Lawsuit (which was in 1992) and while Jolitz
> > may have been demonstrating 386BSD in private, I was certainly never
> > aware of it
>
> At the start of this time, Bill was working for BSDI, who were
> preparing a commercial product that (in March 1992) became BSD/386.
Wikipedia says he was working on 386BSD as early has 1989 and that
clicks with me (Jolitz worked for me around 1992 or 3). I don't
remember him mentioning working at BSDI, are you sure about that
part? Those guys did not like each other at all.
[-- Attachment #2: Type: text/html, Size: 2475 bytes --]
next reply other threads:[~2020-01-18 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 15:35 Jason Stevens [this message]
2020-01-18 15:49 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2020-01-19 16:05 Noel Chiappa
2020-01-19 14:17 Noel Chiappa
2020-01-19 20:49 ` Nemo Nusquam
2020-01-17 16:01 [TUHS] On the origins of Linux - "an academic question" Arrigo Triulzi
2020-01-17 19:59 ` Arno Griffioen
2020-01-18 3:50 ` Theodore Y. Ts'o
2020-01-18 4:19 ` [TUHS] Early Linux and BSD (was: On the origins of Linux - "an academic question") Greg 'groggy' Lehey
2020-01-18 15:25 ` Larry McVoy
2020-01-18 16:19 ` reed
2020-01-19 2:49 ` Theodore Y. Ts'o
2020-01-19 3:12 ` Greg 'groggy' Lehey
2020-01-19 3:58 ` Greg 'groggy' Lehey
2020-01-19 13:25 ` Theodore Y. Ts'o
2020-01-19 13:48 ` Clem Cole
2020-01-20 3:32 ` Greg A. Woods
2020-01-20 3:51 ` George Michaelson
2020-01-20 17:19 ` Clem Cole
2020-01-20 17:49 ` Warner Losh
2020-01-20 19:00 ` Clem Cole
2020-01-20 18:04 ` Larry McVoy
2020-01-20 18:09 ` David Barto
2020-01-20 19:18 ` Clem Cole
2020-01-20 19:46 ` Jon Steinhart
2020-01-20 20:15 ` Clem Cole
2020-01-22 0:14 ` Greg A. Woods
2020-01-21 0:44 ` Bakul Shah
2020-01-20 19:09 ` Theodore Y. Ts'o
2020-01-20 19:51 ` Clem Cole
2020-01-20 23:04 ` Greg A. Woods
2020-01-21 0:13 ` Warner Losh
2020-01-21 23:45 ` Greg A. Woods
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=25E62EB5E090E7CB.0e52e059-5d83-4d31-98f4-bb2d82ede4f8@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=grog@lemis.com \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.org \
/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).