From: madcrow.maxwell@gmail.com (Michael Kerpan)
Subject: [TUHS] Open Sourcing IRIX?
Date: Tue, 28 Nov 2006 08:17:43 -0500 [thread overview]
Message-ID: <8dd2d95c0611280517y7644e8f5x9249b1861be6a161@mail.gmail.com> (raw)
In-Reply-To: <200611282012.58681.wes.parish@paradise.net.nz>
That would never happen as it's SCO, not Novell, that owns System V
and SCO is a M$-funded anti-open source crusader.
On 11/28/06, Wesley Parish <wes.parish at paradise.net.nz> wrote:
> On Tuesday 28 November 2006 03:41, Michael Kerpan wrote:
> > As I said, IRIX itself is nothing but an obsolete kernel. It might be
> > cool for preservation purposes to have the code (and that's what TUHS
> > is all about)
> <snip>
>
> And that's what I for one want to see. The more Un*x branches we have in
> preservation for study purposes, the less chance a software pirate like The
> Societe Commercial du Ondit (The Rumormongers Company) Group has of
> succeeding in meritless law suits.
>
> I think someone should ask Novell to consider declaring the Un*x SySVRx source
> tree available under the GPL or some such license. And releasing OSF/1 and
> such SVRx derivatives from requiring a Un*x source code license, if they want
> to release their ancient source trees for preservation purposes.
>
> It would be a fitting end to the AT&T Un*x role in computer science history.
>
> Wesley Parish
next prev parent reply other threads:[~2006-11-28 13:17 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 [this message]
2006-11-28 13:41 ` John Cowan
2006-11-29 7:04 ` Wesley Parish
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=8dd2d95c0611280517y7644e8f5x9249b1861be6a161@mail.gmail.com \
--to=madcrow.maxwell@gmail.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).