4.4BSD/usr/share/man/cat8/boot_tahoe.0

BOOT(8)                   BSD System Manager's Manual                  BOOT(8)

NNAAMMEE
     bboooott - system bootstrapping procedures

DDEESSCCRRIIPPTTIIOONN
     PPoowweerr ffaaiill aanndd ccrraasshh rreeccoovveerryy.. Normally, the system will reboot itself at
     power-up or after crashes.  An automatic consistency check of the file
     systems will be performed, and unless this fails, the system will resume
     multi-user operations.

     CCoolldd ssttaarrttss.. These are processor-type dependent.  On the CCI Power 6/32
     and related processors, the system will do a standard autoboot from drive
     0 upon power-up or reset.  This automatic boot may be cancelled by typing
     a `#' in the first few seconds after reset.  This enters console mode;
     the console prompt is `>' or `#'. The boot flags can be set to any hex-
     adecimal value --nn with the command

           #> p23 _n.

     The default device may be examined or set; see the Diagnostics and Debug-
     ging manual for the processor for details on device naming and syntax.
     After setting the boot flags and/or device, a bootstrap sequence can be
     initiated with

           #> fb

     A specific device or bootstrap file may be used; for example,

           #> fb xfd(1,0)

     would boot from the `a' partition on XFD drive 1.

     The file specifications used for the boostrap when loaded with the
     ``askme'' flag (register 23 set to 1 or 3) are of the form:

           device(adaptor,controller,unit,minor)

     where _d_e_v_i_c_e is the type of the device to be searched, _a_d_a_p_t_o_r is number
     of the VERSAbus (or VMEbus) to which the device is attached, _c_o_n_t_r_o_l_l_e_r
     is the unit number of the controller on that buss, _u_n_i_t is the unit num-
     ber of the disk or tape, and _m_i_n_o_r is the disk partition or tape file
     number.  Leading adaptor or controller numbers default to 0.  Normal line
     editing characters can be used when typing the file specification.  The
     following list of supported devices may vary from installation to instal-
     lation:

           dk   SMD or ESDI disks on VDDC or SMD-E
           cy   tape on Ciprico Tapemaster controller

     For example, to boot from a file system which starts at cylinder 0 of
     unit 0 of an SMD-E disk, type `dk(0,0)vmunix' to the boot prompt;
     `dk(2,1,0)vmunix' would specify drive 1 on SMD-E controller 2.

     In an emergency, the bootstrap methods described in the paper _I_n_s_t_a_l_l_i_n_g
     _a_n_d _O_p_e_r_a_t_i_n_g _4_._3 _B_S_D_-_t_a_h_o_e _U_N_I_X _o_n _t_h_e _T_a_h_o_e can be used to boot from a
     distribution tape.

FFIILLEESS
     /vmunix  system code
     /boot    system bootstrap

SSEEEE AALLSSOO
     halt(8),  reboot(8),  shutdown(8)

BBUUGGSS
     The disklabel format used by some versions of the console processor is
     different than the format used by UNIX and the bootstrap.

HHIISSTTOORRYY
4.4BSD                           June 9, 1993                                2