From: risner@stdio.com
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 386BSD released
Date: Thu, 15 Jul 2021 22:33:52 -0400 [thread overview]
Message-ID: <5777F7E6-062B-4C5A-9C98-36FFE6AC3414@stdio.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2107161127480.32008@aneurin.horsfall.org>
I was running 386BSD 0.0 on a 386 40 mhz machine in April 1992 with 32
mb of ram.
There was much instability in the OS with more than 8 gb of ram and I
mailed 32 mb of extra to the Jolitz late summer to the fall.
I never heard about Linux until much later in 1993.
There used to be a post on usenet news annoucing the relase with the
FTP, but the best I could google was this FAQ confirming release in
1992.
https://groups.google.com/g/comp.os.386bsd.announce/c/PGltboD6rq4
I have repetively seen discussion suggesting Linux was available first,
but having directly worked for a university at the time installing
SunOS, AT&T SVR3, and other old OS’s, we welcomed the concept of
switching from AT&T SVR3 on 386 machines to 386BSD. We’d probably have
welcomed Linux if anyone in the department knew about it.
James Risner
On 15 Jul 2021, at 21:35, Dave Horsfall wrote:
> On Wed, 14 Jul 2021, Michael Kjörling wrote:
>
>>> In 1992, 386BSD is released by Lynne and William Jolitz, starting
>>> the open source operating system movement (Linux didn't come along
>>> under later).
>>
>> Are you sure? Wikipedia claims that it happened the other way around;
>> that the Linux kernel initial release was 0.02 on 5 Oct 1991, while
>> the 386BSD initial release was 0.0 on 12 March 1992.
>
> Could be; I got that news from one of those daily history sites (I
> don't always trust Wikipedia).
>
>> It seems that work on 386BSD began earlier than work on Linux, but
>> that the initial release of Linux was earlier than the initial
>> release of 386BSD.
>
> That could be the source of the confusion.
>
> -- Dave
next prev parent reply other threads:[~2021-07-16 2:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 22:28 Dave Horsfall
2021-07-14 7:54 ` Michael Kjörling
2021-07-14 8:19 ` Angus Robinson
2021-07-14 8:32 ` Michael Kjörling
2021-07-14 9:07 ` Lars Brinkhoff
2021-07-14 14:09 ` Larry McVoy
2021-07-14 14:54 ` Warner Losh
2021-07-14 15:06 ` Richard Salz
2021-07-14 15:37 ` Steve Nickolas
2021-07-14 10:09 ` Tom Ivar Helbekkmo via TUHS
2021-07-14 10:39 ` arnold
2021-07-14 17:21 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-14 17:32 ` Richard Salz
2021-07-14 15:01 ` Clem Cole
2021-07-14 17:40 ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-14 17:50 ` Larry McVoy
2021-07-14 18:28 ` Clem Cole
2021-07-14 11:49 ` [TUHS] " Andy Kosela
2021-07-14 15:48 ` Theodore Y. Ts'o
2021-07-16 1:35 ` Dave Horsfall
2021-07-16 2:33 ` risner [this message]
2021-07-16 4:25 ` Theodore Y. Ts'o
2021-07-16 5:51 ` Bakul Shah
2021-07-16 13:00 ` Theodore Y. Ts'o
2021-07-16 13:56 ` Larry McVoy
2021-07-16 14:40 ` Clem Cole
2021-07-16 15:44 ` Theodore Y. Ts'o
2021-07-16 16:11 ` Bakul Shah
2021-07-16 19:07 ` Kevin Bowling
2021-07-16 20:17 ` Clem Cole
2021-07-16 20:24 ` Richard Salz
2021-07-18 13:13 ` arnold
2021-07-18 13:23 ` Richard Salz
2021-07-18 13:43 ` [TUHS] MtXinu calendar (was Re: 386BSD released) Al Kossow
2021-07-18 13:51 ` Al Kossow
2021-07-18 16:44 ` Al Kossow
2021-07-18 17:38 ` John Cowan
2021-07-18 18:35 ` Bakul Shah
2021-07-19 3:06 ` Dan Stromberg
2021-07-18 19:00 ` arnold
2021-07-18 21:48 ` Deborah Scherrer
2021-07-18 20:06 ` Lyle Bickley
2021-07-14 21:37 ` [TUHS] 386BSD released Bakul Shah
2021-07-16 21:22 ` Dave Horsfall
2021-07-15 2:21 Douglas McIlroy
2021-07-15 2:41 ` Adam Thornton
2021-07-15 15:07 ` Clem Cole
2021-07-16 17:30 Nelson H. F. Beebe
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=5777F7E6-062B-4C5A-9C98-36FFE6AC3414@stdio.com \
--to=risner@stdio.com \
--cc=dave@horsfall.org \
--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).