From: ralf@uni-koblenz.de
To: Ariel Faigon <ariel@cthulhu.engr.sgi.com>
Cc: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>,
adevries@engsoc.carleton.ca,
Richard Hartensveld <richard@infopact.nl>
Subject: Re: linus.linux.sgi.com
Date: Fri, 15 Jan 1999 22:59:18 +0100 [thread overview]
Message-ID: <19990115225918.25643@uni-koblenz.de> (raw)
In-Reply-To: <199901151909.LAA23245@oz.engr.sgi.com>; from Ariel Faigon on Fri, Jan 15, 1999 at 11:09:53AM -0800
On Fri, Jan 15, 1999 at 11:09:53AM -0800, Ariel Faigon wrote:
> Looks like I need to give a status update on linus.linux.sgi.com.
>
> First, let me tell you all that I'm really taken aback by this
> situation. I've seen postings on slashdot.org suggesting that
> SGI has taken this machine down because it is in bed with
> Microsoft etc. etc. and all kinds of negative speculation and
> nonsense. I was even contacted by the press on this (could
> you believe that :-) Let me make it very clear:
>
> 1) No one at SGI has taken this service down and
> guess what: we are going to bring it back up again.
>
> 2) The machine itself is not down. The problem is in the
> routing to the machine and from what I last heard,
> it seems to be a hardware problem.
The tracroute I just did looks like a) SGI's engineering pipe needs a
serious upgrade due to packet loss and b) there is a routing loop somewhere.
So if the router people can't fix it maybe moivng the machine to an address
which actually has a functional setup?
> 4) The timing when this thing decided to break (close to the
> announcement of the SGI Visual Workstation) is purely
> coincidental.
Seconded. SGI (and actually the whole industry) is _W_A_Y_ more OSS
friendly than /. rumors say.
Quite frankly, having to answer several private emails aobut this topic I'm
still surprised how much policital damage a stupid messed up route can
cause.
Ralf
next prev parent reply other threads:[~1999-01-15 22:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 18:24 linus.linux.sgi.com Alex deVries
1999-01-15 18:28 ` linus.linux.sgi.com Eric Kimminau
1999-01-15 18:44 ` linus.linux.sgi.com Richard Hartensveld
1999-01-15 19:09 ` linus.linux.sgi.com Ariel Faigon
1999-01-15 19:09 ` linus.linux.sgi.com Ariel Faigon
1999-01-15 21:29 ` linus.linux.sgi.com Alan Cox
1999-01-15 21:59 ` ralf [this message]
1999-01-16 3:21 ` linus.linux.sgi.com David S. Miller
1999-01-18 10:40 ` linus.linux.sgi.com Ariel Faigon
1999-01-18 10:40 ` linus.linux.sgi.com Ariel Faigon
1999-01-18 17:25 ` linus.linux.sgi.com Miguel de Icaza
1999-01-18 17:25 ` linus.linux.sgi.com Miguel de Icaza
1999-01-19 4:40 ` linus.linux.sgi.com Eric Kimminau
1999-01-19 5:19 ` linus.linux.sgi.com David S. Miller
1999-01-19 11:21 ` linus.linux.sgi.com dmanddmer
1999-01-19 15:30 ` linus.linux.sgi.com David Watters
1999-01-19 16:46 ` linus.linux.sgi.com Alex deVries
1999-01-19 15:05 ` linus.linux.sgi.com David Watters
1999-01-15 22:38 ` linus.linux.sgi.com Miguel de Icaza
1999-01-15 22:06 ` linus.linux.sgi.com William J. Earl
-- strict thread matches above, loose matches on Subject: below --
1999-01-28 22:07 linus.linux.sgi.com Ulf Carlsson
1999-01-23 2:07 linus.linux.sgi.com ralf
1998-06-14 20:35 linus.linux.sgi.com Alex deVries
1998-06-15 18:02 ` linus.linux.sgi.com Bob Mende Pie
1998-06-15 18:11 ` linus.linux.sgi.com 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=19990115225918.25643@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=richard@infopact.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.