DUMP(8S) — UNIX Programmer’s Manual
NAME
dump − standalone memory dumper
SYNOPSIS
From the powerup monitor:
∗ b 80 dv(un,su) stand/dump dumpdev offset dynixname [ size ] [ −o ]
∗ b 80 dv(un,su) stand/dump −f dumplist dynixname [ −o ]
DESCRIPTION
Dump copies memory to offset blocks (specified as a decimal integer) past the beginning of device dumpdev (specified in standalone file notation; see boot(8S)). Dynixname should be the name of the same device as dumpdev expressed as a DYNIX file (usually beginning with /dev/).
The −f flag allows multiple dump devices to be specified. The dumplist file name must be specified in standalone notation, and dynixname should be the DYNIX equivalent of the standalone filename dumplist. Each line in the dumplist file has the format:
dumpdev offset dynixname [ size ]
Each line of the file describes where a section of the dump will placed.
By default, all of memory is dumped, up to 16 Mbytes minus the offset. Other memory sizes (smaller or larger) may be specified with the size parameter, measured in 512-byte sectors (as a decimal integer).
Dump normally aborts if an attempt is made to overwrite an existing dump. If −o is specified, dump will proceed with the dump even if a previous dump has not been cleared.
The wn1 powerup monitor command, or the n1= option of the bootflags(8) command, can be used to store a permanent dump invocation, so that DYNIX can automatically generate dumps. The standard /etc/rc.local already invokes bootflags to do this. A typical invocation of dump looks like:
b 80 sd(0,0)stand/dump sd(0,1) 1000 /dev/sd0b
A typical use of dump specifying multiple dump partitions looks like:
b 80 sd(0,0)stand/dump -f sd(0,0)etc/DUMPLIST /etc/DUMPLIST
An example of /etc/DUMPLIST looks like:
sd(0,1) 1000 /dev/sd0b 33440
sd(8,1) 0 /dev/sd1b 33440
zd(0,1) 0 /dev/zd0b 67716
SEE ALSO
boot(8S), DYNIX System Administrator’s Guide
DYNIX