From: Nathan Scott <nscott@aconex.com>
To: Daniel Phillips <phillips@phunq.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Semantics of setting an extended attribute to empty vs removexattr?
Date: Thu, 25 Sep 2008 09:41:05 +1000 [thread overview]
Message-ID: <1222299665.4860.5.camel@verge.scott.net.au> (raw)
In-Reply-To: <200809241519.19202.phillips@phunq.net>
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.
cheers.
--
Nathan
next prev parent reply other threads:[~2008-09-25 0:11 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 [this message]
2008-09-25 0:38 ` Daniel Phillips
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=1222299665.4860.5.camel@verge.scott.net.au \
--to=nscott@aconex.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=phillips@phunq.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).