cryun@sdrc.UUCP (Yun-Seng Chao) (07/16/90)
Hi gang!
I've been trying to get a "tapeless" machine to boot from another machine which
has a tape drive I can use. I followed the manual's instruction and first
did a "setenv netaddr <address>" and "setenv tapedevice bootp()sgia:/dev/tape",
then "boot -f $tapedevice(sash.IP4) --m". Unfortunately, all I get back is a
"No server for sgia:/dev/tape(sash.IP4)" message.
On sgia, the inetd.conf entry for bootp is "bootp -d", and tftp entry is
"tftp /usr/local/boot". Of course /usr/local/boot doesn't exist, but I don't
think we even got that far. We took a look at the data packets from sgia and
they were SUN RPC Portmap requests, even though the address is in /etc/hosts!
This has both me and the SGI hotline stumped ... Please email responses, since
I don't always get a chance to read news everyday.
Thanks in advance!
Yun Chao
--
------------------------------------------------------------------------
Yun-seng Chao {uunet, cinnet.com}!sdrc!cryun
SDRC; Milford, Ohiokeving@gaffa.sgi.com (Kevin Gurney) (07/18/90)
In article <1507@sdrc.UUCP> cryun@sdrc.UUCP (Yun-Seng Chao) writes: >Hi gang! >I've been trying to get a "tapeless" machine to boot from another machine which >has a tape drive I can use. I followed the manual's instruction and first >did a "setenv netaddr <address>" and "setenv tapedevice bootp()sgia:/dev/tape", >then "boot -f $tapedevice(sash.IP4) --m". Unfortunately, all I get back is a >"No server for sgia:/dev/tape(sash.IP4)" message. At SGI we do the majority of our installations from remote sources also and every time that someone has called me with this error it's been traced back to the fact that netaddr was set incorrectly in the proms. If I were you I'd doublecheck the <address> that you think your machine is. Assuming you didn't make a typing mistake, perhaps the source of your information is wrong. Just offering my advice based on years of seeing this problem. ---- "Is it hot in here?" keving@gaffa.wpd.sgi.com