heavytull <heavytull@hotmail.com> wrote:
>>> the "loop" module on my linux box is not loaded itself when needed by
>>> mount. when I type mount -o loop ...
>>> While this module does not appear in the blacklist of modprobe
>>> (/etc/modprobe.d/blacklist)

I'm only guessing now, but this is what I would think is the
explanation: Blacklist is used by hotplug. Hotplug loads modules when it
finds new hardware. As there is no particular hardware associated with the
loopback module it won't be loaded by hotplug.

>> i'll bet you've gone and mucked with your kernel, hey?
> you mean?
> you mean that i custom tuned the kernel?
> yes i'm doing so since long. but I don't think this is related to that.

I think it does if the default kernel has loopback built in and not as a
module.

>> so what happens if you force a modprobe loop ?

> the module gets loaded and works fine

So you have 3 choices:

1) Manually load the module before doing a loopback mount and then maybe
manually unload the module after umount.

2) Allways have the module loaded, maybe from /etc/rc.d/rc.modules.

3) If you like the automatic solution nr 2 above you might just as well
build a kernel with loopback support built in.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc8(at)uthyres.com Examples of addresses which go to spammers:
root@variousus.net root@localhost