I think this is really a problem with the libdevmapper package (1.02.08)
in the ubuntu-7.04-beta release which I have tried this on. The problem
seems to be entirely due to the failure to load the main device-mapper
kernel-module either on system boot-up or when libdevmapper is first
used. The debian libdevmapper packages (1.01, 1.02) include a script in
/etc/init.d which automatically modprobes dm-mod (and a few other
modules). An alternative approach would be to modify libdevmapper itself
to execute this modprobe itself.
>From my experiments on ubuntu-7.04-beta, it appears that solely executing:
modprobe dm-mod
(as root) is sufficient to get cryptmount working fine. Clearly this is not
ideal if one wishes to use cryptmount, as intended, without becoming root.
However, as an interim fix, one could add a line of the form:
modprobe dm-mod || true
(and perhaps "modprobe dm-crypt || true" as well, to be on the safe side) to
either /etc/rc.local or to /etc/init.d/cryptmount (just before the line
starting "test -x ${CM_EXE}...."). Both of these should ensure that the
necessary kernel modules are loaded at system startup. Provided the modules
don't get automatically or manually removed, this should be sufficient to
ensure that cryptmount behaves as expected.
However, I must reiterate, that I believe that this bug is far better
addressed through modifications to the libdevmapper package.
--
cannot initialize device-mapper
https://bugs.launchpad.net/bugs/93568
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
