linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. Giovanni A. Orlando" <gorlando@futuretg.com>
To: Hans Reiser <reiser@namesys.com>
Cc: linux-kernel@vger.kernel.org,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: 2.6.9-mm1
Date: Sun, 24 Oct 2004 14:41:01 +0000	[thread overview]
Message-ID: <417BBEFD.9080308@futuretg.com> (raw)
In-Reply-To: <4179425A.3080903@namesys.com>

Hans Reiser wrote:

> Andrew Morton wrote:
>
>>
>>  - reiser4: not sure, really.  The namespace extensions were disabled,
>>    although all the code for that is still present.  Linus's filesystem
>>    criterion used to be "once lots of people are using it, preferably 
>> when
>>    vendors are shipping it".  That's a bit of a chicken and egg thing 
>> though.
>>    Needs more discussion.
>>
>>  
>>
> No distro using reiserfs V3 as the default is going to keep doing so 
> once reiser4 meets their stability requirements. Reiserfs is used by a 
> lot of people, and reiser4 obsoletes it, and the users know that. 

I agree that OS that choose ReiserFS for default now will adopt Reiser4 
instead ReiserFS 3, .... but they need to continue
to support ReiserFS 3 as well Reiser4 ...

In some sense this is equivalent to ext2 and ext3.

Thanks,
Giovanni


> None of the distros have expressed any intent of staying on V3, and 
> they'd be silly to do it. Many of them have expressed a desire to use 
> reiser4. Next year, indications are that reiser4 usage by distros as 
> their default will exceed that which is today possessed by V3. The 
> higher performance of V4 is going to increase our market share.
>
> I would like to encourage its inclusion as an experimental filesystem 
> BEFORE vendors ship it. I think first putting experimental stuff in 
> the kernels used by hackers makes sense. I think it creates more of a 
> community.
>
> I'd like to point out that there is a lot of stuff in the kernel that 
> is a lot less stable than reiser4.
>
> That said, inclusion in -mm found some bugs, and we are still testing 
> one of the fixes which was a bit deep. I want to finish that testing 
> (not more than 7 days) and send you all fixes before asking for 
> inclusion.
>
> Also, Hellwig made a valid point about getting rid of some macros that 
> reduce readability (I also hate code that prevents editors finding 
> called functions), and zam is working on fixing that.
>
> Lindows is planning on shipping with reiser4 in its next release. I 
> would very much like to see our inclusion before that.
>


-- 


-- 
-- 

Check FT Websites ... http://www.futuretg.com  - ftp://ftp.futuretg.com
http://www.FTLinuxCourse.com
    http://www.FTLinuxCourse.com/Certification
http://www.rpmparadaise.org
http://GNULinuxUtilities.com
http://www.YourPersonalOperatingSystem.com

-- 


  parent reply	other threads:[~2004-10-24 12:40 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 10:20 2.6.9-mm1 Andrew Morton
2004-10-22 10:39 ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 10:54   ` 2.6.9-mm1 Andrew Morton
2004-10-22 11:08     ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 17:26       ` 2.6.9-mm1 Hans Reiser
2004-10-22 19:34       ` 2.6.9-mm1 Roman Zippel
2004-10-27 11:19         ` 2.6.9-mm1 Christoph Hellwig
2004-10-22 15:54   ` 2.6.9-mm1 Chris Wright
2004-10-22 12:23 ` 2.6.9-mm1 Eyal Lebedinsky
2004-10-22 19:26   ` 2.6.9-mm1 Adrian Bunk
2004-10-22 13:39 ` 2.6.9-mm1: pc_debug multiple definitions Adrian Bunk
2004-10-22 23:07   ` Russell King
2004-10-24  3:41   ` Luis R. Rodriguez
2004-10-24  9:33     ` Adrian Bunk
2004-10-24 10:05       ` Luis R. Rodriguez
2004-10-22 13:43 ` [patch] 2.6.9-mm1: usb/serial/console.c compile error Adrian Bunk
2004-10-22 18:08   ` Greg KH
2004-10-22 13:50 ` 2.6.9-mm1: timer_event multiple definition Adrian Bunk
2004-10-22 15:24   ` Christoph Lameter
2004-10-22 19:16     ` Adrian Bunk
2004-10-22 19:21       ` Christoph Lameter
2004-10-25 23:07     ` George Anzinger
2004-10-25 23:32       ` Christoph Lameter
2004-10-22 13:59 ` [patch] 2.6.9-mm1: ISDN hisax_fcpcipnp.c: kill unused variable Adrian Bunk
2004-10-22 15:30 ` 2.6.9-mm1 Jason Baron
2004-10-22 17:24 ` 2.6.9-mm1 Hans Reiser
2004-10-23 19:01   ` 2.6.9-mm1 Hilzinger Marcel
2004-10-23 19:39     ` 2.6.9-mm1 Andrew Morton
2004-10-23 19:49       ` 2.6.9-mm1 Jan Engelhardt
2004-10-24 17:42       ` 2.6.9-mm1 Alex Zarochentsev
2004-10-23 20:28     ` 2.6.9-mm1 Hans Reiser
2004-10-24 14:41   ` Dr. Giovanni A. Orlando [this message]
2004-10-24 14:41   ` 2.6.9-mm1 Clifford Beshers
2004-10-24 14:45     ` 2.6.9-mm1 Con Kolivas
2004-10-24 14:54       ` 2.6.9-mm1 Clifford Beshers
2004-10-25 19:52   ` 2.6.9-mm1 Bill Davidsen
2004-10-22 21:06 ` 2.6.9-mm1 (compile stats) John Cherry
2004-10-22 22:22 ` 2.6.9-mm1 Chuck Harding
2004-10-24 18:00   ` 2.6.9-mm1 john cooper
2004-10-25 21:24     ` 2.6.9-mm1 Chuck Harding
2004-10-23  0:12 ` pdc202xx_old broke boot [was Re: 2.6.9-mm1] J.A. Magallon
2004-10-23  0:21   ` Andrew Morton
2004-10-23  0:22     ` J.A. Magallon
2004-10-23  0:34     ` Bartlomiej Zolnierkiewicz
2004-10-27 22:19       ` [PATCH] " J.A. Magallon
2004-10-27 22:42         ` Bartlomiej Zolnierkiewicz
2004-10-23  0:13 ` 2.6.9-mm1 Dominik Karall
2004-10-23 10:37   ` 2.6.9-mm1 Gerd Knorr
2004-10-23  0:44 ` [patch] 2.6.9-mm1: dvb-dibusb.c: remove unused code Adrian Bunk
2004-10-23 10:48   ` Patrick Boettcher
2004-10-23  7:22 ` 2.6.9-mm1 Avuton Olrich
2004-10-23 16:59   ` 2.6.9-mm1 Markus   Törnqvist
2004-10-23 22:03   ` 2.6.9-mm1 Kasper Sandberg
2004-10-25 19:54   ` 2.6.9-mm1 Bill Davidsen
2004-10-23  9:08 ` 2.6.9-mm1 Alexander Nyberg
2004-10-24  8:49   ` 2.6.9-mm1 Andrew Morton
2004-10-23 12:06 ` 2.6.9-mm1 Dominik Karall
2004-10-23 14:37 ` 2.6.9-mm1 Adrian Bunk
2004-10-23 15:55   ` 2.6.9-mm1 Hans Reiser
2004-10-23 16:57     ` 2.6.9-mm1 Markus   Törnqvist
2004-10-24  2:37       ` 2.6.9-mm1 David Masover
2004-10-24  0:47         ` 2.6.9-mm1 Jan Engelhardt
2004-10-24  5:14         ` 2.6.9-mm1 Hans Reiser
2004-10-24 19:40           ` 2.6.9-mm1 David Masover
2004-10-25 20:07           ` 2.6.9-mm1 Bill Davidsen
2004-10-25  0:12 ` 2.6.9-mm1 J.A. Magallon
2004-10-25 11:47 ` 2.6.9-mm1 Arjan van de Ven
2004-10-25 22:31 ` 2.6.9-mm1 Randy.Dunlap
2004-10-25 22:56   ` 2.6.9-mm1 Andrew Morton
2004-10-25 23:14     ` 2.6.9-mm1 Randy.Dunlap
2004-10-25 23:47       ` 2.6.9-mm1 Andrew Morton
2004-10-25 23:36         ` 2.6.9-mm1 Randy.Dunlap
2004-10-26  1:34           ` 2.6.9-mm1 Bartlomiej Zolnierkiewicz
2004-10-26  3:04             ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 15:48               ` 2.6.9-mm1 Randy.Dunlap
2004-10-26 16:40                 ` 2.6.9-mm1 Bartlomiej Zolnierkiewicz
2004-10-26 20:01                   ` 2.6.9-mm1 Randy.Dunlap
2004-10-26  6:49   ` 2.6.9-mm1 Nigel Cunningham
2004-10-26 17:58 ` 2.6.9-mm1 Alexander Nyberg
2004-10-26 20:19   ` 2.6.9-mm1 Andrew Morton
2004-10-31  4:17 ` 2.6.9-mm1 A little build system bug I guess Pedro Larroy
2004-10-31  8:10   ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 20:32 2.6.9-mm1 Matthieu Castet

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=417BBEFD.9080308@futuretg.com \
    --to=gorlando@futuretg.com \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).