From: Daniel Phillips Subject: Re: Semantics of setting an extended attribute to empty vs removexattr? Date: Wed, 24 Sep 2008 17:38:59 -0700 Message-ID: <200809241739.02460.phillips@phunq.net> References: <200809241519.19202.phillips@phunq.net> <1222299665.4860.5.camel@verge.scott.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Nathan Scott Return-path: Received: from phunq.net ([64.81.85.152]:55570 "EHLO moonbase.phunq.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751927AbYIYAjI (ORCPT ); Wed, 24 Sep 2008 20:39:08 -0400 In-Reply-To: <1222299665.4860.5.camel@verge.scott.net.au> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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