From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] A repository with 44 years of Unix evolution gets the MSR '15 Best Data Showcase Award
Date: Thu, 21 May 2015 11:49:01 -0400 [thread overview]
Message-ID: <CAC20D2PaT_724Z3z+7HWwMmJ3ud7GYyj2JRMJdMe3uicskfv1Q@mail.gmail.com> (raw)
In-Reply-To: <b0201a671a073e2c210556ffeaf7582c.squirrel@www.ccil.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
below.
On Thu, May 21, 2015 at 11:09 AM, <cowan at ccil.org> wrote:
> It might be possible to get the vanilla-from-AT&T System V Releases 1-3
> freely licensed, though Novell is presumably still making money from AIX,
> which descends from SVR3.
>
Hmm ..I thought all of the majors >>except<< for DEC bought out their
licenses at some point. I admit I've forgotten the specifics, but that
is my recollection.
> SVR4 has proprietary Microsoft (Xenix) and
> SunOS (Oracle) code in it, plus being the ancestor of still-current HP/UX.
>
HP/UX is an SVR3 & OSF/1 ancester. Solaris is SVR4. In fact it was the
SVR4 license and deal between Sun and AT&T) that forced the whole OSF
creation. One of the "principles" of the OSF was "Fair and Stable" license
terms.
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.
> 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.
> is almost certainly too much work for anyone to want to undertake today.
>
Agreed, unless there is a clear statement from the owners, it's going to
be hard; which is a shame from a historical stand point, but I agree.
C
lem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150521/59f51b7e/attachment.html>
next prev parent reply other threads:[~2015-05-21 15:49 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 [this message]
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
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=CAC20D2PaT_724Z3z+7HWwMmJ3ud7GYyj2JRMJdMe3uicskfv1Q@mail.gmail.com \
--to=clemc@ccc.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).