mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ryan Hope" <rmh3093@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>, "Ryan Hope" <rmh3093@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 for 2.6.27-rc1
Date: Fri, 1 Aug 2008 12:34:53 -0400	[thread overview]
Message-ID: <48f7fe350808010934k32b9de09we657e57087a3e3a5@mail.gmail.com> (raw)
In-Reply-To: <20080801162548.GD8654@mit.edu>

Hmmm, removing the plugin support might not be so hard....  I might
have to try this... I am not impressed with btrfs yet.
-Ryan

On Fri, Aug 1, 2008 at 12:25 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Fri, Aug 01, 2008 at 09:49:55AM -0400, Ryan Hope wrote:
>> Why is reiser4 still not in a vanilla kernel for testing. I have had
>> to apply the reiser4 patches from -mm kernels to vanilla based
>> patchset for over a year now. Reiser4 works fine, what will it take to
>> get it included in vanilla? Here is a patch to add reiser4 to
>> 2.6.27-rc1:
>>
>> http://zen-sources.org/files/reiser4-for-2.6.27-rc1.patch
>
> The reasons laid out in these web pages haven't changed.
>
> http://kernelnewbies.org/WhyReiser4IsNotIn
> http://lkml.org/lkml/2006/7/28/180
> http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=668645;page=1;sb=post_latest_reply;so=ASC;mh=25;list=linux
>
> Now that Hans is out of the picture, and Namesys seems to have
> collapsed, maybe someone can yank out the plugin architecture that
> Linus and others have objected to, which as near as I could tell was
> part of the Namesys's somewhat dodgy business plan of creating and
> selling (possibly proprietary; not sure what license they were going
> to be under) plugin modules for Reiser4 to make money.  The other
> issue that was raised during the review were some locking issues
> raised by Al Viro, if memory serves correctly.  I'm not sure if they
> were ever fixed; at least initially they were brushed aside by Hans.
>
> In the meantime, people who really like reiser4 might want to take a
> look at btrfs; it has a number of the same design ideas that reiser3/4
> had --- except (a) the filesystem format has support for some advanced
> features that are designed to leapfrog ZFS, (b) the maintainer is not
> a crazy man and works well with other LKML developers (free hint: if
> your code needs to be reviewed to get in, and reviewers are scarce;
> don't insult and abuse the volunteer reviewers as Hans did --- Not a
> good plan!).
>
>                                                - Ted
>

  reply	other threads:[~2008-08-01 16:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 13:49 Ryan Hope
2008-08-01 16:25 ` Theodore Tso
2008-08-01 16:34   ` Ryan Hope [this message]
2008-08-01 16:45     ` Theodore Tso
2008-08-01 18:15       ` Ric Wheeler
2008-08-01 22:40         ` Edward Shishkin
2008-08-02 15:47           ` Ryan Hope
2008-08-02 22:56             ` Edward Shishkin
2008-08-02 23:18               ` Ryan Hope
2008-08-04 11:11                 ` Edward Shishkin
2008-08-04 11:18                   ` Dushan Tcholich
2008-08-04 11:34                     ` Dushan Tcholich
2008-08-02  2:30   ` Alexey Dobriyan
2008-08-04 12:26 Tim Tassonis
2008-08-13 12:58 ` Pavel Machek
2008-08-13 13:18   ` Adrian Bunk
2008-08-13 13:24     ` Michael Krufky
2008-08-13 13:34       ` Adrian Bunk
2008-08-13 13:30         ` Alan Cox
2008-08-13 13:46         ` Michael Krufky
2008-08-13 14:50           ` Frans Meulenbroeks
2008-08-13 23:04         ` Jeremy Fitzhardinge
2008-08-25 20:09           ` Bill Davidsen
2008-08-13 13:37       ` Tim Tassonis
2008-08-13 13:36         ` Alan Cox
2008-08-13 14:00           ` Tim Tassonis
2008-08-13 14:59             ` Ryan Hope
2008-08-13 15:24               ` Tim Tassonis
2008-08-13 16:18                 ` Jeff Chua
2008-08-13 16:30                 ` Ryan Hope
2008-08-25 20:04           ` Bill Davidsen
2008-08-13 13:56     ` Andi Kleen
2008-08-13 14:02       ` Tim Tassonis

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=48f7fe350808010934k32b9de09we657e57087a3e3a5@mail.gmail.com \
    --to=rmh3093@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®