9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9pfuse on mac os x
Date: Wed,  6 Aug 2008 08:09:20 -0500	[thread overview]
Message-ID: <31527CF0-1257-438A-B8D6-5C59C631BD15@corpus-callosum.com> (raw)
In-Reply-To: <84d462a30805161042gfe0dc88r67ce92390c479150@mail.gmail.com>


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 finally gotten
around to looking at this again now that there's a nice new utility
from Russ that uses 9pfuse.

9pfuse does mount (on Leopard at least) with the latest MacFUSE 1.7
from the goog, and you can watch all the debug details.  Unfortunately
9pfuse ends up having similar problems to sshfs, I/O failures when
traversing the mount point.  For sshfs it appears as if the latest
MacFUSE keeps everything mounted as root -- so even if you try to
force your uid it ignores it and you end up with a file hierarchy you
can't traverse.

I'll keep looking through to see if the API changed a bit more.  There
are MacFUSE filesystems that do work, http://www.friday.com/bbum/2008/01/10/silly-hack-of-the-day-mount-the-obj-c-runtime-as-a-filesystem/
.  That example goes through a different path to initialize the fuse
mount...

-jas




  parent reply	other threads:[~2008-08-06 13:09 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
2008-05-16 18:23       ` a
2008-08-06 13:09       ` Jeff Sickel [this message]
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=31527CF0-1257-438A-B8D6-5C59C631BD15@corpus-callosum.com \
    --to=jas@corpus-callosum.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).