Salute Martin (and hello to Sjoerd ;) I think it would be somehow a good idea to make the configuration dependent from a user (root) configurable file. One needs to add drive by drive explicitly to this file. In the file the drives should be distinguishable from vendor / model / user-editable-flags and there should be a possibility to set those user-editable-flags on the drive (like a stamp, is there some place left in the partition table? *g*).
Another approach would be, let pmount decide how it mounts a drive, dependent from its udev settings. Lets say a devicenode is created with gid=foo (like it does it right now with the gid "hal" instead of "disk" for usb-disks) pmount could see this as a hint that the mountpoint should be accessable by that group too. Maybe this could be merged with the first approach to save another .conf in /etc ;) but of course, the folks from udev would need to help there. The quick-and-dirty-at-least-it-works-but-is-potentially-insecure-hack would be, let the user decide once how those medias are treated and one rule applies for all. Write a bold, blinking, underlined and screeming (don't know how to make that though) comment in the $foo.conf or make a note in the documentation if one wants this feature, one should need to do "touch /etc/pmount_please_do_as_I_say_I_am_aware_that_it_may_be_dumb" or... whatever. What do you folks think? regards Michael Am Freitag, den 25.02.2005, 18:37 +0100 schrieb Martin Pitt: > Hi Michael! > > Michael Schmitt [2005-02-25 18:07 +0100]: > > Package: pmount > > Version: 0.7.1-1 > > Severity: wishlist > > > > /dev/sdc2 on /media/foobar type vfat > > (rw,noexec,nosuid,nodev,quiet,uid=1033,gid=46,umask=077) > > That is how a drive gets mounted as I plug it in (USB), but I need some > > facility to tweak that behavior. I use gnome-volume-manager and I am not > > absolutely sure that this bugreport is sent to the right place, maybe gvm > > and > > hal needs to be tweaked too to get what I wish. Any hints would be > > appreciated. > > Right now pmount does not offer an option to modify the umask. This is > in order to avoid exposing the new device (which may contain GPG keys > and other secret stuff) to the world. > > I'm not opposed to the idea of an umask option. However, something has > to supply the new option; normally the device policy is read out from > hal (by pmount-hal) and passed to pmount. > > So where and how do you think this policy should be configured? > > Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
