Date: Sun, 08 Apr 2007 20:55:10 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: hackers@freebsd.org Cc: Ulrich Spoerlein <uspoerlein@gmail.com> Subject: 'opaque' flag? Message-ID: <4619B91E.6010803@freebsd.org> In-Reply-To: <20070408080233.GB40103@roadrunner.q.local> References: <20070407174756.GA46385@roadrunner.q.local> <4617F67B.7050304@freebsd.org> <20070408080233.GB40103@roadrunner.q.local>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Any input appreciated, Tim Kientzle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4619B91E.6010803>