From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 9 15:38:23 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 5F37716A401 for ; Mon, 9 Apr 2007 15:38:23 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3FB1F13C45D for ; Mon, 9 Apr 2007 15:38:23 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l39FcMH7084382; Mon, 9 Apr 2007 08:38:23 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <461A5DEE.6000606@freebsd.org> Date: Mon, 09 Apr 2007 08:38:22 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <20070407174756.GA46385@roadrunner.q.local> <4617F67B.7050304@freebsd.org> <20070408080233.GB40103@roadrunner.q.local> <4619B91E.6010803@freebsd.org> In-Reply-To: <4619B91E.6010803@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: 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:38:23 -0000 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? 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. The other two questions still puzzle me. Tim