From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 9 15:59:54 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C65716A402; Mon, 9 Apr 2007 15:59:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id EE82313C448; Mon, 9 Apr 2007 15:59:53 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 2E0CF1A4D84; Mon, 9 Apr 2007 08:59:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 22D9D517C9; Mon, 9 Apr 2007 11:59:52 -0400 (EDT) Date: Mon, 9 Apr 2007 11:59:52 -0400 From: Kris Kennaway To: Tim Kientzle Message-ID: <20070409155952.GA31477@xor.obsecurity.org> References: <20070407174756.GA46385@roadrunner.q.local> <4617F67B.7050304@freebsd.org> <20070408080233.GB40103@roadrunner.q.local> <4619B91E.6010803@freebsd.org> <461A5DEE.6000606@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <461A5DEE.6000606@freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: hackers@freebsd.org, Ulrich Spoerlein Subject: Re: 'opaque' flag? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2007 15:59:54 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 09, 2007 at 08:38:22AM -0700, Tim Kientzle wrote: > Tim Kientzle wrote: > >Does anyone understand the semantics of the 'opaque' flag? > > > >I'm trying to understand an issue with packages built > >on union file systems. It appears the 'opaque' flag > >is set on some symlinks, which the package tools then > >archive. The archived flag is somehow interfering with > >later installation of the package. > > > >I've read McKusick's paper on unionfs which explains > >the opaque flag for directories created on a unionfs, > >but I have a bunch of questions: > > * Why is it appearing on symlinks? > > * How could the opaque flag interfere with package installs? > > * Should bsdtar ignore opaque flags? >=20 > Okay, I now understand the answer to the second question: > there's a bug in libarchive restoring symlinks with flags. > I'll fix that shortly. >=20 > The other two questions still puzzle me. I suspect the opaque flag should be ignored since it is a property of a specific unionfs stack, so it is not suitable for transporting elsewhere via bsdtar. Similarly with the snapshot flag. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGGmL3Wry0BWjoQKURAiaHAKDbFGIbyjSjD3WEjZJt1AaMG/VLgACgmbuj o2h11ybruK5ejOZG9Far7V4= =LpMF -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--