Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!tezcat!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!howland.erols.net!news.sprintlink.net!news-peer.sprintlink.net!newsfeed.internetmci.com!news.bayarea.net!baygate.bayarea.net!thorpej From: thorpej@baygate.bayarea.net (Jason R. Thorpe) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: rbootd Date: 24 Nov 1996 18:31:32 GMT Organization: George's NetBSD answer man Lines: 22 Message-ID: <57a4a4$ko1@news.bayarea.net> References: <57830q$m1u@news.interlog.com> NNTP-Posting-Host: baygate.bayarea.net In article <57830q$m1u@news.interlog.com>, Jamie Reid <batsy@gold.interlog.com> wrote: >A friend an I are trying to netboot an hp300 from a freebsd box using the >hp300 netbsd kernel. It recognezed the ethnet interface when it had a >drive, but the boot prom doesn't have an option (like sun3's ) for a >netboot. (not one that we can find anyway) If anyone knows how to set the >hp300 's bootprom to netboot, I would love to hear it:) >-j The hp300 BOOTROM will automatically search for a network boot server. Hit the spacebar while the machine is running the self-test. Once the self-test is complete, the BOOTROM will display a menu of all possible boot devices. If the rbootd daemon is configured properly, it will appear in this menu. What version of FreeBSD are you using? FreeBSD used to have a bug in its BPF that caused rbootd to not function properly. -- Jason R. Thorpe <thorpej@bayarea.net> NetBSD/hp300 port-meister