The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Dave Horsfall <dave@horsfall.org>, Greg 'groggy' Lehey <grog@lemis.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday, 386BSD!
Date: Wed, 17 Jul 2019 00:38:46 +0000	[thread overview]
Message-ID: <ADFDF14544A65F35.77affc7d-ee11-4fc2-9e54-2d388dcea179@mail.outlook.com> (raw)
In-Reply-To: <20190714062312.GA50604@eureka.lemis.com>

[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]

I dug out my booting copy of 0.0




https://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/386BSD-0.0-with-bochs.7z/download




It runs under bochs.  It's very rough back then, it doesn't run in multiuser, and it's missing a bunch of stuff, making it as distributed impossible to self host.  I had to add in the net2 userland stuff myself to build the kernel, although that isn't in this dump. 




After booting you have to run :




fsck -p


mount -a


update


/etc/netstart




There is no nvi/vi instead elvis is supplied. Naturally many were dismissive of 0.0 as it barely ran. In the months that followed 0.1 was much more complete even running in multi user!  The real magic was in the patch kits, culminating in #24 if I'm remembering it right, which was then followed up with the schisim and NetBSD 0.8, which is really just 386BSD with all the patches applied... That version was impossible to track down, and oddly enough surfaced after I managed to rebuild it by filling in parts from the source control and a bit of work. 




It's a little late for 'on this day' type thing but it's not lost to the winds of time. 






From: Greg 'groggy' Lehey


Sent: Sunday, July 14, 2:24 PM


Subject: Re: [TUHS] Happy birthday, 386BSD!


To: Dave Horsfall


Cc: The Eunuchs Hysterical Society






On Sunday, 14 July 2019 at 16:15:44 +1000, Greg 'groggy' Lehey wrote: > On Sunday, 14 July 2019 at 15:56:21 +1000, Dave Horsfall wrote: >> 386BSD was released on this day in 1992, when William and Lynne Jolitz >> started the Open Source movement; well, that's what my notes say, and >> corrections are welcome (I know that Gilmore likes to take credit for just >> about everything). > > Yes, I recall a release on the French national holiday, with specific > reference to that event, Here we go (http://gunkies.org/wiki/386BSD_0.1_announcement): 386BSD Release 0.1 "Cut the Tape" 14 July 1992 (Bastille Day) "Vive la Revolution" Greg -- Sent from my desktop computer. Finger grog@lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA 





[-- Attachment #2: Type: text/html, Size: 4562 bytes --]

  reply	other threads:[~2019-07-17  0:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14  5:56 Dave Horsfall
2019-07-14  6:01 ` Larry McVoy
2019-07-14  7:15   ` Ed Carp
2019-07-14  8:14     ` Jason Stevens
2019-07-14  6:15 ` Greg 'groggy' Lehey
2019-07-14  6:23   ` Greg 'groggy' Lehey
2019-07-17  0:38     ` Jason Stevens [this message]
2019-07-14  6:53 ` Jason Stevens
2019-07-14  8:17   ` [TUHS] Thanks for Virtuallyfun! (was Re: Happy birthday, 386BSD!) Michael Huff
2019-07-14  9:07     ` Jason Stevens
2019-07-14 17:47       ` Adam Thornton
2019-07-15  1:54         ` Jason Stevens
2019-07-14  7:13 ` [TUHS] Happy birthday, 386BSD! Ed Carp
2019-07-14 12:52   ` Theodore Ts'o

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=ADFDF14544A65F35.77affc7d-ee11-4fc2-9e54-2d388dcea179@mail.outlook.com \
    --to=jsteve@superglobalmegacorp.com \
    --cc=dave@horsfall.org \
    --cc=grog@lemis.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).