Re: Semantics of setting an extended attribute to empty vs removexattr?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux