until recently I put ip=192.178.123.123 in plan9.ini and then wrote a
bit of script in termrc.local to check for its existence and use it
Did you figure out that you could just set the IP with bootargs
instead and skip the bit of script in termrc.local? Because that only
recently dawned on me, when I read a reply on this thread...
(I still recommended that the original poster call ipconfig in
cpurc.local or /cfg/*/cpurc, because he specifically wanted to get
his ip from his existing dhcp setup.)
There are loads of ways to actually get your IP address into the
system,
its like frigging Perl and tmtowtdi!
Somewhat true, though I'm not ready to say I've found anything in
plan 9 that's "like Perl" ;-)
Once you have auth and dhcp going, all the rest of the systems on the
network get configured by dhcp in boot (if diskless) or in
$service^rc (if diskful). And that leads me to the question that I
should have asked Erik a couple days ago:
for the standalone machines i have, i typically use the bootargs to
set up networking
before the root fs is mounted.this is the plan9.ini from the one
machine we have at
coraid that boots stand-alone, the auth server:
bootfile=sdD0!9fat!9myri
bootargs=il -d -g 205.185.197.254 ether /net/ether0 205.185.197.99
255.255.255.0
fs=205.185.197.100
auth=205.185.197.99
console=0
We've typically configured IP for our one standalone auth server
from /cfg/$sysname/cpurc; I want to know if I've understood why
you're doing it with plan9.ini bootargs instead: Is the advantage
that you get the variables set in /net/ndb (fs, auth, etc) that I
don't get when I call ip/ipconfig to set up a manual ip address from
an rc script later in the boot?
--
Josh
