HDTenEightyP/NetNews huggingface dataset:
From: olson@anchor.esd.sgi.com (Dave Olson)
Subject: Re: Should I Get a Barracuda for My Indigo?
Keywords: disk drive
Organization:  Silicon Graphics, Inc.  Mountain View, CA
Date: Wed, 18 Nov 92 23:13:47 GMT

In <1992Nov18.192526.9440@ringer.cs.utsa.edu> senseman@ricky.brainlab.utsa.edu (David M. Senseman) writes:

| SGI machines in general and Indigos in particular seem to work
| well with disk drives from Seagate. Now Seagate has introduced
| a really interesting drive -- the BARRACUDA -- 2.1 GB in a 3 1/2
| inch form factor. It should be much faster than the IBM drive
| SGI is currently shipping since it comes with a 1,024KB cache, 
| giving it an 8 ms access time :-) Best of all, Seagate has priced
| them very competitively ($2,495 in OEM quantitites).
| 
| Has anyone (Dave?) had a chance to look at the ST12550 (Barracuda)
| and/or the other members of the family (i.e. ST12400, ST31200)?

No.  I'd be very surprised if you could go order one and actually
get it.  I can't say much more because of non-disclosure agreements,
but think about how long it was between announcements of 3.5" 1+GB
drives and general availability...

| If someone did buy an ST12550, and put it in an R4K Indigo,
| could the Indigo's SCSI contoller take advantage of the drive's
| support for FAST and FAST/WIDE SCSI-2?

Indigo (all r4k and all the newer r3k)  has a SCSI chip capable of fast
SCSI, but the DMA controller can't handle the full 10 MB a second the
chip is capable of.  We can only sustain 5.5 MB/s.  Future machines
have a newer DMA controller that allows for 10MB/s.  However, even at
5.5MB/s, we are still faster than the drive rate of any *single* SCSI
drive, although drives are fast approaching that.

This is something I've mentioned a number of times, and have really
tried to beat into our sales and marketing folks, since visions of 10
MB/s sustained seem to keep dancing through their heads ;)
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Newsgroups: comp.sys.sgi
From: dhinds@leland.Stanford.EDU (David Hinds)
Subject: Re: More Exabyte 8500c (and SCSI) questions/woes
Organization: DSG, Stanford University, CA 94305, USA
Date: Fri, 20 Nov 92 05:25:01 GMT

Given that the 8mm tape drives with data compression seem to work on
SGI's, what about the 4mm (DAT) drives with compression?  Has anyone
tried one of these on an SGI?  Someone in my lab talked to a salesman
at Parity who claimed they worked; he also claimed an effective max
capacity with compression of 8GB per tape, which sounded too high to
me.

        - David Hinds
          dhinds@allegro.stanford.edu
Newsgroups: comp.sys.sgi
Subject: Reading stuff from the kernal
From: johns@io.datasys.swri.edu (Stephen Johns)
Date: 23 Nov 92 19:10:35 GMT
Organization: Southwest Research Institute, San Antonio

What is the best/approved way of programatically monitoring kernal performance?
I want to watch memory usage, CPU time and network load primarily.
Basically the stuff osview and sar do.  Is using the namelist stuff, ie
struct nlist nl[] = { {"_freemem"} etc.. }  nlist ( "/unix", nl );
ok?  recommented? and if so, where can I find all the availale names
like "_freemem"?

Newsgroups: comp.sys.sgi
From: sherborb@rwep03.dnet.roche.com (Brad Sherborne Ext. 2375)
Newsgroups: comp.sys.sgi
Subject: Re: HP Dat Drive Question
Date: 20 Nov 92 10:24:03 GMT

Unfortunately I don't have the header so I can't
respond directly to the sender ...

but they wrote;

> With the installation documentation are instructions to reconfigure
> the kernel, more or less copying the paragraph,
> in /usr/sysgen/master.d/tpsc, beginning with -
> 
> {DATTAPE, TPDAT,2,8,"HP","HP35480A",0,0,{0,0,0,0},
> 
> And replace the first line in the new paragraph with the line
> below:
> 
> {DATTAPE, TPDAT,2,8,"HP","HP35480A",0,0,{0,0,0,0},
> 
> This works fine, the system knows now knows about the drive.
  
I believe the first line shoudl be different (:-)) and should be

 { DATTAPE, TPDAT, 7, 6, "ARCHIVE", "Python", 0, 0, {0, 0, 0, 0},

I believe the MTCAN_AUDIO reference should be deleted.

... as to the DIP switch settings, I'm currently using;

    Switch 3 4 5 6 7 8
    Set    0 0 0 1 1 0

and have no problems (on a 4D/440 VGX).


All the best




Brad

Brad Sherborne, Roche Products Ltd, PO Box 8, Welwyn
Garden City, HERTS AL7  3AY, England.

Email: sherborb@rwep03.dnet.roche.com
Tel:   +44-707-328128 x2375
Fax:   +44-707-373504
Home:  +44-707-377829
Newsgroups: comp.sys.sgi
From: lamaster@pioneer.arc.nasa.gov (Hugh LaMaster)
Subject: Announcements
Organization: NASA Ames Research Center, Moffett Field, CA
Date: Mon, 16 Nov 1992 21:56:23 GMT

Is there a newsgroup where SGI posts its recent announcements?
It would be nice to be able to get these off the net.


-- 
  Hugh LaMaster, M/S 233-9,     UUCP:      ames!lamaster
  NASA Ames Research Center     Internet:  lamaster@ames.arc.nasa.gov
  Moffett Field, CA 94035-1000  Or:        lamaster@george.arc.nasa.gov 
  Phone:  415/604-1056                     #include <usenet/std_disclaimer.h> 
Xref: sparky comp.sys.sgi:16506 comp.emacs:3566 gnu.emacs.help:4819
From: shankar@PROBLEM_WITH_INEWS_DOMAIN_FILE (Shankar Unni)
Newsgroups: comp.sys.sgi,comp.emacs,gnu.emacs.help
Subject: Re: Problem installing emacs on SGI
Date: 16 Nov 92 20:43:20 GMT
Organization: Silicon Graphics, Inc.
NNTP-Posting-Host: boris.wpd.sgi.com
X-Newsreader: Tin 1.1 PL5

R Moxley (2064aw@gmuvax2.gmu.edu) wrote:

>           Dumping under names xemacs and emacs-18.56.9
>           unexec: 3 sections found instead of 10.
>           *** Termination code 139

Geez, 18.*56*?! That's pretty old stuff there..

You should be able to get the unexmips.c from the 18.59 distribution
and plug it in place, if you really want to try and build 18.56.

A better thing to do would be to pick up Emacs 18.59 from
"prep.ai.mit.edu" (via anon FTP in /pub/gnu, I think).  It should
build right out of the box (after you set up the root Makefile and
config.h according to the instructions).
--
Shankar Unni				E-Mail:	shankar@sgi.com
Silicon Graphics Inc.			Phone:	+1-415-390-2072
Newsgroups: comp.sys.sgi
From: spiff@bert.eecs.uic.edu (Jason Leigh)
Subject: Need help resizing windows
Organization: University of Illinois at Chicago
Date: Tue, 24 Nov 1992 04:06:14 GMT


Hi, I've noticed that by setting prefsize I can produce a window of
a desired size.  But the window produced as a result looses its resize
widgets.  Is there a way I can open a window of a set size and still
use the widgets to resize the window at a later time?

Thanks.

Jason Leigh


-- 
---------------------------------------------------------  ___
| The opinions expressed above are necessarily those of | \\     \\  | \\
| the Electronic Visualization Laboratory, NAAAT!       |  \\---  \\ |  \\
| Send Replies to: spiff@bert.eecs.uic.edu (Jason Leigh)|   \\____ \\|   \\____
Newsgroups: comp.sys.sgi
From: steve@dewey.tamu.edu (Steve Rikli)
Subject: FAQ:  Your input still needed
Keywords: FAQ
Organization: College of Architecture, Texas A&M University
Date: Mon, 16 Nov 1992 16:42:24 GMT

The work on the comp.sys.sgi FAQ is progressing, but we still need your
input.

We're still gathering info, articles, questions (& answers) for inclusion
in the c.s.sgi FAQ, and we want _your_ submissions.  Thanks to everyone
who has kindly contributed things all ready!

To submit anything to the FAQ, email it to:

			sgi-faq@archone.tamu.edu

I'm sorry that I haven't supplied an auto-reply yet, and we can't guarantee
that everything we receive will be included in the FAQ, but I promise a real
person will read and review your submission.

cheers,
sr.
--
|| Steve Rikli 	           |||  Visualization Lab               ||
|| steve@archone.tamu.edu  |||  Texas A&M University            ||
|| 409-845-3465            |||  College Station, TX  77843-3137 ||
Newsgroups: comp.sys.sgi
From: hillig@U.Chem.LSA.UMich.EDU (Kurt Hillig)
Subject: newgrp / multgrps and NIS
Date: Mon, 16 Nov 92 18:07:32 EST
Organization: Department of Chemistry, University of Michigan, Ann Arbor
Keywords: newgrps multgrps NIS YP

I've just installed a big molecular modeling package on our 4D/360
(Irix 4.0.5), which is both a workstation and our NFS/NIS (YP) server.

For political and economic reasons, not all users on all workstations
are allowed to use this.  My plan was to create a "molmodel" group in
/etc/group.yp, use NIS to propagate this to all of the workstations,
and have authorized users either "newgrp" or "multgrps" before trying
to run the software.

To my dismay, I find that neither newgrp nor multgrps seems to believe
in NIS.  I don't really want to have to synchronize the /etc/group file
on a bunch of machines to make this work (since the membership in the
molmodel group seems to change almost daily - at least until everyone
settles on just who is paying how much for their share of the license ;-)

Is this really the way it's supposed to work?  I can't imagine why these
commands should not work with NIS, and I can't believe I'm the only one
to try to use this sort of security (sic) scheme....  Should I be doing
this some other way?

Feel free to respond to the newsgroup, as I DO read it daily!

-- 
      Kurt Hillig
   Dept. of Chemistry      I always tell the     khillig@umich.edu
 University of Michigan     absolute truth    Telephone (313)747-2867
Ann Arbor, MI  48109-1055    as I see it.    hillig@chem.lsa.umich.edu
Newsgroups: comp.sys.sgi
From: isc30092@nusunix1.nus.sg (CHOO GING YANG)
Newsgroups: comp.sys.sgi
Subject: C++ or Motif or X ?
Date: 22 Nov 92 06:31:49 GMT
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]


hi netters ....

	I encountered a very strange error recently.

	I ran into a runtime error when I was on a Silicon Graphics Indigo 
	using C++ 2.1.1, X11R4 and Motif.  After much tracing, I discovered 
	the Motif function "XmStringCreateSimple" routine was giving the 
	segmentation fault message.

	I later ported the SAME program over to a Sun Sparc 2 using C++ 2.1, 
	X11R5 and Motif. it ran smoothly.  Anybody out there encounter any 
	similar problem?  

cgy@kris.iscs.nus.sg
Newsgroups: comp.sys.sgi
From: ledwards@leland.Stanford.EDU (Laurence James Edwards)
Subject: reading audio CD's with CD-ROM drive
Organization: DSG, Stanford University, CA 94305, USA
Date: Mon, 23 Nov 92 23:50:16 GMT

I have a vague recollection that this was asked recently but I couldn't
find it looking through old articles. The question is: can one read
an audio CD using SGI's CD-ROM drive?

Larry Edwards
From: gmt@beach.cis.ufl.edu (Gary McTaggart)
Newsgroups: comp.sys.sgi
Subject: SGI FTP sites
Date: 17 Nov 92 11:15:16 GMT
Organization: Univ. of Florida CIS Dept.

Does anyone have a good list of FTP sites which may include software for
SGIs?


Thanks,
Gary McTaggart


Newsgroups: comp.sys.sgi
From: garvin@cfd.mae.ncsu.edu (Michael Garvin)
Subject: More Exabyte 8500c (and SCSI) questions/woes
Organization: North Carolina State University
Date: Thu, 19 Nov 1992 20:06:17 GMT

	I've also taken receipt of an Exabyte 8500c (compression) 8mm tape
drive, and it's giving me pains.  Following the instructions in Dave Olson's
posting of 17 Nov 92 (thanks for the info!) I reconfigured my kernel, altering
the tpsc config file to read:

        /* Entry for Exabyte 8500c - Michael Garvin, 11/19/92.  Copied entry
         * from 8500, changed "EXB-8500" to "EXB8500c", "{0x0, 0x14, 0x0, 0x0}"
         * to "{0x0, 0x14, 0x8c, 0x0}".
         * There are 3 densities, 8500 mode, 8200 mode, and 8500 mode with
         * compression, in order.
         */
        { EXABYTE8500, TP8MM, 7, 8, "EXABYTE", "EXB8500c", 6,
                "\40\4\16\0\200\7", {0x0, 0x14, 0x8c, 0x0},
          MTCAN_BSF|MTCAN_BSR|MTCAN_PREV|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
            MTCAN_SILI|MTCAN_CHTYPEANY|MTCAN_SETDEN|MTCAN_SPEOD|MTCAN_SYNC|
                MTCAN_SEEK,
          80, 4*60, 25*60, 5*60, 1024, 128*1024},

I installed the drive on controller 0, ID 7, and rebooted the new kernel.  I
then made the following devices:

	crw-r--r--   1 root     sys       23,241 Nov 19 14:13 nrtape
	crw-r--r--   1 root     sys       23,243 Nov 19 14:13 nrtapens
	crw-r--r--   1 root     sys       23,240 Nov 19 14:13 tape
	crw-r--r--   1 root     sys       23,242 Nov 19 14:30 tapens

The minor numbers were upped 16 from the default 224-227 to match the 8500c
(0x8c in the tpsc config file) entry.  I then tried tarring to the drive, which
died with the following error:

	tar: tape write error: I/O error

and produced the following console output (note the tape drive hiccuped first):

	WARNING: dma_map: address not word aligned
	sc0,7,0: cmd=0xA disconnected on non-word boundary (addr=C02185A9,
		0x0 left).  Resetting SCSI bus
	dks0d1s6: retrying request
	dks0d2s6: retrying request

Our setup is a Power Series 4D/440.  SCSI controller 0 has an internal 1.6 gig
system disk (ID 1), an Iris File on the rear external connector with four 2 gig
drives (IDs 2, 3, 4, and 5), an internal CD-ROM (ID 6), and the 8500c mounted
internally (ID 7).  We've also got a Jaguar differential SCSI controller with
four drives on each channel.

	My questions are: am I going too far with that SCSI chain?  I have a
sinking feeling that I'm pushing the length limit, giving me the error I saw
(although the 8500c failing might give me that).  Are my entries for the 8500c
in the tpsc config file correct?  Have I correctly made the devices (in
particular, did I get the minor number correct and do they correspond to the
8500c in compression mode)?  And finally, would someone have the correct density
to feed to BSD dump for this drive (I calculated something around 47.5 million,
which sounds wrong).  Thanks for any help, I'm banging my head at this point.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michael Garvin - Systems Programmer			garvin@mmrc.ncsu.edu
Mars Mission Research Center				(919) 515-5250 [Voice]
North Carolina State University				(919) 515-7968 [FAX]
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: CD-ROM Drive as CD Player
Date: 20 Nov 92 05:19:22 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <1992Nov20.014419.20593@ntuix.ntu.ac.sg> ghblee@ntuix.ntu.ac.sg (H B Lee) writes:
| I'm wondering if there's any software available which acts as a
| "control panel" for the CD-ROM drive so that I can use the drive
| as a CD Player.  System: 4D/35 running Irix 4.0.1.
	
	cdplayer.  Standard software in 401 and later.
	Also, in 405MM and later, cdman (aka datman -cd).
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
From: asgeir@viking.asd.sgi.com (Asgeir Eiriksson)
Newsgroups: comp.sys.sgi
Subject: Re: Help with GNU C/C++
Date: 18 Nov 1992 20:38:18 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA
NNTP-Posting-Host: viking.asd.sgi.com

In <jonv.9.0@bernard.pitzer.claremont.edu> jonv@bernard.pitzer.claremont.edu (Jon Vestal) writes:

>Hi,

>I have recently installed GNU C and can not get libg++ to compile.  I have 
>GNU C 2.3.1 and libg++ 2.2.  I configure for irix4d.  I am runing Indigos 
>with R3000 and Irix4.05.  Here is the error I get when trying to compile 
>libg++:

>cc: Error: no source file
>nm: Error: cannot open dummy.o
>nm: Error: cannot open dummy.o
>nm failed to find FUN in dummy.o!
>./utils/gen-params: -1: bad number
>*** Error code 1


From the g++ FAQ:
=================

20. I am having trouble building libg++-2.2 on Ultrix [and possibly other
    systems].  I get errors referring to "dummy.o".  Help!

(The errors on Ultrix end with somehting like

ldopen: cannot open dummy.o
nm: Error: cannot open dummy.o
ldopen: cannot open dummy.o
nm: Error: cannot open dummy.o
nm failed to find FUNC in dummy.o!
sh: -1: bad number
*** Error code 1

and there may be similar problems on other systems).

The fix for this is to make libg++ by saying "make CC=gcc".


Other hints:
============

 1) Did you run  'make install-fixincludes' ?

    - the rest of the compilation problems (to do with varargs) go away
      if you do this.


I'm still using gcc 2.2.2, and the above is sufficient to build gcc
and libg++.a 

'Asgeir
Newsgroups: comp.sys.sgi
From: atems@plasma.physics.wayne.edu (Dale Atems)
Subject: R4000 Indigo power-up problem
Summary: intermittent failure on power-up, no error messages
Organization: Wayne State University, Detroit, MI
Date: Sat, 21 Nov 1992 19:24:05 GMT

Hi everyone,

Our new R4000 Indigo occasionally fails to power up properly: the LED
on the front of the CPU box turns green immediately, flashes briefly
orange then turns solid orange. The chord ("tune") is never played and
the monitor screen remains blank. I plan to ask the TAC about this,
but I was wondering whether anyone here had any ideas about what could
be wrong.  I've checked the obvious things already: cables,
connections, seating of SIMMs.

Thanks in advance.

------
Dale Atems
Wayne State University, Detroit, MI
Department of Physics and Astronomy
atems@igor.physics.wayne.edu
Newsgroups: comp.sys.sgi
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: Unruly timed
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Mon, 16 Nov 1992 23:58:00 GMT

In article <1992Nov16.211019.20140@cis.uab.edu>, jpg@nrc3d.nrc.uab.edu (Jill Gemmill) writes:
> 
> PROBLEM:  machines synchronizing their clocks keep losing time
> 	(about 5 minutes per day).
> SETUP:
> 	- We have three SGI machines, each running 4.0.5
> 		(names: nrc3d, clsm and nrc-iris)
> 	- The current "timed.options" file on machine nrc3d looks like this:
> 		-P /usr/tmp/.timetrim -F localhost clsm nrc-iris.nrc.uab.edu
> 		(each machine lists itself and the other two as
> 			trusted time machines)
> 	- Each timed starts with the -M option, which SGI writes into
> 		the "network" init script.
> SO:
> 	The machines do keep the same time, but the time drifts backwards
> 	about 5 minutes a day.  Why does this happen, and what can I do
> 	to make it stop??


Please note that "-M" really means "be moderator", not "master."

In the absense of an external standard, all that timed or any other
time gadget can do is combine one or more clocks and hope the result
is better.  

If one of your 3 machines is slow, time on the network will slip.
The most common thing that makes time that slow is lots of "kernel
printf's", because everything including the clock stops while the
kernel is complaining.

Consider also the contents of /usr/tmp/.timetrim on each machine.
Those files contain the recent long term average corrections needed
by each system.

To fix the problem I would:

    I. on each of the 3 systems
	1. delete /usr/tmp/.timetrim
	2. restart timed--either reboot or 
		killall -v timed
		timed -M `cat /etc/config/timed.options`

    II. every day, set the time on one of the 3 machines with the date
	command

(I) will make the three machine forget that they have been taught to
be slow.

(II) should gradually teach them to be faster.  The need to be faster
should gradually appear in each machine's /usr/tmp/.timetrim.


It is also possible use `timeslave` or to port and use xnptd to
synchronize one of the 3 machines to an external clock, and then make
that one machine "free run" (-F) as a moderator of a group of one (i.e.
be a master), and distribute time to the other machines with timed.


Vernon Schryver,  vjs@sgi.com
Newsgroups: comp.sys.sgi
From: markb@neptune.gsfc.nasa.gov (Mark R. Baith)
Subject: Bad PC/TCP term emulation under 4.05
Organization: NASA Code 971, Oceans & Ice Branch
Date: Mon, 16 Nov 1992 19:31:32 GMT

Have any users of the pc/tcp software noted problems with their terminal
emulation under 4.01-4.05? Our version of pc/tcp (2.4) works fine
with 3.3.2, but is having problems with the higher revs of the OS.

-- 
                                    **************************************
                                    * Mark Baith GSC (301)286-5146       *
                                    * Oceans Computing Facility Code 971 *
                                    * NASA Goddard Space Flight Center   *
                                    **************************************
                                    * "markb@neptune.gsfc.nasa.gov"      *
                                    * "baith@ocean1.gsfc.nasa.gov"       *
                                    * "ocean2::baith"                    *
                                    **************************************
From: fred@poly2.nist.gov (Frederick R. Phelan Jr.)
Newsgroups: comp.sys.sgi
Subject: IrisGL to GLX changes
Date: 19 Nov 92 21:00:53 GMT

Hi,

Where can I find a definative list of the functions that are available in IrisGL,
but which can't be used in a mixed mode (GLX) application.

Fred Phelan
---
Fred Phelan
fred@poly2.nist.gov
/*___________________________________________________
   ____ __  ___  __    ___       ___        ___ 
  /__  /_/ /__  / /   /__/ /__/ /__   /    /__/ /\  /  
 /    / ( /__  /_/   /    /  / /___  /___ /  / /  \/
___________________________________________________*/
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: How to lower the default sound level in Indigo
Date: 24 Nov 92 02:07:25 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <1992Nov21.174742.15547@news.yale.edu> dcs@neutron.chem.yale.edu (Dave Schweisguth) writes:

| Dave Olson (olson@anchor.esd.sgi.com) wrote:
| : | >If you have 405F or later:
| : |                  ^^^^^^^^^^
| : |                  Hmmm....Is there now a 4.0.5G or are we up to "H" yet?
| : 
| : I said 'or later', because somebody always asks.  There is no G yet.
| : Sometime 'soon' (i.e., > 1 day, and less than 6 months) there will be.
| : It isn't clear yet just what will be in it, or which systems it will
| : be released for.
| 
| How about a 4.0.6, certified on all systems? 4.0.{2,3,4} were bad enough;
| 4.0.5{A,B,C,D,E,F} has been awful. It is high time we had a "reference
| release".
| 
| And if we must use letters, let's save them for model-specific bugfixes and
| increment numbers for real functional enhancements. It seems awfully foolish
| to have this nice three-level numbering system and never use it.

All the letter releases from D on were model specific.  B and C were
all platforms, and were most definitely bug fixes (that were partially
model specific).

A lot of people at SGI would like an all platform release 'soon'.
There is this minor ;)  battle between that desire, and the number of
people to do development and testing on all those platforms in a short
enough time frame to make it worthwhile (without making other products
later!).

At this point, I wouldn't hold out much hope (speaking only for myself,
and not knowing just what upper management thinks) of seeing an all
platform release before the next major OS release.  It is even possible
that the first minor release of that major release will be machine
specific (as happened with 4.0, which was only supposed to be used on
Indigo).

--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Newsgroups: comp.sys.sgi