2010/1/28 Russ Cox :
> if you ran ls -l /mnt/acme/* in plan 9 you'd get the
> same behavior. the difference is that 9p has
> optimized the star-free case in a way that unix
> cannot take advantage of.
ls -ld /mnt/acme/* would be a better illustration, i think.
> why is it walking there in the first place? i might
> be able to understand fuse reading the top level
> directory. but new isn't even at the top level.
yes it is. /mnt/acme is the root, hence /mnt/acme/new
is in the top level.
ls -l /mnt/acme
does a directory read to obtain just the names
>"Our scripts will read them and cause trouble" is the basic complaint.
unlike reading all those harmless files in /dev with no side-effects whatsoever
On Wed, Jan 27, 2010 at 1:35 PM, Eric Van Hensbergen wrote:
> reflection of Linux VFS operations into 9P is often a strange and
> interesting experience.
Wish I could find Lucho's email on this, but the Linux guys
particularly don't like things like clone files; "Our scripts will
read them and c
reflection of Linux VFS operations into 9P is often a strange and
interesting experience.
-eric
On Wed, Jan 27, 2010 at 3:20 PM, erik quanstrom wrote:
> On Wed Jan 27 09:37:02 EST 2010, rogpe...@gmail.com wrote:
>> fuse is probably just doing a stat of each file, as is
>> conventional and
On Wed Jan 27 09:37:02 EST 2010, rogpe...@gmail.com wrote:
> fuse is probably just doing a stat of each file, as is
> conventional and necessary in unix.
>
> the 9p fuse converter can't legitimately cache the
> qids from the directory read, so there's probably
> no other way.
why is it walking th
Thanks for generating the debug trace, that's a wacky place for a
problem, fidcreate should just be allocating resources. I'll try and
reproduce and add it to the bug list. There were some latent boofhead
bugs in the option parsing code -- its possible that there's one in
the trans_fd option pars
fuse is probably just doing a stat of each file, as is
conventional and necessary in unix.
the 9p fuse converter can't legitimately cache the
qids from the directory read, so there's probably
no other way.
2010/1/27 erik quanstrom :
> On Wed Jan 27 08:42:31 EST 2010, rogpe...@gmail.com wrote:
>>
On Wed Jan 27 08:42:31 EST 2010, rogpe...@gmail.com wrote:
> i guess that's because it's walking into mnt/acme/new,
> which creates a new window.
>
> i've thought in the past that perhaps the first write
> to a file in mnt/acme/new should create the window,
> rather than just walking to it.
>
> i
i guess that's because it's walking into mnt/acme/new,
which creates a new window.
i've thought in the past that perhaps the first write
to a file in mnt/acme/new should create the window,
rather than just walking to it.
it always seems odd to me that du -a /mnt has side effects.
2010/1/27 Lore
Anyway, Russ' suggestion worked.
The only weird behaviour is that listing /mnt/acme opens a new empty window
in acme...
On Wed, Jan 27, 2010 at 11:44 AM, Ethan Grammatikidis
wrote:
>
> On 24 Jan 2010, at 9:51 pm, Russ Cox wrote:
>
> On Sun, Jan 24, 2010 at 12:09 PM, David Leimbach
>> wrote:
>>
On 24 Jan 2010, at 9:51 pm, Russ Cox wrote:
On Sun, Jan 24, 2010 at 12:09 PM, David Leimbach
wrote:
How about on MacFUSE? I remember there being some issues there.
In fact,
I'm now using an SSHFS that is *not* a FUSE module, but a pretty
nicely done
independent implementation.
The on
On Sun, Jan 24, 2010 at 12:09 PM, David Leimbach wrote:
> How about on MacFUSE? I remember there being some issues there. In fact,
> I'm now using an SSHFS that is *not* a FUSE module, but a pretty nicely done
> independent implementation.
The only MacFUSE issues have been using the correct pat
How about on MacFUSE? I remember there being some issues there. In fact,
I'm now using an SSHFS that is *not* a FUSE module, but a pretty nicely done
independent implementation.
Dave
On Sun, Jan 24, 2010 at 11:27 AM, Russ Cox wrote:
> plan9port works well with FUSE.
> It works less well with
plan9port works well with FUSE.
It works less well with the 9p module.
Assuming you have write permission on /mnt/acme
and FUSE installed,
acme -m /mnt/acme
should work just fine.
Russ
On Sun, Jan 24, 2010 at 4:54 PM, Eric Van Hensbergen wrote:
> On Sun, Jan 24, 2010 at 7:02 AM, Lorenzo Bolla wrote:
> > I'm trying to use "9 mount" to mount acme's socket (in `namespace`/acme)
> to
> > some directory in /mnt (let's say /mnt/acme). I'm using ArchLInux:
> > $> uname -a
> > Linux ee
On Sun, Jan 24, 2010 at 7:02 AM, Lorenzo Bolla wrote:
> I'm trying to use "9 mount" to mount acme's socket (in `namespace`/acme) to
> some directory in /mnt (let's say /mnt/acme). I'm using ArchLInux:
> $> uname -a
> Linux eee 2.6.32-ARCH #1 SMP PREEMPT Sat Dec 26 08:26:17 UTC 2009 i686
> Intel(R)
17 matches
Mail list logo
