>Number:         23957
>Category:       install
>Synopsis:       sparc netboot install should allow specification of nfs server
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 03 05:39:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Kenneth Raeburn
>Release:        1.6.1
>Organization:
MIT
>Environment:
(not installed yet)
sun ultra 60
>Description:
Near as I can tell, from the docs and a (somewhat brief) look at
the sources, the ofwboot.net->netbsd.INSTALL boot process doesn't
allow explicit specification of the nfs server to use; it's derived
from the dhcp server.

I believe there's another DHCP server on this network,
and for some reason, ofwboot.net seems to reliably get a server
address and pathname different from what I'm trying to feed it from
my DHCP server.  (I can't verify it, because we're on a switch, not
a hub, so I can't see the packets, and I have no access to the other
machine I suspect is causing me problems.)

For at least some of the Sun workstations, the "boot net" firmware
command can be told the address and filename for tftp loading; it's
just the NetBSD boot loader that's causing me grief.
>How-To-Repeat:
Try installing by netbooting when there's a DHCP server you don't control
on the same subnet, trying to feed different information to the
machine.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: