This was silently dropped the first time.
Assuming it was spam-filtered because gmail chose binary mime types
for the attached output.

Trying again with cat.txt and 9cat.txt, respectively (which is what I
should have done in the first place).

Colin

---------- Forwarded message ----------
From: Colin DeVilbiss <cdevilbiss@gmail.com>
Date: Mar 21, 2007 10:59 PM
Subject: 9pfuse-mounted files don't "work" (Mac OS X on Power)
To: 9fans@cse.psu.edu


I'm running on a Power-based Mac Mini with an up-to-date MacFUSE and
freshly cvs update -d'ed /usr/local/plan9.

In one terminal, I run "plumber" and "9pfuse -D `namespace`/plumb /mnt/plumb".

Snippet from the other terminal:

% 9p read plumb/rules | wc
     126     342    2962
% 9p ls plumb | wc
      11     110     554
% ls /mnt/plumb | wc
      11      11      81
% cat /mnt/plumb/rules | wc
       0       0       0
% 9 cat /mnt/plumb/rules | wc
       0       0       0

The "9pfuse -D" output corresponding to the two "cat" instances are
attached (as cat.out and 9cat.out, respectively, with newlines around
FUSE cmd/rsp pairs).

The same thing happens for acme files: "ls" works, "cat file" and
"echo foo > file" don't.

The MacFUSE demos from that website work also (sshfs, SpotlightFS), so
I don't expect that it's just a FUSE problem.

Has anybody else seen something like this?
Am I doing something obviously wrong?

Thanks in advance for any help.

Colin DeVilbiss