filesystem -> file system; add `.' at end of HISTORY section; sort sections;

don't use Pc/Po/Pq; drop Nm arguments in most places (because they're not
needed); update Dd for mrg's changes today.
This commit is contained in:
wiz 2001-11-24 07:40:22 +00:00
parent 26b511b905
commit 1ea75497ea
1 changed files with 47 additions and 49 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: installboot.8,v 1.11 2001/11/24 01:52:02 mrg Exp $
.\" $NetBSD: installboot.8,v 1.12 2001/11/24 07:40:22 wiz Exp $
.\"
.\" Copyright (c) 1996 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -34,12 +34,12 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd September 29, 1995
.Dd November 24, 2001
.Dt INSTALLBOOT 8 sparc
.Os
.Sh NAME
.Nm installboot
.Nd install a bootstrap on an FFS filesystem partition
.Nd install a bootstrap on an FFS file system partition
.Sh SYNOPSIS
.Nm installboot
.Op Fl U
@ -53,24 +53,22 @@
.Ar bootblk
.Ar device
.Sh DESCRIPTION
.Nm installboot
prepares a FFS filesystem partition for boot-strapping from the PROM.
.Nm
prepares a FFS file system partition for boot-strapping from the PROM.
The sparc bootblocks are split into two parts: a small first-stage program that
is written into the superblock area in a partition
.Po
and hence is limited in size to SBSIZE - DEV_BSIZE bytes
.Pc ,
and a second-stage program that resides in the filesystem proper.
(and hence is limited in size to SBSIZE - DEV_BSIZE bytes),
and a second-stage program that resides in the file system proper.
.Pp
The first-stage program is loaded into memory by the PROM. After it receiving
control, it loads the second stage program from a set of filesystem block
control, it loads the second stage program from a set of file system block
numbers that have been hard-coded into it by the
.Nm installboot
.Nm
program, or, on the UltraSPARC, finds the second stage boot program by a
name lookup in the filesystem.
name lookup in the file system.
.Pp
The second-stage boot program uses the device driver interface to
the PROM and the stand-alone filesystem code in
the PROM and the stand-alone file system code in
.Dq libsa.a
to locate and load the kernel.
For non-UltraSPARC machines,
@ -111,9 +109,7 @@ takes care of this by constructing an artificial a.out header which has
enough of the magic numbers in it to appease
.Tn Openboot
ROMs, while simultaneously consisting of instructions
.Po
in fact, just a branch past the rest of the header
.Pc
(in fact, just a branch past the rest of the header)
for Sun 4
.Dq old monitor
ROMs to execute. On the UltraSPARC machines, the first stage loader
@ -158,38 +154,6 @@ the name of the first stage boot program.
the name of the raw device in which the first-stage boot program
is to be installed.
.El
.Sh EXAMPLES
The following command will install the first-stage bootblocks in the
root filesystem of a SPARC
.Pq assumed to be mounted on Dq sd0a
using the file
.Pa /boot
as the second-level boot program:
.Bd -literal -offset indent
/usr/mdec/installboot /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Pp
The following command will perform the same, but for an UltraSPARC machine.
.Bd -literal -offset indent
/usr/mdec/installboot /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Pp
The following command will install the first-stage bootblocks for a
SPARC machine, whether run on a SPARC or UltraSPARC machine
.Bd -literal -offset indent
/usr/mdec/installboot -U /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Sh BUGS
.Nm
requires simultaneous access to the mounted file system and
the raw device, but that is not allowed with the kernel
.Dv securelevel
variable set to a value greater than zero
.Pq the default ,
so
.Nm installboot
only works in single-user mode
.Pq or insecure mode - see Xr init 8 .
.Sh FILES
.Bl -tag -width /usr/mdec/installboot -compact
.It Pa /usr/mdec/installboot
@ -207,6 +171,28 @@ UltraSPARC second-stage boot block
.It Pa /usr/mdec/ofwboot.net
UltraSPARC second-stage network boot block
.El
.Sh EXAMPLES
The following command will install the first-stage bootblocks in the
root file system of a SPARC
(assumed to be mounted on
.Dq sd0a )
using the file
.Pa /boot
as the second-level boot program:
.Bd -literal -offset indent
/usr/mdec/installboot /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Pp
The following command will perform the same, but for an UltraSPARC machine.
.Bd -literal -offset indent
/usr/mdec/installboot /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Pp
The following command will install the first-stage bootblocks for a
SPARC machine, whether run on a SPARC or UltraSPARC machine
.Bd -literal -offset indent
/usr/mdec/installboot -U /boot /usr/mdec/bootxx /dev/rsd0a
.Ed
.Sh SEE ALSO
.Xr disklabel 8 ,
.Xr init 8
@ -214,4 +200,16 @@ UltraSPARC second-stage network boot block
The
.Nm
first appeared in
.Nx 1.1
.Nx 1.1 .
.Sh BUGS
.Nm
requires simultaneous access to the mounted file system and
the raw device, but that is not allowed with the kernel
.Dv securelevel
variable set to a value greater than zero
(the default),
so
.Nm
only works in single-user mode
(or insecure mode - see
.Xr init 8 ) .