kvar(8) System Manager's Manual kvar(8)Name
kvar - modify RISC kernel variables in memory or on disk
Syntax
/usr/etc/kvar -r(b|w|l) [options] vmunix
/usr/etc/kvar -w(b|w|l) [options] vmunix
Description
The command allows you to read or write RISC kernel variables, either in the on-disk image of or the active in-memory image. The -r form
of the command does variable reads; the -w form does variable writes. The variable length qualifiers are: b (1 byte), w (word, or 2
bytes), and l (longword, or 4 bytes).
Variable contents are displayed in hexadecimal format.
Options-a address Specifies the address of the kernel variable. Either the -a or -s option must be specified. The address is specified as
either a positive decimal or hexadecimal constant.
-k Instructs to use the in-memory image of The default is to use the on-disk copy.
-l Searches for a local symbol. The default is a global symbol search.
-o offset Adds an offset to the address (or address of the symbol name). The offset value is specified as either a positive decimal or
hexadecimal constant.
-s name Specifies the name of the kernel variable.
-v value Specifies the new value to be assigned by the -w form of The -v option is ignored if the -r form of is being used. The value
is specified as either a positive decimal or hexadecimal constant.
Restrictions
You must have appropriate file access permissions for (and for with the -k option).
The command is available only on RISC systems. For VAX systems, use to modify kernel variables.
Examples
This example reads the variable `udpcksum' from the running kernel image:
% kvar -k -rl -s udpcksum /vmunix
This example sets the `xyz' variable to zero in the running kernel image:
% kvar -k -wl -s xyz -v 0 /vmunix
This example sets the variable `xyz' to -1 in the on-disk image of making this value persistent across reboots:
% kvar -wl -s xyz -v 0xffffffff /vmunix
This example sets to zero 1 byte at offset 2 from address 0x80161a98 in the running kernel image:
% kvar -k -wb -o 2 -a 0x80161a98 /vmunix
FilesSee Alsoadb(1), dbx(1)
RISC kvar(8)
Check Out this Related Man Page
od(1) General Commands Manual od(1)Name
od - create file octal dump
Syntax
od [options] [file] [offset] [label]
Description
The command displays file, or its standard input, in one or more dump formats as selected by the first argument. If the first argument is
missing, -o is the default. Dumping continues until end-of-file.
Options
-a[p|P] Interprets bytes as characters and display them with their ACSII names. If the p character is given also, then bytes with even
parity are underlined. The P character causes bytes with odd parity to be underlined. Otherwise the parity bit is ignored.
-b Displays bytes as unsigned octal.
-c Displays bytes as ASCII characters. Certain non-graphic characters appear as C escapes: null= , backspace=, formfeed=f, new-
line=
, return=
, tab= ; others appear as 3-digit octal numbers. Bytes with the parity bit set are displayed in octal.
-d Displays short words as unsigned decimal.
-f Displays long words as floating point.
-h Displays short words as unsigned hexadecimal.
-i Displays short words as signed decimal.
-l Displays long words as signed decimal.
-o Displays short words as unsigned octal.
-s[n] Looks for strings of ASCII characters of n minimum length. By default, the minimum length is 3 characters.
-v Displays all data and indicates lines identical to the last line shown with an * in column 1.
-w[n] Specifies the number of input bytes to be interpreted and displayed on each output line. If w is not specified, 16 bytes are read
for each display line. If n is not specified, it defaults to 32.
-x Displays short words as hexadecimal.
An upper case format character implies the long or double precision form of the object.
The offset argument specifies the byte offset into the file where dumping is to commence. By default this argument is interpreted in
octal. A different radix can be specified; If ``.'' is appended to the argument, then offset is interpreted in decimal. If offset begins
with ``x'' or ``0x'', it is interpreted in hexadecimal. If ``b'' (``B'') is appended, the offset is interpreted as a block count, where a
block is 512 (1024) bytes. If the file argument is omitted, an offset argument must be preceded by ``+''.
The radix of the displayed address is the same as the radix of the offset, if specified; otherwise it is octal.
The label is interpreted as a pseudo-address for the first byte displayed. It is shown in ``()'' following the file offset. It is
intended to be used with core images to indicate the real memory address. The syntax for label is identical to that for offset.
Restrictions
A file name argument can't start with ``+''. A hexadecimal offset can't be a block count. Only one file name argument can be given.
It is an historical botch to require specification of object, radix, and sign representation in a single character argument.
See Alsoadb(1) - VAX only, dbx(1)od(1)