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