Short message : I can't get gnome-volume-manager to mount the karma, does anyone know how it chooses which devices to mount ?
Long message : Details of my trials and few successes follow.
I've been trying to get the karma automounted. I'm trying to use what my
distrib (Ubuntu) uses for mounting usbkeys, digital cameras, iPods (I
think) : udev/hal/gnome-volume-manager.
I found out the way to choose the /dev/ file(s) using the line :
SYSFS{product}=="Rio Karma", SUBSYSTEM=="block", NAME="karma%n"
in /etc/dev/rules.d/10-local.rules (you can rename it to xx-karma.rules
if you want I think)
But I couldn't get gnome-volume-manager to mount it. According to
http://www.reactivated.net/writing_udev_rules.html, you could use a
RUN+="correct_mount_command" to it but it seems like an awful hack, so
instead I chose not to use the udev rule and go only with hal +
gnome-volume manager.
Following http://www.mythic-beasts.com/~mark/random/hal/ and
http://webcvs.freedesktop.org/hal/hal/doc/spec/hal-spec.html?view=co#device-properties
I created a /etc/hal/fdi/policy/karma.fdi file (attached) which should
tell hal to do_what_it_has_to_do_to mount the second partition of the
karma (id-ed by its info.udi) with omfs in /media/karma.
These properties are inherited by hal (I checked with
hal-device-manager) but gnome-volume-manager doesn't do anything with
it.
How does gnome-volume-manager use hal's informations to decide which
device to mount ?
Julien
karma.fdi
Description: application/xml
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ linux-karma-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
