linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Konir <moje@vabo.cz>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 future
Date: Tue, 2 Dec 2003 15:21:54 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312021508470.21855@moje.vabo.cz> (raw)
In-Reply-To: <20031202135423.GB13388@conectiva.com.br>

On Tue, 2 Dec 2003, Arnaldo Carvalho de Melo wrote:

> Em Tue, Dec 02, 2003 at 02:38:54PM -0500, Tomas Konir escreveu:
> > On Tue, 2 Dec 2003, Arnaldo Carvalho de Melo wrote:
> > 
> > > Em Tue, Dec 02, 2003 at 02:06:34PM -0500, Tomas Konir escreveu:
> > > > On Tue, 2 Dec 2003, Arnaldo Carvalho de Melo wrote:
> > > > 
> > > > > Em Tue, Dec 02, 2003 at 12:54:36PM +0100, Ionut Georgescu escreveu:
> > > > > > I can only second that. We've been using XFS here since the days of
> > > > > > 2.4.0-testxx and the only problems we've had were sitting between the
> > > > > > chair and the keyboard.
> > > > > 
> > > > > So if there is no problems at all using it as a patch why add this to a
> > > > > kernel that is phasing out?
> > > > 
> > > > Because me and others are wasting our time when merging xfs with other 
> > > > patches such as grsecurity. XFS in kernel can save our time. The question 
> > > > is, that if JFS and other FS's are in kernel, why not XFS ?
> > > 
> > > Why not ReiserFS4? Or DRBD? Or... :-)
> > 
> > ReiserFS4 is stable ? very new information for me.
> 
> Well, some people may well consider :-) But yes, this was my fault, I should
> have just mentioned DRBD and other patches in similar situation, just look
> at any recent 2.4 rpm from any distro.

Distro kernels contains many features, but a lot of bloat :-(
no one pure distro kernel can be used as server kernel.
(only my opinion)

> 
> > > Like I was discussing with Marcelo: if he stated that 2.4 will get in deep
> > > freeze, it means that the external patches for this kernel will not have to
> > > be maintained, or the maintainance will be very very small, and related to
> > > things that are _outside_ the kernel.
> > 
> > 2.2 external patches are not related to other's now.
> 
> 2.2?
> 
> > Why 2.4 patches will be ?
> 
> Havent you mentioned grsecurity?

grsecurity is good example. I have to merge cca 10 rejects, when adding to 
linux-xfs kernel.

> 
> > This discussion is not about unstable testing feature, but about rock 
> > stable filesystem, used by many. Including in kernel can help without 
> 
> It is about adding a new feature, whatever is the opinion of people about
> its stability or not, in a kernel that is being phased out.

agree
but this feature is wanted by many and still rejected without serious 
reasons.

> > stability compromise. I think, that there is no reliable argument to 
> > not include XFS into main kernel.
> 
> But it is included, in 2.6, where it seems to be showing problems, as
> mentioned by Linus some days ago, I for one was using it and stopped, switched
> to ext3 and have had no problems since.

2.6 is still unstable now. I'm using -test10 on my workstation, but it 
takes minimally an half year to use it on server. I can't use ext3 on 
server, because of missing features such as ACL, dump (with acl's), 
built in qouta and for last much different speed on SMP machine.

> 
> But hey, take this discussion to lkml, there more people will be able to
> discuss with us :-)

roger
cc: to linux-kernel

	MOJE

-- 
Konir Tomas
Czech Republic
Brno
ICQ 25849167


  parent reply	other threads:[~2003-12-02 14:20 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 14:25 Linux 2.4 future Marcelo Tosatti
2003-12-01 15:04 ` Ian Kent
2003-12-01 15:33   ` Christoph Hellwig
2003-12-01 21:36     ` Peter C. Norton
2003-12-01 23:54       ` Arjan van de Ven
2003-12-02  1:11         ` Ian Kent
2003-12-02 20:13           ` Peter C. Norton
2003-12-02 20:10         ` Peter C. Norton
2003-12-02 20:18           ` Arjan van de Ven
2003-12-02 20:46             ` Peter C. Norton
2003-12-03  1:23               ` Ian Kent
2003-12-03 10:36                 ` Matthias Andree
2003-12-03 14:49                   ` Ian Kent
2003-12-03 15:00                     ` Matthias Andree
2003-12-04  6:24                       ` Ian Kent
2003-12-02 21:56             ` Bryan Whitehead
2003-12-02  8:17       ` Christoph Hellwig
2003-12-02  1:09     ` Ian Kent
2003-12-02  2:23     ` snpe
2003-12-02  6:39       ` Jan-Benedict Glaw
2003-12-02 18:04         ` Linus Torvalds
2003-12-02 18:45           ` Jan-Benedict Glaw
2003-12-02 19:09             ` Linus Torvalds
2003-12-02 19:13               ` Jan-Benedict Glaw
2003-12-02 19:39               ` Gene Heskett
2003-12-02 20:13                 ` Jeff Garzik
2003-12-02 20:32                 ` Stephan von Krawczynski
2003-12-02 21:48                   ` Gene Heskett
2003-12-02 21:56                     ` Linus Torvalds
2003-12-03  2:36                       ` Harald Arnesen
2003-12-03  9:21                     ` Helge Hafting
2003-12-02 19:59           ` snpe
2003-12-02 22:30             ` Mike Fedyk
2003-12-02 22:43               ` Arnaldo Carvalho de Melo
2003-12-03 14:08                 ` snpe
2003-12-03 13:26                   ` Christoph Hellwig
2003-12-02  8:18       ` Christoph Hellwig
2003-12-01 15:26 ` Norberto Bensa
2003-12-01 23:30   ` 2.6 security patches merged? was: " Mike Fedyk
2003-12-02  0:06     ` Chris Wright
2003-12-02  0:58       ` Måns Rullgård
2003-12-02  1:56         ` Chris Wright
2003-12-02 11:55     ` Marcelo Tosatti
2003-12-02  9:00   ` Matthias Andree
2003-12-02 11:54   ` Ionut Georgescu
2003-12-02 12:03     ` Arnaldo Carvalho de Melo
2003-12-02 13:13       ` Ionut Georgescu
2003-12-02 13:38         ` Ed Sweetman
2003-12-02 14:12           ` Arnaldo Carvalho de Melo
2003-12-02 16:01           ` Ionut Georgescu
2003-12-02 16:08             ` Jeff Garzik
2003-12-02 18:20               ` John Bradford
2003-12-02 20:19               ` Ville Herva
2003-12-02 21:40                 ` Chris Wright
2003-12-02 20:09       ` Stephan von Krawczynski
2003-12-02 20:24         ` Arnaldo Carvalho de Melo
2003-12-02 20:45           ` Stephan von Krawczynski
2003-12-02 21:03             ` Arnaldo Carvalho de Melo
     [not found]       ` <Pine.LNX.4.58.0312021402360.17892@moje.vabo.cz>
     [not found]         ` <20031202131512.GU13388@conectiva.com.br>
     [not found]           ` <Pine.LNX.4.58.0312021433360.8417@moje.vabo.cz>
     [not found]             ` <20031202135423.GB13388@conectiva.com.br>
2003-12-02 20:21               ` Tomas Konir [this message]
2003-12-02 18:53                 ` Mike Fedyk
2003-12-02 19:06                   ` Valdis.Kletnieks
2003-12-02 23:13                 ` Jose Luis Domingo Lopez
2003-12-03 18:22                 ` bill davidsen
2003-12-04  1:24                   ` jw schultz
2003-12-04  1:47                     ` Mike Fedyk
2003-12-04  3:45                       ` Tim Connors
2003-12-04  5:41                         ` Willy Tarreau
2003-12-05  0:14                       ` jw schultz
2003-12-01 15:56 ` Marcelo Tosatti
2003-12-01 21:02 ` David S. Miller
2003-12-03 21:26 ` Jan Rychter
2003-12-03 20:51   ` Jeff Garzik
2003-12-03 21:14   ` Willy Tarreau
2003-12-05 15:33   ` John Jasen
2003-12-05 22:23     ` Mike Fedyk
2003-12-06 15:49     ` Max Valdez

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=Pine.LNX.4.58.0312021508470.21855@moje.vabo.cz \
    --to=moje@vabo.cz \
    --cc=acme@conectiva.com.br \
    --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;
as well as URLs for NNTP newsgroup(s).