From: William Pechter <pechter@gmail.com>
To: Warren Toomey <wkt@tuhs.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Saving the Unix Bits
Date: Tue, 4 Sep 2018 16:53:43 -0400 [thread overview]
Message-ID: <CALwkMd1A3zn45KC_jLpp8z5J+hZvUF-AKd1-+pNcZW84m5TMSA@mail.gmail.com> (raw)
In-Reply-To: <20180904203311.GA21089@minnie.tuhs.org>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
One thing I'd like to see saved for the historical value is Pyramid OS/x.
It was one of those things I'd have liked to see the internals of -- but I
wasn't supposed to have that level accesss in Ed Services.
It is an interesting mix of both the SysV and BSD environments and it's a
shame it's probably completely gone now.
I think the last work on it may have been at Siemens, since I think the
last bit of Pyramid that was left was rumored to
go to SVR4 (I was there for the DC/OSx transition -- I worked on the
courseware fixes and beta testing).
I heard from a friend that they may have gone to Solaris before the end
hit. I think they were swallowed by Fujitsu.
Amazingly, I heard some of my SVR4 courseware stuff ended up in
illustrations used in Solaris courseware. My name was in the illustration
of the password file. A trainer hired at least 5 years after me went to
Sun and I hear some of my stuff went along for the ride.
I long wished they had done the full Linux dual universe thing on a *BSD
varient.
I'd be running FreeBSD on my desktop if I could just watch Netflix with
it. Linux, Windows and MacOS have enough pull for Google to port their
Widevine
Bill
--
d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
pechter-at-gmail.com
On Tue, Sep 4, 2018 at 4:34 PM Warren Toomey <wkt@tuhs.org> wrote:
> On Tue, Sep 04, 2018 at 01:58:04PM -0400, Noel Chiappa wrote:
> > True; but if all the copies of a particular item are discarded, one can
> make
> > all the lawyers on the planet as happy as clams, and it won't do a bit of
> > good. Save the bits, _then_ work out the legal issues, is my thinking on
> > priorities.
>
> I'll also follow up on Henry and Noel's e-mail w.r.t the Unix Archive that
> TUHS provides. The only files in the public archive are ones where the
> legal
> issues have been resolved. I also keep a hidden archive of files where the
> legal issues have not been resolved.
>
> As always, if you would like me to keep an off-site backup of your Unix
> bits, the hidden Unix archive is write-only. Save the bits, and also
> be mindful of the legal issues.
>
> Cheers, Warren
>
[-- Attachment #2: Type: text/html, Size: 3116 bytes --]
next prev parent reply other threads:[~2018-09-04 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 17:58 [TUHS] SunOS code? Noel Chiappa
2018-09-04 20:33 ` [TUHS] Saving the Unix Bits Warren Toomey
2018-09-04 20:39 ` Clem Cole
2018-09-04 20:53 ` William Pechter [this message]
2018-09-06 0:48 ` Dave Horsfall
2018-09-06 0:39 ` [TUHS] SunOS code? Dave Horsfall
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=CALwkMd1A3zn45KC_jLpp8z5J+hZvUF-AKd1-+pNcZW84m5TMSA@mail.gmail.com \
--to=pechter@gmail.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).