When using baselayout-2, a starting linux-VServer show the following error: FATAL: Could not load /lib/modules/2.6.19-hardened-r6/modules.dep: No such file or directory This is caused by /etc/init.d/localhost on 61: modprobe -q usbcore modprobe complains because the modules.dep file does not exist. I fixed it by putting around the modprobe line: if [ -f /lib/modules/`uname -r`/modules.dep ] ; then // modprobe line here fi Maybe there's a better way than 2 if's... but I'm not an expert with shell scripting
err... localmount, not localhost :)
Dunno about fixing this. Your solution hides the real error of the kernel modules not being installed correctly. If you don't have any modules, or a vserver can't load them, then you should not enable module support in the kernel.
(In reply to comment #2) > Dunno about fixing this. > Your solution hides the real error of the kernel modules not being installed > correctly. If you don't have any modules, or a vserver can't load them, then > you should not enable module support in the kernel. > /lib/modules/2.6.19-hardened-r6/modules.dep is present on the host, but not inside a vserver. I do want to load modules on the host. The baselayout script does use modprobe -q to silence errors in case the usb-core does not exist. This is good. Hoever, -q does not hide the error about the missing modules.dep... which is not present in a vserver.
Then /proc/modules should not be present inside a vserver. It implies by its very existance that the running kernel supports modules.
as Roy said, checking for the existence of the .dep file is not the answer
only a cosmetic bug *** This bug has been marked as a duplicate of bug 186521 ***
It should also be noted with baselayout2 and upwards you can remove the modules init script from the boot runlevel in the vserver.
