On 4/24/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> Here's a proposed change to fix the handling of unmanaged files a bit
> cleaner at the same time as it adds support for unmanaged files to
> FiboSandbox. In short what it does:
> It adds support for mapped mounts to FiboSandbox. This is implemented so
> that for every system directory in the mapped mounts option will have a
> corresponding directory in Resources/Unmanaged in the ${target} directory,
> which will be bind mounted over the system directory redirecting all
> writes into the system directory to the directory in Resources/Unmanaged.
> Easy, huh? :)
> An example:
> /System/Kernel/Modules/$(uname -r)/misc/ndiswrapper.ko is in the unmanaged
> file array. Then
> ${target}/Resources/Unmanaged/System/Kernel/Modules/$(uname -r)/misc will
> be bind mounted over /System/Kernel/Modules/$(uname -r)/misc, so when the
> installer tries to copy the file to /System/Kernel/Modules/$(uname
> -r)/misc it will be redirected, through the mount, to
> ${target}/Resources/Unmanaged/System/Kernel/Modules/$(uname -r)/misc
>
> Union sandbox already had mapped mounts.
>
> Then I made Compile parse the unmanaged_files array and pass it to
> SandboxInstall that made it to mapped mounts, which both FiboSandbox and
> UnionSandbox now supports.

My only fear is that the fact that now the bind-mount is occluding any
existing contents of directories that will receive unmanaged files may
for some strange reason break some recipe. I couldn't think of any
case, but it's a possibility.

Maybe this new support could be added to FiboSandbox but keep Compile
working with unionfs the same way as it does now (and switch
UnionSandbox behavior to use mapped mounts later)? One problem
implementing this idea is that the use of Union vs Fibo is transparent
to Compile now, AFAIK. OTOH, maybe I'm just being too paranoid.

-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to