From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mount acme on plan9port
Date: Wed, 27 Jan 2010 14:35:23 +0000 [thread overview]
Message-ID: <df49a7371001270635i3f5b6efbs30172308dcfbca1b@mail.gmail.com> (raw)
In-Reply-To: <967f8c7c0977f7a2ef9611430135b9b3@brasstown.quanstro.net>
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 <quanstro@quanstro.net>:
> On Wed Jan 27 08:42:31 EST 2010, rogpeppe@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.
>>
>> it always seems odd to me that du -a /mnt has side effects.
>
> seems even more antisocial that fuse is walking
> around for no reason. there's a fine line between
> programs doing things for you and to you.
>
> - erik
>
>
next prev parent reply other threads:[~2010-01-27 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 13:02 Lorenzo Bolla
2010-01-24 16:54 ` Eric Van Hensbergen
2010-01-24 17:55 ` Lorenzo Bolla
2010-01-24 19:27 ` Russ Cox
2010-01-24 20:09 ` David Leimbach
2010-01-24 21:51 ` Russ Cox
2010-01-27 11:44 ` Ethan Grammatikidis
2010-01-27 13:23 ` Lorenzo Bolla
2010-01-27 13:40 ` roger peppe
2010-01-27 14:12 ` erik quanstrom
2010-01-27 14:35 ` roger peppe [this message]
2010-01-27 21:20 ` erik quanstrom
2010-01-27 21:35 ` Eric Van Hensbergen
2010-01-27 21:49 ` ron minnich
2010-01-27 22:47 ` Charles Forsyth
2010-01-28 6:24 ` Russ Cox
2010-01-28 10:43 ` roger peppe
2010-01-27 17:27 ` Eric Van Hensbergen
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=df49a7371001270635i3f5b6efbs30172308dcfbca1b@mail.gmail.com \
--to=rogpeppe@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).