From: Ed Bradford <egbegb2@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Warren Toomey <wkt@tuhs.org>, UNIX Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Documentation for Unix 4.0
Date: Fri, 10 Jun 2022 23:34:58 -0500 [thread overview]
Message-ID: <CAHTagfEey=t72x91=T-fhQsax=YSmMhuYxoB5E-EpHJsO2BNpQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Nb78OriX3DdMyHJbLjObfECSjQ2B5G49qoinUsmKnZ7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Thank you, Clem. You link didn't work but the other information on cssc
worked fine.
Ed
On Fri, Jun 10, 2022 at 9:23 AM Clem Cole <clemc@ccc.com> wrote:
> 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]
> ᐧ
>
> On Fri, Jun 10, 2022 at 2:48 AM Ed Bradford <egbegb2@gmail.com> wrote:
>
>> Hi Warren,
>>
>> Thank you for the amazing Unix documetation.
>> Do you know if there is a source code for SCCS anywhere on the net?
>>
>> Ed Bradford
>>
>> On Sun, Jun 5, 2022 at 8:40 PM Warren Toomey via TUHS <tuhs@tuhs.org>
>> wrote:
>>
>>> Hi all, we have a new addition to the Unix Archive at:
>>> https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/
>>>
>>> This is the documentation for Unix 4.0 which preceded System V. The
>>> documents were provided by Arnold Robbins and scanned in by Matt Gilmore.
>>>
>>> Cheers, Warren
>>>
>>
>>
>> --
>> Advice is judged by results, not by intentions.
>> Cicero
>>
>>
--
Advice is judged by results, not by intentions.
Cicero
[-- Attachment #2: Type: text/html, Size: 4694 bytes --]
next prev parent reply other threads:[~2022-06-11 4:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 1:40 [TUHS] " Warren Toomey via TUHS
2022-06-06 2:15 ` [TUHS] " Warner Losh
2022-06-06 9:19 ` arnold
2022-06-06 2:26 ` Larry McVoy
2022-06-06 9:20 ` arnold
2022-06-07 16:57 ` John Cowan
2022-06-07 19:32 ` G. Branden Robinson
2022-06-09 22:19 ` Derek Fawcus
2022-06-06 6:21 ` G. Branden Robinson
2022-06-06 9:26 ` arnold
2022-06-10 6:47 ` Ed Bradford
2022-06-10 7:31 ` [TUHS] Source code for SCCS (was Re: Re: Documentation for Unix 4.0) arnold
2022-06-10 8:38 ` [TUHS] " Matthias Bruestle
2022-06-10 10:03 ` arnold
2022-06-15 5:32 ` Stuart Remphrey
2022-06-10 14:22 ` [TUHS] Re: Documentation for Unix 4.0 Clem Cole
2022-06-10 19:24 ` John Cowan
2022-06-11 4:34 ` Ed Bradford [this message]
2022-06-11 14:43 ` Clem Cole
2022-06-12 5:45 ` Ed Bradford
2022-06-12 6:41 ` Warren Toomey via TUHS
2022-06-13 13:18 ` Jay Logue via TUHS
2022-06-13 15:49 ` Norman Wilson
2022-06-13 16:39 ` Michael Kjörling
2022-06-15 1:53 ` Stuart Remphrey
2022-06-15 5:57 ` Michael Kjörling
2022-06-15 12:04 ` Dan Cross
2022-06-16 7:45 ` Tom Ivar Helbekkmo via TUHS
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='CAHTagfEey=t72x91=T-fhQsax=YSmMhuYxoB5E-EpHJsO2BNpQ@mail.gmail.com' \
--to=egbegb2@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@tuhs.org \
--cc=wkt@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).