The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Is OpenText Corporation the Current System V Copyright Holder?
Date: Thu, 14 Mar 2024 16:50:46 +0000	[thread overview]
Message-ID: <Azv75tC6fOS8CJYVWoM24u5cIlMLndv8etz8BChmUQOXEio5VmzYAnWalhdpp4oCRK4V83OUphO-wkGtZPN6qOIxNNdEltOJrLen00sCX3Y=@protonmail.com> (raw)
In-Reply-To: <CANCZdfoN3DwafL=Mp-hRNkMSSW_pGDBfAZvfb3C9r-JAibm8NA@mail.gmail.com>

On Thursday, March 14th, 2024 at 8:50 AM, Warner Losh <imp@bsdimp.com> wrote:

> 
> 
> At the time, though I have no reference for it, Sun bought a paid-up license from AT&T and part of that purchase included the right to distribute the source code in the way they did. This was a special deal Sun cut with AT&T.
>
> ...
> 
> I also found:
> 
> > So how is it Sun is permitted to open source Unix outright while IBM is sued for more than US$5 billion in damages? Sun is mum on particulars, but it has said it licensed additional rights in a 2003 deal in which it paid SCO US$9.3 million.
> 
> at https://www.zdnet.com/article/sun-poised-to-take-open-source-solaris-step/ dated in 2005.
>

That makes sense given the collaborative efforts between USL and Sun on SVR4 actually.

On Thursday, March 14th, 2024 at 8:50 AM, Warner Losh <imp@bsdimp.com> wrote:

>
> 
> The main problem with any of this is that all the companies that took System V made changes to customize it for their hardware.
>
> ...
>
> Though much of the later work was done by third parties and consortia, so even if AT&T successor in interest gave the nod, those other parties might not have granted AT&T the right to do this.
> 
> Warner

That's a good point, like many long-standing codebases, System V code is littered with little "this is copyright this subcontractor, this is copyright that contributor, etc." and big thorough license descriptions sitting at the top of source files weren't in vogue at the time so it offers confusion over ownership with little paths to clarity.  Maybe a happy middle ground would be a 4.4BSD-Lite-ish approach to System V in which anything demonstrated to be exact program text that is not out in the open in the form of Research or illumos code can be scrubbed from, say, SVR4, and that fragmentary codebase could then fly under the research license or CDDL or what have you.

As you mention though, what company wants to devote their resources to a revenue-less project like that?  It'd be swell if some sort of publicly funded organization like the Library of Congress, Smithsonian Institution, or equivalents in other locales could take up that mantle on this and other software preservation efforts.  That's something I think about often in my retro video game disassembly work, it'd be nice to preserve these historically significant applications and systems as a formal career rather than just hobby stuff.  But right, where's the revenue stream to convince anyone to do that, especially the legal hurdles involved?  Lawyers ain't cheap...

- Matt G.

      reply	other threads:[~2024-03-14 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  0:33 [TUHS] " segaloco via TUHS
2024-03-14  2:13 ` [TUHS] " Marc Rochkind
2024-03-14  2:25   ` Warner Losh
2024-03-14  3:40   ` Steve Nickolas
2024-03-14 18:38     ` Stuff Received
2024-03-14 19:51       ` Warner Losh
2024-03-14 20:13       ` Daniel Tameling
2024-03-14 21:09         ` Chet Ramey
2024-03-14  8:31 ` John Cowan
2024-03-14 15:50 ` Warner Losh
2024-03-14 16:50   ` segaloco via TUHS [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='Azv75tC6fOS8CJYVWoM24u5cIlMLndv8etz8BChmUQOXEio5VmzYAnWalhdpp4oCRK4V83OUphO-wkGtZPN6qOIxNNdEltOJrLen00sCX3Y=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).