From: Charles H Sauer <sauer@technologists.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Help Contacting Unix Legal People
Date: Sat, 12 Jun 2021 15:32:06 -0500 [thread overview]
Message-ID: <06f8dd8c-ddac-0ee1-3f6a-375e91891152@technologists.com> (raw)
In-Reply-To: <0F0B9BFC06289346B88512B91E55670D3017@EXCHANGE>
IF Micro Focus really has abandoned System V, including SVR4 source, and
that could be documented, then it might be plausible to get Dell SVR4
publicly visible. Charlie
On 6/12/2021 1:58 PM, Jason Stevens wrote:
> I tried sending a letter a while back asking how much is a commercial SYSV
> license anyways, never got a reply. I called their legal and they didn't
> know what a Unix was.
>
>
> I guess shockingly all the public facing micro focus is all on cobol
>
> -----Original Message-----
> From: Warren Toomey
> To: tuhs@tuhs.org
> Sent: 6/10/21 8:32 AM
> Subject: [TUHS] Help Contacting Unix Legal People
>
> All, we need help contacting some people so that Dan Doernberg can make
> progress on a new Unix book that he's working on. I've attached his
> request to the TUHS list below. If you can help out in any way, please
> contact Dan directly.
>
> Cheers, Warren
>
> From: Peer-to-Peer Communications LLC <dan@peerllc.com>
>
> Hello all, I’m the publisher of Lions' Commentary on UNIX (still
> going strong after 25 years!) and I have an “Ancient UNIX” book
> project
> in mind that I need some community help with.
>
> To avoid running into any “who has copyright rights to UNIX” legal
> problems, we’re trying to reach out in advance to any
> companies/organizations that may have such rights (Micro Focus,
> Xinuos,
> Nokia, are there others?) in advance. To that end, I’m trying to find
> staffers there who are:
> 1. sympathetic to sharing information about “ancient UNIX” with
> the
> operating system/UNIX communities
> 2. somewhat familiar with the past legal issues and controversies
> over UNIX ownership (perhaps someone in the legal department)
>
> If you know any such person(s) at Micro Focus, Xinuos, Nokia, and/or
> other relevant organizations that has either quality (or ideally a
> unicorn with both!), please pass on their name and email address to
> me
> (even better, add any context about why they might be helpful to me,
> if
> it’s OK to say that you referred me to them, etc.].
>
> Thanks much, all referrals greatly appreciated!
> Dan Doernberg
> dan@peerllc.com
>
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/Skype/Twitter: CharlesHSauer
next prev parent reply other threads:[~2021-06-12 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 18:58 Jason Stevens
2021-06-12 19:35 ` Steve Nickolas
2021-06-12 19:49 ` joe mcguckin
2021-06-12 20:40 ` Al Kossow
2021-06-12 20:32 ` Charles H Sauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-13 15:23 Paul Ruizendaal via TUHS
2021-06-10 0:32 Warren Toomey
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=06f8dd8c-ddac-0ee1-3f6a-375e91891152@technologists.com \
--to=sauer@technologists.com \
--cc=tuhs@minnie.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).