From: Fernan Bolando <fernanbolando@mailc.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] ape sockets and plan9
Date: Sat, 25 Dec 2010 13:06:19 +0800 [thread overview]
Message-ID: <AANLkTinBPoFpHN1ykc_Ag0sDbwKBVrLTgcpCJmzQYOXM@mail.gmail.com> (raw)
Hi all
what is involved in using APE sockets. Anybody can point me to a
documentation or sample code?
running the sample code in http://www.linuxhowtos.org/data/6/server.c
gives me the following error.
term% ./serv
ERROR, no port provided
term% ./serv 4000
ERROR on accept: Invalid argument
I am not sure where to look for documentation. the ape paper doesnt
seem have much detail.
thanks
fernan
next reply other threads:[~2010-12-25 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 5:06 Fernan Bolando [this message]
2010-12-25 17:04 ` Steve Simon
2010-12-25 19:41 ` Bakul Shah
2010-12-28 13:23 ` Fernan Bolando
2010-12-28 16:34 ` erik quanstrom
2010-12-28 17:41 ` Devon H. O'Dell
2010-12-28 18:39 ` Bakul Shah
2010-12-28 18:50 ` erik quanstrom
2010-12-28 19:45 ` Bakul Shah
2010-12-29 4:02 ` ron minnich
2011-01-01 1:36 ` Fernan Bolando
2011-01-01 14:59 ` erik quanstrom
2011-01-01 15:28 ` 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=AANLkTinBPoFpHN1ykc_Ag0sDbwKBVrLTgcpCJmzQYOXM@mail.gmail.com \
--to=fernanbolando@mailc.net \
--cc=9fans@9fans.net \
/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).