From 6f055ecd96514486114bbbe0605c9489b6511ca9 Mon Sep 17 00:00:00 2001 From: Kirk McKusick Date: Sat, 27 Apr 1985 20:42:48 -0800 Subject: [PATCH] manual page distributed with 4.2BSD SCCS-vsn: sbin/reboot/boot_vax.8 5.1 --- usr/src/sbin/reboot/boot_vax.8 | 46 +++++++++++++++++++++------------- 1 file changed, 29 insertions(+), 17 deletions(-) diff --git a/usr/src/sbin/reboot/boot_vax.8 b/usr/src/sbin/reboot/boot_vax.8 index 84ea854f54..ddfd13c913 100644 --- a/usr/src/sbin/reboot/boot_vax.8 +++ b/usr/src/sbin/reboot/boot_vax.8 @@ -2,9 +2,9 @@ .\" All rights reserved. The Berkeley software License Agreement .\" specifies the terms and conditions for redistribution. .\" -.\" @(#)boot_vax.8 4.1 (Berkeley) %G% +.\" @(#)boot_vax.8 5.1 (Berkeley) %G% .\" -.TH REBOOT 8 5/10/81 +.TH REBOOT 8 5/10/83 .UC 4 .SH NAME reboot \- UNIX bootstrapping procedures @@ -39,8 +39,7 @@ Options to reboot are: .TP .B \-n option avoids the sync. It can be used if a disk or the processor -is on fire. (It is no longer necessary to reboot after rebuilding -the root file system.) +is on fire. .TP .B \-q reboots quickly and ungracefully, without shutting down running @@ -99,11 +98,9 @@ user, and a \fIn\fR of 3 causes both of these actions to occur. 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 of bootstrap programs for the various disks which should be placed -in a new pack via -.IP -cp /usr/mdec/\fIxx\fRboot /dev/\fIxx\fR?a -.PP -whenever a new bootable pack is to be created. +in a new pack automatically by +.IR newfs (8) +when the ``a'' partition file system on the pack is created. .PP On both processors, the .I boot @@ -114,11 +111,15 @@ 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 an rp06, rm05 or rm03 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 +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 ampex 9300 drive, ``rk(0,0)vmunix'' would specify -a RK-07 disk drive. +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. .PP A device specification has the following form: .IP @@ -137,18 +138,23 @@ The following list of supported devices may vary from installation to installation: .ta 5 10 .nf - hp RP06, RM03, RM05, RP07 or RM80 on MASSBUS - up storage module drive on UNIBUS + hp MASSBUS disk drive + up UNIBUS storage module drive ht TE16,TU45,TU77 on MASSBUS + mt TU78 on MASSBUS hk RK07 on UNIBUS + ra storage module on a UDA50 + rb storage module on a 730 IDC + rl RL02 on UNIBUS tm TM11 emulation tape drives on UNIBUS ts TS11 on UNIBUS + ut UNIBUS TU45 emulator .fi .PP For tapes, the minor device number gives a file offset. .PP In an emergency, the bootstrap methods described in the paper -``Setting up the Fourth Berkeley Software Tape'' can be used +``Installing and Operating 4.2bsd'' can be used to boot from a distribution tape. .SH FILES .ta \w'/usr/mdec/mboot 'u @@ -156,4 +162,10 @@ to boot from a distribution tape. .br /boot system bootstrap .SH "SEE ALSO" -crash(8), fsck(8), init(8), rc(8), shutdown(8), halt(8) +crash(8V), +fsck(8), +init(8), +rc(8), +shutdown(8), +halt(8), +newfs(8) -- 2.20.1