From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] APE and listen(2B)
Date: Thu, 4 Dec 2008 19:18:20 +0200 [thread overview]
Message-ID: <56e92ecf94c056a134c3abd9e034abdd@proxima.alt.za> (raw)
>> secondly, "reveal" is meant to drop into background, accepting
>> connections on TCP/4523 where it replies with the concatenation of the
>> originating IPv4 address and port number.
>
> is there a reason for not using listen(8)? all that is needed is a
> script in /bin/service/tcp4523 nearly identical /bin/service/tcp565
Yes, because I'm trying to tighten up on APE so that it makes sense
when in turn it is "ported" to GCC. Enough people think GCC is a
worthwhile investment, even though it seems like a lot of effort to
me, that it is worth getting APE and GNU to converge as much as
possible to avoid unnecessary repetition.
++L
next reply other threads:[~2008-12-04 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 17:18 lucio [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-27 4:35 lucio
2008-11-27 7:49 ` sqweek
2008-11-27 9:40 ` lucio
2008-11-27 14:54 ` erik quanstrom
2008-11-27 15:16 ` lucio
2008-11-28 17:24 ` 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=56e92ecf94c056a134c3abd9e034abdd@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).