9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lib9p help
Date: Fri, 17 Feb 2006 13:10:35 +0000	[thread overview]
Message-ID: <09789f2506fad45a5b6d4a3d96a1df6c@swtch.com> (raw)
In-Reply-To: <82c890d00602170415j54dec388vf4dc945de1548b4f@mail.gmail.com>

> i am using file/tree structures trying to do a read/write filesystem,
> but i cannot make it use my walk functions and cannot create
> directories or files with touch.

If you are using file/tree structures, 
then you don't get to provide the walk function.
(Why would you need to?  Lib9p should know
the entire file tree and be able to do it for you.)

Russ



  reply	other threads:[~2006-02-17 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 12:15 Gabriel Diaz
2006-02-17 13:10 ` Russ Cox [this message]
2006-02-17 21:23   ` Gabriel Diaz
2006-02-17 16:30     ` Russ Cox
2006-02-17 21:50       ` Gabriel Diaz
2006-02-17 17:14         ` Russ Cox
2006-02-17 22:22           ` Gabriel Diaz

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=09789f2506fad45a5b6d4a3d96a1df6c@swtch.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).