From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <26DD1048-064D-43D3-8C62-60450FD411A8@fastmail.fm> References: <80c99e791001240502v3e7c955ek130ded319bb03ef5@mail.gmail.com> <80c99e791001240955m726daae0w16d5f1ab4454d7ee@mail.gmail.com> <3e1162e61001241209j1593ad03m3183aae443427c92@mail.gmail.com> <26DD1048-064D-43D3-8C62-60450FD411A8@fastmail.fm> Date: Wed, 27 Jan 2010 13:23:42 +0000 Message-ID: <80c99e791001270523i4b63f1easffb015894ec38cd4@mail.gmail.com> From: Lorenzo Bolla To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd1eb0aaef840047e254f1d Subject: Re: [9fans] mount acme on plan9port Topicbox-Message-UUID: c855a7d4-ead5-11e9-9d60-3106f5b1d025 --000e0cd1eb0aaef840047e254f1d Content-Type: text/plain; charset=ISO-8859-1 Anyway, Russ' suggestion worked. The only weird behaviour is that listing /mnt/acme opens a new empty window in acme... On Wed, Jan 27, 2010 at 11:44 AM, Ethan Grammatikidis wrote: > > 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 > > > > > --000e0cd1eb0aaef840047e254f1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anyway, Russ' suggestion worked.
The only weird behaviour is that l= isting /mnt/acme opens a new empty window in acme...

On Wed, Jan 27, 2010 at 11:44 AM, Ethan Grammat= ikidis <eekee57= @fastmail.fm> wrote:

On 24 Jan 2010, at 9:51 pm, Russ Cox wrote:

On Sun, Jan 24, 2010 at 12:09 PM, David Leimbach <leimy2k@gmail.com> wrote:
How about on MacFUSE? =A0I remember there being some issues there. =A0In fa= ct,
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. =A0That seems to have settled down.

Russ


Commands may be renamed or missing too. 9pfuse(4) states "The fusermou= nt binary must exist in the current search path," however the nearest = thing I see to that with macfuse 2.0.2 is:

=A0$ 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, b= ecause unix doesn't make things harder enough.


Ethan Grammatikidis
eekee57@fastmail.f= m





--000e0cd1eb0aaef840047e254f1d--