* Cristian Rodríguez [10-22-13 10:07]:

El 22/10/13 01:18, Marc Chamberlin escribió:

...

If this loop kernel module is required by Realcrypt, why didn't YaST load if for me when I selected Realcrypt for installation? Seems like I shouldn't have to go and hunt this solution down like this.

echo "loop" > /etc/modules.load.d/loop.conf

echo "loop" > /etc/modules-load.d/loop.conf

that's it. the next time you reboot the module will be loaded for you.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 22/10/13 13:51, Per Jessen escribió:

That works, but didn't modules such as this used to be loaded on-demand or am I imagining things? I don't recall ever having to add e.g. loop to any file. Now I often have to add e.g. 'loop' and 'ipmi'.

The loop module is an exception as well others might be when the module cannot be automatically loaded either by the kernel or udev. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/22/2013 10:22 AM, Andrey Borzenkov wrote:

В Tue, 22 Oct 2013 18:51:02 +0200 Per Jessen пишет:

...

Patrick Shanahan wrote:

...

* Cristian Rodríguez [10-22-13 10:07]:

...

El 22/10/13 01:18, Marc Chamberlin escribió:

...

If this loop kernel module is required by Realcrypt, why didn't YaST load if for me when I selected Realcrypt for installation? Seems like I shouldn't have to go and hunt this solution down like this. echo "loop" > /etc/modules.load.d/loop.conf echo "loop" > /etc/modules-load.d/loop.conf That works, but didn't modules such as this used to be loaded on-demand or am I imagining things? They are if program is using the right calls. losetup does not need loop to be preloaded.

...

I don't recall ever having to add e.g. loop to any file.

In the past several /dev/loopX devices were pre-created initially which caused loop to be loaded on access. Now loop has API to dynamically allocate new loop device so it is not really needed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Thanks guys for all the feedback and instructions. I have followed them. One more question, is this a bug that should be reported? Unless this addition of the loop module is automated somehow, I think this will become a stumbling block for others as well. I will be happy to submit it if the consensus is yes... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org