From owner-freebsd-questions@FreeBSD.ORG Wed Aug 11 22:37:59 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C48E106564A for ; Wed, 11 Aug 2010 22:37:59 +0000 (UTC) (envelope-from carlj@peak.org) Received: from redcondor1.peak.org (redcondor1.peak.org [69.59.192.54]) by mx1.freebsd.org (Postfix) with ESMTP id D26A98FC16 for ; Wed, 11 Aug 2010 22:37:58 +0000 (UTC) Received: from peak-mail-gateway.peak.org ([69.59.192.42]) by redcondor1.peak.org ({e03e86cd-14ae-47ce-9578-3c080ce9c462}) via TCP (outbound) with ESMTP id 20100811223720350 for ; Wed, 11 Aug 2010 22:37:20 +0000 X-RC-FROM: X-RC-RCPT: Received: from cjlinux.localnet (207.55.91.197.peak.org [207.55.91.197] (may be forged)) (authenticated bits=0) by peak-mail-gateway.peak.org (8.12.10/8.12.8) with ESMTP id o7BMbIw7096109 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 11 Aug 2010 15:37:19 -0700 (PDT) Received: from carlj by cjlinux.localnet with local (Exim 4.69) (envelope-from ) id 1OjJvB-0002CI-M4 for freebsd-questions@freebsd.org; Wed, 11 Aug 2010 15:37:17 -0700 To: freebsd-questions@freebsd.org References: <20100809180022.GA33596@freebsd.org> <20100811100847.GA20045@freebsd.org> From: Carl Johnson Date: Wed, 11 Aug 2010 15:37:17 -0700 In-Reply-To: <20100811100847.GA20045@freebsd.org> (Alexander Best's message of "Wed\, 11 Aug 2010 10\:08\:47 +0000") Message-ID: <87fwykdbdu.fsf@cjlinux.localnet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: chflags(1) unaware utilties X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2010 22:37:59 -0000 Alexander Best writes: > On Tue Aug 10 10, illoai@gmail.com wrote: >> On 9 August 2010 14:00, Alexander Best wrote: >> > hi there, >> > >> > chflags(1) mentions that a few utilities including pax(1) aren't chflags aware yet. is there a list of all those utilties available somewhere? >> > also: i don't quite understand why this is in the BUGS section of chflags(1) and not in the pax(1) manual itself [1]. this doesn't seem very logical, since the bug doesn't exist in chflags, but in pax not supporting chflags. >> > so if someone decides to use pax and wants to know if there are any problem with it, there's no way for the average user to stumble upon the fact that chflags isn't supported in pax. >> > >> > in fact the pax(1) manual states that `pax -p e` will "preserve everything". this is plain wrong! >> > >> > cheers. >> > alex >> > >> > [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/135516 >> > >> >> AFIK, pax is a POSIX thing, and as such working >> correctly or sanely would violate its posix nature. >> (POSIX is an anagram of "Pox? Si!") > > POSIX specs issue 7 state that `pax -p e` should: > > "Preserve the user ID, group ID, file mode bits (see XBD File Mode Bits ), access time, modification time, and any other implementation-defined file characteristics." > > don't chflags fall under "other implementation-defined file characteristics"? > >> >> Is cpio chflags-aware? > > hmm...no idea. sorry. I just did some simple-minded testing and found that BSD tar is chflags aware, but GNU tar, pax, afio, and cpio are not. I also found that BSD cp will copy flags, but GNU cp (from coreutils port) will not. I also checked extended attributes (see lsextattr(8)) and found that only BSD tar will archive them, and cp will not copy them. I didn't check dump since someone already said it will work. I also checked zfs and found that tar doesn't handle extended attributes there and zfs doesn't support flags. The rest of my testings was on the standard ufs2. It doesn't look very encouraging to me. -- Carl Johnson carlj@peak.org