MirOS Manual: installboot(8)

INSTALLBOOT(8)       BSD System Manager's Manual (SPARC)        INSTALLBOOT(8)

NAME

     installboot - install a bootstrap on an FFS filesystem partition

SYNOPSIS

     installboot [-nvh] [-a karch] boot bootxx device

     installboot [-nvh] [-a karch] -s isofsblk -e isofseblk dummy bootxx
                 device

DESCRIPTION

     installboot prepares an FFS or CD9660 filesystem 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 (and hence is limited in size to SBSIZE - DEV_BSIZE bytes), and
     a second-stage program that resides in the filesystem proper. The first-
     stage program is loaded into memory by the PROM. After it receives con-
     trol, it loads the second stage program from a set of filesystem block
     numbers that have been hard-coded into it by the installboot program. The
     second-stage boot program uses the device driver interface to the PROM
     and the stand-alone filesystem code in "libsa.a" to locate and load the
     kernel. The second-stage boot program and the prototype code for the
     first-stage bootprogram can be found in /usr/mdec/boot and
     /usr/mdec/bootxx respectively. The second-stage program commonly resides
     in the root directory as /boot.

     The options are as follows:

     -a karch
           Set the machine architecture. The argument karch can be one of
           "sun4", "sun4c" or "sun4m". Sun 4c models with Openboot PROMs need
           the header to be present, while Sun 4 systems with the "old
           monitor" interface require the header to be stripped off. This is
           normally taken care of by installboot automatically, but it's use-
           ful when preparing a bootable filesystem for another system.

     -h    Leave the a.out(5) header on the installed bootxx program. This op-
           tion has been superseded by the -a karch option.

     -n    Do not actually write anything on the disk.

     -s isofsblk -e isofseblk
           Ignore the boot (dummy) argument and use the isofsblk and isofseblk
           CD9660 block numbers for locating the second-stage boot loader.

     -v    Verbose mode.

     The arguments are:

     boot    the name of the second-stage boot program in the file system
             where the first-stage boot program is to be installed. Ignored if
             -s is used.

     bootxx  the name of the prototype file for the first stage boot program.

     device  the name of the raw device in which the first-stage boot program
             is to be installed. This should correspond to the block device on
             which the file system containing boot is mounted.

EXAMPLES

     The following command will install the first-stage bootblocks in the root
     filesystem (assumed to be mounted on "sd0a") using the file /boot as the
     second-level boot program:

           installboot /boot /usr/mdec/bootxx /dev/rsd0a

SEE ALSO

     disklabel(8), init(8)

HISTORY

     The installboot first appeared in NetBSD 1.1.

BUGS

     installboot requires simultaneous access to the mounted file system and
     the raw device, but that is not allowed with the kernel securelevel vari-
     able set to a value greater than zero (the default), so installboot only
     works in single-user mode (or insecure mode - see init(8)).

MirOS BSD #10-current          August 17, 2006                               1

Generated on 2013-09-18 04:33:42 by $MirOS: src/scripts/roff2htm,v 1.77 2013/01/01 20:49:09 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002‒2013 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.