On Wednesday, April 3, 2013 1:51:25 PM UTC+3, Richard Miller wrote:
> Go ahead. It's called termrc.'local' because it's your own local
>
> configuration to play with as you like. There's no "standard". The
>
> one on sources is an empty template, and the one on the raspberry pi
>
> image is just an initial suggestion.
Oh, I see. I'm just used to trying to separate code from data so much I thought
a default that keeps the users from editing scripts is the norm and would get
"upstreamed". In practice my concern was that I'll replica\pull over it by
mistake... I suppose you can tell I'm a linux user :P
On Wednesday, April 3, 2013 1:54:45 PM UTC+3, Bence Fábián wrote:
> 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
>
Ops. Good call. It returned the ip as the sysname. :)
All better now. Here's some breadcrumbs for any brave adventurers lucky enough
to google this discussion:
term% cat /lib/ndb/local
#
# files comprising the database, use as many as you like, see ndb(6)
#
database=
file=/lib/ndb/local
file=/lib/ndb/common
auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
#
# because the public demands the name localsource
#
ip=127.0.0.1 sys=localhost dom=localhost
ipnet=HOME
ip=10.0.0.0
ipmask=255.255.255.0
ipsubmask=255.255.255.0
ipgw=10.0.0.138
auth=9pi
cpu=9pi
fs=9pi
dns=1.2.3.4
dns=8.8.8.8
dns=8.8.4.4
dns=10.0.0.138
dnsdomain=HOME
ip=10.0.0.13 sys=9pi dom=9pi.HOME proto=il
auth=10.0.0.13 authdom=9pi.HOME
term% ndb/query sys $sysname
ip=10.0.0.13 sys=9pi dom=9pi.HOME proto=il
Thanks !
