From: Hans Reiser <reiser@namesys.com>
To: Grant Miner <mine0057@mrs.umn.edu>
Cc: Boyd Waters <bwaters+mac@aoc.nrao.edu>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: metas Permission Denied
Date: Thu, 29 Apr 2004 21:55:36 -0700 [thread overview]
Message-ID: <4091DC48.1070304@namesys.com> (raw)
In-Reply-To: <40916B01.1050803@mrs.umn.edu>
Grant Miner wrote:
>
>> The traditional semantics of the 'x' bit on directories is awful;
>> Banyan Vines had an explicit 'scan' attrib on directories for this,
>> and I believe Windows has something as well. Some way to express
>> "permission to descend into this directory" as opposed to "permission
>> to readdir() this directory". Something that is NOT the 'x' bit.
>> Would be perhaps too awful or impossible to add to POSIX, I don't know.
>
>
> In Windows they also just have a bit for "traverse directory / execute
> file" and another bit for "list directory / read data".
>
> However, the default policy makes the OS ignore the traverse/execute
> for directory traversal (but not file execution) entirely!
I don't understand the sentence above. Is the bit only used by the
nondefault policies?
> This might be the way to go in Linux as well.
>
>
next prev parent reply other threads:[~2004-04-30 4:55 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 [this message]
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
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=4091DC48.1070304@namesys.com \
--to=reiser@namesys.com \
--cc=bwaters+mac@aoc.nrao.edu \
--cc=mine0057@mrs.umn.edu \
--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.