From: Hans Reiser <reiser@namesys.com>
To: David Masover <jedi@ninja.dynup.net>
Cc: reiserfs-list@namesys.com, nikita@namesys.com
Subject: Re: V4 status
Date: Wed, 03 Dec 2003 22:30:00 +0300 [thread overview]
Message-ID: <3FCE39B8.20307@namesys.com> (raw)
In-Reply-To: <3FCD47C4.50500@ninja.dynup.net>
David Masover wrote:
>
>
> The only thing I might complain about is that, although it was listed
> as a possibility to display file permissions as files within a file
> (for example, I should be able to do 'touch file; ls file'), I have
> had two problems there. First, ls seems to know it's a file, and so I
> can't see any files within it. Second, it needs the executable bit,
> or I get permission denied errors when trying to look at any files
> inside it. Third, even with ls not working, no guesses I've made on
> potential filenames has worked.
Nikita will comment on the state of this code, and your remarks below.
>
> I know almost nothing about the interface behind this. That said,
> here's what I'd suggest (without knowing any better):
> - - If I look at something without using a trailing slash, it should
> be treated as a file, except maybe for compatibility reasons.
> - - If I do use a trailing slash, or as a parent directory to
> anything, it should be treated as a directory.
> - - If it is a regular file (and not a directory pretending to be a
> file through some odd plugin -- /etc/passwd could be a file
> constructed from files in /etc/passwd/) then permission to view it as
> a directory should be assumed for anyone with read access. As an
> alternative, the ability to change into a directory could be
> implemented as another security attribute, which is automatically
> linked to executable permission for "normal" directories.
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-12-03 19:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 1:16 V4 status Fredrik Tolf
2003-12-03 2:17 ` David Masover
2003-12-03 15:29 ` Redeeman
2003-12-04 1:24 ` grub (Re: V4 status) David Masover
2003-12-03 19:27 ` V4 status Hans Reiser
2003-12-03 19:30 ` Hans Reiser [this message]
2003-12-03 19:40 ` Nikita Danilov
2003-12-04 1:33 ` pseudo files (Re: V4 status) David Masover
2003-12-04 23:33 ` V4 status Enrique Perez-Terron
2003-12-05 3:50 ` pseudo files & execute bit (Re: V4 status) David Masover
2003-12-05 5:24 ` The x Bit Problem Grant Miner
2003-12-05 8:07 ` Bob
2003-12-05 12:30 ` Tomasz Rola
2003-12-05 14:04 ` Tomasz Rola
2003-12-05 12:44 ` Hans Reiser
2003-12-05 14:03 ` David Masover
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=3FCE39B8.20307@namesys.com \
--to=reiser@namesys.com \
--cc=jedi@ninja.dynup.net \
--cc=nikita@namesys.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.