public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <jdomingo@internautas.org>
To: Guillaume Boissiere <boissiere@mediaone.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  January 17, 2001
Date: Thu, 17 Jan 2002 22:47:53 +0100	[thread overview]
Message-ID: <20020117214752.GA5085@localhost> (raw)
In-Reply-To: <3C463337.24593.CD1AD57@localhost>
In-Reply-To: <3C463337.24593.CD1AD57@localhost>

On Thursday, 17 January 2002, at 02:13:11 -0500,
Guillaume Boissiere wrote:

> I've seen several times on this list people wondering what features
> were in the works for 2.5 and what the status of the development was.
> I did some grepping on the archive and put together a list of things 
> that have been discussed / worked on for 2.5 over the past year or so.  
> 
Great !!!. I think this "todo list" was much needed. Let me suggest a
couple of things that should find their way into 2.5.x sometime in the
futute, and that I consider important:
. Generic (VFS layer?) ACL implementation: it seems under heavy
  develpment by some groups, and could be something quite interesting to
  have for 2.6.x
. Linux Security Module (LSM)
. LVM 2: it seems LVM developers are about to release a first version of
  the new (version 2.0) LVM (Logical Volume Management) implementation
  for Linux. Seems to solve the problems current code base has.
. devfs 2: new implementation of Richard Gooch's devfs for Linux. devfs
  is a "must have" for some people, and this new code seems to solve
  everything that people complained about. AFAIR, Richard has submitted
  several "cuts" of the new code.

There are other interesting things I don't follow as closely, and that
could be available when 2.5.x is still under development, maybe not.
. reiserfs 4 (later this year): maybe too late for inclusion.
. USAGI IPv6 implementation for Linux: maybe not ready for prime time.
. NFS v4: have read about it, but don't remember about deadlines.
. IPsec in kernel (FreeS/WAN): the neverending story :)

That is what I think are the most important things that _could_ be part
of future 2.6.0, should maintainers consider it as a good idea. Please,
this is only informative, not trying to "sell" you nothing.

Good work !

-- 
José Luis Domingo López
Linux Registered User #189436     Debian Linux Woody (P166 64 MB RAM)
 
jdomingo AT internautas DOT   org  => Spam at your own risk


  parent reply	other threads:[~2002-01-17 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  7:13 [STATUS 2.5] January 17, 2001 Guillaume Boissiere
2002-01-17  9:09 ` Stefan Smietanowski
2002-01-17 10:03 ` Russell King
2002-01-17 11:21   ` Dave Jones
2002-01-17 12:40     ` Erik Mouw
2002-01-17 21:47 ` Jose Luis Domingo Lopez [this message]
2002-01-17 22:14   ` Tim Pepper
2002-01-17 22:21   ` Hans Reiser
2002-01-17 22:39     ` Tim Pepper
2002-01-17 23:02       ` James Simmons
2002-01-18  0:21         ` Hans Reiser
2002-01-18  0:38     ` Alan Cox
2002-01-18 11:36       ` Hans Reiser
2002-01-17 22:22   ` Guillaume Boissiere
2002-01-17 22:30     ` Tim Pepper
2002-01-20  1:02       ` H. Peter Anvin
2002-01-18  4:47     ` Guillaume Boissiere
2002-01-18  0:23 ` Anton Altaparmakov
2002-01-18  0:50   ` Chris Chabot
2002-01-18  4:35     ` Guillaume Boissiere
2002-01-18  2:02 ` Arnaldo Carvalho de Melo
2002-01-21 12:39 ` Pavel Machek
2002-01-24 17:40   ` James Simmons

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=20020117214752.GA5085@localhost \
    --to=jdomingo@internautas.org \
    --cc=boissiere@mediaone.net \
    --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