From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Found: 4.1BSD User's Manual Volume 2C Comb-Bound
Date: Tue, 17 Oct 2023 20:18:24 -0400 (EDT) [thread overview]
Message-ID: <20231018001824.5231718C096@mercury.lcs.mit.edu> (raw)
> From: Clem Cole
> Stakrting with V6, Ken/Dennis masters a tape in research, and the IBM
> shop is imaging that for people licensing the IP -- *i.e.,* everyone is
> getting the same bits on their tape. Although with V6, the famous
> "patch tape" leaks independently
Actually, TUHS contains two microscopically different V6 distros:
Dennis_v6
---------
v6root.gz, v6src.gz and v6doc.gz are a set of three RK05 images of Sixth
Edition with root, /usr and documentation, from Dennis Ritchie.
Ken_Wellsch_v6
--------------
v6.tape.gz is a copy of the Sixth Edition distribution tape which was sent
in by Ken Wellsch.
It notes that there are differences between the two, but hadn't investigated
what they are.
Here are some details: the source files for the kernel are identical, except
for sys/ken/main.c, which has the following added in the Wellsch version:
printf("RESTRICTED RIGHTS\n\n");
printf("Use, duplication or disclosure is subject to\n");
printf("restrictions stated in Contract with Western\n");
printf("Electric Company, Inc.\n");
(What clearly happened is that after they'd done some distribution, the AT+T
lawyers made them add that.) Anyway, as a result, the binary system images
'rkunix', etc are slightly different between the two.
Everything else seems to be identical: everything in /bin, /etc, /lib,
/usr/bin and /usr/lib are all identical.
Noel
next reply other threads:[~2023-10-18 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 0:18 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-09 16:17 [TUHS] " segaloco via TUHS
2023-10-10 2:11 ` [TUHS] " Jonathan Gray
2023-10-15 3:19 ` Mary Ann Horton
2023-10-15 5:49 ` segaloco via TUHS
2023-10-16 18:42 ` Mary Ann Horton
2023-10-16 19:49 ` Clem Cole
2023-10-17 5:30 ` Jonathan Gray
2023-10-17 18:27 ` segaloco via TUHS
2023-10-17 20:11 ` Clem Cole
2023-10-17 21:56 ` segaloco via TUHS
2023-10-18 12:12 ` Rich Salz
2023-10-17 4:00 ` Jonathan Gray
2023-10-19 14:27 ` Mary Ann Horton
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=20231018001824.5231718C096@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).