loop device

Eugene Gorodinsky e.gorodinsky at gmail.com
Sun Sep 6 23:42:18 UTC 2009

Sorry, I meant nobody had stated the reasons for compiling the loop
device into the kernel. Or was that the reason to compile it in rather
than the reason to not compile it in?

2009/9/7 Pete Graner <pgraner at canonical.com>:
> Eugene Gorodinsky wrote:
>> 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.
> It was answered on list on the 2nd:
> https://lists.ubuntu.com/archives/kernel-team/2009-September/007152.html
> ~pete
> --
> Pete Graner             <pgraner at canonical.com>
> Manager
> Ubuntu Kernel Team
> Canonical Ltd.          http://www.canonical.com/

More information about the kernel-team mailing list