9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [9pi] standardize \ normalize setting dns in
Date: Wed,  3 Apr 2013 12:54:45 +0200	[thread overview]
Message-ID: <CAOCRf5U3in-MPbBXSBPvcqKw3s2OUF9mXr=Vsmd1p45ftD+V0g@mail.gmail.com> (raw)
In-Reply-To: <7d57bd30-6e43-4d54-8670-ef6c71fefae1@i5g2000vbk.googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]

what does ndb/query sys $sysname say?

try to add ether and dom like this:

ip=10.0.0.13 sys=9pi ether=xxxxx... dom=9pi.Home



2013/4/3 <c117152@rmqkr.net>

> On Mar 28, 8:41 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > For a machine not receiving net configuration via DHCP, the normal
> > place to define dns= would be in /lib/ndb/local - 'man 6 ndb' for
> > information.
>
> Yes. I've already figured out that much:
>
> term% cat /lib/ndb/local
>
> database=
>         file=/lib/ndb/local
>         file=/lib/ndb/common
>
> auth=sources.cd.bell-labs.com authdom=outside.plan9.bell-labs.com
>
> ip=127.0.0.1 sys=localhost dom=localhost
>
> ipnet=Home ip=10.0.0.0 ipmask=255.255.255.0
>         ipgw=10.0.0.138
>         dns=1.2.3.4 # (my isp's dns)
>         dns=8.8.8.8 # (googleA)
>         dns=8.8.4.4 # (googleB)
>         dns=10.0.0.138 # (my router for when the net is down but I still
> want
> local quarries getting through and local dom - .Home - requests)
>         auth=9pi
>         cpu=9pi
>
> ip=10.0.0.13 sys=9pi
>
> The thing is, the way I understand and implement it, you have your
> basic networking split in at least two places: The /lib/ndb/local file
> and the ip/ipconfig command arguments (being called from
> termrc.local...). Now, if there's a DHCP then you can forgo /lib/ndb/
> local and just specify an empty "ipconfig=". However, on a static ip
> you're only allowed to do everything except feeding it a dns.
>
> My idea is to have a line or two added to termrc.local that will parse
> a single dns var from the cmdline.txt file. This way you can get the
> same convenience you'd get with DHCP in a static setup.
>
> I'm not sure it's a possible needless un +\-foreseen complication,
> lack of interest, an oversight, a security concern or whatever... But
> it seems to me that it could simplify things a little.
>
> Just a thought really.
>
> p.s. This is my third or fourth attempt at a reply. The first two were
> on the new groups interface. This attempt is on the old one. hopefully
> those aren't coming out somewhere as double\triple\quadruple posts...
>
>

[-- Attachment #2: Type: text/html, Size: 2977 bytes --]

      parent reply	other threads:[~2013-04-03 10:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 10:06 c117152
2013-03-28 12:02 ` Jacob Todd
2013-03-28 12:41 ` Richard Miller
2013-04-03 10:39   ` c117152
2013-04-03 10:39   ` c117152
2013-04-03 10:39   ` c117152
2013-04-03 10:51     ` Richard Miller
2013-04-04  8:49       ` c117152
2013-04-04  9:24         ` Bence Fábián
2013-04-04 12:40           ` erik quanstrom
2013-04-04 13:20             ` Bence Fábián
2013-04-04 14:23               ` erik quanstrom
2013-04-04 11:15         ` Richard Miller
2013-04-03 10:54     ` Bence Fábián [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='CAOCRf5U3in-MPbBXSBPvcqKw3s2OUF9mXr=Vsmd1p45ftD+V0g@mail.gmail.com' \
    --to=begnoc@gmail.com \
    --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).