9boot(8) update
This commit is contained in:
cinap_lenrek
parent
c5bcd17a58
commit
69f33ad54d
113
sys/man/8/9boot
113
sys/man/8/9boot
|
|
@ -1,76 +1,78 @@
|
||||||
.TH 9BOOT 8
|
.TH 9BOOT 8
|
||||||
.SH NAME
|
.SH NAME
|
||||||
9bootfat, 9bootiso, 9bootpxe \- bootloaders for pc FAT, ISO and PXE network booting
|
9bootfat, 9bootiso, 9bootpxe \- PC bootloader for FAT, ISO and PXE network booting
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
started by BIOS or chainloaded by partition bootsector
|
started by PC BIOS or chainloaded by partition bootsector
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
The bootloader is responsible for reading the
|
9boot is the bootloader used on PCs to start the Plan 9 kernel.
|
||||||
|
Its task is to read and parse the
|
||||||
.IR plan9.ini (8)
|
.IR plan9.ini (8)
|
||||||
boot parameters and booting a kernel. It interprets the
|
configuration file, gather some basic system information like
|
||||||
|
the amount of usable system memory, do some low level system
|
||||||
|
initialization and load the kernel from the boot media into memory.
|
||||||
|
|
||||||
|
After reading the configuration, the loader will automatically
|
||||||
|
attempt to boot the kernel that was specified by the
|
||||||
.B bootfile=
|
.B bootfile=
|
||||||
parameter as a file path on the current boot media
|
parameter. If there is no such parameter, a key
|
||||||
to locate the kernel image. The path should be in all
|
gets pressed on the keyboard or the kernel file was not
|
||||||
lower case except for
|
found then the loader enters the interactive
|
||||||
.IR 9bootpxe
|
boot console.
|
||||||
wich supports case sensitive file names. Read parameters
|
|
||||||
are echoed on the console. The boot procedure
|
The syntax of the boot console is the same as in
|
||||||
can be interrupted by pressing any key after the configuration
|
|
||||||
was read. The interactive boot console is indicated with a
|
|
||||||
.B >
|
|
||||||
prompt. The syntax of the boot console is the same as in
|
|
||||||
the
|
the
|
||||||
.IR plan9.ini (8)
|
.IR plan9.ini (8)
|
||||||
file. The word
|
file.
|
||||||
.B clear
|
.BR
|
||||||
will reset all current parameters. The word
|
The word
|
||||||
|
.B clear [
|
||||||
|
.I prefix
|
||||||
|
]
|
||||||
|
can be used to remove parameters from the current configuration.
|
||||||
|
If a
|
||||||
|
.IR prefix
|
||||||
|
is specified, the first parameter that matches the prefix
|
||||||
|
is removed. If the
|
||||||
|
.IR prefix
|
||||||
|
argument is omited, the whole configuration will be reset.
|
||||||
|
.BR
|
||||||
|
The word
|
||||||
.B boot
|
.B boot
|
||||||
will end the console and resume booting the kernel. The boot
|
will end the console and resume booting the kernel.
|
||||||
console is entered automatically when: boot failed, no
|
|
||||||
.B bootfile=
|
There are many ways to boot a PC so
|
||||||
parameter was specified or no
|
.IR 9boot
|
||||||
.IR plan9.ini (8)
|
was split into a number of distinct programs one for each boot
|
||||||
was found.
|
method.
|
||||||
.SH FAT BOOTING
|
.SH FAT BOOTING
|
||||||
The
|
When booting Plan 9 from a harddisk or USB pen drive, a
|
||||||
.IR 9bootfat
|
FAT16/32 partition (
|
||||||
program is responsible for loading the kernel from
|
|
||||||
the
|
|
||||||
.IR 9fat
|
.IR 9fat
|
||||||
partition into memory and passing it the
|
) is used to store the kernel and
|
||||||
.IR plan9.ini (8)
|
.IR plan9.ini (8)
|
||||||
boot parameters. It is chainloaded by
|
configuration. Due to size limitations, instead of loading
|
||||||
.IR pbs,
|
the kernel directly, the bootsector (
|
||||||
wich locates it in the root of the active
|
.IR pbs
|
||||||
FAT partition. The
|
) of the FAT partition loads
|
||||||
.IR plan9.ini (8)
|
a 2nd stage bootloader
|
||||||
file is read from the root directory of the FAT
|
.IR 9bootfat
|
||||||
filesystem.
|
from the root directory of the filesystem.
|
||||||
.SH CD-ROM BOOTING
|
.SH CD-ROM BOOTING
|
||||||
Booting from CD-ROM requires
|
Booting from CD-ROM requires only
|
||||||
.IR 9bootiso
|
.IR 9bootiso
|
||||||
to be included in the ISO-9660 image under
|
to be included in the ISO-9660 image under
|
||||||
.B 386/9bootiso,
|
.B 386/9bootiso,
|
||||||
set as a non emulation bootblock (see
|
set as a non emulation bootblock (see
|
||||||
.IR mk9660 (8)).
|
.IR mk9660 (8)).
|
||||||
The BIOS loads the first 2K of
|
|
||||||
.B 386/9bootiso
|
|
||||||
into memory and then executes the program. The remainder
|
|
||||||
of the file is then read to complete the chainloading process.
|
|
||||||
Boot parameters are read from
|
Boot parameters are read from
|
||||||
.B cfg/plan9.ini.
|
.B cfg/plan9.ini.
|
||||||
.SH NETWORK BOOTING
|
.SH NETWORK BOOTING
|
||||||
With a PXE capable BIOS and network card it is possible for
|
With a PXE capable BIOS and network card one can download
|
||||||
a machine to download
|
|
||||||
.IR 9bootpxe
|
.IR 9bootpxe
|
||||||
and a kernel from a tftp server. The location of
|
and boot the kernel from a TFTP server (see
|
||||||
.IR 9bootpxe
|
.IR dhcpd (8),
|
||||||
is defined by the
|
|
||||||
.B bootf=/386/9bootpxe
|
|
||||||
line in the tftp server's
|
|
||||||
.IR ndb (6)
|
.IR ndb (6)
|
||||||
entry.
|
for details). Once started,
|
||||||
.BR
|
|
||||||
Once started,
|
|
||||||
.IR 9bootpxe
|
.IR 9bootpxe
|
||||||
will read the file
|
will read the file
|
||||||
.B /cfg/pxe/$ether
|
.B /cfg/pxe/$ether
|
||||||
|
|
@ -82,3 +84,14 @@ in lower case hex, and use this as its
|
||||||
file.
|
file.
|
||||||
.SH SOURCE
|
.SH SOURCE
|
||||||
.BR /sys/src/boot/pc .
|
.BR /sys/src/boot/pc .
|
||||||
|
.SH FILES
|
||||||
|
.TP
|
||||||
|
.B /386/pbs
|
||||||
|
.TP
|
||||||
|
.B /386/9bootfat
|
||||||
|
.TP
|
||||||
|
.B /386/9bootiso
|
||||||
|
.TP
|
||||||
|
.B /386/9bootpxe
|
||||||
|
.SH "SEE ALSO"
|
||||||
|
.IR plan9.ini (8)
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue