[rescue] rescue Digest, Vol 133, Issue 24

Fri Dec 27 06:33:01 CST 2013

From:	IN%"rescue at sunhelp.org" 26-DEC-2013 13:00:31.02
To:	IN%"rescue at sunhelp.org"
Subj:	rescue Digest, Vol 133, Issue 24

Replying to everyone in one fell swoop.

>Message: 2
>Date: Wed, 25 Dec 2013 23:48:32 -0500 (EST)
>From: Mouse <mouse at Rodents-Montreal.ORG>

>errno 72 is EBADRPC on my NetBSD machines.  My impression is that errno
>values are fairly consistent across all the Unices; if you have another
>machine running the same version it might be worth checking to see if
>that's what it is there.  EBADRPC is rather uninformative, but does
>lead me to ask - you say you captured the whole exchange; did the IPX
>error out early (after just a few packets) or did it load the whole
>thing and error out at the very end, or what?  If it really is a

>From the capture, it looks like it didn't load anything and starting doing
"retries" at the LOOKUP stage in the capture.  However, the NFS/TFTP/etc
server was faithfully replying to those requests.  The SPARC probably wasn't
understanding it.

Now that I know where to look up the error numbers, I downloaded a chart and
now have them for reference.

On a lark, I created an OpenBSD/i386 VM and set up rarpd/bootparamd/tftpd and
NFS, and wouldn't you know?  The bloody thing booted the ramdisk kernel.

So it seems either OpenBSD (or sparc OpenBSD) does not like the Linux flavor
of all the daemons needed to boot, or I had things configured incorrectly. 
Which to me is strange as I configured them the exact same way on OpenBSD and
it worked.

>Date: Thu, 26 Dec 2013 06:00:01 +0000
>From: microcode at zoho.com
>To: rescue at sunhelp.org
>Subject: Re: [rescue] The IPX lives, kinda
>Message-ID: <20131226060001.GA26545 at zoho.com>
>Content-Type: text/plain; charset=us-ascii

>Presuming the OP has downloaded all the necessary files and made them
>available in the correct path on his tftp server, he should ask on the
>openbsd.misc mailing list.

Due to the fact that I am now getting stray interrupts when activating the
onboard NIC when booted into the ramdisk kernel, that is my next stop.

Thanks all for the pointers.

More information about the rescue mailing list