From: "Jeremy C. Reed" <reed@reedmedia.net>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 2.9BSD-Seismo
Date: Fri, 19 Jun 2020 14:50:37 -0500 (CDT) [thread overview]
Message-ID: <alpine.NEB.2.21.2006191439550.11704@t1.m.reedmedia.net> (raw)
In-Reply-To: <CANCZdfqA9_X-RmY5bK91-ai5ztDFWzG5SHmS-odP8iWDwMT-rw@mail.gmail.com>
On Thu, 18 Jun 2020, Warner Losh wrote:
> So in BSD family tree, there's a 2.9BSD-Seismo and a 2.9.1BSD listed.
> Yet I can't seem to find them in the TUHS archive.
>
> There is a 2.9-Patch directory dated 1985 the same as the date that's found
> in the family tree. Is that the Seismo version?
2.9-Patch appears to the Seismo version -- Harvard/CSS (Center for
Seismic Studies) release from Bostic. (It is not a diff file but is a
tarball.) See the README and GOTCHA files.
And see https://www.krsaborio.net/bsd/research/1985/0831.htm I don't
know if the URL will change as it was elsewhere before.)
prev parent reply other threads:[~2020-06-19 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 1:50 Warner Losh
2020-06-19 1:59 ` Larry McVoy
2020-06-19 19:50 ` Jeremy C. Reed [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=alpine.NEB.2.21.2006191439550.11704@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=imp@bsdimp.com \
--cc=tuhs@minnie.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).