9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gorka Guardiola <paurea@gmail.com>
To: "fernanbolando@mailc.net" <fernanbolando@mailc.net>,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] clarification on man 9p
Date: Sat,  3 Oct 2009 13:34:10 +0200	[thread overview]
Message-ID: <497675D4-2435-4B80-93F5-49AAAA119C14@gmail.com> (raw)
In-Reply-To: <1d5d51400910030226j4dc8d8b5x1cfaee68a45fc1e2@mail.gmail.com>

There is a version that is. Its source is with the library.

-
Curiosity sKilled the cat

G.

On Oct 3, 2009, at 11:26 AM, Fernan Bolando <fernanbolando@mailc.net>
wrote:

> On Sat, Oct 3, 2009 at 8:29 AM, Russ Cox <rsc@swtch.com> wrote:
>>> "In general, the File interface is appropriate for maintaining
>>> arbitrary file trees (as in ramfs). The File interface is best
>>> avoided
>>> when the tree structure is easily generated as necessary; this is
>>> true
>>> when the tree is highly structured (as in cdfs and nntpfs) or is
>>> maintained elsewhere."
>>>
>>> Is this referring to avoiding the usage of createfile and friends in
>>> 9pfile.h for highly structured trees?
>>
>> Yes.  You can look at the named examples to see
>> the alternative.  My experience has been, well, what
>> it says in the man page: the File interface was an
>> interesting idea but is rarely useful.
>>
>
> I understand, what confused me was that ramfs is not using File/
> createfile.
> So even though ramfs could have taken advantage of the createfile
> tools it didn't. why?
>
> The only fileserver that I found that was actually using createfile
> is rdbfs.
>
> regards
> fernan
>
>
> --
> http://www.fernski.com
>



      reply	other threads:[~2009-10-03 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 20:29 Fernan Bolando
2009-10-03  0:29 ` Russ Cox
2009-10-03  9:26   ` Fernan Bolando
2009-10-03 11:34     ` Gorka Guardiola [this message]

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=497675D4-2435-4B80-93F5-49AAAA119C14@gmail.com \
    --to=paurea@gmail.com \
    --cc=9fans@9fans.net \
    --cc=fernanbolando@mailc.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).