From: "T. A." <tkhoadfdsaf@hotmail.com>
To: "J Sloan" <jjs@lexus.com>, "Tim Moore" <timothymoore@bigfoot.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Which kernel (Linus or ac)?
Date: Fri, 12 Oct 2001 00:37:01 -0400 [thread overview]
Message-ID: <OE22ITtCsuSYkbAY0Jp0000df3f@hotmail.com> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com>
Well I'd have to agree that for stability I'd also go for 2.2.x. 2.4.x
isn't bad but 2.2.x is just rock stable right now. Furthermore its been
hard to gain confidence in 2.4.x with all the bugs that have yet to be
worked out. I'd use 2.2.x almost exclusively if it would just gain support
for the latest EIDE chipsets, a journaling filesystem, and the latest SMP
boards. iptables and large file support would also be great.
----- Original Message -----
From: "J Sloan" <jjs@lexus.com>
To: "Tim Moore" <timothymoore@bigfoot.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, October 11, 2001 2:23 PM
Subject: Re: Which kernel (Linus or ac)?
> Tim Moore wrote:
>
> > Any special reason to use 2.4?
>
> er... scalability, performance, features?
>
> > I only use 2.2.19p8 and 2.2.20p10 where
> > stability is important.
>
> experimental pre-releases? interesting...
>
> All my 2.4 based servers are running quite
> reliably - the oldest now have over180 days
> uptime, all have been up since install or last
> kernel with no hint of instability.
>
> Red Hat and Late -ac kernels are especially
> stable examples of 2.4 -
>
> cu
>
> jjs
>
>
>
>
>
>
> -
> 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/
>
next prev parent reply other threads:[~2001-10-12 4:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:45 jkp
2001-10-11 17:42 ` Robert Love
2001-10-11 17:52 ` Tim Connors
2001-10-11 18:11 ` Tim Moore
2001-10-12 2:01 ` Horst von Brand
[not found] ` <001901c152ca$0b42c080$0600000a@petersohn.net>
2001-10-12 18:32 ` Tim Moore
2001-10-11 18:13 ` Tim Moore
2001-10-11 18:23 ` J Sloan
2001-10-11 18:56 ` Tim Moore
2001-10-11 19:59 ` [OT] " J Sloan
2001-10-12 4:42 ` T. A.
2001-10-12 6:07 ` J Sloan
2001-10-12 9:14 ` T. A.
2001-10-12 9:59 ` Luigi Genoni
2001-10-12 17:35 ` J Sloan
2001-10-12 22:59 ` J . A . Magallon
2001-10-11 23:50 ` Oden Eriksson
2001-10-11 23:56 ` Arnaldo Carvalho de Melo
2001-10-12 0:09 ` J Sloan
2001-10-12 4:37 ` T. A. [this message]
2001-10-12 6:56 ` Ville Herva
2001-10-12 9:25 ` T. A.
2001-10-12 10:02 ` Ville Herva
2001-10-12 11:35 ` Andrea Arcangeli
2001-10-11 19:43 ` M. R. Brown
2001-10-11 22:05 ` Luigi Genoni
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=OE22ITtCsuSYkbAY0Jp0000df3f@hotmail.com \
--to=tkhoadfdsaf@hotmail.com \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timothymoore@bigfoot.com \
/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
Powered by JetHome