On Tue, Jun 22, 2010 at 02:45:13AM -0000, Sid MacT wrote:
> Is it possible that simply changing the apparmor profile load process to
> follow the creation of the union file system, would allow apparmor to
> execute properly? It seems like an odd coincidence that lots of software
> EXCEPT apparmor appears to run flawlessly on the 'stacked' file system,
> and that apparmor is happy to load profiles after booting the Live CD?
That is precisely the bug: AppArmor does not operate on a stacked
filesystem, so it must be disabled in the LiveCD. AIUI, when proper
union mount support is added to the upstream kernel, these problems will
start to disappear. :)
On Tue, Jun 22, 2010 at 02:45:13AM -0000, Sid MacT wrote:
> Is it possible that simply changing the apparmor profile load process to
> follow the creation of the union file system, would allow apparmor to
> execute properly? It seems like an odd coincidence that lots of software
> EXCEPT apparmor appears to run flawlessly on the 'stacked' file system,
> and that apparmor is happy to load profiles after booting the Live CD?
That is precisely the bug: AppArmor does not operate on a stacked
filesystem, so it must be disabled in the LiveCD. AIUI, when proper
union mount support is added to the upstream kernel, these problems will
start to disappear. :)
http:// valerieaurora. org/union/