.\" sdisklabel - Write secondary SRM bootloader to harddisk
.TH swriteboot 8 "17 January 1995" "David Mosberger" ""
swriteboot \- Write secondary SRM bootloader to harddisk.
\fBswriteboot\fP [-v] [-f#] <dev> <bootloader> [kernel]
\fBswriteboot\fP can be used to write a secondary bootstrap loader
and - optionally - a kernel to
a harddisk. The loader is written in a way that allows the SRM
firmware to boot from that disk (SRM is the firmware that is also used
to boot DEC Unix and OpenVMS). Specifically, the loader is written to
a physically contiguous range of sectors starting at sector 2 and the
first sector is updated such that the SRM firmware can find the boot
loader. \fBswriteboot\fP may fail if the bootstrap loader is too big
to fit into the sectors reserved for boot purposes. It is therefore
suggested to reserve the first 512 sectors of a harddisk for boot
purposes. This will leave 256KB of space for a secondary bootstrap
loader which should be plenty (currently, the \fBaboot\fP bootstrap
loader is about 80KB large). Use more if you want to have a kernel in this
area, too - 2MB should be sufficient in this case.
The \fI<dev>\fP argument specifies the special device to which the
\fI<bootloader>\fP file should be written to. The boot loader file
must be a header-less image (not an object file) containing the raw
contents of the text, data, and bss sections. A typical command to
make SCSI disk 0 bootable with the \fIaboot\fP loader is shown
.I "e2writeboot /dev/fd0 bootlx"
The \fI-v\fP option makes swriteboot be a bit more verbose.
The \fI-f#\fP option tells wrtiteboot to ignore an overlap of the boot area with
.SH SEE ALSO
.IR aboot (8) ,
.IR mke2fs (8) ,
.IR e2writeboot (8)
Bob Manson <email@example.com>
Michael Schwingen <firstname.lastname@example.org>