Installation guide

If the new Version 4.0F generic vmunix kernel fails to boot and complete the
configuration of the updated system software, retry the boot using the c flag.
At the SRM console prompt, issue the following command:
>>> boot -flag c
Do not supply any other arguments. The c flag causes the booted kernel to
use default values instead of the values contained in the old configuration
files. After the new Version 4.0F generic vmunix kernel boots and completes
merging the updates to all of the system files, the system should boot the
/genvmunix kernel successfully without using the c flag.
2.2 Installation Problems Using Console Device EWE0
On a system with more than four Tulip-style network devices, a user is
limited to installation from the first four.
The install kernel is built knowing only of devices tu0 through tu3. With
recent network cards such as the DE504 (four network devices per card), it
will become increasingly likely that a user will attempt installation from a
higher numbered device. The boot will progress to the point where it
attempts to mount the root device (console ewn0, where n is e or further in
the alphabet), and fail.
The workaround is to install from console devices ewa0, ewb0, ewc0,or
ewd0.
2.3 Join Database Migration
If your system provides Dynamic Host Configuration Protocol (DHCP),
Remote Installation Services (RIS), or Dataless Management Services (DMS)
services to to other systems, you must update the database files for the join
daemon after you complete the installation. See Section 4.4.11 for additional
information.
2–2 Installation Notes