From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
Valdis.Kletnieks@vt.edu,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: metas Permission Denied
Date: Thu, 29 Apr 2004 22:19:56 -0700 [thread overview]
Message-ID: <4091E1FC.5080502@namesys.com> (raw)
In-Reply-To: <1083256305.30344.284.camel@watt.suse.com>
Chris Mason wrote:
>On Thu, 2004-04-29 at 12:22, Nikita Danilov wrote:
>
>
>>Valdis.Kletnieks@vt.edu writes:
>> > On Thu, 29 Apr 2004 19:59:22 +0400, Nikita Danilov said:
>> >
>> > > chmod u+rx backup/fsplit.c
>> > >
>> > > "x" bit is necessary for lookups, and "r" bit---for readdir.
>> >
>> > This is going to be *such* a non-starter - there's many decades of
>> > "C files are mode 644 and executables are 755" tradition that this
>> > will fly against. What this basically implies is that the 'execute'
>>
>>Eh? What I described is precisely decades old meaning of rwx bits for
>>directories.
>>
>>Problem is that we have to fit objects that are both regular files and
>>directories into access control scheme that wasn't designed for such a
>>mix. I don't see better solution short of inventing new bit(s).
>>
>>
>
>Please forgive me for jumping into the end of a thread without reading
>the whole thing, but it seems like the r bit should be sufficient here.
>If you can read the file, you should be able to read the metas.
>
>x should be for execution of the file...
>
>-chris
>
>
>
>
>
>
what if the file/directory contains "real" files which are not metas,
and it also has a file body? This is possible in reiser4.
next prev parent reply other threads:[~2004-04-30 5:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 20:16 metas Permission Denied Boyd Waters
2004-04-29 7:56 ` Nikita Danilov
2004-04-29 15:02 ` Boyd Waters
2004-04-29 15:59 ` Nikita Danilov
2004-04-29 16:14 ` Hans Reiser
2004-04-29 20:39 ` Boyd Waters
2004-04-29 20:52 ` Grant Miner
2004-04-29 21:15 ` Boyd Waters
2004-04-30 4:55 ` Hans Reiser
2004-04-30 5:00 ` Grant Miner
2004-04-29 16:14 ` Valdis.Kletnieks
2004-04-29 16:22 ` Nikita Danilov
2004-04-29 16:31 ` Chris Mason
2004-04-30 5:19 ` Hans Reiser [this message]
2004-04-30 12:17 ` Chris Mason
2004-05-02 17:59 ` Hans Reiser
2004-04-29 16:59 ` Valdis.Kletnieks
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=4091E1FC.5080502@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=Valdis.Kletnieks@vt.edu \
--cc=mason@suse.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.