Subject: Typo and update to setup documentation Index: /usr/doc/2.10/setup.2.11 2.11BSD Description: There was a typo in chapter 3 of the setup documentation. /boot now uses information passed by either the block zero code or the kernel in determining the device to load the system image from. The documentation was changed to reflect this. Repeat-By: Examine the documents. Fix: Apply the patches below. *** /usr/doc/2.10/setup.2.11/3.t.old Sat Dec 8 18:38:07 1990 --- /usr/doc/2.10/setup.2.11/3.t Tue May 28 16:09:47 1991 *************** *** 309,315 **** It includes the terminal type and security options that were previously in /etc/ttytype and /etc/securettys. .PP ! \fIsyslog\fP is the same as it ws under \(*Ps. See \fIsyslogd\fP\|(8) for details. It is used by many of the system daemons to monitor system problems more closely, for example --- 309,315 ---- It includes the terminal type and security options that were previously in /etc/ttytype and /etc/securettys. .PP ! \fIsyslog\fP is the same as it was under \*(Ps. See \fIsyslogd\fP\|(8) for details. It is used by many of the system daemons to monitor system problems more closely, for example *** /usr/doc/2.10/setup.2.11/4.t.old Mon Dec 10 14:39:18 1990 --- /usr/doc/2.10/setup.2.11/4.t Tue May 28 16:27:36 1991 *************** *** 28,48 **** .NH 2 Creating a UNIX boot .PP ! The version of \fI/boot\fP distributed with the system is set up to boot ! \fIxp(0,0)unix\fP. If you want to boot from a different file system ! easily and have auto-reboot supported, you will have to recompile the boot. ! This is done very simply as follows: ! .DS ! \fB#\fP cd /sys/pdpstand ! \fB#\fP make clean ! \fB#\fP make RB_DEFNAME="\fIdk\fP(\fIunit\fP,\fPoffset\fP)unix" boot ! \fB#\fP make install ! .DE ! Where \fIdk\fP is the two letter code for the device you want to auto-boot ! from, \fIunit\fP is the slave unit of said device, and \fIoffset\fP is the ! offset in \fI512-byte blocks\fP from the beginning of the selected disk, ! or the file number of the selected tape (note that auto-booting from tape ! is possible, but not recommended.) .NH 2 Kernel configuration .PP --- 28,40 ---- .NH 2 Creating a UNIX boot .PP ! \fI/boot\fP uses the device information passed to it from the bootstrap ! in determining the device, unit and file to load. If an autoreboot ! is being done the kernel will have passed the device information to the ! bootstrap as well as setting the autoreboot flag. ! .PP ! \fI/boot\fP does not require recompilation to adapt to a new autoreboot ! device. .NH 2 Kernel configuration .PP