[Info-vax] SYS$SYSROOT and Local Customizations

[Phillip Helbig undress to reply]

In article <rmv0s6$k8o$1 at dont-email.me>, Stephen Hoffman
<seaohveh at hoffmanlabs.invalid> writes: 

> On 2020-10-23 08:47:59 +0000, Phillip Helbig (undress to reply said:
> 
> > When I move to x86, I'll seriously consider putting a non-system disk 
> > between SYS$SPECIFIC and SYS$COMMON in the definition of SYS$SYSROOT.  

> Relocating the cluster configuration and authorization files via 
> logical name is a (necessary) hack for any configuration that has or 
> might have more than one system disk. 

And one needs more than one system disk in a cluster in order to do a 
rolling upgrade, not to mention mixed-architecture stuff.

> That is, I prefer to keep the local customizations and local files 
> separate, using shims in the SY* files to access the production 
> startups, and logical names to redirect.

> The shim procedures mount the common disk (if required) and then access 
> and invoke the customizations in files there. And reference the 
> authorization and cluster configuration files there, too.

More or less what I'm doing now.

I don't put anything on the system disk except for DEC-related stuff 
which installs there by default.  Dedicated disks for users, third-party 
software, scratch, data, and so on.

> I don't prefer to leave local stuff in SYS$SYSROOT, though will 
> necessarily parallel the approach that an existing site is already 
> using.

I use it only for node-specific stuff.