From: Russ Cox <rsc@swtch.com>
To: erik quanstrom <quanstro@speakeasy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ndb and FQDNs.
Date: Mon, 26 Dec 2005 23:07:44 -0500 [thread overview]
Message-ID: <ee9e417a0512262007j5f55b942uccc43a38ed8030c0@mail.gmail.com> (raw)
In-Reply-To: <20051227040249.314C11B1D63@dexter-peak.quanstro.net>
> well unless russ gets too mad at me, i intend to get the dns stuff going.
> unfortunately, the connection service stuff looks a little too far out
> there for unix.
i got dns running okay last night. converting it to
use libthread will take a little effort, but a single-threaded
one basically just works.
what amazes me about having dns running on unix is
that in plan9port rfork(RFMEM|RFPROC) returns -1,
and dns actually copes gracefully and still functions.
russ
next prev parent reply other threads:[~2005-12-27 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 17:32 erik, quanstrom <quanstro
2005-12-26 18:43 ` lucio
2005-12-26 19:31 ` erik quanstrom
2005-12-27 3:20 ` Russ Cox
2005-12-27 3:51 ` lucio
2005-12-27 4:02 ` erik quanstrom
2005-12-27 4:07 ` Russ Cox [this message]
2005-12-27 3:57 ` erik quanstrom
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=ee9e417a0512262007j5f55b942uccc43a38ed8030c0@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=quanstro@speakeasy.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).