#acl PaulHowarth:read,write,admin,revert,delete All:read

=== Saturday 15th November 2008 ===

==== Kernel loop module now built-in in Fedora 9 ====

Rebooted my build server into the new `2.6.27.5-37.fc9.x86_64` kernel and found that a bunch of loopback-mounted
ISO images didn't get mounted, due to running out of loop devices. This is a problem I'd fixed a long time ago by
creating a file `/etc/modprobe.d/loop` containing this line:
{{{
options loop max_loop=64
}}}
Running `lsmod` revealed that the `loop` module wasn't even loaded.
It turned out that this kernel update has a new configuration in which the `loop` module is built-in to the kernel
rather than being a module:
{{{
$ fgrep LOOP /boot/config-2.6.2*
/boot/config-2.6.26.5-45.fc9.x86_64:CONFIG_BLK_DEV_LOOP=m
/boot/config-2.6.26.5-45.fc9.x86_64:CONFIG_BLK_DEV_CRYPTOLOOP=m
/boot/config-2.6.26.6-79.fc9.x86_64:CONFIG_BLK_DEV_LOOP=m
/boot/config-2.6.26.6-79.fc9.x86_64:CONFIG_BLK_DEV_CRYPTOLOOP=m
/boot/config-2.6.27.5-37.fc9.x86_64:CONFIG_BLK_DEV_LOOP=y
/boot/config-2.6.27.5-37.fc9.x86_64:CONFIG_BLK_DEV_CRYPTOLOOP=m
}}}
I don't know if this is going to a long-term change or not since I didn't see anything in the changelog about it, but the
fix for now is to add the appropriate option in `/boot/grub/grub.conf`:
{{{
title Fedora (2.6.27.5-37.fc9.x86_64)
	root (hd0,1)
	kernel /vmlinuz-2.6.27.5-37.fc9.x86_64 ro root=/dev/VgOS/lvroot max_loop=64
	initrd /initrd-2.6.27.5-37.fc9.x86_64.img
}}}

==== Local Packages ====

 * Final one of the `perl` module package cleanups: `perl-Test-Manifest`


----