{"action":"opened","issue":{"url":"https://api.github.com/repos/libfuse/libfuse/issues/19","repository_url":"https://api.github.com/repos/libfuse/libfuse","labels_url":"https://api.github.com/repos/libfuse/libfuse/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/libfuse/libfuse/issues/19/comments","events_url":"https://api.github.com/repos/libfuse/libfuse/issues/19/events","html_url":"https://github.com/libfuse/libfuse/issues/19","id":134249963,"number":19,"title":"Error specifying subtype: \"/bin/sh: <subtype>: command not found\"","user":{"login":"Balletie","id":3884925,"avatar_url":"https://avatars.githubusercontent.com/u/3884925?v=3","gravatar_id":"","url":"https://api.github.com/users/Balletie","html_url":"https://github.com/Balletie","followers_url":"https://api.github.com/users/Balletie/followers","following_url":"https://api.github.com/users/Balletie/following{/other_user}","gists_url":"https://api.github.com/users/Balletie/gists{/gist_id}","starred_url":"https://api.github.com/users/Balletie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Balletie/subscriptions","organizations_url":"https://api.github.com/users/Balletie/orgs","repos_url":"https://api.github.com/users/Balletie/repos","events_url":"https://api.github.com/users/Balletie/events{/privacy}","received_events_url":"https://api.github.com/users/Balletie/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-17T11:01:34Z","updated_at":"2016-02-17T11:01:34Z","closed_at":null,"body":"When specifying the subtype to the mount command with e.g. `mount -t fuse.bindfs`, I get the following error:\r\n\r\n```\r\n/bin/sh: bindfs: command not found\r\n```\r\n\r\nIt occurs on this line in `mount.fuse`: https://github.com/libfuse/libfuse/blob/e6e7a249c5c70187144dd9cd3767801ed05a1763/util/mount.fuse.c#L228\r\n\r\nIf I turn the subtype to a full path of an executable, it works, e.g. `mount -t fuse./path/to/bindfs`.  But obviously only if the path itself does not contain any dots.\r\n\r\nI have twp questions:\r\n\r\n1. Why is it running `/bin/sh/` instead of running the executable directly?\r\n2. Why not use `execvp`, which searches in the PATH variable for the executable. This way it would find `bindfs` in my case.\r\n\r\n__Disclaimer__: I am using NixOS, which does weird things with executable paths. This is probably why the bug has not occurred in other operating systems"}}