From: Wakko Warner <wakko@animx.eu.org>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org, hants@mailman.lug.org.uk
Subject: Re: 1000 days uptime.
Date: Sat, 10 Jul 2004 18:47:03 -0400 [thread overview]
Message-ID: <20040710224703.GA19378@animx.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0407102122060.21103-100000@linicks.net>
> This is a 486 box serving web pages from a home base (via NFS to gateway).
> No UPS, no special treatment expect dust and usual day-to-day abuse stuck
> under two other boxes in a 'stack' of sorts I done a long time ago...
>
> [nick@486Linux nick]$ uptime
> 9:29pm up 6 days, 1:40, 1 user, load average: 0.15, 0.05, 0.10
>
> [nick@486Linux nick]$ last -xf /var/run/utmp runlevel
> runlevel (to lvl 3) Sun Oct 14 16:07 - 21:29
> (1000+05:22)
>
> [nick@486Linux nick]$ uname -a
> Linux 486Linux 2.2.13-7mdk #1 Wed Sep 15 18:02:18 CEST 1999 i486 unknown
Show off...
[wakko@rod:/home/wakko] uptime ; last -xf /var/run/utmp runlevel
6:56pm up 204 days, 14:40h, 3 users, load average: 0.00, 0.00, 0.00
runlevel (to lvl 5) Thu Nov 18 22:36 - 18:56
(1695+19:20)
utmp begins Thu Nov 18 22:36:07 1999
[wakko@rod:/home/wakko] uname -a
Linux rod 2.2.13 #1 Thu Nov 18 20:59:01 EST 1999 i586 unknown
[wakko@rod:/home/wakko]
However, I do have mine on a UPS (literally =)
Kinda funny that it's basically the same kernel (Just yours is from mandrake
and mine is self compiled)
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2004-07-10 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 20:31 1000 days uptime Nick Warne
2004-07-10 22:41 ` Rob Couto
2004-07-10 22:47 ` Wakko Warner [this message]
2004-07-12 12:50 ` Mark Watts
2004-07-12 13:26 ` Michael Buesch
2004-07-12 13:25 ` Mark Watts
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=20040710224703.GA19378@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=hants@mailman.lug.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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.