summaryrefslogtreecommitdiffstats
path: root/trunk/man/vpddecode.8
diff options
context:
space:
mode:
authornima <nima@abc39116-655e-4be6-ad55-d661dc543056>2009-03-31 11:42:38 +0000
committernima <nima@abc39116-655e-4be6-ad55-d661dc543056>2009-03-31 11:42:38 +0000
commitd7200d96d5b90bcd0013c84ec1b053acbcca86c9 (patch)
tree76b63b8b927bdbb544fa2de66747baa5cd3da058 /trunk/man/vpddecode.8
parent37d1a8117cd212ee9e47bbd4225ba76dece7dad7 (diff)
downloadpython-dmidecode-d7200d96d5b90bcd0013c84ec1b053acbcca86c9.tar.gz
python-dmidecode-d7200d96d5b90bcd0013c84ec1b053acbcca86c9.tar.xz
python-dmidecode-d7200d96d5b90bcd0013c84ec1b053acbcca86c9.zip
Reverting recent (pointless) change.
git-svn-id: svn://svn.autonomy.net.au/python-dmidecode@180 abc39116-655e-4be6-ad55-d661dc543056
Diffstat (limited to 'trunk/man/vpddecode.8')
-rw-r--r--trunk/man/vpddecode.874
1 files changed, 0 insertions, 74 deletions
diff --git a/trunk/man/vpddecode.8 b/trunk/man/vpddecode.8
deleted file mode 100644
index c9e4acf..0000000
--- a/trunk/man/vpddecode.8
+++ /dev/null
@@ -1,74 +0,0 @@
-.TH VPDDECODE 8 "February 2007" "dmidecode"
-.SH NAME
-vpddecode \- \s-1VPD\s0 structure decoder
-.SH SYNOPSIS
-.B vpddecode
-.RB [ OPTIONS ]
-
-.SH DESCRIPTION
-.B vpddecode
-prints the "vital product data" information that can be found in almost
-all IBM and Lenovo computers. Available items are:
-.IP \(bu "\w'\(bu'u+1n"
-\s-1BIOS\s0 Build \s-1ID\s0
-.IP \(bu
-Box Serial Number
-.IP \(bu
-Motherboard Serial Number
-.IP \(bu
-Machine Type/Model
-
-.PP
-Some systems have these additional items:
-.IP \(bu "\w'\(bu'u+1n"
-BIOS Release Date
-.IP \(bu
-Default Flash Image File Name
-
-.PP
-Note that these additional items are not documented by IBM, so this is
-guess work, and as such should not be blindly trusted. Feedback about
-the accuracy of these labels is welcome.
-
-.SH OPTIONS
-.TP
-.BR "-d" ", " "--dev-mem FILE"
-Read memory from device \fBFILE\fR (default: \fB/dev/mem\fR)
-.TP
-.BR "-s" ", " "--string KEYWORD"
-Only display the value of the \s-1VPD\s0 string identified by \fBKEYWORD\fR.
-\fBKEYWORD\fR must be a keyword from the following list: \fBbios-build-id\fR,
-\fBbox-serial-number\fR, \fBmotherboard-serial-number\fR,
-\fBmachine-type-model\fR, \fBbios-release-date\fR.
-Each keyword corresponds to an offset and a length within the \s-1VPD\s0
-record.
-Not all strings may be defined on all \s-1VPD\s0-enabled systems.
-If \fBKEYWORD\fR is not provided or not valid, a list of all valid
-keywords is printed and
-.B vpddecode
-exits with an error.
-This option cannot be used more than once.
-Mutually exclusive with \fB--dump\fR.
-.TP
-.BR "-u" ", " "--dump"
-Do not decode the VPD records, dump their contents as hexadecimal instead.
-Note that this is still a text output, no binary data will be thrown upon
-you. ASCII equivalent is displayed when possible. This option is mainly
-useful for debugging.
-Mutually exclusive with \fB--string\fR.
-.TP
-.BR "-h" ", " "--help"
-Display usage information and exit
-.TP
-.BR "-V" ", " "--version"
-Display the version and exit
-
-.SH FILES
-.I /dev/mem
-.SH AUTHOR
-Jean Delvare
-.SH "SEE ALSO"
-.BR biosdecode (8),
-.BR dmidecode (8),
-.BR mem (4),
-.BR ownership (8)