From: Lexington Luthor <Lexington.Luthor@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: "Why Reuser 4 still is not in" doc
Date: Sun, 16 Jul 2006 23:53:46 +0100 [thread overview]
Message-ID: <e9eg1v$5sf$1@sea.gmane.org> (raw)
In-Reply-To: <bda6d13a0607161428j187b737ft6f3925d9a3b2cc72@mail.gmail.com>
Joshua Hudson wrote:
>> (aside from the VFS integration debate)
> Anybody know what's in Reiser4 that VFS doesn't like (link please)?
Reiser4 plug-ins have (had?) the ability to alter the semantics of
things, like making files into directories inside which you could see
meta-files like file/uid and file/size which contained meta-data and
such accessible as normal files to all the unix tools (which is a very
good idea IMO). You could get things like chmod by just 'echo root
>file/owner' or something, very nice.
This was frowned upon by kernel developers who felt that it belonged in
the kernel VFS (if at all), rather than in reiser4 directly.
Regards,
LL
next prev parent reply other threads:[~2006-07-16 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 16:16 reiserFS? Xavier Roche
2006-07-16 16:28 ` reiserFS? Christian Trefzer
2006-07-16 16:56 ` reiserFS? Theodore Tso
2006-07-16 17:26 ` reiserFS? Lexington Luthor
2006-07-16 17:48 ` reiserFS? Theodore Tso
2006-07-16 20:01 ` "Why Reuser 4 still is not in" doc (was: 'reiserFS?') Diego Calleja
2006-07-16 21:11 ` "Why Reuser 4 still is not in" doc Lexington Luthor
2006-07-16 21:28 ` Joshua Hudson
2006-07-16 22:53 ` Lexington Luthor [this message]
2006-07-17 9:42 ` Jan Engelhardt
2006-07-17 16:38 ` Lexington Luthor
2006-07-20 6:52 ` Tilman Schmidt
2006-07-16 17:46 ` reiserFS? Dr. David Alan Gilbert
2006-07-16 18:14 ` reiserFS? Theodore Tso
2006-07-17 15:01 ` reiserFS? Matthias Andree
2006-07-17 21:07 ` reiserFS? Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2006-07-17 11:25 "Why Reuser 4 still is not in" doc Al Boldi
2006-07-17 14:33 ` Jan Engelhardt
2006-07-17 18:41 ` Horst von Brand
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='e9eg1v$5sf$1@sea.gmane.org' \
--to=lexington.luthor@gmail.com \
--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