From: Crutcher Dunnavant <crutcher@datastacks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Whats in the wings for 2.5 (when it opens)
Date: Fri, 21 Sep 2001 15:58:06 -0400 [thread overview]
Message-ID: <20010921155806.B8188@mueller.datastacks.com> (raw)
In-Reply-To: <20010918001826.7D118A0E5@oscar.casa.dyndns.org> <20010918214904.B29648@vdpas.hobby.nl>
In-Reply-To: <20010918214904.B29648@vdpas.hobby.nl>; from toon@vdpas.hobby.nl on Tue, Sep 18, 2001 at 09:49:04PM +0200
++ 18/09/01 21:49 +0200 - toon@vdpas.hobby.nl:
> On Mon, Sep 17, 2001 at 08:18:25PM -0400, Ed Tomlinson wrote:
> > Hi,
> >
> > Seems like there is a lot of code "ready" for consideration in a 2.5 kernel.
> > I can think of:
> >
> > premptable kernel option
> > user mode kernel
> > jfs
> > xfs (maybe)
>
> ext3
>
> > rc2
> > reverse maping vm
> > ide driver rewrite
> > 32bit dma
> > LTT (maybe)
> > LVM update to 1.01
>
> My opinion is that the LVM update to 1.01 should go into 2.4
> as soon as possible.
>
> > ELVM (maybe)
> > module security stuff
> > UP friendly SMP scheduler
> >
> > What else?
> >
> > TIA
> > Ed Tomlinson
A cleaner handling of module parameters/cmd line options.
--
Crutcher <crutcher@datastacks.com>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$
next prev parent reply other threads:[~2001-09-21 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 0:18 Whats in the wings for 2.5 (when it opens) Ed Tomlinson
2001-09-18 1:24 ` David Weinehall
2001-09-18 2:24 ` James Simmons
2001-09-18 10:49 ` Gábor Lénárt
2001-09-18 19:49 ` toon
2001-09-21 19:58 ` Crutcher Dunnavant [this message]
2001-09-22 2:59 ` Keith Owens
2001-09-22 14:31 ` Crutcher Dunnavant
2001-09-22 14:44 ` Keith Owens
2001-09-22 15:23 ` Crutcher Dunnavant
2001-09-22 14:38 ` Arnaldo Carvalho de Melo
2001-09-23 13:42 ` José Luis Domingo López
-- strict thread matches above, loose matches on Subject: below --
2001-09-18 17:23 Grover, Andrew
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=20010921155806.B8188@mueller.datastacks.com \
--to=crutcher@datastacks.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