[Info-vax] booting on a single disk from a shadowset

[Jan-Erik Soderholm]

Den 2016-02-12 kl. 16:31, skrev Tom Adams:
> On Friday, February 12, 2016 at 3:08:55 AM UTC-5, Phillip Helbig (undress to reply) wrote:
>> In article <Z4NC8wkAhles at eisner.encompasserve.org>,
>> koehler at eisner.nospam.decuserve.org (Bob Koehler) writes:
>>
>>> In article <94e01af7-f13e-4387-bc85-5d6bc76f3f83 at googlegroups.com>, Tom Adams <tadamsmar at gmail.com> writes:
>>>>
>>>> The question is: Is there a quick way to get the system to book as a
>>>> shadow-set on dka100 when dka0 (the master member) is gone?
>>>
>>>     Change the dip switch (or whatever) that sets the unit number?
>>
>> Better: put both members in BOOTDEF_DEV.  This also takes care of the
>> case that one of the members has died---it can then boot from the other
>> one automatically.
>
> Do you also need to put both members in BOOT_DEV?
>
> This seems to imply that:
>
> http://h71000.www7.hp.com/openvms/journal/v8/whats_in_your_alphaserver_conosle.pdf
>

I cannot remember ever have set BOOT_DEV to anything on any
Alpha I have worked with. Only BOOTDEF_DEV...

The DS15 USer Guide says:

 > boot_dev: Device or device list from which booting is to be
 > attempted.

 > bootdef_dev: Device or device list from which booting is to
 > be attempted when no path is specified on the command line.

And also:

 > When auto_action is set to boot, the system boots from the
 > default boot device specified by the value of the bootdef_dev
 > environment variable.

And in the section about the 'boot' command it says:

 > If you do not specify a boot device in the command line,
 > the default boot device is used. The default boot device
 > is determined by the value of the bootdef_dev environment
 > variable...

So, no, I have no idea ehat the BOOT_DEV is for...

Jan-Erik.