From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] ndb and FQDNs.
Date: Mon, 26 Dec 2005 21:57:40 -0600 [thread overview]
Message-ID: <20051227035740.ED8D41B1D6D@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0512261920q4bf9d2b6p664ac6c031892c07@mail.gmail.com>
Russ Cox <rsc@swtch.com> writes
|
| > on a unix machine:
| > ; host dexter-peak
| > ; host dexter-peak.quanstro.net
| >
| > both return a value.
|
| because both look up dexter-peak.quanstro.net,
| the first one only implicitly.
i've worked for more than one registrar and more
than one registry. please don't remind me how it works. ;-)
| dom is for dns names. sys is for local system names
| (yes there is life without dns).
thanks. i've got that straight, now.
|
| > also, how do i enter a multi-homed machine?
|
| put in a second ip= attribute.
didn't work for me. that's why i asked.
ndb/mkdb drops the entry on the floor. i must be doing something wrong.
here's what i had:
ip=192.168.0.4 ip=192.168.0.1 sys=dexter-peak dom=dexter-peak.quanstro.net
how should it be?
| why are you using ndb on unix?
besides plan9 envy, upas is pretty tight with ndb.
(as are many other plan9 applications.)
i thought that it'd be easier to port ndb than to
completely rearrange upas.
i was not planning on using ndb to store much data.
just enough to get by and then have a magic word
in the ndb database that does a call out to the host
system's dns (or yp or whatever).
- erik
prev parent reply other threads:[~2005-12-27 3:57 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
2005-12-27 3:57 ` erik quanstrom [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=20051227035740.ED8D41B1D6D@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).