From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] DHCP weirdness?
Date: Thu, 24 Apr 2003 12:59:49 -0400 [thread overview]
Message-ID: <d87ca46bcdc355cae8df65015f2b66bf@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0304241236160.25655-100000@athena>
You might check which ipconfig binary you have.
The correct one is
--rwxrwxr-x M 543586 glenda sys 102975 Apr 24 12:27 /n/sources/plan9/386/bin/ip/ipconfig
There was a bad one on sources for a little while,
and the current source code (if you were to compile it)
doesn't quite work for reasons I don't know.
next prev parent reply other threads:[~2003-04-24 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 16:09 Dan Cross
2003-04-24 16:24 ` David Presotto
2003-04-24 16:50 ` Sam
2003-04-24 16:53 ` David Presotto
2003-04-24 16:58 ` Charles Forsyth
2003-04-24 16:59 ` Russ Cox [this message]
2003-04-24 20:03 ` [9fans] ipconfig Sam
2003-04-24 20:56 ` David Presotto
2003-04-27 21:20 ` Russ Cox
2003-04-24 16:43 ` [9fans] DHCP weirdness? ron minnich
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=d87ca46bcdc355cae8df65015f2b66bf@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).