From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: rlane9@csc.com
Cc: linux@cthulhu.engr.sgi.com (SGI/Linux mailing list)
Subject: Re: Linux / freeware
Date: Thu, 4 Jun 1998 12:08:57 -0700 (PDT) [thread overview]
Message-ID: <199806041908.MAA42738@oz.engr.sgi.com> (raw)
In-Reply-To: <4A256619.002A27F8.00@cscmail.csc.com> from "rlane9@csc.com" at Jun 4, 98 05:42:13 pm
:
:I'm a SGI at CSC running a network of O2s, O200s and Onyx2s, plus a couple
:of Indys and a Challenge S, running 6.2, 6.3, 6.4 on the approriate
:hardware, plus 6.5B on one of the Indys. All up about 30 machines, and I
:have more or less BOFH level control of them. I've even got a gutless
:(R4000SC / 24bit / 32MB) Indy at home that I can explode at will, which
:is about to be upgraded from 6.2 -> 6.5B.
:
: What I was wondering was: is any of the above useful to you for either
:the Linux port, or freeware support. I am not an expert C programmer,
:but I'm not totally clueless, having ugrad C experience. I'm fairly
:advanced at SGI admin and support, and have Linux on PCs at home. I have
:fast-ish internet connectivity at work (512kB - which is quick for OZ)
:and will have a Linux PC sitting at an ISP shortly.
:
: I have the full SGI developer kit at work + gcc, with gcc at home,
:plus the chunks of IDO required to bootstrap gcc. I can even provide an
:Australian WWW mirror if that would be useful.
:
: I'd be fairly happy to bang my head against a wall trying to get Linux
:running on my Indy, and to help with testing IRIX apps under linux.
:There seems to be little point porting all the Irix apps to Linux with
:the associated licensing probs, when every SGI box comes with the base
:OS already.
:
:-------------------------------------------------------------------------
:Richard Lane, System Administrator
:CSC Australia - Major Defense Projects - Network Engineering
:CSC email: <rlane9@csc.com>
:-------------------------------------------------------------------------
:
:
[CCing the Linux list]
Dear Richard,
Thanks for the offers.
I'm signed on the web pages because I helped put them up
however, I'm swamped with "real" work and am no longer put
my time into coordinating the SGI/Linux port.
My best advice would be: please subscribe to the mailing list
install SGI/Linux on your Indy and communicate your experiences
and suggestions on the list. There are about 100 subscribers
most of them ouside SGI.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: rlane9@csc.com
Cc: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: Linux / freeware
Date: Thu, 4 Jun 1998 12:08:57 -0700 (PDT) [thread overview]
Message-ID: <199806041908.MAA42738@oz.engr.sgi.com> (raw)
Message-ID: <19980604190857.VkLP-BFMmPw6q8UyApQIFF1hfAEwuzgP992xkD-tj00@z> (raw)
In-Reply-To: <4A256619.002A27F8.00@cscmail.csc.com> from "rlane9@csc.com" at Jun 4, 98 05:42:13 pm
:
:I'm a SGI at CSC running a network of O2s, O200s and Onyx2s, plus a couple
:of Indys and a Challenge S, running 6.2, 6.3, 6.4 on the approriate
:hardware, plus 6.5B on one of the Indys. All up about 30 machines, and I
:have more or less BOFH level control of them. I've even got a gutless
:(R4000SC / 24bit / 32MB) Indy at home that I can explode at will, which
:is about to be upgraded from 6.2 -> 6.5B.
:
: What I was wondering was: is any of the above useful to you for either
:the Linux port, or freeware support. I am not an expert C programmer,
:but I'm not totally clueless, having ugrad C experience. I'm fairly
:advanced at SGI admin and support, and have Linux on PCs at home. I have
:fast-ish internet connectivity at work (512kB - which is quick for OZ)
:and will have a Linux PC sitting at an ISP shortly.
:
: I have the full SGI developer kit at work + gcc, with gcc at home,
:plus the chunks of IDO required to bootstrap gcc. I can even provide an
:Australian WWW mirror if that would be useful.
:
: I'd be fairly happy to bang my head against a wall trying to get Linux
:running on my Indy, and to help with testing IRIX apps under linux.
:There seems to be little point porting all the Irix apps to Linux with
:the associated licensing probs, when every SGI box comes with the base
:OS already.
:
:-------------------------------------------------------------------------
:Richard Lane, System Administrator
:CSC Australia - Major Defense Projects - Network Engineering
:CSC email: <rlane9@csc.com>
:-------------------------------------------------------------------------
:
:
[CCing the Linux list]
Dear Richard,
Thanks for the offers.
I'm signed on the web pages because I helped put them up
however, I'm swamped with "real" work and am no longer put
my time into coordinating the SGI/Linux port.
My best advice would be: please subscribe to the mailing list
install SGI/Linux on your Indy and communicate your experiences
and suggestions on the list. There are about 100 subscribers
most of them ouside SGI.
--
Peace, Ariel
next parent reply other threads:[~1998-06-04 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A256619.002A27F8.00@cscmail.csc.com>
1998-06-04 19:08 ` Ariel Faigon [this message]
1998-06-04 19:08 ` Linux / freeware Ariel Faigon
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=199806041908.MAA42738@oz.engr.sgi.com \
--to=ariel@oz.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=rlane9@csc.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