From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: References: <80c99e791001240502v3e7c955ek130ded319bb03ef5@mail.gmail.com> <80c99e791001240955m726daae0w16d5f1ab4454d7ee@mail.gmail.com> <3e1162e61001241209j1593ad03m3183aae443427c92@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <26DD1048-064D-43D3-8C62-60450FD411A8@fastmail.fm> Content-Transfer-Encoding: 7bit From: Ethan Grammatikidis Date: Wed, 27 Jan 2010 11:44:47 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] mount acme on plan9port Topicbox-Message-UUID: c81ffb7a-ead5-11e9-9d60-3106f5b1d025 On 24 Jan 2010, at 9:51 pm, Russ Cox wrote: > On Sun, Jan 24, 2010 at 12:09 PM, David Leimbach > wrote: >> How about on MacFUSE? I remember there being some issues there. >> In fact, >> I'm now using an SSHFS that is *not* a FUSE module, but a pretty >> nicely done >> independent implementation. > > The only MacFUSE issues have been using the correct path > since the installed binaries seemed to move around each time > a new version came out. That seems to have settled down. > > Russ > Commands may be renamed or missing too. 9pfuse(4) states "The fusermount binary must exist in the current search path," however the nearest thing I see to that with macfuse 2.0.2 is: $ locate -i mount | grep -i fuse /System/Library/Filesystems/fusefs.fs/Support/mount_fusefs Running it I get the nice little mesage: "This program is not meant to be called directly. The MacFUSE library calls it." Lovely. -- freedesktop.org, because unix doesn't make things harder enough. Ethan Grammatikidis eekee57@fastmail.fm