Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!cascade.carleton.CDN!holtz
From: holtz@cascade.carleton.CDN (Neal Holtz)
Newsgroups: comp.sys.apollo
Subject: Loading SR10.2 from a tape on an SR9.7 node
Message-ID: <1366*holtz@cascade.carleton.cdn>
Date: 4 Jan 90 13:53:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34

I have a single DN2500 without CTAPE.  The rest of the network are
mostly DN4000's running SR9.7, and I do not want to upgrade any of
them to SR10.2, yet.  That is, the only nodes with CTAPES will be
running SR9.7.  I want to use those SR9.7 CTAPE's to install SR10.2
on my DN2500 -- it currently has only the minimum "hardware
acceptance" software running on it.

The most direct reference to this situation I've found in the release
notes or in the "Installing Domain Software" book (v.A02) is on page
4-4: 
	"Do not, however, use the tools_sr9 tools to install an SR-10
	compatible product from an SR9.7 node to an SR10 node.  The
	resulting ACLs on the installed product will not be correct."

My questions:

1. Does this warning apply when using distaa (& thus rbak) to move
   the software from CTAPE (on an SR9.7 node) to an authorized area
   (on an SR10 node)?

2. If it does apply, is it serious? (I don't worry too much about
   security, but various important protected subsystems could be
   troublesome).

3. If it does apply, and is serious, can I run the cvtrgy procedure
   to make my SR9.7 registries Domain/OS compatible, ahead of time?
   Except, this tool probably has to be installed.  Sigh?

4. Or, is it as I am hoping, and I have nothing to worry about?
   After using the SR9 rbak to load the install directory,
   perhaps I can just run tools_sr9/minst on the SR9.7 node,
   specifying a target authorized area on an SR10 node?

Any experience with this, anyone?