boot_mvme88k - mvme88k system bootstrapping procedures
When powered on, the mvme88k BUG firmware will proceed to
and will boot an operating system if autoboot is enabled. By sending
a ``break'' to the serial line during the initialization
is possible to stop the boot process and interact with the
Warm starts [Toc] [Back]
After a panic, or if the system is rebooted via reboot(8) or
the BUG firmware will only restart the operating system if
enabled and ``Auto Boot at power-up only'' is disabled in
the BUG environment.
Boot process options [Toc] [Back]
The BUG firmware will let the user enter a boot device identification,
kernel filename and boot options. If no filename is specified, /bsd will
be used by default.
The following boot options are recognized:
-a Prompt for the root filesystem device after the
-b On the next system reboot, always halt the system, even if a
reboot is required.
-c Enter the ``User Kernel Configuration'' mode upon startup
-d Enter the debugger, ddb(4), as soon as the kernel console has
-s Boot the system single-user. The system will be
unless this option is specified.
Abnormal system termination [Toc] [Back]
In case of system crashes, the kernel will usually enter the
ddb(4), unless it is not present in the kernel, or
it is disabled
via the ddb.panic sysctl. Upon leaving ddb, or if ddb was
the kernel will halt the system if it was still in device
phase, or attempt a dump to the configured dump device, if
crash dump will then be recovered by savecore(8) during the
boot cycle. It is also possible to force other behaviours from ddb.
/bsd default system kernel
/usr/mdec/bootxx primary bootstrap code for ``ffs''
file system on
/usr/mdec/bootsd secondary bootstrap code for SCSI
also installed as /bootsd)
/usr/mdec/bootst SCSI tape bootstrap code
/usr/mdec/netboot network bootstrap code
/usr/mdec/tftpboot tftp-only network bootstrap code
/usr/mdec/stboot Motorola VID block put as first file
ddb(4), boot_config(8), halt(8), init(8), installboot(8),
OpenBSD 3.6 February 24, 2004
[ Back ]