Date: Sun, 29 Sep 1996 19:42:29 -0700 (PDT) From: graphix@iastate.edu To: freebsd-gnats-submit@freebsd.org Subject: bin/1694: rbootd does not appear to work Message-ID: <199609300242.TAA14046@freefall.freebsd.org> Resent-Message-ID: <199609300250.TAA17612@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1694 >Category: bin >Synopsis: rbootd does not appear to work >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 29 19:50:07 PDT 1996 >Last-Modified: >Originator: Kent Vander Velden >Organization: Iowa State University >Release: -current >Environment: FreeBSD pseudo.cc.iastate.edu 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Sun Sep 22 00:08:01 CDT 1996 root@pseudo.cc.iastate.edu:/usr/src/sys/compile/PSEUDO i386 >Description: Recently I bought an aging hp9000/300 and installed NetBSD on it. This is a diskless system and thus booting, root and swap are done over nfs. As part of the hp's boot sequence it sends a request for the bootcode. FreeBSD's rbootd does not appear to respond to request at least not in a mannor that the hp understands. If I use NetBSD's the requests are answered. >How-To-Repeat: Try running rbootd in debug mode and make a boot request and watch the traffic responses. >Fix: This problem might be associated with the problem report that I made concerning rarpd not working. Perhaps someone could look at the small differences between ours and NetBSD and OpenBSD and merge the differences. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609300242.TAA14046>