Re: [9fans] ndb question

[Charles Forsyth <forsyth@terzarima.net>]

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

try setting  cpu='$cpu' in termrc, with the cpu=... entry in ndb.

the auth=, cpu= ... names in ndb are typically used when cs (via dial) is asked to
look for $X for some X as part of a dial string (eg, net!$auth!fsauth).
since the cpu command puts the value of the environment variable cpu
in a dial string, setting it to the literal '$cpu' puts that in the dial string,
where cs will translate it by looking in ndb.

see the description of metanames in ndb(6)

[-- Attachment #2: Type: message/rfc822, Size: 2934 bytes --]

From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] ndb question
Date: Sat, 31 Jul 2004 16:59:30 -1000 (HST)
Message-ID: <Pine.BSI.4.58.0407311653340.9843@malasada.lava.net>

This doesnt look right.  I edit /rc/bin/termrc, I get rid of the
"cpu=XXX" line.  I edit /lib/ndb/local and setup a default cpu setting
and verify with:

   ndb/ipquery ip <my ip> cpu     (result:  cpu=XXX)

but when I boot the system the cpu variable is unset.  How is the
cpu setting in ndb used, if at all?  I know I can set this in
termrc, but ndb seems more flexible.  I could always set it
from an ipquery, but this seems hacky.  I'm trying to set things
up "properly" here.

Tim N.