tlu: the kernel portion of apparmor had not been accepted in the 2.6.32.x kernels (it was accepted by upstream in 2.6.36). The mainline kernel packages did not include the apparmor patches.
Dale: all of the released Ubuntu 10.04 LTS kernels, including 2.6.32-32, have shipped with apparmor patches incorporated and enabled. The apparmor initscript is what mounts the securityfs/apparmor filesystem. By default, it should be located in /etc/rcS.d/; what does 'ls -l /etc/rcS.d/*apparmor' report? What does /proc/version_signature report?
Anyway, the specific issue that this bug report covered was fixed long ago. Dale, you'd probably be best off reporting a new bug, preferebly via "ubuntu-bug apparmor". Thanks.
tlu: the kernel portion of apparmor had not been accepted in the 2.6.32.x kernels (it was accepted by upstream in 2.6.36). The mainline kernel packages did not include the apparmor patches.
Dale: all of the released Ubuntu 10.04 LTS kernels, including 2.6.32-32, have shipped with apparmor patches incorporated and enabled. The apparmor initscript is what mounts the securityfs/apparmor filesystem. By default, it should be located in /etc/rcS.d/; what does 'ls -l /etc/rcS. d/*apparmor' report? What does /proc/version_ signature report?
Anyway, the specific issue that this bug report covered was fixed long ago. Dale, you'd probably be best off reporting a new bug, preferebly via "ubuntu-bug apparmor". Thanks.