From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] 101 fixes for unix V6?
Date: Sun, 22 Nov 2015 14:59:35 -0600 [thread overview]
Message-ID: <56522CB7.5030309@gmail.com> (raw)
In-Reply-To: <20151122193220.GA23614@www.oztivo.net>
On 11/22/15 1:32 PM, Warren Toomey wrote:
> Hi all, I just receivd this e-mail from Will Senn who has just joined
> the TUHS mailing list:
>
> ----- Forwarded message from Will Senn -----
> Hi,
> I am conducting research on older UNIX operating systems and came
> across a letter from Richard Wolf to Ian Johnstone, dated Feb 5, 1979.
> On p. 29 of the AUUGN, Volume 1 number 3, Mr. Wolf refers to a set of
> 101 fixes for research version 6. In my research, I am currently using
> v6 and wondered if you knew where I might find the fixes or if the
> bits are known to exist?
>
> Kind Regards,
> Will
> ----- End forwarded message -----
>
> Will, there was a "50 bugs" tape for 6th Edition Unix that was "released"
> to Unix owners in a very interesting distribution method: see
> http://www.groklaw.net/articlebasic.php?story=20060616172103795
>
> You can find it in the Unix Archive. Look in Applications/Spencer_Tapes/unsw3.tar.gz. It is the file usr/sys/v6unix/unix_changes.
>
> Does anybody know of something which could be described as "101 fixes for
> research version 6"? The phototypesetter version of Unix was V7.
>
> Cheers all and welcome to the list Will.
>
> Warren
> _______________________________________________
>
Warren,
In looking at the Spencer tape, I can see how this might be considered
the 101 fixes (Wolff's comment that he had only "heard about" the
changes, might indicate a quantity mismatch). The 52 fixes in
usr/sys/v6unix/unix_changes represent "the differences between level 6
unix and bell unix". On top of those changes, there are 31 additional
fixes called "CORRECTIONS to level 6 code" and a whopping 57 "programs
written specifically for or heavily modified for, AUSAM" which I suppose
are what are referred to as "ENHANCEMENTS to level 6 UNIX". The tape
contains "The Second Australian Sixth Edition" and has #ifdef's to
determine if the system is an AUSAM system. The 52 v6 fixes are
straightforward to see because the tape has the original source in one
directory tree and the changes in another. Whereas the other
enhancements and fixes are a bit more challenging because they are
related to AUSAM's mods.
Thanks for the warm welcome, the direction, and for posting my question.
One more question, how did you zero in on
Applications/Spencer_Tapes/unsw3.tar.gz as containing the fixes, the
notes in the archive, from Spencer, are pretty bare:
unsw3.tar is yet another anthology, this one Australian. I can't find a
README file, but some quick experimental grepping doesn't find any dates
later than 1977, so this one may be really early.
Regards,
Will
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151122/15157281/attachment.html>
next prev parent reply other threads:[~2015-11-22 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 19:32 Warren Toomey
2015-11-22 19:33 ` Ronald Natalie
2015-11-22 20:59 ` Will Senn [this message]
2015-11-22 21:59 ` Warner Losh
2015-11-24 2:10 Doug McIlroy
2015-11-24 2:19 ` Warren Toomey
2015-11-24 2:22 ` Larry McVoy
2015-11-24 14:12 ` Milo Velimirović
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=56522CB7.5030309@gmail.com \
--to=will.senn@gmail.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).