public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: clubneon@hereintown.net, bert hubert <ahu@ds9a.nl>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nasty suprise with uptime
Date: Tue, 30 Oct 2001 10:35:32 -0600 (CST)	[thread overview]
Message-ID: <200110301635.KAA01915@tomcat.admin.navo.hpc.mil> (raw)

Chris Meadors <clubneon@hereintown.net>:
>This was a crappy 486/66, with no reset button.  So a power cycle was
>called for.  When I started the machine back up, it did the file system
>has not been checked in a long time thing, and it started the fsck.
...
>I usually follow those rules, but the cute little 486 in the corner with
>the 240MB hard drive, 16MB of RAM, and the monster uptimes was just too
>much fun to brag about.  I'm not bragging anymore, and it is disassembled
>on the floor in my office.

Hey now, I have one of those (8MB instead of 16) and it's still working
fine... HOWEVER, I did replace the disk controller and disk drive during
one of the upgrade/update cycles with a leftover 2GB drive... Dumped the
128MB ftape, and 540 MB disk.

I decided that the backups were easier to do over the net...
Installs are easier that way too...
The Slackware two disk install lets me restore across the net... (haven't
had to do it though).

And it functions just fine as a firewall handling a DSL connection, e-mail
port, and http port. It has been happy for last 73 days (house lost power
for a couple of hours.. UPS only good for 30min). Now that I have a spare
CDROM, it's time to look into another upgrade to migrate from disk drives
to CD boot (if I can cooerce the BIOS to boot a CD.. otherwise I'll just
have to leave a boot floppy in).
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-10-30 16:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 16:35 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-29 20:31 Nasty suprise with uptime J Sloan
2001-10-29 20:40 ` Alan Cox
2001-10-29 20:39   ` J Sloan
2001-10-29 20:47     ` Matthew Dharm
2001-10-29 20:52       ` J Sloan
2001-11-09  0:45         ` Dr. Kelsey Hudson
2001-10-29 21:26       ` David Relson
2001-10-29 23:29         ` Jonathan Briggs
2001-10-30  8:53           ` george anzinger
2001-10-30 13:50             ` Tim Walberg
2001-10-30 14:47               ` GOMBAS Gabor
2001-10-30 15:39                 ` Tim Walberg
2001-10-30 16:18                   ` GOMBAS Gabor
2001-10-30 22:53             ` Mike Castle
2001-10-30  8:20     ` george anzinger
2001-10-30  9:47     ` bert hubert
2001-10-30 10:37       ` Mike Fedyk
2001-10-30 15:56       ` Chris Meadors
2001-10-30 16:22         ` Laurent de Segur
2001-10-30 22:52     ` Jan Dvorak
2001-10-30  7:46   ` Neale Banks
2001-10-30  7:46     ` Mike Fedyk
2001-10-30  8:15       ` Ville Herva
2001-10-30  8:22         ` Ville Herva
2001-10-30  8:36         ` J. Dow
2001-10-30  9:33       ` Alan Cox
2001-10-30 16:25     ` Matt Bernstein
2001-10-30 19:43       ` Oden Eriksson
2001-10-29 23:10 ` Mike Fedyk
2001-10-29 23:20   ` J Sloan
2001-10-29 23:28     ` Mike Fedyk
2001-10-30  8:21     ` Ville Herva
2001-10-31 22:36       ` J Sloan
2001-11-01  0:49         ` Gerhard Mack
2001-10-30  8:49     ` george anzinger
2001-10-30 18:17       ` J Sloan
2001-10-30  9:06     ` Alan Cox
2001-10-30 19:19       ` J Sloan

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=200110301635.KAA01915@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=ahu@ds9a.nl \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@vger.kernel.org \
    /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