[Info-vax] MOUNT/SYSTEM before SHADOWING license loaded: /SYSTEM vs. /NOSYSTEM

[Phillip Helbig---undress to reply]

In article <ikd83h$hn9$1 at online.de>, helbig at astro.multiCLOTHESvax.de
(Phillip Helbig---undress to reply) writes: 

> For a long time now, I have been mounting /CLUSTER a shadowed disk which 
> itself contains the license database.  At least when this is done at 
> startup (and I have to do it at startup, since SYSUAF and most other 
> files which one can move off the system disk are on it), it works, even 
> though the shadowing license is not loaded until after this shadow set 
> is mounted.
> 
> Would such a mount work at startup but /NOSYSTEM?
> 
> The reason I need to do this is that I have to issue SET VOLUME/LIMIT on 
> this shadow set, which requires a /NOSYSTEM mount.  The idea is the 
> following:

Obviously, if something goes wrong, then my cluster won't boot.  I would 
have to remove each system disk, mount it on another machine, change the 
code in SYLOGICALS.COM back to the original code, return the system disk 
to its node, reboot, then wonder how to ever reconfigure DISK$USER 
without mounting it /NOSYSTEM on a machine which doesn't itself need it.

Maybe I'll try MOUNT/NOSYSTEM at startup for a test shadowset first, but 
I would still be interested in opinions from folks here.