updates

SCCS-vsn: sbin/reboot/boot_vax.8 6.2
SCCS-vsn: libexec/rlogind/rlogind.8 6.2

diff --git a/usr/src/libexec/rlogind/rlogind.8 b/usr/src/libexec/rlogind/rlogind.8
index 60422e6..33864c2 100644 (file)
--- a/usr/src/libexec/rlogind/rlogind.8
+++ b/usr/src/libexec/rlogind/rlogind.8
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)rlogind.8   6.1 (Berkeley) %G%
+.\"    @(#)rlogind.8   6.2 (Berkeley) %G%

 .\"
 .TH RLOGIND 8C ""
 .UC 5
 .\"
 .TH RLOGIND 8C ""
 .UC 5


@@ -18,7 +18,7 @@ rlogind \- remote login server
 is the server for the 
 .IR rlogin (1C)
 program.  The server provides a remote login facility
 is the server for the 
 .IR rlogin (1C)
 program.  The server provides a remote login facility

-with authentication based on privileged port numbers.
+with authentication based on privileged port numbers from trusted hosts.

 .PP
 .I Rlogind
 listens for service requests at the port indicated in
 .PP
 .I Rlogind
 listens for service requests at the port indicated in


@@ -34,8 +34,11 @@ aborts the connection.
 The server checks the client's source address.
 If the address is associated with a host for which no
 corresponding entry exists in the host name data base (see
 The server checks the client's source address.
 If the address is associated with a host for which no
 corresponding entry exists in the host name data base (see

-.IR hosts (5)),
-the server aborts the connection.
+.IR gethostbyaddr (3N),
+.IR hosts (5)
+and
+.IR named (8)),
+the dot-notation representation of the host address is used.

 .PP
 Once the source port and address have been checked, 
 .I rlogind
 .PP
 Once the source port and address have been checked, 
 .I rlogind


@@ -70,6 +73,8 @@ interrupt signals to the remote programs.  The login process
 propagates the client terminal's baud rate and terminal type,
 as found in the environment variable, ``TERM''; see
 .IR environ (7).
 propagates the client terminal's baud rate and terminal type,
 as found in the environment variable, ``TERM''; see
 .IR environ (7).

+The screen or window size of the terminal is requested from the client,
+and window size changes from the client are propagated to the pseudo terminal.

 .SH DIAGNOSTICS
 All diagnostic messages are returned on the connection
 associated with the
 .SH DIAGNOSTICS
 All diagnostic messages are returned on the connection
 associated with the


@@ -77,11 +82,6 @@ associated with the
 after which any network connections are closed.
 An error is indicated by a leading byte with a value of 1.
 .PP
 after which any network connections are closed.
 An error is indicated by a leading byte with a value of 1.
 .PP

-.B ``Hostname for your address unknown.''
-.br
-No entry in the host name database existed for
-the client's machine.
-.PP

 .B ``Try again.''
 .br
 A
 .B ``Try again.''
 .br
 A

diff --git a/usr/src/sbin/reboot/boot_vax.8 b/usr/src/sbin/reboot/boot_vax.8
index 4e48a91..5e57cde 100644 (file)
--- a/usr/src/sbin/reboot/boot_vax.8
+++ b/usr/src/sbin/reboot/boot_vax.8
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)boot_vax.8  6.1 (Berkeley) %G%
+.\"    @(#)boot_vax.8  6.2 (Berkeley) %G%

 .\"
 .TH REBOOT 8 ""
 .UC 4
 .\"
 .TH REBOOT 8 ""
 .UC 4


@@ -18,7 +18,7 @@ reboot \- UNIX bootstrapping procedures
 .SH DESCRIPTION
 .PP
 UNIX is started by placing it in memory
 .SH DESCRIPTION
 .PP
 UNIX is started by placing it in memory

-at location zero and transferring to zero.
+at location zero and transferring to the entry point.

 Since the system is not reenterable,
 it is necessary to read it in from disk or tape
 each time it is to be bootstrapped.
 Since the system is not reenterable,
 it is necessary to read it in from disk or tape
 each time it is to be bootstrapped.


@@ -48,8 +48,8 @@ processes first.
 .B "Power fail and crash recovery."
 Normally, the system will reboot itself at power-up or after crashes.
 Provided the auto-restart is enabled on the machine front panel,
 .B "Power fail and crash recovery."
 Normally, the system will reboot itself at power-up or after crashes.
 Provided the auto-restart is enabled on the machine front panel,

-an automatic consistency check of the file systems will be performed
-then and unless this fails the system will resume multi-user operations.
+an automatic consistency check of the file systems will be performed,
+and unless this fails, the system will resume multi-user operations.

 .PP
 .B Cold starts.
 These are processor type dependent.
 .PP
 .B Cold starts.
 These are processor type dependent.


@@ -62,6 +62,11 @@ and multi-user boot from MASSBUS RP06/RM03/RM05 disks,
 UPS and UPM for UNIBUS storage module controller and disks
 such as the EMULEX SC-21
 and AMPEX 9300 pair, or HKS and HKM for RK07 disks.
 UPS and UPM for UNIBUS storage module controller and disks
 such as the EMULEX SC-21
 and AMPEX 9300 pair, or HKS and HKM for RK07 disks.

+There is also a script for booting from the default device,
+which is normally a copy of one of the standard multi-user boot scripts,
+but which may be modified to perform other actions
+or to boot from a different unit.
+The situation on the 8600 is similar, with scripts loaded from the console RL02.

 .PP
 Giving the command
 .IP
 .PP
 Giving the command
 .IP


@@ -72,6 +77,7 @@ check as described in
 .IR fsck (8).
 (Note that it may
 be necessary to type control-P
 .IR fsck (8).
 (Note that it may
 be necessary to type control-P

+and halt the processor

 to gain the attention of the LSI-11 before getting the >>> prompt.)
 The command
 .IP
 to gain the attention of the LSI-11 before getting the >>> prompt.)
 The command
 .IP


@@ -82,6 +88,15 @@ specify any system as the system to be booted.
 It reads from the console a device specification (see below) followed
 immediately by a pathname.
 .PP
 It reads from the console a device specification (see below) followed
 immediately by a pathname.
 .PP

+The scripts may be modified for local configuration if necessary.
+The boot device type is set in register 10 as the device major number.
+The flags and minor device are placed in register 11.
+The register is used in four one-byte fields; from least to most significant,
+they are boot flags (as defined in
+.IR <sys/reboot.h> ),
+disk partition, drive unit, and adaptor number (UNIBUS or MASSBUS as
+appropriate).
+.PP

 On an 11/750, the reset button will boot from the device
 selected by the front panel boot device switch.  In systems
 with RK07's, position B normally selects the RK07 for boot.
 On an 11/750, the reset button will boot from the device
 selected by the front panel boot device switch.  In systems
 with RK07's, position B normally selects the RK07 for boot.


@@ -94,6 +109,12 @@ where, giving a \fIn\fR of 1 causes the boot program
 to ask for the name of the system to be bootstrapped,
 giving a \fIn\fR of 2 causes the boot program to come up single
 user, and a \fIn\fR of 3 causes both of these actions to occur.
 to ask for the name of the system to be bootstrapped,
 giving a \fIn\fR of 2 causes the boot program to come up single
 user, and a \fIn\fR of 3 causes both of these actions to occur.

+The ``DM'' specifies RK07, the ``A'' represents the adaptor number (UNIBUS
+or MASSBUS), and the ``0'' is the drive unit number.
+Other disk types which may be used are DB (MASSBUS), DD (TU58),
+and DU (UDA-50/RA disk).
+A non-zero disk partition can be used by adding (partition times 1000 hex)
+to \fIn\fR.

 .PP
 The 11/750 boot procedure uses the boot roms to load block 0 off of
 the specified device.  The /usr/mdec directory contains a number
 .PP
 The 11/750 boot procedure uses the boot roms to load block 0 off of
 the specified device.  The /usr/mdec directory contains a number


@@ -102,38 +123,31 @@ in a new pack automatically by
 .IR newfs (8)
 when the ``a'' partition file system on the pack is created.
 .PP
 .IR newfs (8)
 when the ``a'' partition file system on the pack is created.
 .PP

-On both processors, the 
+On any processor, the 

 .I boot
 program
 .I boot
 program

-finds the corresponding file on the given device, loads that file
+finds the corresponding file on the given device 
+.RI ( vmunix
+by default), loads that file

 into memory location zero, and starts the program at the entry address
 specified in the program header (after clearing off the high bit
 into memory location zero, and starts the program at the entry address
 specified in the program header (after clearing off the high bit

-of the specified entry address.)
-Normal line editing characters can be used in specifying the pathname.
-.PP
-If you have a MASSBUS disk
-and wish to boot off of a file
-system which starts at cylinder 0
-of unit 0, you can type \*(lqhp(0,0)vmunix\*(rq
-to the boot prompt; \*(lqup(0,0)vmunix\*(rq would specify
-a UNIBUS drive, ``hk(0,0)vmunix'' would specify
-an RK07 disk drive, ``ra(0,0)vmunix'' would specify a
-UDA50 disk drive, and ``rb(0,0)vmunix'' would specify a
-disk on a 730 IDC.
+of the specified entry address).

 .PP
 .PP

-A device specification has the following form:
+The file specifications used with \*(lqBOOT ANY\*(rq or \*(lqB/3\*(rq
+are of the form:

 .IP
 .IP

-device(unit, minor)
+device(unit,minor)

 .PP
 where
 .I device
 is the type of the device to be searched,
 .I unit
 .PP
 where
 .I device
 is the type of the device to be searched,
 .I unit

-is 8* the mba or uba number plus
-the unit number of the device,
+is 8 * the mba or uba number plus
+the unit number of the disk or tape,

 and
 .I minor
 and
 .I minor

-is the minor device index.
+is the disk partition or tape file number.
+Normal line editing characters can be used when typing the file specification.

 The following list of supported devices may vary from installation to
 installation:
 .ta 5 10
 The following list of supported devices may vary from installation to
 installation:
 .ta 5 10


@@ -151,21 +165,36 @@ installation:
        ut      UNIBUS TU45 emulator
 .fi
 .PP
        ut      UNIBUS TU45 emulator
 .fi
 .PP

+For example,
+to boot from a file system which starts at cylinder 0
+of unit 0 of a MASSBUS disk, type \*(lqhp(0,0)vmunix\*(rq
+to the boot prompt; \*(lqup(0,0)vmunix\*(rq would specify
+a UNIBUS drive, \*(lqhk(0,0)vmunix\*(rq would specify
+an RK07 disk drive, \*(lqra(0,0)vmunix\*(rq would specify a
+UDA50 disk drive, and \*(lqrb(0,0)vmunix\*(rq would specify a
+disk on a 730 IDC.

 For tapes, the minor device number gives a file offset.
 .PP
 In an emergency, the bootstrap methods described in the paper
 For tapes, the minor device number gives a file offset.
 .PP
 In an emergency, the bootstrap methods described in the paper

-``Installing and Operating 4.2bsd'' can be used
+``Installing and Operating 4.3bsd'' can be used

 to boot from a distribution tape.
 .SH FILES
 to boot from a distribution tape.
 .SH FILES

-.ta \w'/usr/mdec/mboot   'u
+.ta \w'/usr/mdec/installboot   'u

 /vmunix        system code
 .br
 /boot  system bootstrap
 /vmunix        system code
 .br
 /boot  system bootstrap

+.br
+/usr/mdec/xxboot       sector-0 boot block for 750, xx is disk type
+.br
+/usr/mdec/bootxx       second-stage boot for 750, xx is disk type
+.br
+/usr/mdec/installboot  program to install boot blocks on 750

 .SH "SEE ALSO"
 .SH "SEE ALSO"

+arff(8V),

 crash(8V),
 fsck(8),
 crash(8V),
 fsck(8),

+halt(8),

 init(8),
 init(8),

+newfs(8),

 rc(8),
 rc(8),

-shutdown(8),
-halt(8),
-newfs(8)
+shutdown(8)