9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.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 23:37:48 +0800	[thread overview]
Message-ID: <140e7ec30808060837k54754430p6a4b8cab06627799@mail.gmail.com> (raw)
In-Reply-To: <E5D2D73B-B09C-41A9-8BF9-FBF150321B2B@corpus-callosum.com>

On Wed, Aug 6, 2008 at 10:57 PM, Jeff Sickel <jas@corpus-callosum.com> 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_valid 1 ino 0x8000000000000000 size 0
> blocks 0 atime 1218033034 mtime 1218033034 ctime 1218033034 mode 040500
> nlink 1 uid 501 gid 501 rdev 0
> ls: .: Input/output error

 Is this a 32-bit machine? That's a big frigging inode. I don't have a
clue how mac works, but I recently hit a bug with v9fs where a certain
qid path got mapped to an inode of zero and subsequently disappeared
in the linux vfs layer. Though there was no i/o error there.
-sqweek



  reply	other threads:[~2008-08-06 15:37 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
2008-08-06 14:31         ` Skip Tavakkolian
2008-08-06 14:57           ` Jeff Sickel
2008-08-06 15:37             ` sqweek [this message]
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=140e7ec30808060837k54754430p6a4b8cab06627799@mail.gmail.com \
    --to=sqweek@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).