From: dscherrer@solar.stanford.edu (Deborah Scherrer)
Subject: [TUHS] Reorganising the Unix Archive? (GNU?)
Date: Mon, 20 Feb 2017 10:37:33 -0800 [thread overview]
Message-ID: <42e98887-0440-3903-65f8-cd35e772508c@solar.stanford.edu> (raw)
In-Reply-To: <201702201827.v1KIR4PR012916@freefriends.org>
I was one of the 3 primary authors of the Software Tools system (along
with Dennis Hall and Joe Sventek), and I was the founder of the users
group. (Also served a long time on the Usenix Board, was even president
for a while.) Yes, the Georgia Tech stuff was from our system. And, we
expanded extensively beyond the tape that was available with the
Kernighan/Plauger book.
I would be pleased to contribute our code to the archive. Thanks.
Deborah
On 2/20/17 10:27 AM, arnold at skeeve.com wrote:
> Hi Debborah.
>
> I don't know if we ever met but I certainly recognize your name
> from the Software Tools work.
>
> The original Ratfor and Pascal versions of the tools from the
> Kernighan and Plauger books are already in the archive, donated
> by yours truly many years ago. (They're from the tapes Addison Wesley
> would sell you at the time.)
>
> Nontheless, I think it would be WONDERFUL to have the enhanced
> tools you folks did in the archives.
>
> Please contribute them!
>
> Arnold
>
> P.S. I've asked before, but maybe there are more people around now...
>
> I was involved with the Georgia Tech subsystem for Pr1me computers which
> also built a very Unix like environment in an enhnaced Ratfor to run
> on top of Primos. Some of the doc is archived, and I have some paper
> copies, but I'd love to see that code unearthed...
>
> I've made a very few bits that were ported to C are available under
> http://github.com/arnoldrobbins, and the 'se' editor has been revived
> by Thomas Cort at se-editor.org, but that's all in C.
>
> If anyone has a tape, I might have a program that could extract
> it under *nix.
>
> Thanks!
>
> Deborah Scherrer <dscherrer at solar.stanford.edu> wrote:
>
>> I would like to add the Software Tools to the Unix archive. As you may
>> remember, Brian Kernighan and P. J. Plauger wrote a book about
>> developing Unix-like code for non-Unix systems. We at the Lawrence
>> Berkeley Lab took that idea and ran with it. We eventually produced a
>> set of Unix utilities and a system interface that could be reproduced on
>> virtually any operating system. This was freely distributed and
>> eventually the package was put up on over 50 different
>> computers/systems. There was a user group of about 2000. The movement
>> earned one of the Usenix Flame Awards, way back when.
>>
>> We have the original tapes produced at Lawrence Berkeley Lab, plus a
>> Pascal version, plus a version for CP/M. We would like to add these to
>> the Unix archive, if you think it appropriate.
>>
>> Deborah
next prev parent reply other threads:[~2017-02-20 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 6:14 Jason Stevens
2017-02-20 6:50 ` Warren Toomey
2017-02-20 7:00 ` Nick Downing
2017-02-20 7:23 ` Jason Stevens
2017-02-20 9:08 ` arnold
2017-02-20 9:59 ` jsteve
2017-02-20 11:12 ` arnold
2017-02-20 16:46 ` Deborah Scherrer
2017-02-20 18:27 ` arnold
2017-02-20 18:37 ` Deborah Scherrer [this message]
2017-02-20 18:56 ` arnold
2017-02-20 19:46 ` Brantley Coile
2017-02-20 7:10 ` Lars Brinkhoff
2017-02-20 7:19 ` Jason Stevens
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=42e98887-0440-3903-65f8-cd35e772508c@solar.stanford.edu \
--to=dscherrer@solar.stanford.edu \
/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).