From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] BSD/386 and its ilk
Date: Sat, 5 Jul 2008 17:44:45 +1000 [thread overview]
Message-ID: <20080705074445.GA77107@dereel.lemis.com> (raw)
In-Reply-To: <200807051828.52614.wes.parish@paradise.net.nz>
On Saturday, 5 July 2008 at 18:28:51 +1200, Wesley Parish wrote:
> Hi.
>
> I'm reading TCP/IP Illustrated - for the first time; talk about slack! - and
> noticed Stevens used BSD/386. I remember seeing in DDJ in the early '90s ads
> for various software-plus-source from a Texas repackaging company, and they
> had BSD/[386|i|OS] at various times for $1k.00.
>
> That was then - this is now. Is it likely, or even possible, that BSDi the
> company would be ready to consider BSD/386 and such early releases, legacy
> that could be donated to TUHS? And if so, who should we contact, to ask?
Well, definitely not BSDI, who closed down about 5 years ago. But you
could try Wind River Systems, who bought them out before closing them
down.
It's not impossible; I have a complete BSD/OS 5.x tree somewhere which
was given to me during my work on the FreeBSD SMPng project, which
based on code from BSD/OS. I'm not at liberty to distribute it,
unfortunately, but the impression I got at the time (2000) was that it
wouldn't be too difficult to get code if you had a reason.
Greg
--
Finger grog at Freebsd.org for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20080705/da3d6334/attachment.sig>
prev parent reply other threads:[~2008-07-05 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 6:28 Wesley Parish
2008-07-05 7:44 ` Greg 'groggy' Lehey [this message]
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=20080705074445.GA77107@dereel.lemis.com \
--to=grog@lemis.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).