From: Eric Kimminau <eak@cygnus.detroit.sgi.com>
To: Chad McDaniel <chadm@sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Challenge S
Date: Thu, 07 Aug 1997 10:03:28 -0400 [thread overview]
Message-ID: <33E9D5B0.18B77AE6@cygnus.detroit.sgi.com> (raw)
In-Reply-To: x1jyb6eyivu.fsf@unhinged.engr.sgi.com
Chad McDaniel wrote:
>
> Does anyone have any ideas about SGI-Linux on a Challenge S? As I
> understand it a Challenge S is basically an Indy without video and an
> extra SCSI controller. Plus, costomers with them aren't concerned
> about video or getting X to run & therefore SGI-Linux would be
> considered 'done' on them a bit sooner than the full Indy version.
>
> Is Linux run much on server-only systems?
>
> --
> -chad
I think it would be a great application but Linux is sorely missing a
very important piece - lockd for NFS.
--
Eric Kimminau System Engineer/RSA
eak@detroit.sgi.com Silicon Graphics, Inc
Voice: (248) 848-4455 39001 West 12 Mile Rd.
Fax: (248) 848-5600 Farmington, MI 48331-2903
VNet Extension - 6-327-4455
"I speak my mind and no one else's."
http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html
When confronted by a difficult problem, solve it by reducing
it to the question, "How would the Lone Ranger handle this?"
Windows 95: n.
32 bit extensions and a graphical shell for a 16 bit patch to an
8 bit operating system originally coded for a 4 bit microprocessor,
written by a 2 bit company that can't stand 1 bit of competition.
Author unknown.
next prev parent reply other threads:[~1997-08-07 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-06 23:46 Challenge S Chad McDaniel
1997-08-07 14:03 ` Eric Kimminau [this message]
1997-08-07 14:35 ` Mike Shaver
1997-08-07 14:51 ` Eric Kimminau
1997-08-07 19:43 ` Miguel de Icaza
1997-08-07 20:43 ` Alan Cox
1997-08-07 20:39 ` Eric Kimminau
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=33E9D5B0.18B77AE6@cygnus.detroit.sgi.com \
--to=eak@cygnus.detroit.sgi.com \
--cc=chadm@sgi.com \
--cc=eak@detroit.sgi.com \
--cc=linux@cthulhu.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