From: Georg Lehner <jorge-plan9@magma.com.ni>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] walk and find again
Date: Tue, 9 Feb 2010 22:27:54 +0100 [thread overview]
Message-ID: <4B71D35A.5070304@magma.com.ni> (raw)
In-Reply-To: <8909eef9c8d57660ccd6e1cfa4aa2091@ladd.quanstro.net>
erik quanstrom wrote:
>> One usage scenario of walkfs is to implement find, du, walk, rdup and
>> the like. Another usage [scenario] of walkfs, with the -s option, is to add file
>> indexing to a
>> fileserver.
>>
>
> this seems more complicated than a straightforward
> non-fileserver based implementation. why do you
> need a fileserver for this?
>
> - erik
>
>
- Every three months there need to be a discussion about 'find', right ;)
- walkfs can cache/reuse results from previous runs
- arbitrary filesystem indexing and lookup schemes can be implemented
without changing the frontend-interface. Consider mime-type or
keyword lookup
- no more hassle with space or other special characters in filenames
- inaccessible parts of the filesystem are just masked out, instead of
returning
errors.
- ...
frontend tools are simple straightforward rc-scripts, consider:
find:
get a new walker thread
write filter to ctl file
write path to root file
while !eof {
path = read data
do with path whatever has been specified
}
du -s:
get a new walker thread
write path to root file
write "mode=stat" to the ctl file
read data (and block until walk is done)
print count and size
Best Regards,
Jorge-Le�n
next prev parent reply other threads:[~2010-02-09 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 6:32 Georg Lehner
2010-02-09 15:06 ` erik quanstrom
2010-02-09 21:27 ` Georg Lehner [this message]
2010-02-09 21:33 ` erik quanstrom
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=4B71D35A.5070304@magma.com.ni \
--to=jorge-plan9@magma.com.ni \
--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).