From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Free/NetBSD revision history (was Code bloat)
Date: Thu, 9 Feb 2017 21:11:19 -0700 [thread overview]
Message-ID: <CANCZdfqGSwNfO+r4OZsae0dX-7zQC98SboTG8uFPsza-EsgU5g@mail.gmail.com> (raw)
In-Reply-To: <59edd244efc6fca1609f5707dd39833e@xs4all.nl>
On Thu, Feb 9, 2017 at 4:38 PM, Jacob Goense <dugo at xs4all.nl> wrote:
> On 2017-02-09 11:14, Warner Losh wrote:
>>
>> I thought someone had posted a github project to merge the history of
>> all publicly available sources of unix.
>
>
> That's the thing, it banks on what is publicly available.
>
> NetBSD and FreeBSD both started out from 386BSD + patchkits. They threw
> it is cvs, and engineered a release.
>
> This was all, in essence, Net/2 based, then the USL vs. BSDi lawsuit
> kicked in and was settled by a.o. "encumbering" Net/2 by agreement.
>
> Panic ensued and the NetBSD and FreeBSD teams took a chainsaw against
> what they had released until then.
That was actually part of the agreement with AT&T to end the hostilities.
NetBSD did it by butchery. FreeBSD did it by reimporting from 4.4lite,
basically (the basically part is a bit messy).
> The publicly available repos from that period are butchered.
True. I had thought the original FreeBSD 1 repo was now publicly
available. I know I can get copies of it as a FreeBSD project member.
> The number of people on earth trying to curate stuff like the history
> of locore.s/tty.c between 386BSD and the reboots of Net/FreeBSD is a
> handfull, and I'm being optimistic here.
Yea, the FreeBSD CVS tree I think has that history. It started out
life trying to make the patch-kit to 386BSD make sense as dealing with
a boatload of patches soon grew unwieldy as the number proliferated
and you started getting patches on patches.
> This stuff has been deliberately purged and hard to find. Jason Stevens
> went as far as reconstructing a NetBSD 0.8 kernel because the complete
> sources where nowhere to be found. Then he ran into the proverbial
> coughing, chain smoking guy in a raincoat in a parking garage with
> a manilla folder of a CD-ROM of
> ftp://agate.berkeley.edu/pub/NetBSD/NetBSD-0.8,
> or was it a forgotten ftp site?
Don't know anything about that... But the Truth is Out There.
> Anyway, the revision history of the "encumbered" pieces in NetBSD is
> probably lost, but at least the 0.8 checkpoint was unearthed.
I thought it was just shielded from public view and many of the NetBSD
folks had copies. Could be wrong though.
> If you take a close look at the publicly available revision history of
> FreeBSD you'll notice some serious gaps as well. Someone went through
> that cvs with an axe or surgical knife for legal reasons (and made a mess
> teleporting AMD64 to the early 90s).
Yea, CVS doesn't support repo-copying for crap. But it was done to go
from i386 to amd64.
> What dspinellis did with git is truly awesome. But I see the scars the
> USL vs. BSDi lawsuit made. I have no idea why I care, but I do. I respect
> that not everything can be made publicly available, but I pray stuff
> such as an original FreeBSD revision history is at least dumped into
> hidden archives like Warren and friends keep until the time is right.
The old CTM archives might have stuff, it that was up and running
before the lawsuit.
I know that the FreeBSD 1 archive exists in multiple places.
Compressed it is 18MB, or 185MB uncompressed (clang's history is
bigger than that, though checked out it is only about 131MB).
Warner
next prev parent reply other threads:[~2017-02-10 4:11 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 3:03 [TUHS] How Unix brings people together, or it's a small Doug McIlroy
2017-02-07 4:06 ` Marc Rochkind
2017-02-07 23:10 ` Clem Cole
2017-02-07 23:38 ` Steve Johnson
2017-02-08 2:55 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Greg 'groggy' Lehey
2017-02-08 3:47 ` Nick Downing
2017-02-08 3:56 ` Jason Stevens
2017-02-08 8:25 ` Wesley Parish
2017-02-08 9:57 ` Steve Nickolas
2017-02-08 11:21 ` Nick Downing
2017-02-08 11:59 ` [TUHS] Code bloat (was: How Unix brings people together, or it'sa small...) jsteve
2017-02-08 12:24 ` Nick Downing
2017-02-08 12:29 ` [TUHS] Code bloat Jacob Goense
2017-02-08 12:57 ` Nick Downing
2017-02-08 13:10 ` jsteve
2017-02-08 14:10 ` Jacob Goense
2017-02-08 14:34 ` Ron Natalie
2017-02-08 14:43 ` Brantley Coile
2017-02-08 15:09 ` Dan Cross
2017-02-08 15:26 ` Nick Downing
2017-02-08 15:18 ` Jason Stevens
2017-02-08 16:25 ` Tony Finch
2017-02-09 14:03 ` Jacob Goense
2017-02-09 14:41 ` jsteve
2017-02-09 15:03 ` Jacob Goense
2017-02-09 15:08 ` Jason Stevens
2017-02-09 15:30 ` Tony Finch
2017-02-09 16:14 ` Warner Losh
2017-02-09 23:38 ` [TUHS] Free/NetBSD revision history (was Code bloat) Jacob Goense
2017-02-10 4:11 ` Warner Losh [this message]
2017-02-10 4:17 ` Warner Losh
2017-02-08 13:56 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Paul Ruizendaal
[not found] ` <CAH1jEzZqRPYenwzBbUwFVanA-NVvWMGzYiADVoAXCDOqnUrMrg@mail.gmail.com>
2017-02-09 3:02 ` [TUHS] Fwd: " Nick Downing
2017-02-09 9:19 ` [TUHS] " Paul Ruizendaal
2017-02-09 9:58 ` Michael Kjörling
2017-02-09 10:08 ` Paul Ruizendaal
2017-02-09 16:36 ` Larry McVoy
2017-02-09 16:42 ` Warner Losh
2017-02-09 16:49 ` Larry McVoy
2017-02-09 17:24 ` Steffen Nurpmeso
2017-02-09 17:27 ` [TUHS] offtopic: broadband (redirect from bloat) Larry McVoy
2017-02-09 19:05 ` Steffen Nurpmeso
2017-02-09 22:48 ` Joerg Schilling
2017-02-09 19:54 ` [TUHS] Code bloat (was: How Unix brings people together, Corey Lindsly
2017-02-09 20:08 ` pechter
2017-02-09 20:30 ` Arthur Krewat
2017-02-09 23:47 ` Jacob Goense
2017-02-09 21:06 ` Larry McVoy
2017-02-09 21:02 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Joerg Schilling
2017-02-09 16:58 ` [TUHS] Code bloat William Pechter
2017-02-09 19:50 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Clem Cole
2017-02-08 5:37 ` Peter Jeremy
2017-02-08 12:16 ` [TUHS] How Unix brings people together, or it's a small ches@Cheswick.com
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=CANCZdfqGSwNfO+r4OZsae0dX-7zQC98SboTG8uFPsza-EsgU5g@mail.gmail.com \
--to=imp@bsdimp.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).