On Tue 16 Jan 2001 at 00:42:36 +0100, Johnny Billquist wrote:
> Well, the boot roms don't know how to tftp either, so I wouldn't say mop
> is a replacement for tftp. If you use the tftp/bootparams stuff, the
> sequence is:
> 
> 1. Get bootloader via mop.
> 2. Get system parameters through bootparams
> 3. Get kernel via tftp.
> 4. Mount root through nfs.
> 
> The dhcp/bootp way is:
> 
> 1. Get bootloader via mop.
> 2. Get system parameters through dhcp/bootp
> 3. Get kernel via nfs.
> 4. Mount root through nfs.
> 
> On the server side in this case, item 3 and 4 can be handled as one, which
> is nice.

Well, I have a Sun that netboots and acts as an X server, and as far
as I can tell (and remember, for it is late) it does

. Get IP number via RARP
. Get bootloader via tftp.
. Get system parameters through bootparams (root, to get the kernel)
. Get kernel via nfs.
. Get system parameters through RARP and bootparams (again, this time for the
  kernel - the info is not passed from the boot loader)
. Mount root through nfs.

I boot my VAXen (when diskless) much the same way (with MOP instead of
the initial RARP bootparams) because that saves setting up an extra dhcp
server.

> 	Johnny
-Olaf.
-- 
___ Olaf 'Rhialto' Seibert - rhialto@polder --Soep van de dag, wat zal dat zijn
\X/ land.nl     --wat kan dat wezen, beter maar het ergste vrezen -Boy Bensdorp