From: txomsy@yahoo.es (Jose R. Valverde)
Subject: [TUHS] original SCCS code?
Date: Wed, 26 Jan 2005 21:46:01 +0100 [thread overview]
Message-ID: <20050126214601.461cb04d.txomsy@yahoo.es> (raw)
In-Reply-To: <200501261419.j0QEJ4cK001907@skeeve.com>
On Wed, 26 Jan 2005 16:19:04 +0200
Aharon Robbins <arnold at skeeve.com> wrote:
> Is the original code for SCCS under the Caldera license? In particular,
> is there a URL where it's available? Or should someone wishing to work
> with SCCS files use GNU CSSC?
>
Sure, it's all in the archive. I'm now locked at home by the snow and can't
access the DVD I had created with the expanded sources of TUHS, but it is
certainly there.
I would look into either Ultrix, SystemIII or any PWB release.
Quick check: look into
.../PDP11/Distributions/dec/Ultrix-3.1-src/ultrix11-src.tar.gz
.../VAX/Distributions/Ultrix-32M/old-ultrix-32.tar.gz
j
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20050126/1a75b24f/attachment.sig>
prev parent reply other threads:[~2005-01-26 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 14:19 Aharon Robbins
2005-01-26 20:46 ` Jose R. Valverde [this message]
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=20050126214601.461cb04d.txomsy@yahoo.es \
--to=txomsy@yahoo.es \
/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).