Arch Linux

twilightning

Member

Registered: 2007-11-04

Posts: 49

NTFS automount with HAL using NTFS-3G

I have just managed to automount NTFS external usb hard drives.

I read this wiki page: http://wiki.archlinux.org/index.php/HAL but it didnt work for me.

Since hal-0.5.9.1 and later the above instructions dont seem to work but if you put the 10-ntfs-policy.fdi to /usr/share/hal/fdi/policy/10osvendor/ makes this work!

I have done research about this for two days but nothing worked.

Please someone edit the wiki

Last edited by twilightning (2007-11-04 18:33:24)

fwojciec

Member

Registered: 2007-05-20

Posts: 1,411

Re: NTFS automount with HAL using NTFS-3G

I have everything set up as per current wiki (10-ntfs-policy.fdi in /etc/hal/fdi/policy/) and my usb hard drive mounts correctly with the right privileges.  Hal package version is 0.5.10-1.  So maybe your solution shouldn't replace what's written in the wiki at the moment, but maybe you could add your solution as an alternative or something...

And by the way - anyone, including you, can edit the wiki.  Just sign up and make the edits you think are necessary.

twilightning

Member

Registered: 2007-11-04

Posts: 49

Re: NTFS automount with HAL using NTFS-3G

It works for you because probably the new package instructed the system to symlink to the old location, check it out (I think)

fwojciec

Member

Registered: 2007-05-20

Posts: 1,411

Re: NTFS automount with HAL using NTFS-3G

It works for you because probably the new package instructed the system to symlink to the old location, check it out (I think)

Well, there are no symlinks for the 10-ntfs-policy.fdi anywhere on my system, there is just this one instance in /etc/hal/fdi/policy/.  Something else must be at work here...

Edit: By the way - I use openbox with thunar-volman to do the mounting, in case that is relevant...

Last edited by fwojciec (2007-11-04 21:24:04)

twilightning

Member

Registered: 2007-11-04

Posts: 49

Re: NTFS automount with HAL using NTFS-3G

I use KDE (my favorite). Perhaps it is KDE centric issue.