From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] NetBSD 0.8
Date: Fri, 19 Nov 2010 00:26:30 +0100 [thread overview]
Message-ID: <ed3d052bd2c629a2589c30c16ab89bde.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <AANLkTimuwh=V4=1pqnAaoCMzh7ETJUdocqMjroB98_9U@mail.gmail.com>
> I don't suppose anyone has this kicking around,
The closest I ever got to erecting a tomb stone in the form of an
emulator image for the fallen Net/2 derived recompilable operating
environments is a fully patched up 386BSD 0.1.
I can't get 386BSD 1.0 to rebuild itself yet, hence the Moby Dick quote
on gunkies.org for that release. Probably you and I are the only ones
who give 2 GB and those who can have a last name ending in olitz.
Would love to get my hands on NetBSD 0.8/0.9. I assume the USL v UB
settlement resulted in pressure to get them purged. In lieu of the
distribution any good storys on how that went down?
/Jacob
next prev parent reply other threads:[~2010-11-18 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 0:15 Jason Stevens
2010-11-18 23:26 ` Jacob Goense [this message]
[not found] <mailman.1.1289959202.23203.tuhs@minnie.tuhs.org>
2010-12-02 15:16 ` Johnny Billquist
2010-12-02 15:26 ` Jason Stevens
2010-12-02 18:46 ` Johnny Billquist
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=ed3d052bd2c629a2589c30c16ab89bde.squirrel@webmail.xs4all.nl \
--to=dugo@xs4all.nl \
/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).