'opaque' flag?

[Kris Kennaway]

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?
> 
> 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.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20070409/33591404/attachment.pgp