All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Ville Herva <vherva@mail.niksula.cs.hut.fi>
Cc: "T. A." <tkhoadfdsaf@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Which kernel (Linus or ac)?
Date: Fri, 12 Oct 2001 13:35:51 +0200	[thread overview]
Message-ID: <20011012133551.H714@athlon.random> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com> <OE22ITtCsuSYkbAY0Jp0000df3f@hotmail.com> <20011012095618.R22640@niksula.cs.hut.fi>
In-Reply-To: <20011012095618.R22640@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Fri, Oct 12, 2001 at 09:56:19AM +0300

On Fri, Oct 12, 2001 at 09:56:19AM +0300, Ville Herva wrote:
> On Fri, Oct 12, 2001 at 12:37:01AM -0400, you [T. A.] claimed:
> > 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.
> 
> Of course, you can get most of the IDE chipset support, fs support (reiserfs
> 3.5, ext3) and LFS support as patches for 2.2:

btw, just a reminder, 2.2.20pre10aa1 has full lfs support too
(everything, including getdents64, nfv3, lockd all 64bit).

	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.20pre10aa1.bz2
	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.20pre10aa1/40_lfs-2.2.20pre10aa1-28.bz2

Andrea

  parent reply	other threads:[~2001-10-12 11:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 14:45 Which kernel (Linus or ac)? 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.
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 [this message]
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=20011012133551.H714@athlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tkhoadfdsaf@hotmail.com \
    --cc=vherva@mail.niksula.cs.hut.fi \
    /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.