On Wed, Oct 25, 2000 at 02:50:32AM +0200, Andreas Gruenbacher wrote:
On Tue, 24 Oct 2000, Christoph Hellwig wrote:
[...] But the ACL implementation is not generic enough, IMHO.
The ACL implementation is Posix 1003.1e draft standard 17 compliant. AFAIK
neither of the other ACL
--On 10/27/00 14:33:33 -0700 Hans Reiser [EMAIL PROTECTED] wrote:
The atomic restriction can be enforced in a component separate. I mean,
ACLs have all sorts of restrictions on them, and atomicity is one of a
great many of them, so you have to have a separate component restricting
things
On Thu, Oct 26, 2000 at 04:14:06PM +0100, Stephen C. Tweedie wrote:
Either way, the point stands -- building APIs on assumptions about
implementation details (in this case, that ACLs are built on top of
EAs) is a bad thing.
True enough.
The interface I proposed doesn't enforce
Curtis Anderson wrote:
So it's not clear how you reached to the conclusion that directories
shouldn't be pressed into service as compound files. I'm sure you have
a reason, but it wasn't revealed here!
It's an aesthetics argument. There are no new features in a directory-based
On Thu, 26 Oct 2000 [EMAIL PROTECTED] wrote:
For an existing API (which I am not proposing be taken as is) take a look
at the xfs man pages here:
http://oss.sgi.com/projects/xfs/manpages.html
Sorry, but I think the root namespace is a serious misdesign. The root
user shouldn't be
Andreas Gruenbacher wrote:
On Thu, 26 Oct 2000 [EMAIL PROTECTED] wrote:
For an existing API (which I am not proposing be taken as is) take a look
at the xfs man pages here:
http://oss.sgi.com/projects/xfs/manpages.html
Sorry, but I think the root namespace is a serious
On Fri, Oct 27, 2000 at 12:24:19AM +0200, Andreas Gruenbacher wrote:
I don't think so. My suggestion would be this: All user EAs are prefixed
with "user." when passed to the kernel. The prefix is not actually stored
on the filesystem. Likewise, all root EAs are prefixed with "root.".
If they
Curtis Anderson wrote:
The problem with streams-style attributes comes from stepping onto the
slippery slope of trying to put too much generality into it. I chose the
block-access style of API so that there would be no temptation to start
down that slope.
I understand you right up until
Daniel Phillips wrote:
Curtis Anderson wrote:
For example, "mv" will devolve to "cp" when the source and destination
filesystems are different. So "mv" will preserve attributes for some
operations, and will drop them on the floor for others. Unexpected by the
average user, and