From: bs <bs@nospam.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] BOOTP vs DHCP
Date: Sat, 21 Jun 2003 20:49:58 -0400 [thread overview]
Message-ID: <3EF4FD36.3060507@nospam.com> (raw)
In-Reply-To: <1d41fec1925f41c51a00fadfe678c1f3@plan9.bell-labs.com>
David Presotto wrote:
> I'ld like to have 9load/9pxeload only support DHCP, i.e., assume
> its always there when booting over the ether. Is there anyone
> that only has BOOTP out there anymore?
DHCP is the way to go. Setup is pretty easy for booting and a DHCP
server can be found anywhere in an enterprise.
However, I am a little confused in what 9pxeload actually does, or why
it has 'pxe' in it's name.
Does it use the 'next-server & filename' option from DHCP? or does
it need a real pxeserver somewhere to hand out layers and bootagents?
next prev parent reply other threads:[~2003-06-22 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 0:14 David Presotto
2003-06-22 0:49 ` bs [this message]
2003-06-22 1:05 ` David Presotto
2003-06-22 1:32 ` bs
2003-06-22 2:27 ` David Presotto
2003-06-22 2:53 ` bs
2003-06-22 2:56 ` bs
2003-06-22 1:21 ` northern snowfall
2003-06-22 2:38 ` Dan Cross
2003-06-22 2:46 ` Christopher Nielsen
2003-06-22 4:14 ` northern snowfall
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=3EF4FD36.3060507@nospam.com \
--to=bs@nospam.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).