All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@phunq.net>
To: Nathan Scott <nscott@aconex.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Semantics of setting an extended attribute to empty vs removexattr?
Date: Wed, 24 Sep 2008 17:38:59 -0700	[thread overview]
Message-ID: <200809241739.02460.phillips@phunq.net> (raw)
In-Reply-To: <1222299665.4860.5.camel@verge.scott.net.au>

On Wednesday 24 September 2008 16:41, Nathan Scott wrote:
> On Wed, 2008-09-24 at 15:19 -0700, Daniel Phillips wrote:
> > Hi,
> > 
> > Does anybody have an opinion on whether setting an extended attribute
> > to empty using the setxattr interface is supposed to be semantically
> > equivalent to removing the xattr using removexattr?
> 
> attr(5) states...
> 
> NAME
>        attr - Extended attributes
> 
> DESCRIPTION
> Extended  attributes  are  name:value pairs associated permanently with
> files and directories, similar to the  environment  strings  associated
> with  a  process.   An attribute may be defined or undefined.  If it is
> defined, its value may be empty or non-empty.
> 
> 
> XFS and extN certainly implement this property, I'd imagine all of the
> other filesystems supporting extended attributes do as well.

Yes, and Tux3 will be revised to toe the line, it's no big deal.  Thanks
for reading me the man page :-/

Regards,

Daniel

      reply	other threads:[~2008-09-25  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 22:19 Semantics of setting an extended attribute to empty vs removexattr? Daniel Phillips
2008-09-24 23:41 ` Nathan Scott
2008-09-25  0:38   ` Daniel Phillips [this message]

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=200809241739.02460.phillips@phunq.net \
    --to=phillips@phunq.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nscott@aconex.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.