From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ip/ipconfig
Date: Thu, 26 Oct 2000 00:02:47 -0400 [thread overview]
Message-ID: <20001026040251.80783199D5@mail> (raw)
//This could avoid creating conflicts between the arguments
//give ipconfig and what is in the network database.
but if the arguements to ipconfig come from from cs (which,
in turn, gets them from the ndb files), where's the risk of
conflict? you pretty much need cs anyway, and in the scheme
proposed, ipconfig now has to know how to parse the ndb
files, complete with imposed ipnet heirarchy. i'm in favor
of limiting how many places that magic gets included in.
especially since the big win seems to be saving a few lines
in /rc/bin/[term,cpu]rc.
-α.
next reply other threads:[~2000-10-26 4:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 4:02 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-26 17:02 presotto
2000-10-25 7:34 anothy
2000-10-25 20:30 ` Mark C. Otto
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=20001026040251.80783199D5@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).