The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 17:30:08 -0600	[thread overview]
Message-ID: <CANCZdfqwfsbDBPR5r8Lo7yv69he-btyRpy1i8mfVgU74J2Y_Dg@mail.gmail.com> (raw)
In-Reply-To: <C5B04CCD-D814-4064-A9AF-46B734691828@canb.auug.org.au>

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

On Wed, Mar 15, 2023 at 3:56 PM steve jenkin <sjenkin@canb.auug.org.au>
wrote:

> "What “uses” would SysV codebase have now?" may be a better Q.
>

A System V release 2 might have very limited use (old VAXen are all it ran
on from
AT&T though there were at least a few ports: 68k for sure).

The successor code base of OpenIndiana which forked from OpenSolaris which
was System Vr4 plus a bunch... And that's open... illumos is still using
that for its distribution... They'd have been totally dead, imho, were it
not for OpenZFS using illumos for so long as the reference platform (that's
changed, so now Linux and FreeBSD are the reference platforms, though one
of those two is more equal than the other).

But the successor code base being open isn't quite the same as System V
being open. There's no 'orphan exception' or 'abandonware rider' that would
allow us to distribute this without any legal risk.

But there's the rub: what's the legal risk. The legal risk here is that
somebody could show up and assert they have rights to the software, and
that we're distributing it illegally. Actual damages likely are near $0
these days, but statutory damages could become quite excessive. But to get
damages, one would likely need a lot of money to fight it, and there's not
any kind of real revenue stream from System V today (let alone from System
V r2). Plus, were this successfully prosecuted, it's not like that would
increase that revenue stream: TUHS has no assets, so the current IP owner
would have to somehow assess there was blood to be had from this stone,
which is unlikely... So, how do you rate the risk of a low-probability,
high damage outcome vs the near certainty of a no-damage outcome. Since
it's none of our butt's but Warren's, he gets to decide his comfort zone
here. :)

So the risk of adverse consequences is likely low, but not zero were we to
distribute this without a license to do so. There's plenty of others that
are doing so today, but that's between the others and whatever IP owners

Disclaimer: I'm not a lawyer, and this isn't legal advice...

Warner

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

  parent reply	other threads:[~2023-03-15 23:30 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 11:59 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08   ` Clem Cole
2023-03-15 21:15     ` Luther Johnson
2023-03-15 21:18     ` Seth Morabito
2023-03-15 21:22       ` Larry McVoy
2023-03-15 21:27         ` Clem Cole
2023-03-15 21:38           ` KenUnix
2023-03-16 23:18             ` Clem Cole
2023-03-16 23:48               ` Charles H. Sauer (he/him)
2023-03-17  1:08                 ` Steve Nickolas
2023-03-15 21:46           ` Steve Nickolas
2023-03-15 21:50         ` Luther Johnson
2023-03-15 21:56         ` steve jenkin
2023-03-15 22:15           ` Larry McVoy
2023-03-15 23:30           ` Warner Losh [this message]
2023-03-15 23:41             ` Luther Johnson
2023-03-16  0:29               ` Warner Losh
2023-03-16  0:36                 ` Rich Salz
2023-03-16  1:55                   ` G. Branden Robinson
2023-03-16 21:14                   ` Dave Horsfall
2023-03-17  0:33                     ` Rich Salz
2023-03-17  1:03                       ` [TUHS] copyright (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17  1:05                       ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 segaloco via TUHS
2023-03-17  2:03                         ` G. Branden Robinson
2023-03-17  3:17                           ` Dave Horsfall
2023-03-17  3:30                             ` [TUHS] Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 15:12                               ` [TUHS] " Pete Turnbull
2023-03-17 15:33                                 ` segaloco via TUHS
2023-03-17 16:42                                   ` Steve Nickolas
2023-03-17 18:27                                     ` Marc Donner
2023-03-16  1:15               ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Larry McVoy
2023-03-16  2:14                 ` Luther Johnson
2023-03-15 23:44             ` Brad Spencer
2023-03-16  4:37         ` Dave Horsfall
2023-03-15 23:56   ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
2023-03-17  2:28   ` [TUHS] Re: UNIX System V Warren Toomey via TUHS
  -- strict thread matches above, loose matches on Subject: below --
2023-03-15 22:25 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 22:39 ` segaloco via TUHS
2023-03-15  0:59 Noel Chiappa
2023-03-15  8:05 ` arnold
2023-03-15  8:52   ` Dave Horsfall
2023-03-15 11:09     ` KenUnix

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=CANCZdfqwfsbDBPR5r8Lo7yv69he-btyRpy1i8mfVgU74J2Y_Dg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=sjenkin@canb.auug.org.au \
    --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).