I reopen this bug with a one line fix (patch included).
Since 0.9.7-2 the infrastructure to have pmount-hal read the policy is
almost complete, but there remains a little bug: the first option never
matches.
Here is the patch:
--- pmount-0.9.9/src/pmount-hal.c.orig 2006-03-03 17:29:00.000000000
+0100
+++ pmount-0.9.9/src/pmount-hal.c 2006-03-13 15:05:58.000000000
+0100
@@ -303,7 +303,7 @@
debug( "options: %s\n", options );
const char* s;
- for( s = options; s; s = strchr( s, ',') ) {
+ for( s = (options-1); s; s = strchr( s, ',') ) {
++s; /* skip comma */
if( !strncmp( s, "exec", 4 ) )
exec = TRUE;
Here is a test case:
(put in /etc/hal/fdi/policy/preferences.fdi)
<device>
<match key="block.is_volume" bool="true">
<match key="@block.storage_device:storage.hotpluggable"
bool="true">
<merge key="volume.policy.mount_option.exec"
type="bool">true</merge>
</match>
</match>
</device>
Restart hal, try to pmount-hal any usb-key. Now, the key is mounted with
exec option. Before, it was not, since 'xec' did not match exec. This is
a stupid bug, but it is now a dead bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
