From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <13426df10706281822w118cf2f2yc92cca4e7d6da5e9@mail.gmail.com> Date: Thu, 28 Jun 2007 18:22:32 -0700 From: "ron minnich" 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 ? In-Reply-To: <1183079101.19286.6.camel@linux.site> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070628133155.GB11624@nibiru.local> <13426df10706280820l13119c42r6b107e0eed489339@mail.gmail.com> <20070628173628.GA8212@nibiru.local> <20070628174934.GF28917@kris.home> <1183079101.19286.6.camel@linux.site> Topicbox-Message-UUID: 8b409e1a-ead2-11e9-9d60-3106f5b1d025 On 6/28/07, Roman Shaposhnik 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