On Sat, Oct 11, 2008 at 10:01:56PM +0200, Vincent Fourmond wrote: > 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.
It saves one from remembering the correct options for cryptsetup, and one could allow the users to fsck the volume via sudo. > 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. That output is rather copious. > I'm a little reluctant to modify pmount more than is necessary, as it > is used to give privileges to (not-so-trusted) users. It's your prerogative to tag the bug wontfix or even close it, it's wishlist after all. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
