mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Thunder from the hill <thunder@ngforever.de>
Cc: JorgP <jorgp@bartnet.net>, linux-kernel@vger.kernel.org
Subject: Re: What is the most stable kernel to date?
Date: Fri, 12 Jul 2002 18:54:02 +0200	[thread overview]
Message-ID: <20020712165402.GP29993@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207121046090.3421-100000@hawkeye.luckynet.adm>

> > > Has anyone conducted any tests to determine what is the most stable (as in
> > > reliable) kernel available?
> > 
> > There is no such test because there's no way to describe "being stable"
> > in formulas.
> > 
> > You might as well like to stick with a kernel that has worked for you
> > for a long enough time. If you don't need the features of 2.4, go with
> > 2.2-latest.
> 
> Well, about stability: I'm running 2.4.19-rc1-aa2 for some days now, I 
> didn't yet have any problems. My sparc64, meanwhile, is running 2.5.24-ct1, 
> stable for more than a week of uptime yet.

As for me,

$ arch
i686
$ uname -r
2.4.19-pre10-ac2
$ uptime
  6:51pm  up 36 days, 19:14, 19 users,  load average: 0.00, 0.00, 0.00
(config: p2, 2 ide controllers, raid0, 2 network adapters)
--
$ arch 
sparc
$ uname -r
2.4.19-pre10
$ uptime
  6:51pm  up 38 days,  8:46,  7 users,  load average: 0.00, 0.01, 0.00
(config: smp ss10, scsi, raid0, 1 network adapter)

The latter is with my dynamic-nocache patch included.


T.

  reply	other threads:[~2002-07-12 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 16:08 JorgP
2002-07-12 16:35 ` Tomas Szepe
2002-07-12 16:48   ` Thunder from the hill
2002-07-12 16:54     ` Tomas Szepe [this message]
2002-07-12 17:16       ` Steven Cole
2002-07-12 21:18         ` Kelsey Hudson
2002-07-12 19:16     ` Juergen Sawinski
2002-07-12 19:29       ` Richard B. Johnson
2002-07-12 21:53         ` Adrian Bunk
2002-07-12 22:18           ` Urban Widmark
2002-07-13  6:06             ` Adrian Bunk
2002-07-12 16:38 ` Paul Larson
2002-07-12 17:31 ` jbradford
2002-07-15 19:15 ` Bill Davidsen
2002-07-15 19:30   ` 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=20020712165402.GP29993@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=jorgp@bartnet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@ngforever.de \
    /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

all inboxes | Powered by JetHome®