The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Source code abundance?
Date: Sun, 05 Mar 2017 18:54:28 +0100	[thread overview]
Message-ID: <58bc50d4.JPVfFYF8i6in8XO1%schily@schily.net> (raw)
In-Reply-To: <20170304153927.9EAB018C08D@mercury.lcs.mit.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

jnc at mercury.lcs.mit.edu (Noel Chiappa) wrote:

>     > From: Wesley Parish
>
>     > I think the best thing for all would be the release of the Unix SysV
>     > source trees under a suitable open source license.

> Any volunteers to make something actually happen?

As mentioned before, Sun in theory had the right, but this did not include the 
networking code and code that includes code from Xenix (e.g. ls.c).

Now that Oracle bought Sun, there is few chance even for that because Oracle is 
not known to be OSS friendly.

The other rights owner was SCO....

SCO has been OSS friendly. SCO created the historical UNIX license and a bit
later, I was able to convince SCO to make SCCS OpenSource and got a "final" 
OK in April 2001. But in May 2001, SCO was sold to Caldera Linux and the new
owner was not OSS friendly and canceled the agreement.

This caused a delay for making SCCS OpenSource, as I now had to convince Sun 
and succeeded in December 2006.

Now that a judge ignored the contract between Novell and SCO and followed the 
oral claims from a Novell employee, it seems that somebody would need to 
convince Novell. I doubt that this will have a chance to work.


Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/


  parent reply	other threads:[~2017-03-05 17:54 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 15:39 Noel Chiappa
2017-03-04 16:02 ` Jason Stevens
2017-03-04 17:53 ` Jacob Goense
2017-03-04 18:37   ` Steve Nickolas
2017-03-04 18:38     ` Ron Natalie
2017-03-04 20:39   ` Cory Smelosky
2017-03-04 21:05     ` Jacob Goense
2017-03-05 17:54 ` Joerg Schilling [this message]
2017-03-05 18:24   ` Mutiny 
  -- strict thread matches above, loose matches on Subject: below --
2017-03-08 12:26 Doug McIlroy
2017-03-03 20:06 Noel Chiappa
2017-03-03 20:28 ` Clem Cole
2017-03-03 23:12   ` Larry McVoy
2017-03-03 23:56   ` Wesley Parish
2017-03-04  0:29     ` Steve Nickolas
2017-03-04  1:01     ` Henry Bent
     [not found]       ` <CAH1jEzZPonQuq_4YJWN=cpaB9J8q2+TU-zRWx+Bg+29SUvfOVQ@mail.gmail.com>
2017-03-04  3:23         ` Nick Downing
2017-03-04 10:04   ` Joerg Schilling
2017-03-04 16:28     ` Clem Cole
2017-03-04 16:34       ` Clem Cole
2017-03-05 19:15       ` Joerg Schilling
2017-03-05 19:25         ` Warner Losh
2017-03-05 19:55           ` Clem Cole
2017-03-06  9:35             ` Joerg Schilling
2017-03-06  0:13         ` Josh Good
2017-03-05 15:44     ` Larry McVoy
2017-03-05 18:26       ` Joerg Schilling
2017-03-05 18:55         ` Larry McVoy
2017-03-05 19:10           ` Joerg Schilling
2017-03-05 21:36             ` Larry McVoy
2017-03-05 22:03               ` Mutiny 
2017-03-01 18:01 Arthur Krewat
2017-03-01 18:07 ` Cory Smelosky
2017-03-01 18:13 ` Henry Bent
2017-03-01 18:27   ` Steve Nickolas
2017-03-01 19:18     ` Arthur Krewat
2017-03-01 19:25       ` Henry Bent
2017-03-01 19:29         ` Steve Nickolas
2017-03-01 19:32           ` Henry Bent
2017-03-01 19:49           ` Random832
2017-03-01 19:51             ` Warner Losh
2017-03-01 20:18             ` Joerg Schilling
2017-03-01 20:28           ` Clem Cole
2017-03-01 20:32             ` Warner Losh
2017-03-02 13:55             ` Paul Ruizendaal
2017-03-02 14:15               ` Jim Capp
2017-03-02  1:22 ` Jason Stevens
2017-03-02  6:50   ` Cory Smelosky
2017-03-02 13:36     ` Arthur Krewat
2017-03-04  3:29 ` Warren Toomey
2017-03-04 12:51   ` Arthur Krewat
2017-03-06 15:33 ` Angelo Papenhoff
2017-03-06 15:57   ` ron minnich
2017-03-06 16:20     ` Joerg Schilling
2017-03-06 22:52       ` Clem Cole
2017-03-07  6:52         ` Angelo Papenhoff
2017-03-07 13:25           ` Clem Cole
2017-03-06 16:21     ` Dan Cross
2017-03-06 16:45       ` Ron Natalie
2017-03-06 20:50         ` Dave Horsfall
2017-03-07 15:07           ` Ron Natalie
2017-03-07 15:13             ` Ron Natalie
2017-03-07 15:28               ` Larry McVoy
2017-03-07 19:44                 ` Ron Natalie
2017-03-06 18:00       ` ron minnich
2017-03-06 18:22         ` Dan Cross
2017-03-06 19:24         ` Nemo
2017-03-06 16:48     ` Clem Cole
2017-03-06 15:57   ` Clem Cole
2017-03-06 22:29     ` ron minnich
2017-03-06 22:59       ` Clem Cole
2017-03-06 23:31         ` Steve Johnson
2017-03-06 23:32           ` Cory Smelosky
2017-03-06 23:44             ` Steve Johnson
2017-03-06 23:48               ` Larry McVoy
2017-03-06 23:53                 ` Larry McVoy
2017-03-07  0:42             ` Warren Toomey
2017-03-07  0:33           ` Random832
2017-03-07  0:50         ` Clem Cole
2017-03-06 16:19   ` Jason Stevens
2017-03-06 19:06     ` Paul Ruizendaal
2017-03-06 20:32       ` ron minnich
2017-03-06 19:36     ` Warren Toomey
2017-03-06 20:17       ` Larry McVoy
2017-03-06 22:19         ` 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=58bc50d4.JPVfFYF8i6in8XO1%schily@schily.net \
    --to=schily@schily.net \
    /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).