From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p srv-ing on a port
Date: Fri, 16 Jan 2004 19:17:44 -0500 [thread overview]
Message-ID: <cd9922c13e490c570678ed5a1f0bdde4@plan9.bell-labs.com> (raw)
In-Reply-To: <a9700a6b8c0098292a15f4f84aee65fa@plan9.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 71 bytes --]
Of course, several do, for example 17007.
What is the real question?
[-- Attachment #2: Type: message/rfc822, Size: 1911 bytes --]
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: [9fans] 9p srv-ing on a port
Date: Fri, 16 Jan 2004 16:06:13 -0700
Message-ID: <a9700a6b8c0098292a15f4f84aee65fa@plan9.ucalgary.ca>
Is it possible (i.e. simple enough) to set up a 9p server that will
work on a port a-la fossil/kfs?
Instead of doing postmountsrv() is it possible to do listen() -
accept() - fork and srv(s) with the network fd? What should s->infd
and s->outfd be set to in this case?
next prev parent reply other threads:[~2004-01-17 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 23:06 mirtchov
2004-01-17 0:17 ` David Presotto [this message]
2004-01-17 0:40 ` mirtchov
2004-01-17 0:56 ` Skip Tavakkolian
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=cd9922c13e490c570678ed5a1f0bdde4@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).