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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

With 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
(application/octet-stream)    local.fdi (0.5 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 22 November 2004, 21:16 GMT
Reason for closing:  Fixed
Comment by Tor Krill (tor) - Monday, 08 November 2004, 07:22 GMT
I have added the local.fdi file, from /usr/share/hal/fdi/95userpolicy, that i use to get more decent fstab entries.

Seems to work fine with all usb-storage devices i have tried.
Comment by Tor Krill (tor) - Monday, 08 November 2004, 07:23 GMT
The forum discussion about this:

http://bbs.archlinux.org/viewtopic.php?t=7900
Comment by arjan timmerman (blaasvis) - Monday, 22 November 2004, 19:12 GMT
Jan, could you please look into it ?

Loading...