Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!think!ames!sun-barr!lll-winken!arisia!sgi!shinobu!odin!renegade!jweldon
From: jweldon@renegade.sgi.com (Jack Weldon)
Newsgroups: comp.sys.sgi
Subject: Re: help needed with distcp
Message-ID: <2231@odin.SGI.COM>
Date: 26 Dec 89 17:24:25 GMT
References: <8912211321.AA00221@avelon.lerc.nasa.gov>
Sender: news@odin.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 34

In article <8912211321.AA00221@avelon.lerc.nasa.gov> fsfacca@AVELON.LERC.NASA.GOV (Tony Facca) writes:
>
>I am trying to install 3.2 from a server on the net.  (via remote tape drive)
>
>	boot -f $tapedevice(sash.ip6) --m     (page 3-14)
>
>It doesn't specify what tapedevice should be set to.  The remote server is 
>called "avelon".  So I try:
>
>Tony Facca 

I'm not sure what manual you are looking in, but in the 4D1-3.2 Release Notes,
Page 2-13, in the section for installing via a remote tape drive, it says:

"Set the 'tapedevice' environment variable as shown in the example below.
Replace 'remotehost' in the command line below with the name of the remote
computer"

	setenv tapedevice bootp()remote_host:/dev/tape

Then boot the standalone shell 'sash' from the tape on the remote computer.
Replace CPU with your appropriate CPU type (IP4, IP5, IP7...):

	boot -f $tapedevice(sash.CPU) --m

So, for a 4D70GT loading from machine blitzen, the commands would be:

	setenv tapedevice bootp()blitzen:/dev/tape
	boot -f $tapedevice(sash.IP4) --m

Hope that helps.

Jack Weldon
SGI Product Support