From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] 10th Edition, 8th Edition
Date: Sat, 02 Feb 2013 19:58:31 +1300 [thread overview]
Message-ID: <D3B5149F-34E0-45EF-99DD-D6A8EC43B8A9@paradise.net.nz> (raw)
In-Reply-To: <82d6f574a75e78bc92dcc9f21a2e1542@localhost>
That would make sense. SysV is about twenty years old, and its status
as an ultra-holy reliquary of trade secrets and whatnot has been
severely dented by Sun's open-sourcing of Solaris.
If anyone knows who to contact at Attachmate, I'd say, go for the
full bag, of Research Unix and commercial Unix.
Wesley Parish
On 2/02/2013, at 1:20 AM, Angelo Papenhoff wrote:
> On Fri, 1 Feb 2013 01:55:43 +0000, Benjamin Huntsman wrote:
>> While the subject of historical stuff has been brought up, anyone
>> thought about going another round with Attachmate to see if they'd
>> extend the Ancient UNIX License to include v10, v9, and v8?
>> Attachmate is the current owner these days, aren't they?
>> I'm sure they, Novell, AT&T, and Lucent all don't care. But
>> someone's still got to sign the line. I'm really hoping to see
>> v10x86, like v7x86 someday!!
>>
>> I've got a copy of v8 I'd love to make available some day, and I know
>> there are at least one or two copies of v10 still in existence. last
>> I heard, there was no v9.
>>
>> Anyone here know anybody at Attachmate?
>>
>> Many thanks!
>>
>> -Ben
>
> Great to hear there still exist copies of later research Unices.
> We should definitely ask for an extension of the Ancient UNIX License
> (possibly to include SysIII or even SysV as well?).
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2013-02-02 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 1:55 Benjamin Huntsman
2013-02-01 12:20 ` Angelo Papenhoff
2013-02-02 6:58 ` Wesley Parish [this message]
2013-02-02 7:38 ` Ronald Natalie
2013-02-03 15:34 ` Rox 64
2013-02-03 16:37 ` Larry McVoy
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=D3B5149F-34E0-45EF-99DD-D6A8EC43B8A9@paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/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).