From: "ron minnich" <rminnich@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: Thu, 28 Jun 2007 18:22:32 -0700 [thread overview]
Message-ID: <13426df10706281822w118cf2f2yc92cca4e7d6da5e9@mail.gmail.com> (raw)
In-Reply-To: <1183079101.19286.6.camel@linux.site>
On 6/28/07, Roman Shaposhnik <rvs@sun.com> wrote:
> 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?
if you are on unix and don't *ever* intend to go to plan 9, reduce to
npfs, spfs, ixp
if you don't need threads, reduce to spfs, ixp
libspfs lets you do stuff like this (from xbootfs)
static void
fsinit(void)
{
Spfile *file;
root = spfile_alloc(NULL, "", 0555 | Dmdir, Qroot, &root_ops, NULL);
root->parent = root;
spfile_incref(root);
root->atime = root->mtime = time(NULL);
root->uid = root->muid = user;
root->gid = user->dfltgroup;
create_file(root, "ctl", 0644, Qctl, &ctl_ops, NULL, NULL);
datafile = create_file(root, "data", 0444, Qdata, &data_ops,
NULL, NULL);
datafile->length = filelen;
create_file(root, "avail", 0666, Qavail, &avail_ops, NULL, NULL);
file = create_file(root, "redir", 0444, Qredir, &redir_ops, NULL, NULL);
/* make it too long, it matters not ... */
file->length = 32;
}
if you don't need stuff like that, use libixp
or, if you want to read a nice, tight implementation of 9p in c, just
get libixp anyway. It's neat.
ron
next prev parent reply other threads:[~2007-06-29 1:22 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 [this message]
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=13426df10706281822w118cf2f2yc92cca4e7d6da5e9@mail.gmail.com \
--to=rminnich@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).