[Info-vax] "cloning" disks initially, after upgrades, after patches

[Phillip Helbig---undress to reply]

In article <uHHJUd8ckIIk at eisner.encompasserve.org>,
koehler at eisner.nospam.encompasserve.org (Bob Koehler) writes: 

>    I keep as few as possible system disks.  Why use up storage for
>    multiple copies if I don't need to?  From decades of experience,
>    I find that every time you copy something you double the
>    maintenance effort.

Some background: hobbyist cluster, so each node has its own system disk
(apart from satellites, but those are not relevant here); dual-ported
disks are something I don't have, nor do I have controllers which
support this (as far as I know).  SYSUAF and friends are on a shared
non-system disk, so no trouble here.

>    I kept SYSTARTUP_VMS.COM in SYS$COMMON and had it call node specific
>    scripts only where needed, and then by using f$getsyi("nodename").

I have little, if any, node-specific startup stuff.

>    When applying the same change to lots of systems, I would update the
>    appropriate system disk and then update any node specific scripts on
>    that disk by writing an EDT command file and starting it on all those
>    nodes via SYSMAN.

I'm thinking more of changes due to upgrades and patches.