The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: steve jenkin <stevej098@gmail.com>, TUHS <tuhs@tuhs.org>,
	Marc Donner <marc.donner@gmail.com>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 10:59:24 -0400	[thread overview]
Message-ID: <CAC20D2Nm+_VSYOS-wQb-ycer3o6kobPPqMuua0mn=ri7SM4u-Q@mail.gmail.com> (raw)
In-Reply-To: <20220703143906.GD18597@mcvoy.com>

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

On Sun, Jul 3, 2022 at 10:39 AM Larry McVoy <lm@mcvoy.com> wrote:

> Has anyone ported v7 to any of these devices and seen it take off?

I agree with your observation BTW, but I will point out that every server
based on Intel Si runs a V7 flavor called Minux in the IPMI node.

WRT to Licenses - it does matter for a practical purpose.  As Larry points
out no one cares ... (until they do).

Without going into specifics (this is a real example BTW), let's take a
famous Science and Technology Museum in the EU that wants to use simh to
put up a demo of traditional computing (in this case it's different from
but let's say - using a PiDP-8 or PiDP-11 like display), they would like to
know that it's a legitimate thing to do so.

Lawyers are unlikely to look at the file called Metadata -- as I said, just
last week, I would be easily able to point some of them to the top of
Warren's tree for the Caldera license.   The more licenses we have together
in one place will make folks like that a lot more comfortable with
proceeding.   Again keeping the specific licenses with each release is
probably a good thing (I would suggest links the master copy), just make it
100% clear we are *trying to do the right thing*.
ᐧ

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

  reply	other threads:[~2022-07-03 15:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 18:15 [TUHS] " Clem Cole
2022-07-02 19:07 ` [TUHS] " Marc Donner
2022-07-02 20:57   ` Warner Losh
2022-07-02 21:02     ` Larry McVoy
2022-07-02 23:54       ` Clem Cole
2022-07-03  2:03         ` Warner Losh
2022-07-03  2:27           ` Larry McVoy
2022-07-03  8:11             ` steve jenkin
     [not found]             ` <F579710B-5568-431D-92CC-88D49C3D9BE6@gmail.com>
2022-07-03 14:39               ` Larry McVoy
2022-07-03 14:59                 ` Clem Cole [this message]
2022-07-03 15:30                   ` Bakul Shah
2022-07-03 16:26                     ` Clem Cole
2022-07-03 16:55                       ` Kevin Bowling
2022-07-03 17:15                         ` Clem Cole
2022-07-03 17:48                       ` Bakul Shah
2022-07-03 19:48                         ` Clem Cole
2022-07-03 21:23                           ` Matthias Bruestle
2022-07-03 22:40                             ` Clem Cole
2022-07-04  3:01                               ` Norman Wilson
2022-07-04 12:33                             ` Paul Winalski
2022-07-03 21:38 ` Jay Logue via TUHS

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='CAC20D2Nm+_VSYOS-wQb-ycer3o6kobPPqMuua0mn=ri7SM4u-Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=lm@mcvoy.com \
    --cc=marc.donner@gmail.com \
    --cc=stevej098@gmail.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).