Summary: | sys-apps/hal-0.5.9.1 does not mount my NTFS partition using ntfs-3g but ntfs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Dratva <raquacontact> |
Component: | [OLD] Core system | Assignee: | Project Gentopia <gentopia> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | dopey |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Dratva
2007-06-24 22:07:49 UTC
EDIT: I emerged back to version 0.5.9-r6 not the one stated above. the only versions of HAL in the tree are: 0.5.7.1-r3 0.5.7.1-r5 0.5.9 (masked) 0.5.9-r1 0.5.9.1 I don't know where you're getting -r6 from. Also, my NTFS partition mounts every single time I login to GNOME via ntfs-3g, are you sure you have it installed? marking this as works for me since no feedback was received and I use this feature on a daily basis. The only trick was making sure I emerged ntfs-3g and it just worked. Reading the HAL rules, it will attempt to use ntfs-3g and fall back to ntfs if it can't find ntfs-3g, which sounds like the user's issue and the previously suggested steps I told the user to take. *** Bug 187033 has been marked as a duplicate of this bug. *** Can you re-open this bug? I'm having the same problem. hal-0.9.5-r1 and ntfs3g-1.0. without ANY debug info or steps to reproduce, no I can't. what kind of steps do you want? emerge hal ntfs3g plug in usb external harddrive formated as NTFS check mount and /media/.hal-mtab and both use ntfs not ntfs-3g. check dmesg, kernel NTFS driver is used not ntfs-3g. sorry for the double comment. I don't know how to debug hal. If you have suggestions on the kind of debug info that would help, let me know. Otherwise, I grep'ed through all the directories that have hal installed files and the only reference to ntfs is in /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi. and it only references ntfs, not ntfs-3g. I'm not sure HAL would be capable of using ntfs-3g out of the box which I believe you are saying it does for you. The ntfs reference in /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi simply lists the allowable mount options for a filesystem of type ntfs. The same filesystem type exists whether using the ntfs3g or ntfs driver. HAL is simply calling the mount app to mount your device, the issue is one of configuration. In a simplified description what's happening, mount reads /proc/filesystems and will attempt each filesystem in order. On your machine, you have ntfs loaded before fuse. And so ntfs is attempted first and is successful. If you use GNOME, you can right click on the volume and give it a mount option of -t fuse, and it will use fuse by default. If you use KDE or some other way to mount (pmount), you will have to do a little bit of digging on your own to discover the magic. Thanks, I forgot KDE uses pmount still to handle this. I tested it out in Gnome and it did mount ntfs3g if the fuse module was loaded ahead of time. I'll tinker with KDE to get it working. |