Here are my conclusions: 1. As per comment from ArchWiki:
https://wiki.archlinux.org/index.php/Udev#About_udev_rules [...] Warning: To mount removable drives, do not call mount from udev rules. In case of FUSE filesystems, you will get Transport endpoint not connected errors. Instead use udisks that handles automount correctly. [...] 2. Adding ntfs-3g to FILESYSTEMS *never* work because the `in_list` implementation does: $ cat /usr/share/usbmount/usbmount [...] in_list() { for v in $2; do [ "$1" != "$v" ] || return 0 done return 1 } [...] Which means that for `ntfs` in_list will always returns an error when matched against `ntfs-3g` driver. The documentation is clearly wrong. So user should always add `ntfs` in FILESYSTEMS (mount will then use ntfs-3g) 3. There is a typo in: $ zmore /usr/share/doc/usbmount/README.gz [...] * add "fuseblk" to /etc/usb/usbmount.conf's variable FILESYSTEMS (for unmounting purposes). [...] It should read `/etc/usbmount/usbmount.conf` instead. 4. The documentation states that one should use: [...] The latter can be accomplished by the use of the command udevadm trigger --action=add /dev/sdd2 [...] But `trigger` action does not take a `devpath` `5. It is not clear why usbmount rules are located in `/lib/udev/rules.d/usbmount.rules` while I assumed it should be in `/etc/udev/rules.d` Because of 1, I am tempted to mark this bug as grave, since it prevent user from mount fuse system. From jessie on, the default ntfs backend is now always ntfs-3g (fuse) which means usbmount will not be able to mount any ntfs USB key in the future. Comments ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
