[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libsa & bootp
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: libsa & bootp
- From: Jesse Kempf <kempf_(_at_)_rpi_(_dot_)_edu>
- Date: 25 Sep 2004 03:15:03 -0400
I tried to netboot one of my Ultra5s using DHCP + RFC1497 extensions,
rather than RARP and Bootparams. This was a distinct failure due to the
apparent lack of support for DHCP in ofwboot.net. The BOOTP requests
broadcast by the loader did not include any options that might give
ofwboot a clue as to where its root is located.
I've tracked the problem back to libsa, against which ofwboot is linked.
For bootp, ofwboot calls bootp() in libsa, which does not process the
vendor extensions. Considering that root-path is an RFC1497 extension,
this is inconvenient. So, I have a pair of questions:
1) Is anyone currently working on adding support for DHCP (not bootp) to
libsa, and by extension, the Sparc64 network bootloader?
2) Should I seek to extend the bootp support in libsa to encompass DHCP
and RFC2132, add a new set of functions, or just tear bootp out and
replace it completely with a stripped-down RFC2131/2132 implementation?
Visit your host, monkey.org