The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] A repository with 44 years of Unix evolution gets the MSR '15 Best Data Showcase Award
Date: Thu, 21 May 2015 20:17:20 -0400	[thread overview]
Message-ID: <20150522001720.GA23248@mercury.ccil.org> (raw)
In-Reply-To: <CAC20D2PaT_724Z3z+7HWwMmJ3ud7GYyj2JRMJdMe3uicskfv1Q@mail.gmail.com>

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

Clem Cole scripsit:

> Which begs a question - since Solaris was SVR4 based and was made freely
> available via OpenSolaris et al, does that not make SVR4 open?   I'm not a
> lawyer (nor play one on TV), but it does seem like that sets some sort of
> precedent.

The fact that a specific copy bears a specific license may affect the
license on later copies by a means such as the GPL, but can't possibly
affect earlier copies, which are still bound by the earlier grave and
perilous license.  So you can use any SVR4 bits that are still part of
OpenSolaris freely within the terms of the CDDL, but not so any other
SVR4 bits.

> > Scrubbing proprietary third-party code to make an open-source release
> > of any of these ancient versions, as had to be done for Solaris (and Java),
> 
> ​Interesting - how did they "scrub" SVR4 from it?   The whole idea was to
> take SVR4 and "enhance it" using the SVR4 API's.  ​

I wasn't speaking of SVR4, but other non-Sun cruft that accumulated
between SVR4 and Solaris 10.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
What has four pairs of pants, lives in Philadelphia,
and it never rains but it pours?
        --Rufus T. Firefly



  parent reply	other threads:[~2015-05-22  0:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 20:07 Diomidis Spinellis
2015-05-19  9:24 ` Tom Ivar Helbekkmo
2015-05-19 10:04   ` Erik E. Fair
2015-05-19 13:19     ` Jacob Goense
2015-05-19 13:48       ` Steffen Nurpmeso
2015-05-19 14:36         ` SPC
2015-05-19 15:55   ` Warner Losh
2015-05-19 16:48     ` Tom Ivar Helbekkmo
2015-05-19 17:30       ` Clem Cole
2015-05-19 18:06         ` Tom Ivar Helbekkmo
2015-05-19 18:55         ` cowan
2015-05-20  3:07           ` Andy Kosela
2015-05-19 14:53 ` Clem Cole
2015-05-21  1:42 ` Derrik Walker v2.0
2015-05-21 11:50   ` Diomidis Spinellis
2015-05-21 15:09     ` cowan
2015-05-21 15:49       ` Clem Cole
2015-05-21 17:03         ` Jacob Ritorto
2015-05-21 18:04           ` Clem Cole
2015-05-25 16:46             ` Mary Ann Horton
2015-05-25 17:21               ` John Cowan
2015-05-25 21:15               ` Cory Smelosky
2015-05-26 17:55               ` Scot Jenkins
2015-05-29 14:14                 ` Mary Ann Horton
2015-05-22  0:17         ` John Cowan [this message]
2015-05-26 19:12   ` Doug McIntyre
2015-05-21 19:54 ` scj
2015-05-19 15:40 Doug McIlroy
2015-05-19 16:26 ` cowan
2015-05-19 17:29   ` Doug McIlroy
2015-05-21 19:41     ` scj
2015-05-25 19:05 Noel Chiappa
2015-05-26 10:07 Berny Goodheart

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=20150522001720.GA23248@mercury.ccil.org \
    --to=cowan@mercury.ccil.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).