I've got dhcpd setup and it claims that it's got a boot request from 
the Qube I'm trying to netboot:
Nov 27 20:07:09 bluesky dhcpd: BOOTREQUEST from 00:10:e0:00:d1:f9 via 
tlp0
Nov 27 20:07:09 bluesky dhcpd: BOOTREPLY for 10.0.1.8 to 
iceqube.thille.org (00:10:e0:00:d1:f9) via tlp0

And I think I've got the dhcpd.conf file setup correctly (it give 
address out to all the machines just fine):

# This block should be commented out unless we are trying to netboot
# iceqube to fix something :-(
   host iceqube.thille.org {
       hardware ethernet 00:10:E0:00:D1:F9;
       fixed-address iceqube.thille.org.;
       option host-name "iceqube";      # name if dns lookup doesn't 
resolve
       filename "/netbsd.gz";           # name of the bootloader or 
kernel to download
       next-server bluesky.thille.org.; # which machine to tftp filename 
from
       server-name="10.0.1.5";
       option root-path "/home/iceqube/root";   #the path on the NFS 
server.
   }

But it's unclear from the FAQ and the Diskless NetBSD guide whether I 
really need the tftp server setup or not?  Can I get away with just the 
NFS server?  Does the ROM in the Cobalt Qube2 understand NFS, or only 
TFTP?

I think I'll go ahead and try to setup the TFTPD if I don't hear from 
someone soon, but figured asking might save me some time.

Thanks,

Robert