From: Perry Kundert <perry.kundert@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: EACCESS vs ENOENT for nonexistent files-within-files
Date: Thu, 16 Sep 2004 16:40:37 -0600 [thread overview]
Message-ID: <2f9ccaae04091615404085f41e@mail.gmail.com> (raw)
In-Reply-To: <2f9ccaae04091615395cfd0730@mail.gmail.com>
On Thu, 16 Sep 2004 20:55:38 +0100, Toby Dickenson
<tdickenson@geminidataloggers.com> wrote:
> On Wednesday 15 September 2004 15:45, Nikita Danilov wrote:
>
> > The real problem is that in reiser4 regular files and directories are
> > indistinguishable by design.
>
> Indistinguishable?
>
> Ive been following the reiser4 message so far and felt comfortable with
> performing directory-like operations on files. But I think this is the first
> mention that files and directories would be *indistinguisable*. What does
> 'ls' show, and how?
I would agree. Clearly, in reiser4 'files' can (optionally) have
a 'directory' personality, presumably containing metadata associated
with the file (and hence, being accessible with the same level of
access as the file itself). If you want to have data that is NOT
accessed with the same level of permissions as the file -- then don't
put it "in" the file's 'directory'!
The obverse would be true of a 'directory' with metadata; This
directory's metadata would be accessible with the same level of
permission as the directory.
If the primary "personality" of a file and directory are
indistinguishable (which I don't believe is true), then every
filesystem file/directory will indeed need two sets of permissions;
one for accessing it as a "file", and one for accessing it as a
"directory". This is, of course, ridiculous, and will break
everything worse than the concept of file's w/ a directory of metadata
ever would, on its own.
--
-pjk
> --
> Toby Dickenson
>
next prev parent reply other threads:[~2004-09-16 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 13:18 EACCESS vs ENOENT for nonexistent files-within-files Paul Wagland
2004-09-15 14:04 ` Hans Reiser
2004-09-15 14:16 ` Paul Wagland
2004-09-15 15:12 ` Nikita Danilov
2004-09-15 14:45 ` Nikita Danilov
2004-09-15 16:15 ` daniel.poelzleithner
2004-09-15 22:40 ` Hans Reiser
2004-09-16 19:55 ` Toby Dickenson
[not found] ` <2f9ccaae04091615395cfd0730@mail.gmail.com>
2004-09-16 22:40 ` Perry Kundert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 14:06 Joe Orton
2004-09-13 14:25 ` Wayne Scott
2004-09-13 15:21 ` Michael Weissenbacher
2004-09-13 16:13 ` Alex Zarochentsev
2004-09-13 18:52 ` Joe Orton
2004-09-13 19:44 ` Nikita Danilov
2004-09-15 10:55 ` evilninja
2004-09-15 11:41 ` Nikita Danilov
2004-09-16 0:00 ` evilninja
2004-09-13 20:58 ` Alex Zarochentsev
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=2f9ccaae04091615404085f41e@mail.gmail.com \
--to=perry.kundert@gmail.com \
--cc=perry@kundert.ca \
--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.