projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| 61dbfbf1 KB |
1 | .\" Copyright (c) 1980 The Regents of the University of California. |
| 2 | .\" All rights reserved. | |
| 6f5c285b | 3 | .\" |
| 31b39933 | 4 | .\" %sccs.include.redist.man% |
| 61dbfbf1 | 5 | .\" |
| 31b39933 | 6 | .\" @(#)boot_tahoe.8 6.3 (Berkeley) %G% |
| 6f5c285b MK |
7 | .\" |
| 8 | .TH REBOOT 8 "" | |
| 9 | .UC 4 | |
| 10 | .SH NAME | |
| 11 | reboot \- UNIX bootstrapping procedures | |
| 12 | .SH SYNOPSIS | |
| 31b39933 | 13 | .B reboot |
| 6f5c285b MK |
14 | [ |
| 15 | .B \-n | |
| 16 | ] [ | |
| 17 | .B \-q | |
| 18 | ] | |
| 19 | .SH DESCRIPTION | |
| 20 | .PP | |
| 21 | UNIX is started by placing it in memory | |
| 22 | at location zero and transferring to the entry point. | |
| 23 | Since the system is not reenterable, | |
| 24 | it is necessary to read it in from disk or tape | |
| 25 | each time it is to be bootstrapped. | |
| 26 | .PP | |
| 27 | .B Rebooting a running system. | |
| 28 | When a UNIX is running and a reboot is desired, | |
| 29 | .IR shutdown (8) | |
| 30 | is normally used. | |
| 31 | If there are no users then | |
| 31b39933 | 32 | .B reboot |
| 6f5c285b MK |
33 | can be used. |
| 34 | Reboot causes the disks to be synced and allows the system | |
| 35 | to perform other shutdown activities such as resynchronizing | |
| 36 | hardware time-of-day clocks. | |
| 37 | A multi-user reboot (as described below) is then initiated. | |
| 38 | This causes a system to be | |
| 39 | booted and an automatic disk check to be performed. If all this succeeds | |
| 40 | without incident, the system is then brought up for many users. | |
| 41 | .PP | |
| 42 | Options to reboot are: | |
| 43 | .TP | |
| 44 | .B \-n | |
| 45 | option avoids the sync. It can be used if a disk or the processor | |
| 46 | is on fire. | |
| 47 | .TP | |
| 48 | .B \-q | |
| 49 | reboots quickly and ungracefully, without shutting down running | |
| 50 | processes first. | |
| 51 | .PP | |
| 52 | .I Reboot | |
| 53 | normally logs the reboot using | |
| 54 | .IR syslog (8) | |
| 55 | and places a shutdown record in the login accounting file | |
| 31b39933 | 56 | /var/log/wtmp. |
| 6f5c285b MK |
57 | These actions are inhibited if the |
| 58 | .B \-n | |
| 59 | or | |
| 60 | .B \-q | |
| 61 | options are present. | |
| 62 | .PP | |
| 63 | .B "Power fail and crash recovery." | |
| 64 | Normally, the system will reboot itself at power-up or after crashes. | |
| 65 | An automatic consistency check of the file systems will be performed | |
| 66 | as described in | |
| 67 | .IR fsck (8). | |
| 68 | and unless this fails, the system will resume multi-user operations. | |
| 69 | .PP | |
| 70 | .B Cold starts. | |
| 71 | These are processor-type dependent. | |
| 72 | On the CCI Power 6/32 and related processors, | |
| 73 | the system will do a standard autoboot from drive 0 | |
| 74 | upon power-up or reset. | |
| 75 | This automatic boot may be cancelled by typing a \*(lq#\*(rq | |
| 76 | in the first few seconds after reset. | |
| 77 | This enters console mode; the console prompt is \*(lq>\*(rq or \*(lq#>\*(rq. | |
| 78 | The boot flags can be set to any hexadecimal value \fIn\fP with the command | |
| 79 | .IP | |
| 80 | #> p23 \fIn\fP. | |
| 81 | .LP | |
| 82 | The default device may be examined or set; see the Diagnostics and Debugging | |
| 83 | manual for the processor for details on device naming and syntax. | |
| 84 | After setting the boot flags and/or device, | |
| 85 | a bootstrap sequence can be initiated with | |
| 86 | .IP | |
| 87 | #> fb | |
| 88 | .LP | |
| 89 | A specific device or bootstrap file may be used; for example, | |
| 90 | .IP | |
| 91 | #> fb xfd(1,0) | |
| 92 | .LP | |
| 93 | would boot from the `a' partition on XFD drive 1. | |
| 94 | .PP | |
| 95 | The file specifications used for the boostrap | |
| 96 | when loaded with the \*(lqaskme\*(rq flag | |
| 97 | (register 23 set to 1 or 3) | |
| 98 | are of the form: | |
| 99 | .IP | |
| 100 | device(adaptor,controller,unit,minor) | |
| 101 | .PP | |
| 102 | where | |
| 103 | .I device | |
| 104 | is the type of the device to be searched, | |
| 105 | .I adaptor | |
| 106 | is number of the VERSAbus (or VMEbus) to which the device is attached, | |
| 107 | .I controller | |
| 108 | is the unit number of the controller on that buss, | |
| 109 | .I unit | |
| 110 | is the unit number of the disk or tape, | |
| 111 | and | |
| 112 | .I minor | |
| 113 | is the disk partition or tape file number. | |
| 114 | Leading adaptor or controller numbers default to 0. | |
| 115 | Normal line editing characters can be used when typing the file specification. | |
| 116 | The following list of supported devices may vary from installation to | |
| 117 | installation: | |
| 118 | .LP | |
| 119 | .ta 5 10 | |
| 120 | .nf | |
| 121 | dk SMD or ESDI disks on VDDC or SMD-E | |
| 122 | cy tape on Ciprico Tapemaster controller | |
| 123 | .fi | |
| 124 | .PP | |
| 125 | For example, | |
| 126 | to boot from a file system which starts at cylinder 0 | |
| 127 | of unit 0 of an SMD-E disk, type \*(lqdk(0,0)vmunix\*(rq | |
| 128 | to the boot prompt; \*(lqdk(2,1,0)vmunix\*(rq | |
| 129 | would specify drive 1 on SMD-E controller 2. | |
| 130 | .PP | |
| 131 | In an emergency, the bootstrap methods described in the paper | |
| 132 | ``Installing and Operating 4.3BSD-tahoe UNIX on the Tahoe'' can be used | |
| 133 | to boot from a distribution tape. | |
| 134 | .SH FILES | |
| 135 | .ta \w'/vmunix 'u | |
| 136 | /vmunix system code | |
| 137 | .br | |
| 138 | /boot system bootstrap | |
| 139 | .SH "SEE ALSO" | |
| 140 | crash(8), | |
| 141 | disklabel(8), | |
| 142 | fsck(8), | |
| 143 | halt(8), | |
| 144 | init(8), | |
| 145 | rc(8), | |
| 146 | shutdown(8), | |
| 147 | syslogd(8) | |
| 148 | .SH BUGS | |
| 149 | The disklabel format used by some versions of the console processor | |
| 150 | is different than the format used by UNIX and the bootstrap. |