From: "William J. Earl" <wje@fir.engr.sgi.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: ariel@cthulhu.engr.sgi.com, miguel@nuclecu.unam.mx,
linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
Date: Wed, 8 Oct 1997 10:46:29 -0700 [thread overview]
Message-ID: <199710081746.KAA23629@fir.engr.sgi.com> (raw)
In-Reply-To: <m0xIqiF-0005FiC@lightning.swansea.linux.org.uk>
Alan Cox writes:
> > My take on this is that since whoever bought that Indy
> > already paid for the OS including the X server and other
> > binaries there should be no reason why not to allow
> > them to run it on top of linux.
>
> Thats simple until someone builds a clone SGI box. RedHat rpms
> actually have some provision for a tool called rhmask which
> requires you have some "original" to generate the new rpm. Anyway
> we don't want to encourage folks not to make the Linux version
> kick the backside of any SGI original item..
It makes no sense to clone an SGI box, since there is no
long-term standard hardware profile. That is, the combination
of hardware and system software provides a consistent model, but
the hardware/software interface changes each generation, both
in graphics and in I/O. For people building MIPS-based linux boxes,
starting with the XFree86 source base, and adding good OpenGL support,
is a better model than trying to use Xsgi. Using Xsgi (and libGL.so)
is simply an expedient way to get graphics support for linux on an
SGI box.
WARNING: multiple messages have this Message-ID (diff)
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ariel@cthulhu.engr.sgi.com, miguel@nuclecu.unam.mx,
linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
Date: Wed, 8 Oct 1997 10:46:29 -0700 [thread overview]
Message-ID: <199710081746.KAA23629@fir.engr.sgi.com> (raw)
Message-ID: <19971008174629.goqfepBTj-s0aIzO6dhjNIKLelhlCoBpWPIgjMpWsk4@z> (raw)
In-Reply-To: <m0xIqiF-0005FiC@lightning.swansea.linux.org.uk>
Alan Cox writes:
> > My take on this is that since whoever bought that Indy
> > already paid for the OS including the X server and other
> > binaries there should be no reason why not to allow
> > them to run it on top of linux.
>
> Thats simple until someone builds a clone SGI box. RedHat rpms
> actually have some provision for a tool called rhmask which
> requires you have some "original" to generate the new rpm. Anyway
> we don't want to encourage folks not to make the Linux version
> kick the backside of any SGI original item..
It makes no sense to clone an SGI box, since there is no
long-term standard hardware profile. That is, the combination
of hardware and system software provides a consistent model, but
the hardware/software interface changes each generation, both
in graphics and in I/O. For people building MIPS-based linux boxes,
starting with the XFree86 source base, and adding good OpenGL support,
is a better model than trying to use Xsgi. Using Xsgi (and libGL.so)
is simply an expedient way to get graphics support for linux on an
SGI box.
next prev parent reply other threads:[~1997-10-08 17:47 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 [this message]
1997-10-08 17:46 ` William J. Earl
1997-10-08 0:30 ` William J. Earl
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=199710081746.KAA23629@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ariel@cthulhu.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