9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ip/ipconfig
Date: Wed, 25 Oct 2000 03:34:57 -0400	[thread overview]
Message-ID: <20001025073503.7878D199CF@mail> (raw)

i'm unconvinced. given the different ways a system can get its
ip address, i'm not so sure i want them all in ipconfig. i'm
not even entirely comfortable with having the dhcp client in
there. but i guess there's something to be said for having _a_
automatic configuration method in there. that being said...

you probably don't want to duplicate the functionality of
ndb/cs. and if you're not using DHCP, doing cs queries seems
like the right way to get the info (whether they're done in
ipconfig or [term,cpu]rc). loads of other apps are going to
expect ndb/cs as well, so it's got to be running at _some_
point. so the only real differences are 1) where ndb/cs gets
started and 2) what does the queries.

is it really worthwhile to increase the complexity of
ipconfig, when there's an existing, more modular way to get
the same results, and most setups won't need it anyway?

and what's the issue with using ipconfig for ppp? i find that
the easiest way to go about it. but again, that's additional
magic in one program. i'd sort of rather see a /net/ppp0 or
such, and treat it like /net/ether0.
-α.



             reply	other threads:[~2000-10-25  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-25  7:34 anothy [this message]
2000-10-25 20:30 ` Mark C. Otto
  -- strict thread matches above, loose matches on Subject: below --
2000-10-26 17:02 presotto
2000-10-26  4:02 anothy
2000-10-25  0:50 baldwin
2000-10-25  2:52 ` Scott Schwartz
2000-10-25  4:52   ` Boyd Roberts

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=20001025073503.7878D199CF@mail \
    --to=anothy@cosym.net \
    --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).