From: "Russ Cox" <rsc@swtch.com>
To: lucio@proxima.alt.za, 9fans@cse.psu.edu
Subject: Re: [9fans] Re: new termrc
Date: Mon, 30 Apr 2007 11:42:39 -0400 [thread overview]
Message-ID: <20070430154237.67EC81E8C3A@holo.morphisms.net> (raw)
In-Reply-To: <c45453db16008564460612e815019fda@proxima.alt.za>
> But that is ugly, as you now need to track the ethernet address in
> /lib/ndb/local and possibly in the DHCP configuration, when all the
> pertinent details can be obtained from the DHCP server. Are there any
> philosophical reasons that the DHCP data, retrieved using ip/ipconfig,
> say, cannot at least supplement whatever may have been already set up
> by termrc (or cpurc)? If there isn't I'll gladly look into it, DHCP
> isn't entirely alien to me.
The pertinent details cannot be obtained
from a non-Plan 9 DHCP server.
If you are using a Plan 9 DHCP server
then you are correct -- all the details
do get used from DHCP and no extra work
is necessary. But it sounds like his DHCP
server is a random NAT box.
All you need to put in /lib/ndb/local in that
case is
sys=yourname ether=010203040506
and the DHCP info will be used (via /net/ndb,
which ipconfig fills in) for the rest.
Truth be told, when I set up a standalone
system I don't even bother doing this. I just do
sysname=foo
echo -n foo >/dev/sysname
in cpurc before starting cs. It doesn't really
matter one way or the other.
Russ
next prev parent reply other threads:[~2007-04-30 15:42 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 ` [9fans] " Alex Brainman
2007-04-30 15:09 ` 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 [this message]
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=20070430154237.67EC81E8C3A@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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).