I crashed Linux

[jnoller at allaire.com (Jesse Noller)]

Talking about uptime!!!

	My workstation here at work, a HP kayak dual 366 w/ .5 gigs of ram,
running redhat and Helix Gnome has had an uptime of about 3 months steady. I
amaze my coworkers with this wonderful, slowly converting them to the 'dark
side', although, my advocacy will gain a boon if I can get linux installed
on this little sony vaio 505tx... Damnable machine.

Just my depreciated .02 cents.

=]

-Jesse

Ps: I have a slackware box at a company that has changed ownership/staff
about 4 times. It's a little p60 with 32 megs of ram running slackware...
It's had an uptime of nearly 5 years... Except that is, until last month
when the disk finally toasted. I called the people that owned the company at
the time, and mentioned they had a server sitting in back which might be
emitting funny noises and smoking a bit.

They told me that they had found it, did not know what it was, and
therefore, threw it away.

I promptly went into a dark depression.

-----Original Message-----
From: Michael Bilow [mailto:mike at bilow.com]
Sent: Thursday, December 07, 2000 3:58 AM
To: Ron Peterson
Cc: discuss at Blu.Org
Subject: Re: I crashed Linux


Nice to see yellowbank.com back with us!

I've crashed Linux lots of times.  We have one ancient server that usually
goes hundreds of days between reboots, and at least half of its crashes
have been a result of building electrical failures.  (Hurricanes have
accounted for two such crashes!)  Next to that, the most common cause of
crashes is that the SCSI tape drive in the machine hangs up, and this
requires a power cycle.  Any hardware or drivers, which is what is at
issue with your scanner, has a fairly high potential to hang the machine.  
This is actually one of the big things that makes PCs unsuitable for
high-availability environments where mainframes are typically used.

-- Mike


On 2000-12-06 at 23:47 -0500, Ron Peterson wrote:

> I crashed Linux.  For the first time.  I didn't think it was possible.
> 
> I was trying to get my old Microtek ScanMaker E3 going vis-a-vis RH 7.0,
> kernel 2.4-test10 and SANE 1.0.3.  It was ugly, but it wasn't pretty. 
> SANE's 'scanimage' saw my scanner o.k., but when I ran:
> 
> scanimage --format=tiff --mode Color --speed 2
> --device=microtek:/dev/scanner -l 0 -t 0 -x 100 -y 150 
> 
> the scanner just make a couple of blurps, then... nothing.  My KDE
> session was dead.  I killed X o.k., but then I couldn't get a console. 
> I had to hard reboot.
> 
> I don't really know what the point of this post is.  Just interesting
> that it could even happen.  I guess it is a test kernel.
> 
> -Ron-

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).