IF the problem is the stacked file system, then why am I able to, after booting, do:
sudo /etc/init.d/apparmor start
on my persistent 9.10 Live CD and have no errors?
Is it possible that this 'bug' with the stacked file system is just a problem caused by the Ubuntu initrd.lz trying to load apparmor profiles before the casper script has had a chance to fully create the stacked file system? (please see prior post #44 that addresses the sequence of script events during the Live CD boot process) I am just wondering if the problem is with the Ubuntu customization of the 'init' and 'casper' scripts within the Ubuntu initrd.lz, and not really an upstream problem at all.
IF the problem is the stacked file system, then why am I able to, after booting, do:
sudo /etc/init. d/apparmor start
on my persistent 9.10 Live CD and have no errors?
Is it possible that this 'bug' with the stacked file system is just a problem caused by the Ubuntu initrd.lz trying to load apparmor profiles before the casper script has had a chance to fully create the stacked file system? (please see prior post #44 that addresses the sequence of script events during the Live CD boot process) I am just wondering if the problem is with the Ubuntu customization of the 'init' and 'casper' scripts within the Ubuntu initrd.lz, and not really an upstream problem at all.