mo0nykit
September 28th, 2009, 11:44 AM
Hello!
I have succeeded in compiling, installing, and booting from a 2.6.31 kernel in Jaunty. But when I look at the startup screens, it says loading AppArmor module... FAILED. When I finally get into the desktop, then into a terminal, I look up the apparmor_status and here's the output: $apparmor_status
apparmor module is loaded.
apparmor filesystem is not mounted.Is this a conflicting report, considering that it FAILED at bootup? Is there something wrong?
Going back to the top of my source tree, I do a make menuconfig I go into Ubuntu Supplied Third Party Drivers --> and yes, AppArmor support is set as built-in. AppArmor boot parameter default value is 1, meaning, "start during boot up". Well I read an AppArmor bug report here apparmor fails to load at startup (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/375422). It refers to kernel 2.6.30. I don't know if it holds true for the patched 2.6.31 (Ubuntu patch 11.36)
I have succeeded in compiling, installing, and booting from a 2.6.31 kernel in Jaunty. But when I look at the startup screens, it says loading AppArmor module... FAILED. When I finally get into the desktop, then into a terminal, I look up the apparmor_status and here's the output: $apparmor_status
apparmor module is loaded.
apparmor filesystem is not mounted.Is this a conflicting report, considering that it FAILED at bootup? Is there something wrong?
Going back to the top of my source tree, I do a make menuconfig I go into Ubuntu Supplied Third Party Drivers --> and yes, AppArmor support is set as built-in. AppArmor boot parameter default value is 1, meaning, "start during boot up". Well I read an AppArmor bug report here apparmor fails to load at startup (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/375422). It refers to kernel 2.6.30. I don't know if it holds true for the patched 2.6.31 (Ubuntu patch 11.36)