1.\" $NetBSD: boot.8,v 1.9 2002/01/15 16:38:29 wiz Exp $ 2.\" 3.\" Copyright (c) 1980, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 35.\" 36.Dd January 15, 2002 37.Dt BOOT 8 x68k 38.Os 39.Sh NAME 40.Nm boot 41.Nd system bootstrapping procedures 42.Sh DESCRIPTION 43.Ss Power fail and crash recovery 44Normally, the system will reboot itself at power-up or after crashes. 45An automatic consistency check of the file systems will be performed, 46and unless this fails, the system will resume multi-user operations. 47.Ss Cold starts 48The X68000/X68030 system boots from the device 49which is determined by the configuration of 50battery-backuped SRAM. 51By default, the boot ROM attempts to boot from 52floppy disk drives (from 0 to 3) first, 53and then attempts to boot from hard disk (SASI or SCSI). 54On the 55.Nx Ns Tn /x68k , 56booting from SCSI disks (sd??) 57and 2HD floppy disks (fd?a, fd?c) is currently supported. 58.Ss Bootstrapping from a floppy 59When the floppy disk is selected as the boot device, the initial 60program loader of the IOCS (firmware) reads the 61.Pa fdboot_ufs 62program at the top of the disk, and then the fdboot_ufs program loads the 63.Pa /boot 64program from the FFS or LFS file system. Normally, the 65.Pa /boot 66program then loads the 67.Nx 68kernel 69.Pa /netbsd 70from the same floppy. In addition, the 71.Pa /boot 72program has abilities to uncompress gzip'ed kernels, to read 73the kernel from other disks of other file systems etc (see below). 74.Pp 75For floppy disks, 76.Pa fdboot_ustar 77is also provided to read large 78kernels which do not fit one a single floppy. 79.Ss Bootstrapping from a SCSI hard disk 80When a SCSI hard disk is selected as the boot device, the initial 81program loader on the SCSI host adapter's ROM reads the 82operating system-independent IPL menu program at the top of the disk. 83The IPL menu program recognizes the partition table, and selects the partition 84to read the operating system kernel. During this phase, when the 85HELP key on the keyboard is pressed, the IPL menu program displays 86the partition menu of that disk to prompt the user to select the boot 87partition (although the 88.Nx 89implementation of the IPL menu, 90.Pa /usr/mdec/mboot , 91does not have this functionality). 92.Pp 93Next, the IPL menu reads the OS-dependent boot program from the 94top of the selected partition. For 95.Nx 96FFS/LFS file systems 97.Pa sdboot_ufs 98is used. The 99.Pa sdboot_ufs 100program then loads the 101.Pa /boot 102program from that partition. 103.Ss Normal Operation 104Once running, a banner similar to the following will appear: 105.Bd -literal -offset indent 106NetBSD Multi-boot, Revision 1.1 107(user@buildhost, builddate) 108Press return to boot now, any other key for boot menu 109booting sd0a:netbsd - starting in 5 110.Ed 111.Pp 112After a countdown, the system image listed will be loaded. (In the 113example above, it will be 114.Dq Li sd0a:netbsd 115which is the file 116.Nm netbsd 117on partition 118.Dq a 119of the 120.Nx 121SCSI hard disk of ID 0. 122Pressing a key within the time limit will enter interactive mode. 123.Ss Interactive mode 124In interactive mode, the boot loader will present a prompt, allowing 125input of these commands: 126.Bl -tag -width 10n -offset indent 127.It Xo Ic boot 128.Op Ar device : Ns 129.Op Ar filename 130.Op Fl adqsv 131.Xc 132The default 133.Ar device 134will be set to the disk that the boot loader was 135loaded from. 136To boot from an alternate disk, the full name of the device should 137be given at the prompt. 138.Ar device 139is of the form 140.Xo Ar xd 141.Op Ar N Ns Op Ar x 142.Xc 143where 144.Ar xd 145is the device from which to boot, 146.Ar N 147is the unit number, and 148.Ar x 149is the partition letter. 150.Pp 151The following list of supported devices may vary from installation to 152installation: 153.Pp 154.Bl -hang -compact 155.It sd 156SCSI disks on a controller recognized by the IOCS. The 157unit number is the SCSI ID. 158.It fd 159Floppy drives as numbered by the IOCS. 160.El 161.Pp 162The default 163.Ar filename 164is 165.Pa netbsd ; 166if the boot loader fails to successfully 167open that image, it then tries 168.Pa netbsd.gz 169(expected to be a kernel image compressed by 170.Xr gzip 1 ) . 171Alternate system images can be loaded by just specifying the name of the image. 172.Pp 173Options are: 174.Bl -tag -width xxx 175.It Fl a 176Prompt for the location of the root file system and the system crash 177dump device. 178.It Fl d 179Bring the system up in debug mode. Here it waits for a kernel 180debugger connect; see 181.Xr ddb 4 . 182.It Fl q 183Boot the system in quiet mode. 184.It Fl s 185Bring the system up in single-user mode. 186.It Fl v 187Boot the system in verbose mode. 188.El 189.It Ic help 190Print an overview about commands and arguments. 191.It Ic ls Op Pa path 192Print a directory listing of 193.Pa path , 194containing inode number, filename and file type. 195.Pa path 196can contain a device specification. 197.It Ic halt 198Reboot the system. 199.El 200.Ss Model-specific notes 201Note for X68030+MC68030 systems: 202Nothing special to be attended to; you can boot 203.Nx 204just like as 205other operating systems such as Human68k and OS-9. 206.Pp 207Note for X68030/040turbo(68040 accelerator by BEEPs) systems: 208.Nx 209can boot under 040 mode. 210It can also boot under 030 mode if you have MC68030 on the board. 211.Pp 212Note for X68000/Xellent30(68030 accelerator by TSR)+MC68030 systems: 213In order to boot 214.Nx , 215you must choose 030 mode by using 216.Pa CH30.SYS , 217which must reside in the battery-backuped SRAM. 218.Pp 219Note for X68000/Jupiter-X(68040/060 accelerator by FTZ-net) systems: 220The system must be in 040/060 processor mode. 221.Sh FILES 222.Bl -tag -width /usr/mdec/xxboot_ufs -compact 223.It Pa /netbsd 224system code 225.It Pa /netbsd.gz 226gzip-compressed system code 227.It Pa /usr/mdec/xxboot_ufs 228boot block (read by installboot), xx is disktype 229.It Pa /usr/mdec/boot 230source of /boot (can be just copied to the root directory) 231.It Pa /boot 232main part of the boot program 233.El 234.Sh SEE ALSO 235.Xr reboot 2 , 236.Xr disklabel 8 , 237.Xr halt 8 , 238.Xr reboot 8 , 239.Xr shutdown 8 240.\" installboot(8) must be written 241