ip/ipconfig: make ra6 daemon less chatty, log to /sys/log/ipconfig instead of /sys...

[plan9front.git] / sys / man / 8 / boot

diff --git a/sys/man/8/boot b/sys/man/8/boot
index eb995e397212e1951a9e5cc898f77221eeb9b8b4..fbdf3be81911eb52a9e37a42c2bf466ddecdbb1b 100644 (file)
--- a/sys/man/8/boot
+++ b/sys/man/8/boot
@@ -3,29 +3,17 @@
 boot, bootrc \- connect to the root file server
 .SH SYNOPSIS
 .B /boot/boot
-[
-.B -fkm
-]
-[
-.BI -u username
-]
-[
-.IB method ! fs-addr
-]
-[
-.I args
-]
 .SH DESCRIPTION
 .I Boot
 is the first program run after a kernel has been loaded. It
 mounts
-.B bootfs.paq,
+.BR bootfs.paq ,
 a compressed filesystem contained in
 .IR root (3),
 sets up the
 .IR rc (1)
 environment and executes
-.I /boot/bootrc
+.I bootrc
 passing on its arguments.
 .I Bootrc
 connects to the file server that will serve the root, performs any 
@@ -71,23 +59,17 @@ of the form
 .IB name = value
 is passed to the boot program as an environment
 variable with the same name and value.
-The command line is
-.IP
-.B /boot/boot
-.IB method ! server
 .PP
 After
 .I boot
 passed its execution to
 .I bootrc,
-it must determine the file
-.I server
-to use
-and a
+it must determine the fileserver to use and a
 .I method
 with which to connect to it.
-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.
+Typically
+.I device
+will name a local disk partition or ethernet interface.
 The complete list of methods is given below.
 .PP
 .I Bootrc
@@ -98,11 +80,11 @@ when challenged.
 .I Bootrc
 will prompt for these.
 .PP
-Method and address are prompted for first.
+Method and device are prompted for first.
 The prompt lists all valid methods, with the default in brackets, for example:
 .IP
 .EX
-bootargs is (tcp, local!device) [local!/dev/sdC0/fscache]
+bootargs is (tcp, il, local!device) [local!/dev/sdC0/fscache]
 .EE
 .PP
 A newline picks the default. Entering
@@ -111,9 +93,11 @@ breaks into the
 .IR rc (1)
 shell.
 Other possible responses are
-.I method
+.IR method ,
+.IB method ! device
 or
-.IB method ! address\f1.
+.IB method ! device
+.IR args .
 .PP
 The other interactions depend on whether the system
 is a
@@ -122,9 +106,10 @@ terminal or a CPU server.
 A terminal must have a
 .I username
 set.
-If none is specified with the
-.B -u
-option,
+If not specified with the
+.B user=
+.IR plan9.ini (8)
+parameter,
 .I boot
 will prompt for one on the console:
 .IP
@@ -154,7 +139,7 @@ for subsequent processes to
 .I Boot
 completes by 
 .IR exec (2)'ing
-.B /$objtype/init
+.B /$cputype/init
 .BR -t .
 If the
 .B -m
@@ -183,22 +168,12 @@ then
 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
-.B -f
-flag commands
-.IR cfs (4)
-to reformat the cache partition.
 .SS CPU Servers
 The user owning devices and console processes on CPU servers
 and that user's domain and encryption key are
 read from NVRAM on all machines except PCs.
 PCs keep the information in the disk partition
 .BI /dev/sd XX /nvram.
-If a
-.B -k
-option is given or if no stored information is found
-.I boot
-will prompt for all three items and store them.
 .IP
 .EX
 password: 
@@ -213,7 +188,7 @@ Once connected,
 .I boot
 behaves as on the terminal except for
 .IR exec (2)'ing
-.B /$objtype/init
+.B /$cputype/init
 .BR -c .
 .SS Booting Methods
 The methods available to any system depend on what was
@@ -223,6 +198,8 @@ The complete list of booting methods are listed below.
 .BR tcp
 connect via Ethernet using the TCP protocol.
 The
+.I device
+and
 .I args
 are passed to
 .IR ipconfig (8)
@@ -233,30 +210,27 @@ variables
 .B fs
 and
 .BR auth
-override the file server and authentication server IP addresses
+override the file server and authentication servers
 obtained (if any) from DHCP during
 .IR ipconfig (8).
 .TP 8
-.B local
+.BR il
+the same as
+.B tcp
+but uses the IL protocol to connect to the fileserver.
+.TP 8
+.BR local
 connect to the local file system.
-The first argument is a disk holding a file system.
-.I Boot
-inspects the disk.
-.I Boot
-will configure the IP stack by passing
-.IR args ,
-if any, to
-.IR ipconfig (8).
+The 
+.I device
+is a disk partition file holding a file system.
+.I Bootrc
+inspects the disk partition with
+.IR fstype (1)
+to determine the file system type and starts the
+appropriate server with
+.IR args .
 .RE
-.PP
-For the
-.B tcp
-method,
-the address must be a numeric IP address.
-If no address is specified,
-a file server address will be found from another
-system on the network using the BOOTP protocol and
-the Plan 9 vendor-specific fields.
 .SH EXAMPLES
 On PCs, the default arguments to boot are constructed using
 the 
@@ -302,3 +276,9 @@ line is split only for presentation; it is one line in the file.)
 The use of
 .B bootargs
 in general is odd.
+.SH HISTORY
+.I Boot
+first appeared in Plan 9 from Bell Labs. It was rewritten
+in
+.I rc
+for 9front (April, 2011).