loop device

[Eugene Gorodinsky]

Since nobody answered, I guess there's no reason for it. Is it
possible then to change the option "CONFIG_BLK_DEV_LOOP=y" to
"CONFIG_BLK_DEV_LOOP=m"? This allows to enable loop device partitions
(by setting the max_part option, which doesn't work when the module is
compiled in) as well as change the number of loop devices. I wanted to
submit a patch, but apparently the configs are generated
automatically, so I'm not really sure how to do that.

2009/9/2 Eugene Gorodinsky <e.gorodinsky at gmail.com>:
> Hi all, I've noticed yesterday when working with the loop device that
> it's compiled into the kernel on my 9.04. Are there any particular
> reasons for that? It seems to me that it would be better if it was
> compiled as a loadable module (since users don't require it all the
> time).
>