From: "jeev" <naptime@cervnet.com>
To: "'Dan Maas'" <dmaas@dcine.com>, <linux-kernel@vger.kernel.org>
Subject: RE: kudos - 2.4.9-ac10 @ 130 days
Date: Fri, 25 Jan 2002 19:21:32 -0800 [thread overview]
Message-ID: <000501c1a618$8f5edfb0$0200a8c0@mainframe> (raw)
In-Reply-To: <045201c1a616$1a696290$1d01a8c0@allyourbase>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
naptime@thunder:~$ uptime
8:20pm up 157 days, 6:51, 1 user, load average: 0.08, 0.08, 0.03
naptime@thunder:~$ uname -a
Linux thunder 2.4.9 #2 SMP Tue Aug 21 12:14:00 MST 2001 i686 unknown
naptime@thunder:~$
here is a slackware box, been running fine, doesn't look like the kernel
messed up anywhere for uptime.
j
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Dan Maas
> Sent: Friday, January 25, 2002 7:04 PM
> To: linux-kernel@vger.kernel.org
> Subject: kudos - 2.4.9-ac10 @ 130 days
>
> Just wanted to give some long-term feedback on an old kernel... My
primary
> NFS/Samba/DHCP/mail server machine has been running 2.4.9-ac10 for 130
> days
> under moderate load with no problems whatsoever. Kudos to all
developers.
>
> Now I have to reboot the thing to add ext3 and software RAID; I'll be
> trying
> 2.4.17 with Andre's IDE patch and Rik's rmap...
>
> Regards,
> Dan
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3224 bytes --]
prev parent reply other threads:[~2002-01-26 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 3:03 kudos - 2.4.9-ac10 @ 130 days Dan Maas
2002-01-26 3:21 ` jeev [this message]
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='000501c1a618$8f5edfb0$0200a8c0@mainframe' \
--to=naptime@cervnet.com \
--cc=dmaas@dcine.com \
--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