Hello list.
  Today I've tried netbooting sparc64 machines on a network, where I had
no administravie access to DHCP/BOOTP server.
  I've set up my own RPC bootparams server, but I couldn't find a way to
force machines to use that server.

ok boot net
Boot device: /pci@1f,0/pci@1,1/network@1,1  File and args:
>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.9
>> (me@spam.goes.here.com, Wed Dec  6 21:14:18 CET 2006)
net_open: client addr: 10.73.210.186
net_open: subnet mask: 255.255.128.0
net_open: net gateway: 10.73.255.254
net_open: server addr: 0.0.0.0
Using BOOTP protocol: ip address: 10.73.210.186, netmask: 255.255.128.0,
gateway: 10.73.255.254
root addr=0.0.0.0 path=
open netbsd: Unknown error: code 60
Failed to load 'netbsd'.
(...)

  Clients were stuck trying to netboot many different kernels from
0.0.0.0. Finally, after trying "vmunix" it failed with:

Boot:

  Typing anything started netbooting with BOOTP again.

  So I've written a simple patch. It adds new parameter -B to ofwboot.
Using this paramater swaps BOOTP with bootparams (so bootparams are
tried first, BOOTP second). This solved my problem.

http://strim.aster.net.pl/stuff/bootparamsfirst.diff

  It is against -current.

  Maybe this patch is worth including in NetBSD. Sorry for not updating
manual page, but I feel that my english is lacking.

  BTW. I noticed that ofwboot options -C and -D are also undocumented.
What does -C do?

Greets
Radek Kujawa