From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] accept in dial(2)
Date: Wed, 18 Aug 2004 21:18:37 +0200 [thread overview]
Message-ID: <016601c48558$2aebcfd0$73587d50@SOMA> (raw)
In-Reply-To: <03b03ce59989a2203272881dc2226cd9@vitanuova.com>
ahh, 8th Ed did this right.
these TCP/IP auto accept semantics are just stupid.
sure, i don't have much to go on (unlike datakit) but
it lets me raise the bar much earlier on if i so wish.
that BSD listen(2) fiasco is a joke.
this remings me of EGREG. it'd be nice to hack
ape so various stupid calls returned ESYSV or
EBSD regardless of the supplied arguments.
prev parent reply other threads:[~2004-08-18 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 3:30 geoff
2004-08-17 15:36 ` andrey mirtchovski
2004-08-17 16:03 ` rog
2004-08-17 17:51 ` rog
2004-08-17 21:12 ` Russ Cox
2004-08-18 17:33 ` rog
2004-08-18 19:18 ` boyd, rounin [this message]
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='016601c48558$2aebcfd0$73587d50@SOMA' \
--to=boyd@insultant.net \
--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).