From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Open Sourcing IRIX?
Date: Tue, 28 Nov 2006 20:12:58 +1300 [thread overview]
Message-ID: <200611282012.58681.wes.parish@paradise.net.nz> (raw)
In-Reply-To: <8dd2d95c0611270641v289bf26ag9bbd2b5310b9fc60@mail.gmail.com>
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
>
> On 11/26/06, Paul Duffy <dubhthach at compsoc.nuigalway.ie> wrote:
> > Highly unlikely. After all they didn't buy out their Unix license like
> > Sun did. IRIX has been basically abandoned by SGI which is a pity.
> > However their is quite an IRIX user community at Nekochan with 1500
> > members on the forums: http://forums.nekochan.net/index.php
> >
> > Nekoware as it called is probably the best repositry of
> > freeware/opensource software out their for IRIX these days. Even SGI's
> > own freeware site points to them.
> >
> > -Paul
> >
> > "There is no greater sorrow then to remember times of happiness when
> > miserable" -- Dante "The Inferno"
> >
> > On Sun, 26 Nov 2006, Lord Doomicus wrote:
> > > Since SGI is EOL'ing IRIX at the end of the year, has anyone asked them
> > > if they would donate it's source ( under some sort of OSI license of
> > > course ) to the UNIX archive?
> > >
> > > Or is there too much SysV code in it?
> > >
> > > It would be cool to have easy access to the older IRIX versions for
> > > older SGI hardware.
> > >
> > > - Derrik
> > >
> > > Derrik Walker v2.0, RHCE
> > > lorddoomicus at mac.com
> > > http://www.doomd.net
> > >
> > > ... I am using an Apple Macintosh to design the Cray-3 supercomputer.
> > > -- Seymour Cray, 1986
> >
> > _______________________________________________
> > TUHS mailing list
> > TUHS at minnie.tuhs.org
> > https://minnie.tuhs.org/mailman/listinfo/tuhs
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
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.
next prev parent reply other threads:[~2006-11-28 7:12 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 [this message]
2006-11-28 13:17 ` Michael Kerpan
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=200611282012.58681.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).