From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipconfig
Date: Sun, 27 Apr 2003 17:20:19 -0400 [thread overview]
Message-ID: <51aa11ff10795cb516d214a870b017be@plan9.bell-labs.com> (raw)
In-Reply-To: <acf9f1b8a58e15844c337ac6d31680df@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
if booting with root from the network the kernel
will run it using /ipconfig in order to dial the file
server. it doesn't need to be in termrc. if you
want a termrc that works in both places you can
do
if(! test -e /net/ipifc/0/ctl) ip/ipconfig
[-- Attachment #2: Type: message/rfc822, Size: 3453 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 163 bytes --]
9load doesn't currently pass the IP address it got to the kernel
Therefore, the booted kernel runs dhcp when it comes up (and can
get more info than bootp does).
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1693 bytes --]
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] ipconfig
Date: Thu, 24 Apr 2003 16:03:06 -0400 (EDT)
Message-ID: <Pine.LNX.4.30.0304241556210.26650-100000@athena>
Just to clarify this for me, is there any reason
ipconfig needs to be in termrc for bootp'd terminals?
I think our termrc has been around since 3rd ed
which had ipconfig by default (iirc). If it's
redundant I'd like to pull it.
Sam
next prev parent reply other threads:[~2003-04-27 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 16:09 [9fans] DHCP weirdness? 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
2003-04-24 20:03 ` [9fans] ipconfig Sam
2003-04-24 20:56 ` David Presotto
2003-04-27 21:20 ` Russ Cox [this message]
2003-04-24 16:43 ` [9fans] DHCP weirdness? ron minnich
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 12:53 [9fans] ipconfig presotto
2001-07-13 9:31 Grunditz Mikael - migu
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=51aa11ff10795cb516d214a870b017be@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).