Re: [9fans] [9pi] standardize \ normalize setting dns in

[c117152@rmqkr.net]

On Thursday, March 28, 2013 2:41:42 PM UTC+2, 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.