From: Alex Brainman <alex.brainman@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: new termrc
Date: Mon, 30 Apr 2007 08:29:01 +0000 [thread overview]
Message-ID: <1177892013.171851.236980@u30g2000hsc.googlegroups.com> (raw)
In-Reply-To: <3989f6b97fb407ccb8a844a5897a4dcd@plan9.bell-labs.com>
On Apr 27, 9:16 am, g...@plan9.bell-labs.com wrote:
> I've just pushed out a new (and I hope stable) /rc/bin/termrc
> and /cfg/example/termrc. Machine-specific configuration should
> go into /cfg/$sysname/termrc. If you don't use DHCP (i.e., you
> statically configure terminal IP addresses), this affects you.
> You'll probably want to look at the diffs in any case.
I need an advice. I have a standalone plan9 computer, and if I use
the /rc/bin/termrc, then my $sysname is blank. It's, obviously,
because I use DHCP to set my ip address and other parameters, and I
use those settings as part of my network database. But at the time
when /rc/bin/termrc sets $sysname, network is not started yet and all
those parameters aren't available yet.
My /lib/ndb/local includes line:
file=/lib/ndb/common
and I use DHCP to get my address and /lib/ndb/common contains:
ip=192.168.21.14 ipmask=255.255.255.128 ipgw=192.168.21.1
sys=plan9term
dom=plan9term.linux.sge.local sge.local
dns=192.168.21.1
If I move
sysname=`{cat /dev/sysname}
line down after section where network is set, $sysname gets correct
value all right.
What am I doing wrong? Or is my setup "non-standard" enough and
I'can't use this general /rc/bin/termrc?
Thank you.
Alex
next prev parent reply other threads:[~2007-04-30 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 23:15 [9fans] " geoff
2007-04-30 8:29 ` Alex Brainman [this message]
2007-04-30 15:09 ` [9fans] " Russ Cox
2007-04-30 15:23 ` Lucio De Re
2007-04-30 15:32 ` erik quanstrom
2007-04-30 15:41 ` Lucio De Re
2007-04-30 15:42 ` Russ Cox
2007-04-30 19:49 ` Steve Simon
2007-04-30 20:00 ` Devon H. O'Dell
2007-05-01 9:39 ` matt
2007-05-02 8:36 ` Alex Brainman
2007-05-02 8:36 ` Alex Brainman
2007-05-02 8:36 ` Alex Brainman
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=1177892013.171851.236980@u30g2000hsc.googlegroups.com \
--to=alex.brainman@gmail.com \
--cc=9fans@cse.psu.edu \
/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).