From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] What do I need for a small 9P2000 server @ Linux ?
Date: Fri, 29 Jun 2007 07:37:35 +0200 [thread overview]
Message-ID: <5d375e920706282237v710fa5d5kdccb41ed111e6fcb@mail.gmail.com> (raw)
In-Reply-To: <1183079101.19286.6.camel@linux.site>
On 6/29/07, Roman Shaposhnik <rvs@sun.com> wrote:
> On Thu, 2007-06-28 at 13:49 -0400, Kris Maglione wrote:
> > On Thu, Jun 28, 2007 at 07:36:29PM +0200, Enrico Weigelt wrote:
> > >Okay folks, grabbed npfs and spfs from CVS.
> >
> > Might I suggest you try libixp instead of npfs? Aside from .u
> > and auth, it does nearly everything that spfs does, only in
> > about 1/10th the size, and with much clearer code, in my
> > opinion. The API is based largely on lib9p. If you need
> > something that it doesn't have (threading support?), it should
> > be easy to add (I'd even be willing to add threading support, if
> > you tell me the threading API to use).
> >
> > http://www.suckless.org/wiki/libs/libixp
>
> Now I'm *completely* confused. ;-) So it seems that we have 4
> choices: lib9client (part of Plan9 from userspace), npfs, spfs
> and now libixp. Are they completely different? Under which
> circumstances does each make the most sense?
There are many more choices, see http://9p.cat-v.org/implementations
uriel
next prev parent reply other threads:[~2007-06-29 5:37 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
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 [this message]
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=5d375e920706282237v710fa5d5kdccb41ed111e6fcb@mail.gmail.com \
--to=uriel99@gmail.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).