| 1 |
On Mon, Feb 19, 2007 at 12:35:13PM +0200, Alan McKinnon wrote |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> Kernel 2.6.20-gentoo |
| 5 |
> |
| 6 |
> My various /dev/loop/* devices used to always JustWork, until a recent |
| 7 |
> update. Unfortunately I can't tell when the breakage happened. |
| 8 |
> |
| 9 |
> Right now what happens is I don't get these devices automatically |
| 10 |
> and 'mount - o loop' fails. A simple 'modprobe loop' fixes this, the |
| 11 |
> kernel is configured as I've been using it for ages: |
| 12 |
> |
| 13 |
> config-2.6.20-gentoo:CONFIG_BLK_DEV_LOOP=m |
| 14 |
> config-2.6.20-gentoo:CONFIG_KMOD=y |
| 15 |
> |
| 16 |
> Oddly, I never had 'loop' in /etc/modules.autoload.d/kernel-2.6 before |
| 17 |
> (I do now), anyone know of a recent change that would cause this? |
| 18 |
|
| 19 |
If you want loopback devices to "just work", they should be compiled |
| 20 |
into the kernel, like so... |
| 21 |
|
| 22 |
make menuconfig |
| 23 |
Device Drivers ---> |
| 24 |
Block devices ---> |
| 25 |
<*> Loopback device support |
| 26 |
|
| 27 |
My guess is that somewhere along the line, the "<*>" got changed to a |
| 28 |
"<M>". Change it back to "<*>", recompile the kernel and any necessary |
| 29 |
modules, and reboot. |
| 30 |
|
| 31 |
-- |
| 32 |
Walter Dnes <waltdnes@××××××××.org> In linux /sbin/init is Job #1 |
| 33 |
My musings on technology and security at http://techsec.blog.ca |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives