LUNA-II (68040 based LUNA) support
[unix-history] / usr / src / sbin / reboot / boot_i386.8
CommitLineData
fbcbf93f 1.\" Copyright (c) 1991 The Regents of the University of California.
49177589
WN
2.\" All rights reserved.
3.\"
4.\" This code is derived from software written and contributed
5.\" to Berkeley by William Jolitz.
6.\"
fbcbf93f 7.\" %sccs.include.redist.roff%
49177589 8.\"
50d77188 9.\" @(#)boot_i386.8 1.3 (Berkeley) %G%
49177589 10.\"
fbcbf93f 11.Dd
50d77188 12.Dt BOOT 8
fbcbf93f
CL
13.Os
14.Sh NAME
50d77188 15.Nm boot
fbcbf93f 16.Nd
50d77188 17system bootstrapping procedures
fbcbf93f 18.Sh DESCRIPTION
fbcbf93f 19.Sy Power fail and crash recovery.
49177589 20Normally, the system will reboot itself at power-up or after crashes.
50d77188 21An automatic consistency check of the file systems will be performed,
49177589 22and unless this fails, the system will resume multi-user operations.
fbcbf93f 23.Pp
50d77188 24.Sy Cold starts.
fbcbf93f
CL
25The 386
26.Tn "PC AT"
50d77188
KB
27clones attempt to boot the floppy disk drive A (otherwise known as drive
280) first, and failing that, attempt to boot the hard disk C (otherwise
29known as hard disk controller 1, drive 0).
fbcbf93f
CL
30The automatic boot will attempt to load
31.Pa vmunix
50d77188
KB
32from partition A of either the floppy or the hard disk.
33This boot may be aborted by typing any character on the keyboard repeatedly
34(four or five times at least) during the operating system load phase, after
35which the bootstrap will prompt for the file that you wish to load instead.
fbcbf93f
CL
36.Pp
37One exception to this is the
38.Ql d
50d77188 39key, which will not abort the load but instead silently force the
fbcbf93f 40.Dv DEBUG
50d77188
KB
41boot flags.
42The boot flags for an autoboot are 0, and 3 for the successive boot after
43an aborted autoboot sequence.
49177589
WN
44No other provison is made for setting boot flags (yet).
45A specific device or bootstrap file may be used; for example,
fbcbf93f 46.Pp
49177589 47The file specifications used for the boostrap
fbcbf93f
CL
48when loaded with the
49.Dq askme
50flag
49177589
WN
51(e.g. an aborted autoboot)
52are of the form:
fbcbf93f
CL
53.Pp
54.Dl device unit partition:
55.Pp
49177589 56where
fbcbf93f 57.Ar device
49177589 58is the type of the device, assumed to be on the ISA bus, to be searched,
fbcbf93f 59.Ar unit
49177589
WN
60is the unit number of the disk or tape,
61and
fbcbf93f 62.Ar partition
49177589
WN
63is the disk partition or tape file number.
64Normal line editing characters can be used when typing the file specification.
65The following list of supported devices may vary from installation to
66installation:
fbcbf93f
CL
67.Bd -unfilled -offset indent
68wd ST506, IDE, ESDI, RLL disks on a WD100[2367] or lookalike
69 controller
70fd 5 1/4" or 3 1/2" High density floppies
71.Ed
72.Pp
49177589
WN
73For example,
74to boot from a file system which starts at cylinder 0
fbcbf93f
CL
75of unit 0 of an IDE disk, type
76.Dq Li wd0a:vmunix
77to the boot prompt;
78.Dq Li fd0a:vmunix
49177589 79would specify a 3 1/2" floppy drive 0 .
fbcbf93f 80.Pp
49177589 81In an emergency, the bootstrap methods described in the paper
fbcbf93f
CL
82.%T "Installing and Operating 4.3 BSD-Reno UNIX on the AT/386"
83can be used
49177589 84to boot from a distribution tape.
fbcbf93f
CL
85.Sh FILES
86.Bl -tag -width /vmunixxx -compact
87.It Pa /vmunix
88system code
89.It Pa /boot
90system bootstrap
91.El
92.Sh SEE ALSO
fbcbf93f 93.Xr halt 8 ,
50d77188
KB
94.Xr reboot 8 ,
95.Xr shutdown 8
fbcbf93f
CL
96.Sh BUGS
97The disklabel format used by this version of
98.Bx
99is quite
100different from that of other architectures.