The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stuart Remphrey <stu@remphrey.net>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Source code for SCCS
Date: Wed, 15 Jun 2022 13:15:12 +0800	[thread overview]
Message-ID: <CAD0_1cnmwV0Rf37y17jX=GPd07Oyj4E5PGoE6xrRRhhBwENMtw@mail.gmail.com> (raw)
In-Reply-To: <B9C0E0DD-9B7A-4B17-BC75-C35A61A172AB@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]

We used RCS & some SCCS for Pyramid DC/OSx (mid/late 80s?)
I've no idea whether Pyramid sources survive anywhere: if anyone's aware of
any, I'd be very interested to know...



On Sat, 11 Jun 2022, 18:09 Paul Ruizendaal, <pnr@planet.nl> wrote:

> It would seem that a Spinellis-like exercise for SCCS is possible:
>
> PWB1.0 (1978):
> https://www.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/sccs4
> SysIII (1980):
> https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/sccs
> SysVr1
> <https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/sccsSysVr1>
> (1983): https://www.tuhs.org/cgi-bin/utree.pl?file=pdp11v/usr/src/cmd/sccs
> SysVr2
> <https://www.tuhs.org/cgi-bin/utree.pl?file=pdp11v/usr/src/cmd/sccsSysVr2>
> (1984):
> https://github.com/ryanwoodsmall/oldsysv/tree/master/sysvr2-vax/src/cmd/sccs
> SysVr3
> <https://github.com/ryanwoodsmall/oldsysv/tree/master/sysvr2-vax/src/cmd/sccsSysVr3>
> (1987):
> https://github.com/ryanwoodsmall/oldsysv/tree/master/sysvr3/301/usr/src/cmd/sccs
> SysVr4
> <https://github.com/ryanwoodsmall/oldsysv/tree/master/sysvr3/301/usr/src/cmd/sccsSysVr4>
> (1988):
> https://github.com/ryanwoodsmall/oldsysv/tree/master/sysvr4/svr4/cmd/sccs
> Ultrix3.1 (1988):
> https://www.tuhs.org/cgi-bin/utree.pl?file=Ultrix-3.1/src/cmd/sccs
>
> I did not find SCCS sources included with the BSD sources on TUHS, but
> there is a front-end “sccs” command. For sure, SCCS was used for BSD
> development. Kirk McKusick’s DVD has a directory "CSRG/historic1/sccscmds”,
> but I did not look into this further.
>
> From here the trail probably continues with Solaris, GNU and Bitmover --
> all very much outside my timeframe of research.
>
> Paul
>
> > The original Marc Rochchild/John Mashey and team code from PWB 1.0 can be
> > found:  http://tuhs.org/Archive/Distributions/USDL/spencer_pwb.tar.gz
> > In the directory: sys/source/sccs4
> > The man pages are in the same archive but mixed with the rest of the
> > commands in usr/man/man*
> >
> > That said, there is Gnu version of same written C++ if IIRC:
> > https://www.gnu.org/software/cssc/
> >
> > And there's more ... but I'll Larry offer details here other than point
> out
> > his: http://www.bitmover.com/bitsccs/ [which is of BitKeeper] is a
> > more modern implementation still]
>

[-- Attachment #2: Type: text/html, Size: 3636 bytes --]

  reply	other threads:[~2022-06-15  5:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 10:09 Paul Ruizendaal
2022-06-15  5:15 ` Stuart Remphrey [this message]
2022-06-15  6:21 ` Ed Bradford

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='CAD0_1cnmwV0Rf37y17jX=GPd07Oyj4E5PGoE6xrRRhhBwENMtw@mail.gmail.com' \
    --to=stu@remphrey.net \
    --cc=pnr@planet.nl \
    --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).