From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <557505e462b705571e7e9d1ba4f9c0b8@terzarima.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] ndb question From: Charles Forsyth Date: Mon, 2 Aug 2004 09:53:20 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-zixjzxqagyqqzqocdbijfosdws" Topicbox-Message-UUID: d08e2b36-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-zixjzxqagyqqzqocdbijfosdws Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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) --upas-zixjzxqagyqqzqocdbijfosdws Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by lavoro; Sun Aug 1 04:01:10 BST 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id BC70D19E6E for ; Sat, 31 Jul 2004 22:59:54 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (neuromancer.cse.psu.edu [130.203.4.2]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1977219E3D for <9fans@cse.psu.edu>; Sat, 31 Jul 2004 22:59:35 -0400 (EDT) Received: from mail.cse.psu.edu ([130.203.4.6]) by localhost (neuromancer [130.203.4.2]) (amavisd-new, port 10024) with LMTP id 03255-02-40 for <9fans@cse.psu.edu>; Sat, 31 Jul 2004 22:59:31 -0400 (EDT) Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 586E019DE2 for <9fans@cse.psu.edu>; Sat, 31 Jul 2004 22:59:31 -0400 (EDT) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by gau.lava.net (Postfix) with ESMTP id C74A2171D1 for <9fans@cse.psu.edu>; Sat, 31 Jul 2004 16:59:30 -1000 (HST) Date: Sat, 31 Jul 2004 16:59:30 -1000 (HST) From: Tim Newsham To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at cse.psu.edu Subject: [9fans] ndb question X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu Errors-To: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu 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 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. --upas-zixjzxqagyqqzqocdbijfosdws--