All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Lexington Luthor <Lexington.Luthor@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Another article abour Reiser4 on linux.com
Date: Sun, 06 Aug 2006 15:17:15 -0400	[thread overview]
Message-ID: <44D6403B.1010701@slaphack.com> (raw)
In-Reply-To: <eb4o19$5ik$1@sea.gmane.org>

Lexington Luthor wrote:
> Bernd Schubert wrote:
>> An alternative might be a reiser4 fuse port. Has some advantages:

> Please please no. The kernel people will use that as an argument for 
> keeping it out of the kernel.

They'll use anything as an argument for keeping it out of the kernel. 
This one is particularly shallow, especially if we still have the kernel 
version, because the performance difference will be significant.

If it isn't, maybe it is time for things like FUSE to take us in the 
direction of microkernels...

> I want reiser4 to be popular enough to 
> make my apps depend on it and not have the users complain about having 
> to use an obscure fs.

Well, an obscure program (FUSE) is probably a lot easier to convince 
users of than an obscure filesystem (reiser4 in-kernel).

> Besides, the only thing about reiser4 that interests me more than XFS or 
> reiserfs is the speed.

That's you.  There are other reasons to like it.

But I agree with you in that I don't think it's worth the resources to 
do a FUSE port, especially when there is (again) NO guarantee that 
anything we do will get us in the kernel, so better to do things that 
will either get us users anyway (like distro inclusion) or do things the 
kernel people specifically ask for.

  parent reply	other threads:[~2006-08-06 19:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05 12:55 Another article abour Reiser4 on linux.com Tassilo Horn
2006-08-05 14:55 ` David Masover
2006-08-05 16:17   ` Maciej Sołtysiak
2006-08-05 16:22     ` Maciej Sołtysiak
2006-08-05 18:07       ` Clay Barnes
2006-08-05 21:40         ` David Masover
2006-08-06  0:44           ` Clay Barnes
2006-08-06  1:39             ` David Masover
2006-08-06  2:14               ` TongKe Xue
2006-08-06  2:51                 ` David Masover
2006-08-06  4:07                 ` TongKe Xue
2006-08-06  8:20                 ` Hans Reiser
2006-08-06 11:04                   ` Bernd Schubert
2006-08-06 12:41                     ` Lexington Luthor
2006-08-06 13:15                       ` Bernd Schubert
2006-08-06 17:06                         ` Lexington Luthor
2006-08-06 19:17                       ` David Masover [this message]
2006-08-06 19:21                         ` TongKe Xue
2006-08-09  8:07                     ` Hans Reiser
2006-08-06  9:19 ` Hans Reiser
2006-08-06 16:26   ` Clemens Eisserer
2006-08-06 22:55   ` Bruce Byfield
2006-08-09  8:28     ` Hans Reiser
2006-08-09  9:47       ` Andreas Schäfer
2006-08-09 15:51         ` David Masover
2006-08-09 18:38       ` Bruce Byfield
2006-08-09 17:37         ` Hans Reiser

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=44D6403B.1010701@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=Lexington.Luthor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.