boot(8) manpage

sys/man/8/boot

@@ -1,6 +1,6 @@
 .TH BOOT 8
 .SH NAME
-boot \- connect to the root file server
+boot, bootrc \- connect to the root file server
 .SH SYNOPSIS
 .B /boot/boot
 [
@@ -17,8 +17,15 @@ boot \- connect to the root file server
 ]
 .SH DESCRIPTION
 .I Boot
-is the first program run after a kernel has been loaded.
-It connects to the file server that will serve the
+is the first program run after a kernel has been loaded. It
+mounts
+.B bootfs.paq,
+a compressed filesystem contained in
+.IR root (3),
+setups the rc enviroment and execs
+.I bootrc
+passing on its arguments.
+.I Bootrc connects to the file server that will serve the
 root, performs any authentication needed to
 connect to that server, and
 .IR exec (2)'s
@@ -62,13 +69,14 @@ is passed to the boot program as an environment
 variable with the same name and value.
 The command line is
 .IP
-.B /386/9dos
+.B /boot/boot
 .IB method ! server
 .PP
-(The first argument is ignored by
-.IR boot .)
-.I Boot
-must determine the file
+After
+.I boot
+passed its execution to
+.I bootrc,
+it must determine the file
 .I server
 to use
 and a
@@ -78,12 +86,12 @@ Typically this will name a file server on the network,
 or state that the root file system is on local disk and name the partition.
 The complete list of methods is given below.
 .PP
-.I Boot
+.I Bootrc
 must also set a user name to be used
 as the owner of devices and all console
 processes and an encryption key to be used
 when challenged.
-.I Boot
+.I Bootrc
 will prompt for these.
 .PP
 Method and address are prompted for first.
@@ -93,13 +101,15 @@ The prompt lists all valid methods, with the default in brackets, for example:
 bootargs is (tcp, local!device)[/dev/sdC0/fscache]:
 .EE
 .PP
-A newline picks the default.
+A newline picks the default. Entering
+.B !rc
+breaks into the
+.IR rc(1)
+shell.
 Other possible responses are
 .I method
 or
 .IB method ! address\f1.
-To aid in automatic reboot, the default is automatically
-taken on CPU servers if nothing is typed within 15 seconds.
 .PP
 The other interactions depend on whether the system
 is a
@@ -126,37 +136,6 @@ be used as an encryption key on each
 password: 
 .EE
 .PP
-With most
-.I methods
-.I boot
-can now connect to the file server.
-However, with the serial line
-.I methods
-.B 9600
-and
-.BR 19200 ,
-the actual mechanics of setting up the complete connection
-are too varied to put into the boot program.
-Instead
-.I boot
-lets the user set up the connection.
-It prints a prompt on the console and then simulates
-a dumb terminal between the user and the serial line:
-.IP
-.EX
-Connect to file system now, type ctrl-d when done.
-(Use the view or down arrow key to send a break)
-.EE
-.PP
-The user can now type at the modem to
-dial the number.  What is typed depends on
-the modem and is beyond this discussion.
-.PP
-When the user types a control-D,
-.I boot
-stops simulating a terminal and starts the file
-system protocol over the serial line.
-.PP
 Once connected,
 .I boot
 mounts
@@ -183,7 +162,9 @@ is set (via
 .IR plan9.ini (8)),
 it is used as a command line to exec instead.
 .PP
-If the kernel has been built with the cache file system,
+If the
+.I bootfs.paq
+has been built with the cache file system,
 .IR cfs (4),
 the local disk partition
 .BI /dev/sd XX /cache
@@ -191,7 +172,9 @@ the local disk partition
 .B XX
 is a unit specifier)
 exists, and the root file system is from a remote server,
-then the kernel will insert a user level cache
+then
+.I bootrc
+will insert a user level cache
 process between the remote server and the local namespace
 that caches all remote accesses on the local partition.
 The
@@ -301,6 +284,8 @@ line is split only for presentation; it is one line in the file.)
 .B #s/boot
 .br
 .B #//boot/boot
+.br
+.B #//boot/bootfs.paq
 .SH SOURCE
 .B /sys/src/9/boot
 .SH "SEE ALSO"