From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] NetBSD 0.8/0.9
Date: Fri, 3 Dec 2010 13:10:47 +0100 [thread overview]
Message-ID: <cd8b98f0028b2465fcbb5acfb556aa35.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <AANLkTikDXeXeYNrgpRmWcW1TuzQGS_Qf8_vQSK7O0d81@mail.gmail.com>
> This is by no means complete.....
> Although we do have kern_exit.c from NetBSD 0.9 and from 386BSD 0.0 pl24
> I'll have to mash things around to see what happens... I didn't get a
> chance yesterday with some great white north type nation blocking
> ipsec.........
[snip list of missing 0.8 source files]
You mean 386BSD 0.1 pl24 right, that, 0.9, the Net/2 tarball and the CVS
comments might help in rebuilding something resembling NetBSD 0.8.
Sounds a bit like back breeding extinct species ;)
/Jacob
next prev parent reply other threads:[~2010-12-03 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1291341601.16646.tuhs@minnie.tuhs.org>
2010-12-03 10:28 ` [TUHS] NetBSD 0.9 Johnny Billquist
2010-12-03 11:14 ` Jason Stevens
2010-12-03 12:10 ` Jacob Goense [this message]
2010-12-03 12:49 ` [TUHS] NetBSD 0.8/0.9 Johnny Billquist
2010-12-03 13:28 ` Jason Stevens
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=cd8b98f0028b2465fcbb5acfb556aa35.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).