🚀 go-pugleaf

In article <685@elf1.iastate.EDU>, GR.SLK@isumvs.iastate.edu (Steve Kunz) writes:
> Phil:
> 
> RE: Your query to comp.sys.dec
> 
> >  it is NOT installed as I expected so then I used
> >
> >                   setld /dev/rmt0h -a SUBSETNAME
> >
> >  to try to load the software.  The system obviously searches the entire

> 
> My docs say it should be as follows:
> 
>      setld -a /dev/rmt0h SUBSETNAME

	That's the right order if you want to use -a.  It's best
	to let setld(8) do most of work and use -l.  This will
	see what's on the tape and give you a menu of everything
	not installed.  If the subset you want is still missing
	you might have a bad tape.

	To check, get the subset list and look at it:

		foreach i ( SPACE.1 SPACE.2 SPACE.3 INSTCTRL )
			dd if=/dev/nrmt0h of=$i bs=10k
		end

	Then use tar(1) to look for the XXX.image file in the
	INSTCTRL archive.  It gives the sum(1) information and
	order of the files on the tape.  The subsets start after
	the INSTCTRL file.  If the tape has a ROOT file it, it
	is actually the 3rd file.

		+-------------------------+
		| Bootable image or SPACE |
		+-------------------------+
		|         SPACE		  |
		+-------------------------+
		|   Root dump or SPACE	  |
		+-------------------------+
		|	 INSTCTRL  	  |
		+-------------------------+
		|			  |
		~	 Subsets	  ~
		|			  |
		+-------------------------+

	The SPACE file is a 10k placeholder.  The "Guide to Preparing
	Software for Distribution on ULTRIX Systems" will contain
	more information about how setld tapes are constructed.
> 
> Steve Kunz
> GR.SLK@ISUMVS.IASTATE.EDU


-- 
Alan Rollow				alan@nabeth.enet.dec.com