From: Greg 'groggy' Lehey <grog@lemis.com>
To: Steve Mynott <steve.mynott@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BSDI git repo?
Date: Sat, 1 Aug 2020 10:12:07 +1000 [thread overview]
Message-ID: <20200801001207.GT1032@eureka.lemis.com> (raw)
In-Reply-To: <CANuZA8R--kw-DUgGGaByY1QpJqpipRLX1uhXfugCxSESgHgcEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
On Friday, 31 July 2020 at 10:05:55 +0100, Steve Mynott wrote:
> Is there full bsdi git repo anywhere?
>
> I've vague recollections parts were merged into FreeBSD in the early
> 2000s so I assume it was open sourced?
From June to September 2000 (exactly 20 years ago) I merged some parts
of BSD/OS 5.0 into FreeBSD version 4, releasing it as FreeBSD 5.0.
This was part of an agreement (obviously) with BSDI to improve
FreeBSD's SMP processing.
For this purpose I received three source trees, labeled 4.1-RELEASE,
4.1 and 5.0-smp-devel. I still have them, and as far as I can see
they're complete.
Clearly they weren't maintained under git, since it didn't exist yet.
The headers suggest RCS or (probably) CVS. For example:
* BSDI exec_elf.c,v 1.7 1998/08/24 19:03:08 torek Exp
* BSDI kern_fork.c,v 2.10 1999/04/20 22:40:19 cp Exp
None of this was "open sourced"; we were allowed to use it for this
specific purpose. But if you can get approval from the copyright
owners, I'll happily give you a copy.
You might also be interested in my report of the meeting which set
this off, at http://www.lemis.com/grog/diary-jun2000.php#15
In passing, it was an interesting experience. Both BSD/OS and FreeBSD
derived from (most recently) 4.4BSD Lite, but they had diverged to a
point where it was really painful to merge the code.
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2020-08-01 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:05 Steve Mynott
2020-08-01 0:12 ` 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=20200801001207.GT1032@eureka.lemis.com \
--to=grog@lemis.com \
--cc=steve.mynott@gmail.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).