The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Open Sourcing IRIX?
Date: Wed, 29 Nov 2006 20:04:10 +1300	[thread overview]
Message-ID: <200611292004.11077.wes.parish@paradise.net.nz> (raw)
In-Reply-To: <20061128134120.GB15984@ccil.org>

I would say that since the copyrights on the Santa Cruz Operation Unixware 
2.1.3 man pages are Novell's, that Novell actually has the copyrights.  Doing 
man pages seems to be the role of the source code maintainer.  Ergo, they 
didn't sell the copyrights, they sold a business opportunity.

groklaw.net has most of the info and analysis.

Wesley Parish

On Wednesday 29 November 2006 02:41, John Cowan wrote:
> Michael Kerpan scripsit:
> > That would never happen as it's SCO, not Novell, that owns System V
>
> Novell claims otherwise, that SCO is not the copyright owner but
> simply has a license to distribute.

-- 
Clinersterton beademung, with all of love - RIP James Blish
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.



  reply	other threads:[~2006-11-29  7:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 23:13 Lord Doomicus
2006-11-26 23:46 ` Michael Kerpan
2006-11-27  3:34 ` Paul Duffy
2006-11-27 14:41   ` Michael Kerpan
2006-11-28  7:12     ` Wesley Parish
2006-11-28 13:17       ` Michael Kerpan
2006-11-28 13:41         ` John Cowan
2006-11-29  7:04           ` Wesley Parish [this message]
2006-11-29  7:14             ` M. Warner Losh
     [not found]         ` <8B9D43B4-BCF3-4768-98D3-E2D77248458E@vetsystems.com>
2006-11-28 16:57           ` Michael Kerpan

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=200611292004.11077.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).