Device Notifier use HAL, s that so?
By editing /etc/hal/fdi/policy/user-options.fdi i'm obtain what lshal contain for vfat device:

Code: Select all

volume.mount.valid_options = {'rw', 'quiet', 'flush', 'remount', 'iocharset=utf8', 'codepage=866', 'noexec', 'showexec', 'dirsync', 'noatime', 'nodiratime', 'gid=users', 'uid='} (string list)


but

Code: Select all

~> cat /media/.hal-mtab
/dev/sdc  1000    0  vfat  nosuid,nodev,uid=1000,flush     /media/disk


1. Why KDE not use hal parameters on mount?
2. How i can add extra parameters for all vfat removable devices?
3. Why by default guid=root and all files is executable? (Stupid defaults, not so?)

I have checked the code of KDE's HAL Solid backend, and it does not take any config file specified options into account.

The only options it sets are the "-L", "-C", "iocharset", "shortname", "flush" and "locale", and only if HAL specifies that they are supported. The remainder are HAL's own defaults.

The only way to add options would be to modify the code to retrieve the options from HAL if possible, and then add it to the options it sends.

bcooksley wrote:The only way to add options would be to modify the code to retrieve the options from HAL if possible, and then add it to the options it sends.

Why it's not realized? It's so hard or nobody wants this functional?

This feature was likely not seen as part of what was needed when KDE's HAL Solid backend, I would recommend making a feature request at bugs.kde.org, however given that HAL has been deprecated, it is probable that the feature would not be implemented.