Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!caen!ox.com!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Problems booting diskless on Ethernet
Message-ID: <50081142.1bc5b@pisa.ifs.umich.edu>
Date: 25 Feb 91 20:58:17 GMT
References: <HANCHE.91Feb25182545@hufsa.imf.unit.no>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 14

In article <HANCHE.91Feb25182545@hufsa.imf.unit.no>, hanche@imf.unit.no (Harald Hanche-Olsen) writes:

  Does anybody know anything about the protocol used when booting
  diskless from another node?

The net read routine in the PROM is very simple-minded.  It does no timeout/
retransmission.  That means that if you have trouble loading netboot, you
have to start over.  I don't remember whether netboot (the thing that says
".......loaded xxx bytes" does much better, but you used to be able to get
it to retry by hitting the space bar.

You can also read the stdout from netman (by running it in a pad, for
example) and it may tell you about problems it's having communicating with
the partner.


Brought to you by Super Global Mega Corp .com