From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What do I need for a small 9P2000 server @ Linux ?
Date: Thu, 28 Jun 2007 15:15:47 -0400 [thread overview]
Message-ID: <20070628191547.GJ28917@kris.home> (raw)
In-Reply-To: <20070628190339.GD9717@nibiru.local>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On Thu, Jun 28, 2007 at 09:03:39PM +0200, Enrico Weigelt wrote:
>What does this exactly mean ?
See 9pfile(1). lib9p has a feature to do most of the work of
managing trees, especially walking and cloning. It's convenient
in many circumstances, and works very well for things like
ramfs, but is not very useful when you provide a synthetic
filesystem that represents program state, or the like. In that
case, you'd have to manage two instances of the date if you were
to use 9pfile.
I've been meaning to experiment with some methods of doing
similar on top of libixp, as well as providing some more
convenience functions for common, complex things, but haven't
gotten to it yet. (There are a few of them used in wmii already,
just not migrated to libixp).
--
Kris Maglione
A pat on the back is only a few inches from a kick
in the pants.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-06-28 19:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 13:31 Enrico Weigelt
2007-06-28 14:28 ` Eric Van Hensbergen
2007-06-28 15:20 ` ron minnich
2007-06-28 17:36 ` Enrico Weigelt
2007-06-28 17:40 ` erik quanstrom
2007-06-28 17:49 ` Kris Maglione
2007-06-28 18:45 ` Enrico Weigelt
2007-06-28 18:49 ` Kris Maglione
2007-06-28 19:01 ` Enrico Weigelt
2007-06-28 19:10 ` Kris Maglione
2007-06-28 19:37 ` Enrico Weigelt
2007-06-28 19:50 ` Kris Maglione
2007-06-28 20:12 ` Enrico Weigelt
2007-06-30 0:51 ` Enrico Weigelt
2007-06-30 0:55 ` Kris Maglione
2007-06-30 11:39 ` Enrico Weigelt
2007-06-30 16:16 ` Kris Maglione
2007-06-30 17:39 ` Enrico Weigelt
2007-06-30 17:45 ` Kris Maglione
2007-06-30 18:15 ` Latchesar Ionkov
2007-06-30 19:32 ` Kris Maglione
2007-06-30 20:34 ` geoff
2007-06-30 20:39 ` Kris Maglione
2007-06-30 21:18 ` geoff
2007-06-30 18:05 ` Latchesar Ionkov
2007-06-28 20:17 ` Kris Maglione
2007-06-28 18:52 ` ron minnich
2007-06-28 18:57 ` Kris Maglione
2007-06-28 19:03 ` Enrico Weigelt
2007-06-28 19:15 ` Kris Maglione [this message]
2007-06-29 1:05 ` Roman Shaposhnik
2007-06-29 1:22 ` ron minnich
2007-06-29 4:31 ` Kris Maglione
2007-06-29 5:37 ` Uriel
2007-06-29 11:56 ` Enrico Weigelt
2007-06-29 12:37 ` Eric Van Hensbergen
2007-06-29 14:12 ` Enrico Weigelt
2007-06-29 14:25 ` Charles Forsyth
[not found] ` <c0ae573a0daa29e787cf87aa9deaae79@terzarima.net>
2007-06-29 20:13 ` Enrico Weigelt
2007-06-29 20:30 ` Francisco J Ballesteros
2007-06-29 21:32 ` Enrico Weigelt
2007-06-29 21:40 ` ron minnich
2007-07-11 18:52 ` Jack Johnson
2007-06-29 21:53 ` Francisco J Ballesteros
2007-06-30 12:03 ` Enrico Weigelt
2007-06-28 16:51 ` Uriel
2007-07-11 18:16 ` Eric Van Hensbergen
2007-06-29 0:56 ` Roman Shaposhnik
2007-06-29 1:07 ` Kris Maglione
2007-06-29 1:10 ` ron minnich
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=20070628191547.GJ28917@kris.home \
--to=bsdaemon@comcast.net \
--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).