On Nov 11, 2004, at 12:04 AM, Urban Boquist wrote:

>  Ummmm.  Not to be dense, but where's the network bootloader?
>
> It is in /usr/mdec, as usual... ;-)

The only things in there from the snapshot are:
-r--r--r--  1 root  wheel  54337 Nov  8 04:18 boot
-r-xr-xr-x  1 root  wheel  13313 Nov  8 04:18 mkboot*
-r--r--r--  2 root  wheel   8192 Nov  8 04:18 sdboot
-r--r--r--  2 root  wheel   8192 Nov  8 04:18 xxboot

/export/hardball/root/usr/mdec/boot:   ELF 32-bit MSB executable, 
PA-RISC (LP64) version 1 (HP-UX), statically linked, not stripped
/export/hardball/root/usr/mdec/mkboot: ELF 32-bit MSB executable, 
PA-RISC (LP64) version 1 (NetBSD), for NetBSD 2.99.10, dynamically 
linked (uses shared libs), not stripped
/export/hardball/root/usr/mdec/sdboot: lif file
/export/hardball/root/usr/mdec/xxboot: lif file

None of them are network boot loaders that could be used to bootstrap a 
kernel from SCSI disk (say, installed from another platform).

> nbhp700-mkboot -v /export/gecko/root/usr/mdec/boot netbsd netbsd.lif
>
> The netbsd.lif is what you should make available via TFTP.

Ahhhh.  Yes, that does seem to work.  That step really ought to be in 
the ./build.sh release step.  Also, it might be handy to also run:

nbhp700-mkboot -v /export/gecko/root/usr/mdec/boot netboot.lif

Anyone know how to make these changes?

TIA,
   -- MW