The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wlc@jctaylor.com (William Corcoran)
Subject: [TUHS] Reorganising the Unix Archive?
Date: Sun, 19 Feb 2017 20:48:32 -0500	[thread overview]
Message-ID: <6961AB0F-422F-47E3-8204-C555B3F62E52@jctaylor.com> (raw)
In-Reply-To: <201702190012.v1J0CGml026966@coolidge.cs.Dartmouth.EDU>

Hello Mr. Mcllroy, 

Well, along the lines of early UNIX preservation, I have a question.

At some point SCCS began to take shape and take hold of the core of the early UNIX distributions.  Google says SCCS has been around since 1972. 

Now, let's take my favorite UNIX releases Research 7, v7m and BSD 2.11.  They are my favorite since I have access to the complete distributions and I have all working independently via simulators on dedicated hardware.  

Now, it's simply wonderful to view the sources.  Even more wonderful, through simulation, to relink these distributions.  And it's fun to read code and comments---most of it way over my head.   

But, is there somewhere a main distribution for Research 7, v7m 2.1, or BSD 2.11 that has all of the original SCCS deltas (leaf and non-leaf)? 

This would be extremely revealing. If we could view the SCCS comments (sccs prs) and the underlying code, it would be incredibly valuable. 

Please forgive me if this has been asked a million times.  I just can't find it.  Once SCCS was heavily used, was there a codebase that housed all of these distributions?  

I always wondered if there were some kind of SCCS or SCCS-like repository that maintained the final distribution and all of the deltas leading up to a minor or even major release.

RELEASE, LEVEL, BRANCH and SEQUENCE:

I do see "SCCSID" strings sprinkled throughout various distributions.  So, this way the application could automatically report the RLBS to the end user. 

But, is there an early UNIX distribution that housed  the complete SCCS repository---I want to dig deep, really deep.  This way I could see the paths that were taken, the solutions that partially worked, or ended up causing other problems.

Truly,

Bill Corcoran



> On Feb 18, 2017, at 7:12 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> 
> 
> OMG. I don't know how many times I've consulted the Unix
> Tree and blissfully ignored the cross-links that come at
> the top of every file--I'm so intent on the content.
> 
> Apologies for cluttering the mailing list about a solved topic.
> 
> Doug


  reply	other threads:[~2017-02-20  1:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  0:12 Doug McIlroy
2017-02-20  1:48 ` William Corcoran [this message]
2017-02-20  2:33   ` Doug McIlroy
2017-02-20  2:52     ` Larry McVoy
2017-02-20 18:06   ` Joerg Schilling
  -- strict thread matches above, loose matches on Subject: below --
2017-02-18 18:49 Doug McIlroy
2017-02-18  3:30 Doug McIlroy
2017-02-18  4:40 ` Warren Toomey
2017-02-18 17:19   ` Random832
2017-02-18  0:12 Warren Toomey
2017-02-18  0:21 ` Warren Toomey
2017-02-18  0:40 ` Clem Cole
2017-02-18  1:09   ` Warren Toomey
2017-02-18 17:17 ` Random832

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=6961AB0F-422F-47E3-8204-C555B3F62E52@jctaylor.com \
    --to=wlc@jctaylor.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).