Re: [9fans] ip/ipconfig

[presotto@plan9.bell-labs.com]

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

You must have a fairly different situation.  I always use ipconfig
to start ppp, like now from san diego:

	ip/ipconfig -b115200 ppp /dev/eia000

Part of that may be that every situation I live in uses dhcp to
get everything I need.  Ditto for ethernet ipconfig.  Clearly
I'm missing a lot of people's situations.  I can easily change
ipconfig to use lib/ndb/* or cs to get it's info and only use
dhcp if the former fails of if specificly asked to using a flag.

I can only defend putting dhcp into ipconfig because we don't run
systems standalone at all and that's all ipconfig every does to
get info at our lab.  However, I agree that separating the funcions
might be useful.  If I ever need dhcp for anything other than configuring
IP, I'll probably do it (or someone will probably beat me  to it).

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

From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ip/ipconfig
Date: Tue, 24 Oct 2000 22:52:25 -0400
Message-ID: <20001025025225.26800.qmail@g.bio.cse.psu.edu>

| pardon, but does anyone else think that ipconfig maybe should
| figure out the ip stuff all by itself?  these elaborate ipquery
| dances seem a bit tedious.

I agree.  ipconfig does significant magic, but stops short in an
unexpected way.

Also, when launching ppp I find that it's easier to not use ipconfig,
which makes me believe that it needs rethinking.