reboot.tproj/boot_tahoe.8

   1 .\" Copyright (c) 1980, 1991, 1993
   2 .\"     The Regents of the University of California.  All rights reserved.
   3 .\"
   4 .\" Redistribution and use in source and binary forms, with or without
   5 .\" modification, are permitted provided that the following conditions
   6 .\" are met:
   7 .\" 1. Redistributions of source code must retain the above copyright
   8 .\"    notice, this list of conditions and the following disclaimer.
   9 .\" 2. Redistributions in binary form must reproduce the above copyright
  10 .\"    notice, this list of conditions and the following disclaimer in the
  11 .\"    documentation and/or other materials provided with the distribution.
  12 .\" 3. All advertising materials mentioning features or use of this software
  13 .\"    must display the following acknowledgement:
  14 .\"     This product includes software developed by the University of
  15 .\"     California, Berkeley and its contributors.
  16 .\" 4. Neither the name of the University nor the names of its contributors
  17 .\"    may be used to endorse or promote products derived from this software
  18 .\"    without specific prior written permission.
  19 .\"
  20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
  21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  23 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
  24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  30 .\" SUCH DAMAGE.
  31 .\"
  32 .\"     @(#)boot_tahoe.8        8.2 (Berkeley) 4/19/94
  33 .\"
  34 .Dd April 19, 1994
  35 .Dt BOOT 8 tahoe
  36 .Os
  37 .Sh NAME
  38 .Nm boot
  39 .Nd
  40 system bootstrapping procedures
  41 .Sh DESCRIPTION
  42 .Sy Power fail and crash recovery.
  43 Normally, the system will reboot itself at power-up or after crashes.
  44 An automatic consistency check of the file systems will be performed,
  45 and unless this fails, the system will resume multi-user operations.
  46 .Pp
  47 .Sy Cold starts.
  48 These are processor-type dependent.
  49 On the
  50 .Tn CCI
  51 Power 6/32 and related processors,
  52 the system will do a standard autoboot from drive 0
  53 upon power-up or reset.
  54 This automatic boot may be cancelled by typing a
  55 .Ql \&#
  56 in the first few seconds after reset.
  57 This enters console mode; the console prompt is
  58 .Ql >
  59 or
  60 .Ql \&# .
  61 The boot flags can be set to any hexadecimal value
  62 .Fl n
  63 with the command
  64 .Pp
  65 .Bd -filled -offset indent -compact
  66 .Li \&#> p23
  67 .Ar n .
  68 .Ed
  69 .Pp
  70 The default device may be examined or set; see the Diagnostics and Debugging
  71 manual for the processor for details on device naming and syntax.
  72 After setting the boot flags and/or device,
  73 a bootstrap sequence can be initiated with
  74 .Pp
  75 .Dl #> fb
  76 .Pp
  77 A specific device or bootstrap file may be used; for example,
  78 .Pp
  79 .Dl \&#> \&fb xfd(1,0)
  80 .Pp
  81 would boot from the `a' partition on
  82 .Tn XFD
  83 drive 1.
  84 .Pp
  85 The file specifications used for the boostrap
  86 when loaded with the
  87 .Dq askme
  88 flag
  89 (register 23 set to 1 or 3)
  90 are of the form:
  91 .Pp
  92 .Dl device(adaptor,controller,unit,minor)
  93 .Pp
  94 where
  95 .Ar device
  96 is the type of the device to be searched,
  97 .Ar adaptor
  98 is number of the
  99 .Tn VERSAbus
 100 (or
 101 .Tn VMEbus )
 102 to which the device is attached,
 103 .Ar controller
 104 is the unit number of the controller on that buss,
 105 .Ar unit
 106 is the unit number of the disk or tape,
 107 and
 108 .Ar minor
 109 is the disk partition or tape file number.
 110 Leading adaptor or controller numbers default to 0.
 111 Normal line editing characters can be used when typing the file specification.
 112 The following list of supported devices may vary from installation to
 113 installation:
 114 .Pp
 115 .Bd -unfilled -offset indent -compact
 116 dk      SMD or ESDI disks on VDDC or SMD-E
 117 cy      tape on Ciprico Tapemaster controller
 118 .Ed
 119 .Pp
 120 For example,
 121 to boot from a file system which starts at cylinder 0
 122 of unit 0 of an
 123 .Tn SMD-E
 124 disk, type
 125 .Ql dk(0,0)vmunix
 126 to the boot prompt;
 127 .Ql dk(2,1,0)vmunix
 128 would specify drive 1 on
 129 .Tn SMD-E
 130 controller 2.
 131 .Pp
 132 In an emergency, the bootstrap methods described in the paper
 133 .%T "Installing and Operating 4.3 BSD-tahoe UNIX on the Tahoe"
 134 can be used
 135 to boot from a distribution tape.
 136 .Sh FILES
 137 .Bl -tag -width /vmunix -compact
 138 .It Pa /vmunix
 139 system code
 140 .It Pa /boot
 141 system bootstrap
 142 .El
 143 .Sh SEE ALSO
 144 .Xr halt 8 ,
 145 .Xr reboot 8 ,
 146 .Xr shutdown 8
 147 .Sh BUGS
 148 The disklabel format used by some versions of the console processor
 149 is different than the format used by
 150 .Tn UNIX
 151 and the bootstrap.
 152 .Sh HISTORY