Netbooting Sparc64

Miles Nordin carton at Ivy.NET
Sun Apr 22 00:21:05 UTC 2007


>>>>> "dm" == Didrik Madheden <didrik at kth.se> writes:

    dm> A push in the right direction,

set up RARP and TFTP on the boot server.  Put /boot/loader onto the
TFTP server and name it after your machine's IP address in hex, in all
caps, such as '0A64648E' for 10.100.100.142.

When you type 'boot net' at the ok prompt, OpenPROM will do RARP, and
then TFTP for that filename to whatever IP answered the RARP lookup.

When /boot/loader gets control, it will call back to OpenPROM for
access to the network chip and console.  It will use DHCP.  Set up
DHCP on some machine, and use 'options root-path' to point
/boot/loader to the root filesystem.  ex.:

host amber {
  fixed-address amber;
  hardware ethernet 08:00:20:01:02:03;
  option root-path "69.31.131.61:/export/nboot/amber";
}

/boot/loader will read all the other /boot/... stuff it needs over
NFS, so make an NFS share for it.  Use '-maproot=root' in the exports
file on the NFS server.

Don't use bootparams at all.

RARP and TFTP must run on the same machine.  DHCP can run on a
different machine if you like.  The NFS server can be a third machine.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 304 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20070422/5bc00cdb/attachment.pgp


More information about the freebsd-sparc64 mailing list