On Saturday 21 July 2007 17:44, Frans Pop wrote: > The actual name of the module is loop-aes.ko. I've just verified that > if the regular loop.ko is already loaded, 'modprobe loop-aes' seems to > succeed, but does not do anything. modprobe can be made to fail by using the --first-time option: # modprobe loop # modprobe --first-time loop-aes || echo $? FATAL: Module loop already in kernel. 1 > As the CD image is mounted at that time (and so in theory could other > things), I think what we'd need to do when loading loop-aes is: > - test if loop is already loaded > - somehow test if it is the correct variant of the module or not I think the current code is already smart enough that it will not try setting up crypto support more than once. If that is the case that we can probably just: if ! modprobe --first-time loop-aes; then # umount loop-mounted devices modprobe -r loop modprobe --first-time loop-aes # remount loop-mounted devices fi
Attachment:
pgpgVhat0Jm3F.pgp
Description: PGP signature