From: "Skip Tavakkolian" <skip.tavakkolian@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] 9pfuse on mac os x
Date: Fri, 16 May 2008 10:42:24 -0700 [thread overview]
Message-ID: <84d462a30805161042gfe0dc88r67ce92390c479150@mail.gmail.com> (raw)
In-Reply-To: <55015545760152d4cf771739dccf44d6@9srv.net>
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 mount_fusefs, which then forks,
but waiting on something. i didn't see any references to fuse.version
in p9p source. what file?
On Fri, May 16, 2008 at 6:21 AM, <a@9srv.net> wrote:
> : vav; ls -ld /System/Library/Extensions/fusefs.kext
> ls: /System/Library/Extensions/fusefs.kext: No such file or directory
> : vav; ls -ld /Library/Filesystems/fusefs.fs/Support/fusefs.kext
> drwxr-xr-x 3 root wheel 102 Mar 31 15:44 /Library/Filesystems/fusefs.fs/Support/fusefs.kext
>
> Also, the sysctl bit in /9/bin/mount no longer turns up anything useful;
> it needs to look for macfuse.version rather than fuse.version.
>
next prev parent reply other threads:[~2008-05-16 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:24 Skip Tavakkolian
2008-05-16 8:28 ` jas
2008-05-16 9:27 ` Fco. J. Ballesteros
2008-05-16 13:21 ` a
2008-05-16 17:42 ` Skip Tavakkolian [this message]
2008-05-16 18:23 ` a
2008-08-06 13:09 ` Jeff Sickel
2008-08-06 14:31 ` Skip Tavakkolian
2008-08-06 14:57 ` Jeff Sickel
2008-08-06 15:37 ` sqweek
2008-08-19 14:56 ` jas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84d462a30805161042gfe0dc88r67ce92390c479150@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).