Re: Renaming a root from [SYS0] to [SYS1] ?
- From: etmsreec@xxxxxxxxxxx
- Date: 28 Dec 2006 04:26:57 -0800
Rename SYS0 on the _running_ system to be SYS1 ???
Be interested to know the results (if VMS lets you, whether things then
break, etc) but I suspect that the only safe way to do this is to
reboot from another disk (whether a minimum environment on another disk
or via a CD) and rename the system-specific directory from that.
Steve
JF Mezei wrote:
Node BIKE is now in [SYS0] of a system disk for Alpha.
Node GEAR is just a concept. (big debate between CHAIN and GEAR for the name).
What I would like to do is this;
on BIKE, rename [SYS0] to [SYS1], then create a new SYS0 root for GEAR.
And from then on, BIKE would boot with the boot flags set to look for root
"1" while GEAR would look for root 0.
GEAR can then do an integral copy of BIKE's system disk onto its own. And
it then remains faily easy to keep both system disks in synch, as well as
make it possible for either node to act as a boot node for the other.
Question:
If I rename the disk:[000000]SYS0.DIR to [000000]SYS1.DIR on a running system,
Will redefining SYS$SYSROOT and SYS$COMMON to use SYS1 instead of SYS0 be
enough to continue to function at the DCL level ? (aka, make use of the
sys$manager:makeroot.com to create the new root and populate it with infor
for my new GEAR node ) ?
I realise that BIKE will need to reboot to get a properly defined root
pointing to SYS1. But if I can hav it reboot after GEAR has been able to
copy the disk and be self-sustaining and participate to keep cluster quorum
then loss of BOKE while it reboots wouldn't be bad.
.
- References:
- Renaming a root from [SYS0] to [SYS1] ?
- From: JF Mezei
- Renaming a root from [SYS0] to [SYS1] ?
- Prev by Date: Re: Relationship between node numbers, alloclass etc
- Next by Date: Re: Setting sound frequency for BEEPs on DS10L
- Previous by thread: Renaming a root from [SYS0] to [SYS1] ?
- Next by thread: Re: Renaming a root from [SYS0] to [SYS1] ?
- Index(es):
Relevant Pages
|
|
