Hello,
Marc Haber wrote:
> when one uses pmount to mount a crypted volume, one forgets how to use
> cryptsetup. Thus, it is hard to fsck the crypted file system since
> pmount immediately mounts the file system.
>
> Please consider implementing a --no-mount option which does everything
> short of the actual mount and optionally prints the device name so
> that one can manually fsck the volume.
Sorry for the late reply, I'm slowly trying to lower the number of
accumulated bugs for pmount...
I'm afraid I don't really see the point of this option: unless I'm
very much mistaken, you will need to be root to fsck the unmounted
device, so there is nothing that pmount will be able to bring.
If you really want to know what pmount is doing so you are able to
reproduce it by hand (being root, of course), just launch it with the
--debug switch.
I'm a little reluctant to modify pmount more than is necessary, as it
is used to give privileges to (not-so-trusted) users.
Cheers,
Vincent
--
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/
find(1):
A `%' at the end of the format argument causes undefined behaviour
since there is no following character. In some locales, it may
hide your door keys, while in others it may remove the final page
from the novel you are reading.
Vincent, listening to Love Me Do (The Beatles)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
