The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mike Haertel <tuhs@ducky.net>
To: The Unix Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Sun, 10 Mar 2019 08:50:36 -0700	[thread overview]
Message-ID: <201903101550.x2AFoaZp036647@ducky.net> (raw)
In-Reply-To: <201903100820.x2A8KjsZ029408@freefriends.org>

arnold@skeeve.com writes:
> Isn't 4.1 on Kirk McKusick's disks?

McKusick's disks look sketchy to me too:

# cd /mnt/CSRG/disk1
# diff --exclude=.MAP -r 4.0 4.1 | grep -v 'not a regular file or directory'
Only in 4.0: 4.0.boot.Z
Only in 4.1: 4.0.upgrade
Only in 4.1: TAPE
Only in 4.1: boot.file
Only in 4.0/dev: cua0
Only in 4.0/dev: cua1
Only in 4.1/tmp: x.f
Only in 4.1/tmp: x.s
Only in 4.0/usr/src/lib/libpc: RANDOM.c
Only in 4.0/usr/src/lib/libpc: RANG4.c
Only in 4.0/usr/src/lib/libpc: READ4.c
Only in 4.0/usr/src/lib/libpc: READ8.c
Only in 4.0/usr/src/lib/libpc: READC.c
Only in 4.0/usr/src/lib/libpc: READE.c
Only in 4.0/usr/src/lib/libpc: READLN.c
Only in 4.0/usr/src/lib/libpc: RELEQ.c
Only in 4.0/usr/src/lib/libpc: RELNE.c
Only in 4.0/usr/src/lib/libpc: RELSGE.c
Only in 4.0/usr/src/lib/libpc: RELSGT.c
Only in 4.0/usr/src/lib/libpc: RELSLE.c
Only in 4.0/usr/src/lib/libpc: RELSLT.c
Only in 4.0/usr/src/lib/libpc: RELTGE.c
Only in 4.0/usr/src/lib/libpc: RELTGT.c
Only in 4.0/usr/src/lib/libpc: RELTLE.c

So it appears to me the only 4.1 material in his 4.1 tree is under the
4.1/4.0.upgrade directory.

The 4.0 and 4.1 trees on his disks are otherwise basically the same,
except for a handful of /usr/src/lib/libpc/*.c source files that appear
only in the 4.0 tree.

Or, perhaps the 4.0 tree is misidentified and is really a 4.1 tree, and
what is lost is 4.0?

Anyway, there definitely seems to be a missing link somewhere.

	Mike

  reply	other threads:[~2019-03-10 15:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10  7:31 Mike Haertel
2019-03-09 23:24 ` Nigel Williams
2019-03-10 11:18   ` Lars Brinkhoff
2019-03-10 20:55     ` Warner Losh
2019-03-10 22:53       ` Mike Haertel
2019-03-11  0:25         ` Al Kossow
2019-03-11  1:15           ` Mike Haertel
2019-03-11  5:46           ` Jason Stevens
2019-03-11 17:28             ` Mike Haertel
2019-03-11 17:38               ` Larry McVoy
2019-03-11 18:33                 ` Lars Brinkhoff
2019-03-11 18:41                 ` Clem Cole
2019-03-12  6:21                 ` Nigel Williams
2019-03-12  6:32                   ` Jason Stevens
2019-03-12 12:44                 ` arnold
2019-03-11 21:47             ` Al Kossow
2019-03-23 17:50         ` reed
2019-03-24  4:19           ` Lars Brinkhoff
2019-03-10  8:20 ` arnold
2019-03-10 15:50   ` Mike Haertel [this message]
2019-03-10 19:54     ` arnold
2019-03-10 20:33       ` Warner Losh
2019-03-25 17:19 Richard Tobin

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=201903101550.x2AFoaZp036647@ducky.net \
    --to=tuhs@ducky.net \
    --cc=tuhs@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).