1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)boot_tahoe.8 8.2 (Berkeley) 04/19/94 7.\" 8.Dd 9.Dt BOOT 8 tahoe 10.Os 11.Sh NAME 12.Nm boot 13.Nd 14system bootstrapping procedures 15.Sh DESCRIPTION 16.Sy Power fail and crash recovery. 17Normally, the system will reboot itself at power-up or after crashes. 18An automatic consistency check of the file systems will be performed, 19and unless this fails, the system will resume multi-user operations. 20.Pp 21.Sy Cold starts. 22These are processor-type dependent. 23On the 24.Tn CCI 25Power 6/32 and related processors, 26the system will do a standard autoboot from drive 0 27upon power-up or reset. 28This automatic boot may be cancelled by typing a 29.Ql \&# 30in the first few seconds after reset. 31This enters console mode; the console prompt is 32.Ql > 33or 34.Ql \&# . 35The boot flags can be set to any hexadecimal value 36.Fl n 37with the command 38.Pp 39.Bd -filled -offset indent -compact 40.Li \&#> p23 41.Ar n . 42.Ed 43.Pp 44The default device may be examined or set; see the Diagnostics and Debugging 45manual for the processor for details on device naming and syntax. 46After setting the boot flags and/or device, 47a bootstrap sequence can be initiated with 48.Pp 49.Dl #> fb 50.Pp 51A specific device or bootstrap file may be used; for example, 52.Pp 53.Dl \&#> \&fb xfd(1,0) 54.Pp 55would boot from the `a' partition on 56.Tn XFD 57drive 1. 58.Pp 59The file specifications used for the boostrap 60when loaded with the 61.Dq askme 62flag 63(register 23 set to 1 or 3) 64are of the form: 65.Pp 66.Dl device(adaptor,controller,unit,minor) 67.Pp 68where 69.Ar device 70is the type of the device to be searched, 71.Ar adaptor 72is number of the 73.Tn VERSAbus 74(or 75.Tn VMEbus ) 76to which the device is attached, 77.Ar controller 78is the unit number of the controller on that buss, 79.Ar unit 80is the unit number of the disk or tape, 81and 82.Ar minor 83is the disk partition or tape file number. 84Leading adaptor or controller numbers default to 0. 85Normal line editing characters can be used when typing the file specification. 86The following list of supported devices may vary from installation to 87installation: 88.Pp 89.Bd -unfilled -offset indent -compact 90dk SMD or ESDI disks on VDDC or SMD-E 91cy tape on Ciprico Tapemaster controller 92.Ed 93.Pp 94For example, 95to boot from a file system which starts at cylinder 0 96of unit 0 of an 97.Tn SMD-E 98disk, type 99.Ql dk(0,0)vmunix 100to the boot prompt; 101.Ql dk(2,1,0)vmunix 102would specify drive 1 on 103.Tn SMD-E 104controller 2. 105.Pp 106In an emergency, the bootstrap methods described in the paper 107.%T "Installing and Operating 4.3 BSD-tahoe UNIX on the Tahoe" 108can be used 109to boot from a distribution tape. 110.Sh FILES 111.Bl -tag -width /vmunix -compact 112.It Pa /vmunix 113system code 114.It Pa /boot 115system bootstrap 116.El 117.Sh SEE ALSO 118.Xr halt 8 , 119.Xr reboot 8 , 120.Xr shutdown 8 121.Sh BUGS 122The disklabel format used by some versions of the console processor 123is different than the format used by 124.Tn UNIX 125and the bootstrap. 126.Sh HISTORY 127