Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1758 - HAL produces invalid fstab entries
Attached to Project:
Arch Linux
Opened by Tor Krill (tor) - Monday, 08 November 2004, 07:18 GMT
Last edited by arjan timmerman (blaasvis) - Monday, 22 November 2004, 19:11 GMT
Opened by Tor Krill (tor) - Monday, 08 November 2004, 07:18 GMT
Last edited by arjan timmerman (blaasvis) - Monday, 22 November 2004, 19:11 GMT
|
DetailsWith the default settings in hal. fstab-sync produces entries in /etc/fstab that mount does not understand.
Example when adding a removable device the following option gets added: pamconsole,exec,noauto,managed The mount version shipped with arch does not recognize neither the pamconsole or the managed keyword. This is due to HALs default configuration in /usr/share/hal/fdi/90defaultpolicy/storage-policy.fdi |
This task depends upon
local.fdi
Seems to work fine with all usb-storage devices i have tried.
http://bbs.archlinux.org/viewtopic.php?t=7900