From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9ports lib9p question: serving to a plain 'ol tcp socket
Date: Tue, 24 May 2005 07:53:03 -0500 [thread overview]
Message-ID: <a4e6962a05052405537980653a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505232152020.7716@enigma.lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On 5/23/05, Ronald G. Minnich <rminnich@lanl.gov> wrote:
> I am starting to look at this but wonder if someone has beat me to it.
>
> I need to make a simple, single-threaded 9p server that will sit on a
> normal Unix TCP socket in an accept/serve loop . It seems like the bits
> are there to do this in lib9p, but I'm still untangling a few things; I
> don't need the /tmp/ns.whatever Unix domain socket stuff, for example, but
> all the other superstructure there is really nice. Anybody done this. I
> can't use newsham's python server as I am sitting on a nice, bare node and
> python is not really an option. I was simply hacking u9fs until a minute
> or two ago, and I feel like I'm re-inventing something I'm sure someone
> has already done -- must be somebody there who has beat me to this, I
> figure.
>
You should be able to use the plan9ports infrastructure just fine,
even if its more than you need. I'm going to attach a really simple
devcons style driver I wrote using plan9ports as an example. Almost
all of the code can be thought of as a template. Search for Qtime and
Qcons to get the parts that really do anything.
One of these days I'll get around to writing a synthetic file systems
SDK to help make stuff like this more straightforward.
-eric
[-- Attachment #2: devcons.tar --]
[-- Type: application/x-tar, Size: 20480 bytes --]
next prev parent reply other threads:[~2005-05-24 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 3:56 Ronald G. Minnich
2005-05-24 12:53 ` Eric Van Hensbergen [this message]
2005-05-24 14:43 ` Russ Cox
2005-05-24 15:01 ` Ronald G. Minnich
2005-05-24 20:20 ` Ronald G. 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=a4e6962a05052405537980653a@mail.gmail.com \
--to=ericvh@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).