All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Andreas Gruenbacher <agruen@suse.de>,
	acl-devel@bestbits.at, linux-fsdevel@vger.kernel.org,
	Luka Renko <luka.renko@hermes.si>
Subject: Re: JFS extended attributes and ACLs - New Patches
Date: Fri, 13 Sep 2002 15:06:40 +1000	[thread overview]
Message-ID: <20020913050640.GC532@frodo> (raw)
In-Reply-To: <200209121234.29784.shaggy@austin.ibm.com>

hi Dave,

On Thu, Sep 12, 2002 at 12:34:29PM -0500, Dave Kleikamp wrote:
> On Thursday 12 September 2002 12:04, Andreas Gruenbacher wrote:
> 
> > Can you implement the `os2.' namespace in the JFS patches? I'd be
> > much happier with the patch.
> 
> I believe I can.  I will use the 'os2.' prefix externally, but store it 
> without the prefix.  On the other side, any attribute that doesn't 
> begin with a known prefix will get 'os2.' prepended when listing the 
> xattrs.

This is basically what we do in XFS - we have a separate namespace
for accessing the actual ondisk names &/ values of what on IRIX is
called the ROOT namespace - on Linux the "xfsroot" namespace.  This
is how xfsdump and xfsrestore are able to work with the same on-tape
format that is used in IRIX - they manipulate attributes in this
XFS-specific namespace while the generic ACL tools (setfacl, getfacl,
and co) access the system.posix_acl names, which are then independent
of the underlying filesystem type.

I would shy away from a "hierarchical" namespace approach; if I grok
what you're saying, I think it would mean that the value for the name
"user.os2.a" would be different between filesystems (for JFS it would
mean "a" in the user.os2 namespace, for everyone else it would mean
"os2.a" in the user namespace) - that'd be pretty confusing.

cheers.

-- 
Nathan

  reply	other threads:[~2002-09-13  5:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10  7:40 JFS extended attributes and ACLs - New Patches Luka Renko
2002-09-12 15:13 ` Andreas Gruenbacher
2002-09-12 16:16   ` Dave Kleikamp
2002-09-12 17:04     ` Andreas Gruenbacher
2002-09-12 17:34       ` Dave Kleikamp
2002-09-13  5:06         ` Nathan Scott [this message]
2002-09-13  9:27           ` Andreas Gruenbacher
2002-09-13 12:18           ` Dave Kleikamp
2002-09-13 13:20             ` [Acl-Devel] " Andreas Gruenbacher
2002-09-13 13:33               ` Dave Kleikamp
2002-09-13  9:32         ` Andreas Gruenbacher
     [not found] <Pine.LNX.4.33.0209061703200.26258-100000@wotan.suse.de>
     [not found] ` <200209061718.59114.agruen@suse.de>
2002-09-09 14:58   ` Dave Kleikamp
2002-09-09 15:02     ` Andreas Gruenbacher
2002-09-09 15:28       ` Dave Kleikamp
2002-09-09 15:30         ` Dave Kleikamp

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=20020913050640.GC532@frodo \
    --to=nathans@sgi.com \
    --cc=acl-devel@bestbits.at \
    --cc=agruen@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=luka.renko@hermes.si \
    --cc=shaggy@austin.ibm.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.