From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
Date: Tue, 7 Oct 1997 17:30:41 -0700 [thread overview]
Message-ID: <199710080030.RAA22931@fir.engr.sgi.com> (raw)
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx>
Miguel de Icaza writes:
...
> 3. Would it be possible to negotiate with SGI management
> the posibility of shipping the IRIX runtime libraries and
> the X server as found on IRIX with a Linux disrtibution?
...
Perhaps Ariel can check on this, but I suspect that there are licensing
problems. Each SGI system comes with a license to use one copy of the
software, where the fees which SGI must pay for each copy are bundled
in the cost of the system. That is, if you have a system, the system
includes the license. The licenses involved include more than just
the basic UNIX and NFS licenses. For example, the X server includes
optional Display Postscript support licensed from Adobe.
You could consider a scheme for automatically extracting the parts
you need from an IRIX distribution CD. That is, the system normally
comes with the CD for the software (although that may be lost for an older
system), and the user has the right to use the CD on that system.
If the linux installation were willing to mount that CD and pull out
the components, the user model would not be too awkward (although obviously
not as nice as having one distribution). If you were able to run the
IRIX inst on linux, you could extract it from the CD and ask it
to pull the files from the distribution. (There is a miniroot EFS file
system image on the CD, and inst is on that image; the rest of the distribution
is in packed data files decoded by inst.)
next prev parent reply other threads:[~1997-10-08 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-07 22:41 More Linux/SGI status Miguel de Icaza
1997-10-07 23:28 ` Ralf Baechle
1997-10-07 23:28 ` Ralf Baechle
1997-10-07 23:56 ` Ariel Faigon
1997-10-07 23:56 ` Ariel Faigon
1997-10-08 7:39 ` Alan Cox
1997-10-08 17:46 ` William J. Earl
1997-10-08 17:46 ` William J. Earl
1997-10-08 0:30 ` William J. Earl [this message]
1997-10-08 7:32 ` Alan Cox
1997-10-08 7:32 ` Alan Cox
1997-10-16 4:48 ` Ralf Baechle
1997-10-16 13:07 ` Eric Kimminau
1997-10-16 15:39 ` Alex deVries
1997-10-16 19:08 ` Alan Cox
1997-10-16 19:08 ` Alan Cox
1997-10-16 20:16 ` Alex deVries
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=199710080030.RAA22931@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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