Currently, hald mounts NTFS file systems readonly using the in-kernel ntfs module. When installing ntfs3g, the IMHO expected behaviour is to mount them writable instead. The attached ebuild and fdi do this when hal is in USE. Reproducible: Always Steps to Reproduce: 1. emerge ntfs3g 2. mount an NTFS volume via hald, e.g. with konqueror 3. Actual Results: Volume is mounted readonly using the kernel's NTFS support Expected Results: Volume should be mounted R/W using ntfs3g
Created attachment 160013 [details] Ebuild to include the fdi policy file with hal USE flag
Created attachment 160015 [details] The fdi policy file
Created attachment 160018 [details] Same, but DEPEND on sys-apps/hal accordingly Oops, forgot the dependency
Sorry about those dependency emails. New version sys-fs/ntfs3g-2531-r1 commited to CVS with HAL use flag that installs the FDI file.