From: offer@sgi.com (richard offer)
To: linux@morgaine.engr.sgi.com
Subject: Re: Good news: no more begging for HW
Date: Tue, 17 Jun 1997 09:23:12 -0700 [thread overview]
Message-ID: <9706170923.ZM15068@sgi.com> (raw)
In-Reply-To: "David S. Miller" <davem@jenolan.rutgers.edu> "Re: Good news: no more begging for HW" (Jun 16, 10:01pm)
* $ from davem@jenolan.rutgers.edu at "16-Jun:10:01pm" | sed "1,$s/^/* /"
*
*
* From: ariel@yon.engr.sgi.com (Ariel Faigon)
* Date: Mon, 16 Jun 1997 18:06:41 -0700 (PDT)
*
* I cannot promise anything since there may be some oversubscription
* to the service :-)
*
* I think the fairest way would be to publish all these requests on
* this forum and have the people who care (us) vote on who should get
* them. I certainly don't want to be the fascist person who decides
* who gets what.
*
* Before this gets out of control, I just want to express one sentiment
* of high caution.
*
* Although it may seem desirable to contribute most of the donation
* hardware to kernel level hackers, this can be a mistake in the making.
* At this stage in the game it is just as important to get userland/libc
* developers machines.
*
* Therefore I suggest that at least one person who knows GNU libc,
* binutils, _and_ gcc internals backwards and forwards be on the top of
* the donation list.
We need an X server if we are ever going to get it usable by real users---or is
everyone assuming its for headles machines only. I would put an X server above
most applications in terms of priority (just below native gcc/libc).
Perhaps one ought to go to Xfree86/someone who knows our hardware (not to start
this thread all over again).
This should be very tighly focused, since an X server is a lot of work and we
need a lot of them, one per board (okay in version one we could only support
1280x1024x8, but that seems a waste of all our spiffy hardware).
I used to have a contact in Xfree86, but I haven't heard from him for a while.
If someone takes the server, I'll try and get the clients libraries done
(assuming that I can get remote access to a box).
richard.
____________________________________________________________________
A Guest Signature from Laurent Duperval <Laurent at Grafnetix.com>
I don't understand why people break up and then get back together.
It's like going to the fridge, taking a carton of milk that has
gone bad, then saying: "I'll put it back and see if it's better
tomorrow."
next prev parent reply other threads:[~1997-06-17 16:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199706170046.CAA17216@informatik.uni-koblenz.de>
1997-06-17 1:06 ` Good news: no more begging for HW Ariel Faigon
1997-06-17 1:06 ` Ariel Faigon
1997-06-17 1:53 ` Alex deVries
1997-06-17 2:01 ` David S. Miller
[not found] ` <davem@jenolan.rutgers.edu>
1997-06-17 16:23 ` richard offer [this message]
1997-06-17 17:10 ` Miguel de Icaza
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:53 ` richard offer
1997-06-17 18:00 ` Miguel de Icaza
1997-06-17 18:30 ` Martin Knoblauch
1997-06-17 18:45 ` David S. Miller
1997-06-18 0:00 ` John Wiederhirn
1997-06-18 0:15 ` richard offer
1997-06-18 0:32 ` Ralf Baechle
1997-06-18 0:32 ` Ralf Baechle
1997-06-19 19:23 ` William J. Earl
1997-06-18 0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18 0:34 ` Ariel Faigon
1997-06-18 16:28 ` Christopher W. Carlson
1997-06-18 19:30 ` Nigel Gamble
1997-06-18 2:47 ` Good news: no more begging for HW Miguel de Icaza
1997-06-18 12:38 ` William J. Earl
1997-06-18 12:38 ` William J. Earl
1997-06-18 6:37 Larry McVoy
1997-06-18 6:37 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
1997-06-17 6:22 Larry McVoy
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 16:08 ` Miguel de Icaza
1997-06-17 2:25 Larry McVoy
1997-06-17 2:25 ` Larry McVoy
1997-06-17 5:31 ` Alex deVries
1997-06-16 23:25 Ariel Faigon
1997-06-17 3:59 ` Christopher W. Carlson
1997-06-17 8:15 ` Martin Knoblauch
1997-06-17 16:18 ` Miguel de Icaza
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=9706170923.ZM15068@sgi.com \
--to=offer@sgi.com \
--cc=linux@morgaine.engr.sgi.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