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

[Phillip Helbig---undress to reply]

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

> I asked a similar question somewhat more briefly here a while back but
> got surprisingly little response.  There must be many other folks with 
> multiple system disks who want to save time and effort.

> So, we have nine scenarios.

One disadvantage of creating a modified system disk is that one first 
has to create it, then hope it works.  Any fiddling afterwards means 
something went wrong.  So, such a procedure is difficult to perfect 
iteratively.

Another alternative might be to set up a new node as a satellite and
configure it as one configures a normal satellite.  Then, when all is
done, make a copy of the disk, then change the boot device in the
console from the network to the appropriate root on the new disk.  The
only problem I see here is that one has previously set up this node as a
satellite while removing it in the usual way would remove its root.  Or 
does the cluster care HOW it boots as long as it does boot?  Or will it 
say "I expect this node to boot as a satellite, so I won't allow it to 
join the cluster"?