From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3EF4FD36.3060507@nospam.com>
From: bs <bs@nospam.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] BOOTP vs DHCP
References: <1d41fec1925f41c51a00fadfe678c1f3@plan9.bell-labs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Sat, 21 Jun 2003 20:49:58 -0400
Topicbox-Message-UUID: d5d93628-eacb-11e9-9e20-41e7f4b1d025

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?