The culprit was simply the structure changes in MacFUSE version of
fuse_kernel.h, at least for the Leopard versions that are now
distributed.
I've got a patch that I'm forwarding to Russ and anyone else
interested in the changes. Not tested on Tiger as I'm no longer
running that version of the OS
On Wed, Aug 6, 2008 at 10:57 PM, Jeff Sickel <[EMAIL PROTECTED]> wrote:
>
> On Aug 6, 2008, at 9:31 AM, Skip Tavakkolian wrote:
>
> More depressing that sqweek's change works for OS X 10.4.x but not with the
> MacFUSE build for 10.5.x. All I get is:
>
> % ls
...
> FUSE <- unique 0x3 (Getattr) attr
On Aug 6, 2008, at 9:31 AM, Skip Tavakkolian wrote:
i was able to get Rangboom snsa -- which uses code from Russ' 9pfuse
-- to work with macfuse 1.7 (on os x 10.4.x). the latest 9pfuse has
the patch sqweek sent for xattr; i wonder if that's the problem?
it's depressing to see that Finder acts
i was able to get Rangboom snsa -- which uses code from Russ' 9pfuse
-- to work with macfuse 1.7 (on os x 10.4.x). the latest 9pfuse has
the patch sqweek sent for xattr; i wonder if that's the problem?
it's depressing to see that Finder acts as demented as Explorer with
incessant directory traver
On May 16, 2008, at 12:42 PM, Skip Tavakkolian wrote:
it's a little deeper; i'm wading in the mire that is libfuse to see if
i can spot the difference from what 9pfuse has. i'm hoping some
combination of '-o's to mount_fusefs will fix it.
Sadly it's not the mount_fusefs that's failing. I've
// i didn't see any references to fuse.version
// in p9p source. what file?
$PLAN9/bin/mount does a 'sysctl fuse.version' to see if it's
already loaded, and looks for the kext explicitly (and as of
v1.3, in the wrong place).
not part of 9pfuse, but support staff.
a
it's a little deeper; i'm wading in the mire that is libfuse to see if
i can spot the difference from what 9pfuse has. i'm hoping some
combination of '-o's to mount_fusefs will fix it.
about path changes, 9pfuse cleverly checks and remembers the right one
when access() succeeds. 9pfuse exec's moun
// I sure hope the macfuse team didn't move things around yet again.
Oh, you'd like that, wouldn't you? If things just stayed where they were
so you could find them when you wanted them? Sheesh. We listen to
guys like you and we'll end up with all the fun taken out of computing.
: vav; ls -ld /Sy
Also, faster interaction may be achieved by running o/dav to export
a namespace imported using Op via o/ofs. This saves many rpcs.
> From: [EMAIL PROTECTED]
> To: 9fans@9fans.net
> Reply-To: 9fans@9fans.net
> Date: Fri May 16 10:36:54 CET 2008
> Subject: Re: [9fans] 9pfuse on ma
On May 14, 6:26 pm, [EMAIL PROTECTED] (Skip Tavakkolian) wrote:
> is anyone able to use 9pfuse on mac os x 10.4 (macfuse 1.5.0)?
Earlier builds did work on OS X 10.4, I sure hope the macfuse team
didn't move things around yet again... Though to be honest, the
choice used for default locations on
is anyone able to use 9pfuse on mac os x 10.4 (macfuse 1.5.0)?
in my case, after dial succeeds and mount_fusefs is done,
9pfuse gets stuck waiting to read from fuse device. i've verified
that macfuse is working with sshfs. maybe the handshake has changed?
11 matches
Mail list logo
