From: Ruediger L. <ru...@ma...> - 2009-10-21 16:02:35
|
another issue: If a device is unmounted without rox-media ( shell, rox-filer, another user,..), the green mount light disappears instantly, although file system buffers are not flushed (a common situation with usb flash devices ). Only If I use rox-media to unmount the device, the orange light is displayed during this phase. It would be possible to indicate the current state even if an external tool is used for unmountig. The signal "job-changed" seems to be emitted at the begin and end of a flush operation. cosmetic issues: - if a device is already mounted, a left click should open a filer windows instead of trying to mount it again and display an error message ( or at least refuse to mount it ) - don't tie it to rox as filer, but let the users set an custom command. It might be useful in other contexts, too ( e.g. fluxbox without a complete desktop environment ). On Tue, 20 Oct 2009 00:31:55 +0100 Tony Houghton <h...@re...> wrote: > That would do as a temporary measure, but it should be possible to > get a password from the user and mount it shouldn't it? Ok, a small patch for luks support as attachment (If the mailing list don't support attachments: http://pastebin.com/m11818a34 ) Implementation is easy; Gdu* even provides an interface to gnome-keyring for passphrase input and management. However, there is an issue I'm not sure how to deal with. GduDevice supports tree states in this context: 1) the luks device is locked ( just encrypted /dev/sdxN accessible) 2) the luks device is unlocked but not mounted ( cleartext access at /dev/mapper/xyz is possible, but /dev/mapper/xyz is not mounted ) 3) luks device is unlocked and /dev/mapper/xyz is mounted. I find this confusing for everyday usage. Users normally just want to mount or umount their external devices (they only need this distinction, if they want to format an encrypted device or run fsck). Therefore, I try to avoid the second state. If an luks device was opened by rox-media and they unmount /media/XYZ with rox-filer or another tool, the device is automatically locked. So only a "mount" and "unmount" button is needed - just as in the case of not encrypted devices. Another solution would be to provide two additional buttons for encrypted devices ( lock and unlock ) and don't hide these details from the users. The usual gnome and kde interface don't support the second state, too ( but perhaps just because hal doesn't support this state) It's also easier for them, because hal/gdu is integrated in their filers as well. There are no different "mount/unmount" buttons users could click on. |