Custom kernel not (auto)loading capabilities modules

[Jaime]

Hi.

When I boot from the "stock" Ubuntu kernel 2.6.8.1-3-386 (2.6.8.1-14),
the linux security modules "capability" and "commoncap" both get loaded.
The relevant part of my dmesg is:

<snip file="dmesg">
lp0: using parport0 (interrupt-driven).
Capability LSM initialized
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm at uk.sistina.com
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
</snip>

I'm currently using a custom kernel (built using kernel-package) with
both capability and commoncap enabled as modules, but when I boot I get
the following error message from the init scripts:

<snip>
 * Starting system message bus... [OK]
 * Starting Hardware absatraction layer...
00:22:08.204 [W] hald.c:301: Your kernel does not support capabilities;
some features will not be available
 * Starting file alteration monitor... [OK]
</snip>

The dmesg from my custom kernel shows the missing line:

<snip>
lp0: using parport0 (interrupt-driven).
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm at uk.sistina.com
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
</snip>

The bit I don't understand is that I _can_ manually load the
capabilities modules - "modprobe capaility" successfully loads
"capability" and "commoncap".
Here's the relevant section from my .config:

<snip>
# Security options
#
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=m
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set
<snip>

Should I just compile the modules into the kernel or put them
into /etc/modules, or is this a kernel bug (I'll log it if so)?

Thanks,

Jaime