The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Anyone have any luck trying to contact Micro Focus regarding Unix licensing?
Date: Fri, 19 Oct 2018 16:25:16 -0500	[thread overview]
Message-ID: <CAC20D2OguYKM0VPxDBX7M7NsQ0hb=p4x=A6gF2kKhTsv7bmc1A@mail.gmail.com> (raw)
In-Reply-To: <9f76d002-1530-4745-8fb6-2dba1baf36ce@SG2APC01FT042.eop-APC01.prod.protection.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

On Fri, Oct 19, 2018 at 10:57 AM <jsteve@superglobalmegacorp.com> wrote:

> I know after the whole SCO personal licenses and then Ransom Loves’s
> making 32v and all prior open was great but apparently it wasn’t his to
> give away.  Or am I wrong?
>
Sigh ...  Yes...   Where did you hear this?   On second thought, I really I
don't want to know...  Whomever is spreading that information is tad
uninformed and really does understand what happened.

Simply put, the AT&T case made it clear, *the technology has been published*.
 The issue is closed.  It is 'open' - free - 'libre.'  It's all public
information and has been and was required to be by the US Courts in the
AT&T / USL vs UCB/BSDi law suit.   It's really not an interesting argument
at this point. The US courts made is clear, * AT&T was required to make the
barn doors open, and horses left the barn.*

This is why >>Novell<< released the implementation (i.e. source code) and*
it was Novell's to make available - which again the US courts have already
determined. *

All of this has been discussed here and elsewhere and really does not need
to be rehashed (please). *  In fact, *I wrote and published a very long
paper about how UNIX can to be.   The presentation of same can be seen and
the paper downloaded:
http://technique-societe.cnam.fr/colloque-international-unix-en-france-et-aux-etats-unis-innovation-diffusion-et-appropriation--945215.kjsp


Clem

ᐧ

[-- Attachment #2: Type: text/html, Size: 4141 bytes --]

      reply	other threads:[~2018-10-19 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 15:04 jsteve
2018-10-19 21:25 ` Clem Cole [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='CAC20D2OguYKM0VPxDBX7M7NsQ0hb=p4x=A6gF2kKhTsv7bmc1A@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=jsteve@superglobalmegacorp.com \
    --cc=tuhs@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).