This procedure can be used when a different Sbus card is being used to access
the boot disk and the /devices entry for the card does not exist. It can also
be used when the target ID of the boot disk is changed to one which did not
previously exist.

(boot -r fails due to the drvconfig command being located on /usr, which cannot
be mounted until drvconfig is executed.)

If it is possible to, then attach a disk via the path where you want the boot
disk to be, then run the following commands before rebooting:

   drvconfig
   devlinks
   disks
   tapes
   ports
   audlinks
   vi /etc/vfstab

However, if the system has to be shutdown before you can change the hardware
configuration, then after you have done so, boot from net or cdrom and run the
same commands as follows:

   mount <boot-disk> /a
   drvconfig -r /a/devices -p /a/etc/path_to_inst
   devlinks -r /a
   disks -r /a
   tapes -r /a
   ports -r /a
   audlinks -r /a
   vi /a/etc/vfstab

NOTE: Sometimes, there are odd circumstances in which the drvconfig doesn't
create the devices due to the CDROM environment differing from the OS on the
disk.

There is an alternative method of doing this documented in INFODOC 13133.