Hello community,
here is the log from the commit of package kdump
checked in at Sun Aug 10 01:22:18 CEST 2008.
--------
--- kdump/kdump.changes 2008-08-07 13:13:16.000000000 +0200
+++ /mounts/work_src_done/STABLE/kdump/kdump.changes 2008-08-09 18:49:22.000000000 +0200
@@ -1,0 +2,6 @@
+Sat Aug 9 18:37:52 CEST 2008 - bwalle@suse.de
+
+- update to 0.6.1
+ o add kdump(7) manual page
+
+-------------------------------------------------------------------
Old:
----
kdump-0.6.0.tar.bz2
New:
----
kdump-0.6.1.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ kdump.spec ++++++
--- /var/tmp/diff_new_pack.n10232/_old 2008-08-10 01:22:08.000000000 +0200
+++ /var/tmp/diff_new_pack.n10232/_new 2008-08-10 01:22:08.000000000 +0200
@@ -1,5 +1,5 @@
#
-# spec file for package kdump (Version 0.6.0)
+# spec file for package kdump (Version 0.6.1)
#
# Copyright (c) 2008 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
@@ -21,7 +21,7 @@
Name: kdump
License: GPL v2 or later
-Version: 0.6.0
+Version: 0.6.1
Release: 1
Requires: curl openssh makedumpfile
Summary: Script for kdump
@@ -93,6 +93,7 @@
%{_sbindir}/kdumptool
%{_sbindir}/mkdumprd
%{_mandir}/man5/kdump.5.gz
+%{_mandir}/man7/kdump.7.gz
%{_mandir}/man8/kdumptool.8.gz
%{_mandir}/man8/mkdumprd.8.gz
/sbin/rckdump
@@ -102,6 +103,9 @@
%config %{_sysconfdir}/udev/rules.d/70-kdump.rules
%changelog
+* Sat Aug 09 2008 bwalle@suse.de
+- update to 0.6.1
+ o add kdump(7) manual page
* Thu Aug 07 2008 bwalle@suse.de
- update to 0.6.0
o add vmcore(5) manual page
++++++ kdump-0.6.0.tar.bz2 -> kdump-0.6.1.tar.bz2 ++++++
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/ChangeLog new/kdump-0.6.1/ChangeLog
--- old/kdump-0.6.0/ChangeLog 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/ChangeLog 2008-08-09 18:43:53.000000000 +0200
@@ -1,3 +1,7 @@
+2008-08-07 Bernhard Walle
+
+ * add kdump(7) manual page
+
2008-08-06 Bernhard Walle
* implement email support (send_notification command)
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/CMakeLists.txt new/kdump-0.6.1/CMakeLists.txt
--- old/kdump-0.6.0/CMakeLists.txt 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/CMakeLists.txt 2008-08-09 18:43:53.000000000 +0200
@@ -26,7 +26,7 @@
cmake_minimum_required(VERSION 2.4)
set (PACKAGE_STRING "kdump")
-set (PACKAGE_VERSION "0.6.0")
+set (PACKAGE_VERSION "0.6.1")
include_directories("${PROJECT_BINARY_DIR}")
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/doc/man/CMakeLists.txt new/kdump-0.6.1/doc/man/CMakeLists.txt
--- old/kdump-0.6.0/doc/man/CMakeLists.txt 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/doc/man/CMakeLists.txt 2008-08-09 18:43:53.000000000 +0200
@@ -17,6 +17,21 @@
# 02110-1301, USA.
#
+ADD_CUSTOM_COMMAND(
+ OUTPUT
+ ${CMAKE_CURRENT_BINARY_DIR}/kdump.7.gz
+ COMMAND
+ ${A2X_EXECUTABLE} ${A2X_MAN_OPTIONS}
+ -D ${CMAKE_CURRENT_BINARY_DIR}
+ ${CMAKE_CURRENT_SOURCE_DIR}/kdump.7.txt &&
+ rm -f ${CMAKE_CURRENT_SOURCE_DIR}/kdump.7.xml &&
+ gzip -f ${CMAKE_CURRENT_BINARY_DIR}/kdump.7
+ DEPENDS
+ ${CMAKE_CURRENT_SOURCE_DIR}/kdump.7.txt
+ WORKING_DIRECTORY
+ ${CMAKE_CURRENT_BINARY_DIR}
+)
+
ADD_CUSTOM_COMMAND(
OUTPUT
@@ -85,6 +100,7 @@
ADD_CUSTOM_TARGET(
manpages
DEPENDS
+ ${CMAKE_CURRENT_BINARY_DIR}/kdump.7.gz
${CMAKE_CURRENT_BINARY_DIR}/vmcore.5.gz
${CMAKE_CURRENT_BINARY_DIR}/kdump.5.gz
${CMAKE_CURRENT_BINARY_DIR}/kdumptool.8.gz
@@ -100,9 +116,9 @@
INSTALL(FILES
- ${CMAKE_CURRENT_BINARY_DIR}/kdumptool.8.gz
+ ${CMAKE_CURRENT_BINARY_DIR}/kdump.7.gz
DESTINATION
- share/man/man8
+ share/man/man7
)
INSTALL(FILES
@@ -112,6 +128,7 @@
)
INSTALL(FILES
+ ${CMAKE_CURRENT_BINARY_DIR}/kdumptool.8.gz
${CMAKE_CURRENT_BINARY_DIR}/mkdumprd.8.gz
DESTINATION
share/man/man8
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/doc/man/kdump.5.html new/kdump-0.6.1/doc/man/kdump.5.html
--- old/kdump-0.6.0/doc/man/kdump.5.html 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/doc/man/kdump.5.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,247 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>kdump</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /></head><body><div class="refentry" lang="en" xml:lang="en"><a id="id212088"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>kdump — Configuration of kdump</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p>/etc/sysconfig/kdump</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_description"></a><h2>DESCRIPTION</h2><p>This configuration file provides various options for the kdump loading and
-saving process. It's mostly read by <span class="strong"><strong>kdumptool</strong></span>(8) but also by the kdump init
-script.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_options"></a><h2>OPTIONS</h2><p>The file format consists of shell variables (which means that the configuration
-file is actually parsed by a <span class="strong"><strong>sh</strong></span>(1) compatible shell) that are described below.
-It's recommended to use a pair of double quotes to assign values to that
-variables.</p><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_kernelver"></a><h3>KDUMP_KERNELVER</h3><p>Kernel Version string for the -kdump kernel, such as "2.6.25-5-kdump".
-The init script will use a kernel named <span class="emphasis"><em>/boot/vmlinu[zx]-$KDUMP_KERNELVER</em></span>.
-Using "kdump" will default to the most recently installed kdump kernel
-(to which the symbolic link <span class="emphasis"><em>/boot/vmlinuz-kdump</em></span> points).</p><p>If no version is specified, then the init script will try to find a
-kdump kernel with the following algorithm:</p><div class="orderedlist"><ol type="1"><li>
-Use $(uname -r)-kdump
-</li><li>
-If that doesn't exist, use -kdump
-</li><li>
-If that doesn't exist, use $(uname -r)
-</li><li>
-If that doesn't exist, use ""
-</li></ol></div><p>On each item, it tries:</p><div class="orderedlist"><ol type="1"><li>
-/boot/*vmlinuz
-</li><li>
-/boot/*vmlinux
-</li><li>
-/boot/*vmlinux.gz
-</li></ol></div><p>If the name does not contain "kdump", the kernel is checked for relocatability
-using <span class="emphasis"><em>kdumptool identify_dump</em></span>.</p><p>Default is "".</p><div class="refsect3" lang="en" xml:lang="en"><a id="_initrd"></a><h4>Initrd</h4><p>For the initrd, if the kernel name already contains "kdump", then the initrd
-<span class="emphasis"><em>/boot/initrd-<kernelver></em></span> is used. Else, we use
-<span class="emphasis"><em>/boot/initrd-<kernelver>-kdump</em></span> (the kernel flavour is not replaced, so for
-example this means <span class="emphasis"><em>/boot/initrd-2.6.25.9-0.2-default-kdump</em></span>. This is because
-the initrd used for kdump always has to be special, and it makes no sense to
-load the normal initrd that would not save the dump.</p></div></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_commandline"></a><h3>KDUMP_COMMANDLINE</h3><p>Command line used to boot the kdump kernel. By default, the <span class="emphasis"><em>/etc/init.d/kdump</em></span>
-script tries to build a command line automatically from the command line of the
-running system, preserving root partition, serial console, etc. If you manually
-create a command line, make sure to include:</p><div class="itemizedlist"><ul type="disc"><li>
-the <span class="emphasis"><em>root</em></span> parameter,
-</li><li>
-any <span class="emphasis"><em>console</em></span> parameters (for serial console),
-</li><li>
-<span class="emphasis"><em>maxcpus=1</em></span>,
-</li><li>
-<span class="emphasis"><em>irqpoll</em></span>,
-</li><li>
-<span class="emphasis"><em>reset_devices</em></span>,
-</li><li>
-<span class="emphasis"><em>elevator=deadline</em></span> to save the memory footprint.
-</li></ul></div><p>The last three parameters are special for kdump and should always be included,
-if you don't have a good reason to exclude them.</p><p>If you just want have an own command line parameter to be added additionally,
-use KDUMP_COMMANDLINE_APPEND.</p><p>Default is "".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_commandline_append"></a><h3>KDUMP_COMMANDLINE_APPEND</h3><p>This variable describes all command line parameters that are passed to the kdump
-kernel additionally to the default parameters. See also KDUMP_COMMANDLINE.</p><p>Default is "".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kexec_options"></a><h3>KEXEC_OPTIONS</h3><p>Additional options for <span class="strong"><strong>kexec</strong></span>(8).</p><p>Default is "" except on IA64 where it is "--noio".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_makedumpfile_options"></a><h3>MAKEDUMPFILE_OPTIONS</h3><p>Additional options for <span class="strong"><strong>makedumpfile</strong></span>(8). makedumpfile will be used to save the
-dump if KDUMP_DUMPLEVEL is non-zero or KDUMP_DUMPFORMAT is not <span class="emphasis"><em>ELF</em></span>.
-Normally, you don't have to specify any options here, but you may be asked in
-Bugzilla to add the <span class="emphasis"><em>-D</em></span> option for debugging.</p><p>Default is "".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_immediate_reboot"></a><h3>KDUMP_IMMEDIATE_REBOOT</h3><p>Immediately reboot after saving the core in the kdump kernel? Use "yes" or "no".</p><p>Default is "yes".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_transfer"></a><h3>KDUMP_TRANSFER</h3><p>A script or command executed to process and transfer the dump image.
-It can read the dump image either via /proc/vmcore or /dev/oldmem. Most other
-variables will have no effect if you use a custom command here.</p><p>It's important that all requirements including that script itself are included
-in KDUMP_REQUIRED_PROGRAMS.</p><p>It's strongly recommended that the default mechanism is used, it should provide
-everything that is needed, together with KDUMP_PRESCRIPT and
-KDUMP_POSTSCRIPT. We can't support problems with using that variable.</p><p>KDUMP_PRESCRIPT and KDUMP_POSTSCRIPT are not executed if KDUMP_TRANSFER is set.</p><p>Default: "".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_savedir"></a><h3>KDUMP_SAVEDIR</h3><p>The directory where dumps are saved to. If the directory does not exist, it will
-be created. The directory is a URL and must conform to the syntax described in
-the section "URL FORMAT" below. If the directory does not exist, it will be
-created. (That is true for all targets, even network targets. Of course the user
-must have the permission to create directories.)</p><p>Below that directory, for each dump a directory with a time stamp in the
-following format will be created: "YYYY-MM-TT-HH:MM". That directory contains
-the dump and various other files, depending which dump target will be used and
-which dump settings are made.</p><p>If KDUMP_COPY_KERNEL is set, that directory will also contain the kernel.</p><p>Default: "file:///var/log/dump".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_keep_old_dumps"></a><h3>KDUMP_KEEP_OLD_DUMPS</h3><p>Number of old dumps to keep. That variable is only honored on local directories
-(i.e., if KDUMP_SAVEDIR starts with <span class="emphasis"><em>file</em></span>) because we think it's bad from a
-security point of view if other hosts delete stuff (that may be from another
-hosts) on a dump server. The deletion process takes place before the dumps are
-saved. So if you specify 3 here, then after the dump has been saved, 4 dumps are
-on disk.</p><p>Set that variable to "0" to disable the deletion of dumps entirely, and set
-that variable to "-1" to delete all dumps, i.e. then only the just saved dump is
-on disk.</p><p>Default: "5"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_free_disk_size"></a><h3>KDUMP_FREE_DISK_SIZE</h3><p>Don't save the dump (or delete it afterwards) if after saving the dump less than
-KDUMP_FREE_DISK_SIZE megabytes are free. Because when dump compression or dump
-filtering (see KDUMP_DUMPLEVEL and KDUMP_DUMPFORMAT) is used, we don't know in
-advance how large the dump will be, we have to delete the dump after saving it.</p><p>That option applies only to local file systems, i.e. KDUMP_SAVEDIR must start
-with <span class="emphasis"><em>file</em></span>.</p><p>Default: "64"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_verbose"></a><h3>KDUMP_VERBOSE</h3><p>Bit mask of several options that set the verbosity of the dump process. To apply
-several options, you have to add their value. The options are:</p><div class="variablelist"><dl><dt><span class="term">
-1
-</span></dt><dd>
- kdump command line is written to system log when executing /etc/init.d/kdump.
-</dd><dt><span class="term">
-2
-</span></dt><dd>
- Progress is written to stdout while dumping.
-</dd><dt><span class="term">
-4
-</span></dt><dd>
- kdump command line is written so standard output when executing
- /etc/init.d/kdump.
-</dd><dt><span class="term">
-8
-</span></dt><dd>
- Debugging for kdump transfer mechanism. That is executed in initrd and
- generates lots of output. However, it's very useful if something does not
- work.
-</dd></dl></div><p>So, for example, if you want to have the command line on stdout when loading the
-kernel and also in the system log, just use KDUMP_VERBOSE = 5 (i.e. 1 + 4).</p><p>Default: "3".</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_dumplevel"></a><h3>KDUMP_DUMPLEVEL</h3><p>Determines the dump level. If KDUMP_DUMPLEVEL is non-zero, then
-<span class="strong"><strong>makedumpfile</strong></span>(8) is used to strip pages that may not be necessary for
-analysing. 0 means no stripping, and 31 is the maximum dump level, i.e.
-0 produces the largest dump files and 31 the smallest.</p><p>The following table from makedumpfile(8) shows what each dump level means:</p><pre class="literallayout"> dump | zero | cache|cache | user | free
- level | page | page |private| data | page
--------+------+------+-------+------+------
- 0 | | | | |
- 1 | X | | | |
- 2 | | X | | |
- 3 | X | X | | |
- 4 | | X | X | |
- 5 | X | X | X | |
- 6 | | X | X | |
- 7 | X | X | X | |
- 8 | | | | X |
- 9 | X | | | X |
- 10 | | X | | X |
- 11 | X | X | | X |
- 12 | | X | X | X |
- 13 | X | X | X | X |
- 14 | | X | X | X |
- 15 | X | X | X | X |
- 16 | | | | | X
- 17 | X | | | | X
- 18 | | X | | | X
- 19 | X | X | | | X
- 20 | | X | X | | X
- 21 | X | X | X | | X
- 22 | | X | X | | X
- 23 | X | X | X | | X
- 24 | | | | X | X
- 25 | X | | | X | X
- 26 | | X | | X | X
- 27 | X | X | | X | X
- 28 | | X | X | X | X
- 29 | X | X | X | X | X
- 30 | | X | X | X | X
- 31 | X | X | X | X | X</pre><p>Default: "0"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_dumpformat"></a><h3>KDUMP_DUMPFORMAT</h3><p>This variable specifies the dump format.</p><div class="variablelist"><dl><dt><span class="term">
-<span class="strong"><strong>ELF</strong></span>
-</span></dt><dd>
- <span class="emphasis"><em>ELF</em></span> has the advantage that it's a standard format and GDB can be used to
- analyse the dumps. The disadvantage is that the dump files are larger.
-</dd><dt><span class="term">
-<span class="strong"><strong>compressed</strong></span>
-</span></dt><dd>
- <span class="emphasis"><em>compressed</em></span> is the kdump compressed format that produces small dumps, see
- <span class="strong"><strong>makedumpfile</strong></span>(8). However, only <span class="strong"><strong>crash</strong></span>(8) can analyse the dumps and
- makedumpfile must be installed (but you need it anyway if you set
- KDUMP_DUMPLEVEL to non-zero before).
-</dd></dl></div><p>Default: "compressed"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_continue_on_error"></a><h3>KDUMP_CONTINUE_ON_ERROR</h3><p>If something goes wrong while saving the dump or deleting old dumps in initrd,
-then <span class="strong"><strong>kdumptool</strong></span>(8) normally just tries to execute the next action. However,
-it can be usedful to open a shell at that point of time to fix the problem
-or just debug it, therefore you can set KDUMP_CONTINUE_ON_ERROR to "true".</p><p>Default: "false"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_required_programs"></a><h3>KDUMP_REQUIRED_PROGRAMS</h3><p>This is a space-separated list of programs (full path) that are required by
-KDUMP_TRANSFER, KDUMP_PRESCRIPT or KDUMP_POSTSCRIPT. Dynamic libraries that are
-required by that programs don't have to be included as they are resolved
-automatically. However, it's necessary to include other runtime requirements
-because it's not possible to resolve them automatically.</p><p>Default: ""</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_prescript"></a><h3>KDUMP_PRESCRIPT</h3><p>Program that is executed before taking the dump. You have to include that
-program in KDUMP_REQUIRED_PROGRAMS.</p><p>Default: ""</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_postscript"></a><h3>KDUMP_POSTSCRIPT</h3><p>Program that is executed after taking the dump and before the system is
-rebooted. You have to include that program in KDUMP_POSTSCRIPT.</p><p>Default: ""</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_copy_kernel"></a><h3>KDUMP_COPY_KERNEL</h3><p>Not only copy the dump to KDUMP_SAVEDIR but also the installed kernel. Valid
-values are "yes" and "no". If you want to have the debugging information also
-copied, which is required to open the program, you also have to install the
-<span class="emphasis"><em>kernel-<flavour>-debuginfo</em></span> package.</p><p>Modules are not copied, only the kernel image and the debugging file.</p><p>Default: "yes"</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdumptool_flags"></a><h3>KDUMPTOOL_FLAGS</h3><p>This is a space-separated list of flags to tweak the run-time behaviour of
-<span class="strong"><strong>kdumptool</strong></span>(8). Currently, only one flag is supported:</p><div class="variablelist"><dl><dt><span class="term">
-<span class="strong"><strong>NOSPARSE</strong></span>
-</span></dt><dd>
- Disable the creation of sparse-files. This flag is for debugging purposes,
- e.g. if the file system or network protocol has problems with sparse files.
- Because SFTP and FTP are not mounted, that option has no meaning when saving
- the dump to SFTP and FTP.
-</dd></dl></div><p>Default: ""</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_kdump_netconfig"></a><h3>KDUMP_NETCONFIG</h3><p>Network configuration for kdump. Because the dump process runs in initrd, the
-network configuration is different from the normal network configuration. Use
-<span class="emphasis"><em>auto</em></span> to auto-detect the network configuration, this is also the default.</p><p>Use a <span class="emphasis"><em>netdevice:mode</em></span> string to force a specific network device to be used. A
-<span class="emphasis"><em>netdevice</em></span> is for example "eth0". The <span class="emphasis"><em>mode</em></span> can be either "dhcp" or "static".
-If you use "static", you have to set the IP address with <span class="emphasis"><em>ip=ipspec</em></span>. <span class="emphasis"><em>ipspec</em></span>
-is <client>:<server>:<gateway>:<netmask>:<hostname>:<device>:<proto>. See
-<span class="strong"><strong>mkinitrd</strong></span>(8) for details.</p><p>You can set KDUMP_NETCONFIG to "" if you want no network in initrd, i.e. you use
-disk dumping.</p><p>Default: "auto"</p></div></div><div class="refsect1" lang="en" xml:lang="en"><a id="_url_format"></a><h2>URL FORMAT</h2><p>In general, the URL format is</p><p><span class="emphasis"><em>protocol</em></span>://<span class="emphasis"><em>specification</em></span></p><p>where <span class="emphasis"><em>protocol</em></span> is one of:</p><div class="itemizedlist"><ul type="disc"><li>
-<span class="strong"><strong>file</strong></span>,
-</li><li>
-<span class="strong"><strong>ftp</strong></span>,
-</li><li>
-<span class="strong"><strong>sftp</strong></span> (aliases are <span class="strong"><strong>ssh</strong></span> or <span class="strong"><strong>scp</strong></span>),
-</li><li>
-<span class="strong"><strong>nfs</strong></span>
-</li><li>
-<span class="strong"><strong>cifs</strong></span> (alias is <span class="strong"><strong>smb</strong></span>).
-</li></ul></div><p>The <span class="emphasis"><em>specification</em></span> varies for each protocol.</p><div class="refsect2" lang="en" xml:lang="en"><a id="_local_files_emphasis_file_emphasis"></a><h3>Local files (<span class="emphasis"><em>file</em></span>)</h3><p>That type describes a local path.</p><p><span class="emphasis"><em>Format:</em></span> <code class="literal">file://]<span class="emphasis"><em>path</em></span></code></p><p>As shown, the <span class="emphasis"><em>file</em></span> prefix is optional, i.e. a simple path is still valid.
-The <span class="emphasis"><em>path</em></span> must start with a leading slash (/), i.e. only absolute paths are
-allowed.</p><p><span class="emphasis"><em>Examples:</em></span></p><div class="itemizedlist"><ul type="disc"><li>
-<code class="literal">/var/log/dump</code>
-</li><li>
-<code class="literal">file:///var/log/dump</code>
-</li></ul></div></div><div class="refsect2" lang="en" xml:lang="en"><a id="_file_transfer_protocol_emphasis_ftp_emphasis"></a><h3>File Transfer Protocol (<span class="emphasis"><em>ftp</em></span>)</h3><p>This URL type is used to specify paths on a remote FTP server.</p><p><span class="emphasis"><em>Format:</em></span> <code class="literal">ftp:// [ <span class="emphasis"><em>user</em></span> [:<span class="emphasis"><em>password</em></span>]@ ] <span class="emphasis"><em>hostname</em></span> [:<span class="emphasis"><em>port</em></span>] ] <span class="emphasis"><em>path</em></span></code></p><p>The remote <span class="emphasis"><em>user</em></span> is optional, if no user is specified, anonymous FTP is
-assumed. Even if a username is specified, the <span class="emphasis"><em>password</em></span> is optional, if no
-password is specified, an empty password is used. When the username is
-"anonymous", then "$USER@$HOSTNAME" is used as password because some FTP
-servers deny anonymous FTP with empty passwords.</p><p><span class="emphasis"><em>hostname</em></span> can be either a (DNS-)resolvable hostname, with or without a domain
-name, or an IP address in totted decimal format. <span class="emphasis"><em>port</em></span> can be used to
-specify the remote port, if no port is specified in the URL, the default FTP
-port is used. Finally, <span class="emphasis"><em>path</em></span> must conform to the same rules as for local
-files (see above).</p><p><span class="emphasis"><em>Examples:</em></span></p><div class="itemizedlist"><ul type="disc"><li>
-<code class="literal">ftp://neptunium/var/log/dump</code>
-</li><li>
-<code class="literal">ftp://<a class="ulink" href="mailto:bwalle@neptunium.suse.de" target="_top">bwalle@neptunium.suse.de</a>/var/log/dump</code>
-</li><li>
-<code class="literal">ftp://bwalle:dontsay@strauss.suse.de:123/var/log/dump</code>
-</li><li>
-<code class="literal">ftp://192.168.0.70/var/log/dump</code>
-</li></ul></div></div><div class="refsect2" lang="en" xml:lang="en"><a id="_secure_file_transfer_protocol_emphasis_sftp_emphasis"></a><h3>Secure File Transfer Protocol (<span class="emphasis"><em>sftp</em></span>)</h3><p>This URL type is used to specify paths on a remote server that is reachable via
-SFTP. It's important that an SFTP server must be running (which is the default
-on SUSE), the <span class="strong"><strong>kdumptool</strong></span> does not use FISH (FIles transferred over SHell
-protocol).</p><p><span class="emphasis"><em>Format:</em></span> <code class="literal">sftp:// [ <span class="emphasis"><em>user</em></span> [:<span class="emphasis"><em>password</em></span>]@ ] <span class="emphasis"><em>hostname</em></span> [:<span class="emphasis"><em>port</em></span>] ] <span class="emphasis"><em>path</em></span></code></p><p>It's valid to use the alias "ssh" or "scp" as alias for "sftp" (for backward
-compatibility), but the "sftp" prefix is recommended.</p><p>For the elements, see the description of FTP above. Please note that the use of
-an password here is not recommended. The recommended way is to add the key where
-the file should be copied to to the "authorized_keys" file of the user where the
-dump is saved. For example, if you want to save the dump to the "kdump" user of
-the machine "collector", then generate a private/public key pair on the machine
-that saves the dump with <code class="literal">ssh-keygen -t dsa</code>. Append the file <span class="emphasis"><em>id_dsa.pub</em></span> (in
-<span class="emphasis"><em>root/.ssh/</em></span>) to <span class="emphasis"><em>~dump/.ssh/authorized_keys</em></span> on "collector".</p><pre class="screen">root@earth:~# ssh-keygen -t dsa
-...
-root@earth:~# cat /root/.ssh/id_dsa.pub \
- | ssh kdump@collector "cat - >> /root/.ssh/authorized_keys"</pre><p>Don't use any password to encrypt the key. <span class="strong"><strong>kdumptool</strong></span> is designed to be used
-non-interactively.</p><p><span class="emphasis"><em>Examples:</em></span></p><div class="itemizedlist"><ul type="disc"><li>
-<code class="literal">sftp://<a class="ulink" href="mailto:kdump@collector" target="_top">kdump@collector</a>:22/var/log/dump</code>
-</li><li>
-<code class="literal">sftp://neptunium/var/log/dump</code>
-</li><li>
-<code class="literal">scp://neptunium/var/log/dump</code>
-</li></ul></div></div><div class="refsect2" lang="en" xml:lang="en"><a id="_network_file_system_emphasis_nfs_emphasis"></a><h3>Network File System (<span class="emphasis"><em>nfs</em></span>)</h3><p>NFS is used to specify remote hosts that export their file system via NFS.
-NFS doesn't use username and password. Also, the URL format cannot be used
-to specify options. As default, the <span class="emphasis"><em>nolock</em></span> option is used.</p><p><span class="emphasis"><em>Format:</em></span> +nfs://<span class="emphasis"><em>host</em></span> [:<span class="emphasis"><em>port:] _path</em></span></p><p><span class="emphasis"><em>host</em></span> is the hostname, <span class="emphasis"><em>port</em></span> is optional (should not be used, it is only
-implemented for completeness with the other URL formats). <span class="emphasis"><em>path</em></span> specifies
-the path that is exported via NFS in <span class="emphasis"><em>/etc/exports</em></span> (or a subdirectory of a
-path that is exported).</p><p><span class="emphasis"><em>Examples:</em></span></p><div class="itemizedlist"><ul type="disc"><li>
-<code class="literal">nfs://neptunium/var/log/dump</code>
-</li><li>
-<code class="literal">nfs://10.10.2.120/var/log/dump</code>
-</li></ul></div></div><div class="refsect2" lang="en" xml:lang="en"><a id="_common_internet_file_system_emphasis_cifs_emphasis"></a><h3>Common Internet File System (<span class="emphasis"><em>cifs</em></span>)</h3><p>CIFS is used to specify remote hosts that export a file system via CIFS,
-also known as SMB (although they are technically different, CIFS is the
-successor of SMB). This could be a Microsoft Windows server, or a Samba
-Server running on Unix or MacOS.</p><p><span class="emphasis"><em>Format:</em></span> +cifs:// [<span class="emphasis"><em>user</em></span> [:<span class="emphasis"><em>password</em></span>] @] <span class="emphasis"><em>host</em></span> <span class="emphasis"><em>path</em></span></p><p>Although it's technically not 100 % correct, <span class="emphasis"><em>smb</em></span> is used as an alias for
-<span class="emphasis"><em>cifs</em></span>, so the program will always return <span class="emphasis"><em>cifs</em></span> even if you specify <span class="emphasis"><em>smb</em></span>.</p><p>The parts of the URL are described in the FTP section above.</p><p><span class="strong"><strong>Note:</strong></span> You have to use the slash as path separator, not the backslash as on
-Microsoft Windows.</p><p><span class="emphasis"><em>Examples:</em></span></p><div class="itemizedlist"><ul type="disc"><li>
-<code class="literal">cifs://neptunium/var/log/dump</code>
-</li><li>
-<code class="literal">cifs://bwalle:dontsay@neptunium:/var/log/dump</code>
-</li><li>
-<code class="literal">smb://<a class="ulink" href="mailto:bwalle@192.168.0.70" target="_top">bwalle@192.168.0.70</a>:/var/log</code>
-</li></ul></div></div></div><div class="refsect1" lang="en" xml:lang="en"><a id="_bugs"></a><h2>BUGS</h2><p>Please report bugs and enhancement requests at <a class="ulink" href="https://bugzilla.novell.com" target="_top">https://bugzilla.novell.com</a>.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_copying"></a><h2>COPYING</h2><p>Copyright (c) 2008 Bernhard Walle <<a class="ulink" href="mailto:bwalle@suse.de" target="_top">bwalle@suse.de</a>>. Free use of this software is
-granted under the terms of the GNU General Public License (GPL), version 2 or
-later.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_see_also"></a><h2>SEE ALSO</h2><p><span class="strong"><strong>kexec</strong></span>(8), <span class="strong"><strong>kdump</strong></span>(5), <span class="strong"><strong>makedumpfile</strong></span>(8)
-<a class="ulink" href="http://en.opensuse.org/Kdump" target="_top"><span class="emphasis"><em>http://en.opensuse.org/Kdump</em></span></a></p></div></div></body></html>
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/doc/man/kdump.5.txt new/kdump-0.6.1/doc/man/kdump.5.txt
--- old/kdump-0.6.0/doc/man/kdump.5.txt 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/doc/man/kdump.5.txt 2008-08-09 18:43:53.000000000 +0200
@@ -259,41 +259,42 @@
The following table from makedumpfile(8) shows what each dump level means:
- dump | zero | cache|cache | user | free
- level | page | page |private| data | page
- -------+------+------+-------+------+------
- 0 | | | | |
- 1 | X | | | |
- 2 | | X | | |
- 3 | X | X | | |
- 4 | | X | X | |
- 5 | X | X | X | |
- 6 | | X | X | |
- 7 | X | X | X | |
- 8 | | | | X |
- 9 | X | | | X |
- 10 | | X | | X |
- 11 | X | X | | X |
- 12 | | X | X | X |
- 13 | X | X | X | X |
- 14 | | X | X | X |
- 15 | X | X | X | X |
- 16 | | | | | X
- 17 | X | | | | X
- 18 | | X | | | X
- 19 | X | X | | | X
- 20 | | X | X | | X
- 21 | X | X | X | | X
- 22 | | X | X | | X
- 23 | X | X | X | | X
- 24 | | | | X | X
- 25 | X | | | X | X
- 26 | | X | | X | X
- 27 | X | X | | X | X
- 28 | | X | X | X | X
- 29 | X | X | X | X | X
- 30 | | X | X | X | X
- 31 | X | X | X | X | X
+'------------.----------.----------.-------------.---------.----------
+dump level zero page cache page cache private user data free page
+----------------------------------------------------------------------
+ 0
+ 1 X
+ 2 X
+ 3 X X
+ 4 X X
+ 5 X X X
+ 6 X X
+ 7 X X X
+ 8 X
+ 9 X X
+10 X X
+11 X X X
+12 X X X
+13 X X X X
+14 X X X
+15 X X X X
+16 X
+17 X X
+18 X X
+19 X X X
+20 X X X
+21 X X X X
+22 X X X
+23 X X X X
+24 X X
+25 X X X
+26 X X X
+27 X X X X
+28 X X X X
+29 X X X X X
+30 X X X X
+31 X X X X X
+----------------------------------------------------------------------
Default: "0"
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/doc/man/kdump.7.txt new/kdump-0.6.1/doc/man/kdump.7.txt
--- old/kdump-0.6.0/doc/man/kdump.7.txt 1970-01-01 01:00:00.000000000 +0100
+++ new/kdump-0.6.1/doc/man/kdump.7.txt 2008-08-09 18:43:53.000000000 +0200
@@ -0,0 +1,377 @@
+//{{{ Copyright (c) 2008, SUSE LINUX Products GmbH
+//
+// All rights reserved.
+//
+// Redistribution and use in source and binary forms, with or without
+// modification, are permitted provided that the following conditions are met:
+//
+// Redistributions of source code must retain the above copyright notice, this
+// list of conditions and the following disclaimer.
+//
+// Redistributions in binary form must reproduce the above copyright notice,
+// this list of conditions and the following disclaimer in the documentation
+// and/or other materials provided with the distribution.
+//
+// Neither the name of the Novell nor the names of its contributors may be used
+// to endorse or promote products derived from this software without specific
+// prior written permission.
+//
+// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+// AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+// ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+// LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+// CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+// SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+// INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN
+// CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+// ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+// POSSIBILITY OF SUCH DAMAGE.
+//}}}
+
+kdump(7)
+========
+Bernhard Walle
+
+Name
+----
+kdump - Saving kernel dumps in SUSE
+
+Synopsis
+--------
+(not applicable)
+
+Description
+-----------
+This manual page gives an overview about kdump configuration on SUSE. This
+version applies to SUSE LINUX Enterprise 11 and openSUSE 11.1.
+
+Kdump is a technology to save the memory contents of a crashed system and save
+it to disk or network to analyse it later and find the cause of the crash.
+When the system crashes, the mechanism uses _kexec_ to boot a normal Linux
+kernel (that has been loaded into the system previously) which then has access
+to the old memory contents via _/proc/vmcore_ interface and can save that away.
+
+After the memory has been saved, the system reboots (without kexec).
+
+As mentioned above, that _panic kernel_ has to be loaded into the system. That
+is accomplished via *kexec*(8) in an init script at system bootup. To have
+memory for that panic kernel and also have RAM for the execution of that panic
+kernel, one has to reserve kernel memory with a special boot parameter
+(_crashkernel_).
+
+While it's possible in theory to boot the full system by that panic kernel, on
+SUSE we use the approach of having a special _initramfs_ that saves the dump to
+disk or network and then reboots. That has the advantage that less memory
+is necessary and the root file system also must not be intact if you save to
+another file system or to network.
+
+
+Automatic Configuration with YaST
+---------------------------------
+
+A simple method to use kdump on SUSE is to use the YaST kdump module. Just
+install the package _yast2-kdump_ (for example with
+
+----------------------------------
+# zypper install yast2-kdump
+----------------------------------
+
+and start the YaST2 module with
+
+----------------------------------
+# yast2 kdump
+----------------------------------
+
+Everything should be self-explanatory there.
+
+Manual Setup
+------------
+
+Following steps are needed to setup kdump manually (the description of the steps
+will follow):
+
+. Install the required software packages,
+. add the _crashkernel_ parameter to bootloader configuration,
+. enable the _kdump_ service,
+. configure kdump (/etc/sysconfig/kdump) and
+. load the kdump kernel.
+
+Required software
+~~~~~~~~~~~~~~~~~
+
+Following software packages are required for kdump:
+
+* kexec-tools
+* kdump
+* makedumpfile
+
+There is no special _kernel-kdump_ required like in earlier versions of SUSE
+LINUX Enterprise. The technical reason is that the normal kernel is relocatable
+now and can be used as kdump kernel, i.e. it's possible to load and execute the
+normal kernel at any address, not only the compiled-in address as before.
+
+Bootloader configuration
+~~~~~~~~~~~~~~~~~~~~~~~~
+It's necessary to reserve a certain amount of memory in the normal system at
+boot time which will be used by *kexec*(8) to load the panic kernel. To achieve
+that, you have to add a parameter called _crashkernel_ in bootloader
+configuration. The syntax is:
+
+ crashkernel=size@offset
+
+The _offset_ is the load offset, i.e. the physical base address on which the
+memory reservation area starts. Starting with version 2.6.27, it's not necessary
+to specify that _offset_ manually since the kernel chooses a suitable base
+address automatically.
+
+For the _size_, following values are recommended:
+
+`-----------------`--------------------------------------------
+Architecture Size
+---------------------------------------------------------------
++i386+ +64M+
++x86_64+ +64M+ or +128M+ on large machines
++ppc64+ +128M+
++ia64+ +512M+ (or more on very large machines)
+---------------------------------------------------------------
+
+Example: +crashkernel=64M+ (on a normal PC system)
+
+[NOTE]
+There's also a more advanced syntax that makes the amount of memory dependent on
+system RAM. Read _Documentation/kernel-parameters.txt_ and
+_Documentation/kdump/kdump.txt_ of the kernel source for more information.
+
+Enable kdump service
+~~~~~~~~~~~~~~~~~~~~
+The kdump runlevel script just loads the kdump kernel at boot. To enable it, use
+the YaST runlevel editor or simply
+
+--------------------------
+# chkconfig kdump on
+--------------------------
+
+on a shell. You can also execute it manually with +rckdump start+.
+
+Configure kdump
+~~~~~~~~~~~~~~~
+The default configuration should work out of the box. You can tweak several
+configuration options in the _/etc/sysconfig/kdump_ configuration file.
+
+[IMPORTANT]
+If you make changes in that configuration file, you always have to execute
+_rckdump restart_ manually to make that changes apply. If you don't, that
+changes will only apply after system reboot.
+
+See the section “CONFIGURATION” later and/or *kdump*(5) for a description of
+the configuration options.
+
+Load the kdump kernel
+~~~~~~~~~~~~~~~~~~~~~
+As mentioned above, the init script _/etc/init.d/kdump_ takes the part of
+loading the kdump kernel. As kdump kernel, the normal system kernel is used, no
+special kernel image is required.
+
+However, as initramfs, a special initramfs is built by *mkdumprd*(8). Normally,
+you don't have to take care about that step since the init script checks if the
+initramfs is up to date (reading the configuration file modification time) and
+rebuilds it if necessary.
+
+To manually load the kdump kernel (i.e, without the SUSE init script), you have
+to use the *kexec*(8) tool with the _-p_ (panic kernel) parameter like:
+
+--------------------------------------------------------------------
+# kexec -p /boot/vmlinuz-version --initrd=/boot/initrd-version-kdump
+--reuse-cmdline
+--------------------------------------------------------------------
+
+
+Testing
+-------
+It perfectly makes sense to test the kdump configuration in a sane system state,
+i.e. not when the system really crashes but to trigger the dump manually. To
+perform that, use the SysRq mechanism, i.e. just execute
+
+---------------------------------------
+# echo s > /proc/sysrq-trigger
+# echo u > /proc/sysrq-trigger
+# echo c > /proc/sysrq-trigger
+---------------------------------------
+
+After that, the panic kernel should boot and the dump should be saved.
+
+Configuration
+-------------
+
+The configuration file is _/etc/sysconfig/kdump_. Just edit this file with a
+plain text editor to adjust the settings. You can also use the YaST2 sysconfig
+editor. All variables are described in *kdump*(5). Here's a brief overview about
+some variables that are worth tweaking.
+
+Save Directory
+~~~~~~~~~~~~~~
+The most important setting is where the dump should be saved. Following methods
+are available:
+
+* local file,
+* FTP,
+* SFTP (SSH),
+* NFS,
+* CIFS.
+
+The recommendation is to use FTP or SFTP for network dumping or the local file
+dump. The configuration variable _KDUMP_SAVEDIR_ has to be filled with a URL to
+where the dump should be saved. The syntax is described in *kdump*(5).
+
+If the directory does not exist, it will be created. Since the dump is taken in
+initrd, the network and mount configuration is a bit different from the normal
+system. However, the *mkdumprd*(8) script is designed to do everything
+automatically for you. If you would like to use a special network interface, see
+the _KDUMP_NETCONFIG_ setting.
+
+Example:
+
+* +file:///var/log/dump+
+* +ftp://user@host:server/incoming/dumps+
+
+[NOTE]
+If you want to use SFTP with public key authentication, make sure to read the
+"Secure File Transfer Protocol" section in *kdump*(5).
+
+Deletion of old dumps
+~~~~~~~~~~~~~~~~~~~~~
+If you save the dumps to your local file system, you may want that kdump deletes
+automatically old dumps. Set _KDUMP_KEEP_OLD_DUMPS_ to the value how much old
+dumps should be preserved. To disable deletion of old dumps, set it to _0_, and
+to delete all old dumps, set it to _-1_.
+
+If the partition has less than _KDUMP_FREE_DISK_SIZE_ megabytes free disk space
+after saving the dump, the dump is not copied at all.
+
+[IMPORTANT]
+That two options don't apply to network dump targets.
+
+Dump Filtering and Compression
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The size of kernel dumps is uncompressed and unfiltered as large as your system
+has RAM. To get smaller files (for example, to send it to support), you can
+compress the whole dump file afterwards. However, the drawback is that the dump
+has to be uncompressed afterwards before opening, so the disk space needs to be
+there in any case.
+
+To use page compression which compresses every page and allows dynamic
+uncompression with the *crash*(8) debugging tool, set _KDUMP_DUMPFORMAT_ to
+_compressed_ (which is actually the default).
+
+To filter the dump, you have to set the _KDUMP_DUMPLEVEL_. Then not all memory
+is saved to disk but only memory that does not fulfil some criteria. I.e. you
+may want to leave out pages that are completely filled by zeroes as they don't
+contain any useful information. The following table lists for each
+_KDUMP_DUMPLEVEL_ the pages that are *skipped*, i.e. _0_ produces a full dump
+and _31_ is the smallest dump.
+
+'------------.----------.----------.-------------.---------.----------
+dump level zero page cache page cache private user data free page
+----------------------------------------------------------------------
+ 0
+ 1 X
+ 2 X
+ 3 X X
+ 4 X X
+ 5 X X X
+ 6 X X
+ 7 X X X
+ 8 X
+ 9 X X
+10 X X
+11 X X X
+12 X X X
+13 X X X X
+14 X X X
+15 X X X X
+16 X
+17 X X
+18 X X
+19 X X X
+20 X X X
+21 X X X X
+22 X X X
+23 X X X X
+24 X X
+25 X X X
+26 X X X
+27 X X X X
+28 X X X X
+29 X X X X X
+30 X X X X
+31 X X X X X
+----------------------------------------------------------------------
+
+Automatic Reboot and Error handling
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+If you want to have your machine rebooted automatically after the dump has been
+copied, set _KDUMP_IMMEDIATE_REBOOT_ to _yes_. The variable
+_KDUMP_CONTINUE_ON_ERROR_ controls if a shell should be opened if something goes
+wrong while saving the dump to be able to fixup manually. This is mostly for
+debugging.
+
+In production, use that only if you have a serial console since VGA console and
+keyboard is not reliable in kdump environment.
+
+Notification
+~~~~~~~~~~~~
+If you enable notification support, then you get an email after the dump has
+been copied (and before the _KDUMP_IMMEDIATE_REBOOT_ takes place). Because we
+don't have a mail server running in initrd where the mail has to be sent, you
+have to configure a SMTP server:
+
+* _KDUMP_SMTP_SERVER_ must hold a hostname (and an optional port, separated by a
+ colon) to a SMTP server.
+* _KDUMP_STMP_USER_ and _KDUMP_SMTP_PASSWORD_ must be set to username and
+ password if SMTP AUTH should be used, or empty otherwise (plain SMTP without
+ authentication will be used).
+
+Then an email will be sent to the address in _KDUMP_NOTIFICATION_TO_ (only one
+address possible) and _KDUMP_NOTIFICATION_CC_ (multiple addresses possible).
+
+
+Debugging options
+~~~~~~~~~~~~~~~~~
+If something goes wrong and you possibly opened a bug report, you may be asked
+to increase verbosity to report what's going wrong. Also, this is useful if you
+would like to find the cause yourself.
+
+At first, you can increase _KDUMP_VERBOSE_. The maximum log level is _15_. That
+gives both information when loading the dump kernel (i.e. the _rckdump start_
+command) and also when copying the dump in initrd.
+
+[WARNING]
+If you use a VGA console and trigger the dump when X11 is running (i.e. your
+graphical desktop), you might not see any output. Use a serial console in that
+case, or try to trigger the dump from Linux console (i.e. press _Ctrl-Alt-F1_
+in your graphical desktop and log in there).
+
+If the problem is the *makedumpfile*(8) filtering tool, then set
+_MAKEDUMPFILE_OPTIONS_ to _-D_ to get debugging output of makedumpfile.
+
+
+
+
+Bugs
+----
+Please report bugs and enhancement requests at https://bugzilla.novell.com[].
+
+Copying
+-------
+Copyright (c) 2008 Bernhard Walle . Free use of this software is
+granted under the terms of the GNU General Public License (GPL), version 2 or
+later.
+
+See also
+--------
+*kexec*(8), *kdump*(5), *makedumpfile*(8), *crash*(8)
+http://en.opensuse.org/Kdump[_http://en.opensuse.org/Kdump_]
+
+
+// vim: set sw=4 ts=4 et tw=80 fdm=marker: :collapseFolds=1:
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/doc/man/vmcore.5.html new/kdump-0.6.1/doc/man/vmcore.5.html
--- old/kdump-0.6.0/doc/man/vmcore.5.html 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/doc/man/vmcore.5.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,92 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>vmcore</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /></head><body><div class="refentry" lang="en" xml:lang="en"><a id="id212088"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vmcore — Kernel dump file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p>/var/log/dump/<span class="emphasis"><em><timestamp></em></span>/vmcore</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_description"></a><h2>DESCRIPTION</h2><p>A kernel crash dump provides the complete (or filtered) memory dump from the
-machine that crashed. Both <span class="strong"><strong>crash</strong></span>(8) and <span class="strong"><strong>lcrash</strong></span>(8) can be used to analyse
-kernel dumps. For the ELF dump format, <span class="strong"><strong>gdb</strong></span>(1) can also be used with some
-limitations.</p><p>To set up the machine to generate a dump when it crashes using kdump, see
-<span class="strong"><strong>kdump</strong></span>(7). That manual page describes the structure of various dump formats
-available. It's an implementation detail that you don't have to be familiar with
-when analysing kernel dumps. However, it's useful to have some documentation
-about that file formats.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_overview"></a><h2>OVERVIEW</h2><p>Following dump formats are currently known:</p><div class="variablelist"><dl><dt><span class="term">
-<span class="strong"><strong>ELF</strong></span>
-</span></dt><dd>
- This is the normal dump format used also for userspace core dumps.
-</dd><dt><span class="term">
-<span class="strong"><strong>Kdump compressed format</strong></span>
-</span></dt><dd>
- This format (with or without compression) is a diskdump-based format used
- by <span class="strong"><strong>makedumpfile</strong></span>(8) and supported by <span class="strong"><strong>crash</strong></span>(8) to represent kernel dumps in
- a more compact form than ELF dumps. It supports per-page compression.
-</dd><dt><span class="term">
-<span class="strong"><strong>LKCD</strong></span>
-</span></dt><dd>
- There are various versions of the LKCD format available. That has been used by
- the LKCD project (obsolete kernel patch) and the <span class="strong"><strong>lcrash</strong></span>(8) tool, but is also
- supported by <span class="strong"><strong>crash</strong></span>(8) and is still used by s390 dump tools.
-</dd><dt><span class="term">
-<span class="strong"><strong>Netdump</strong></span>
-</span></dt><dd>
- ELF format, used by RedHat's netdump. Not described here.
-</dd><dt><span class="term">
-<span class="strong"><strong>Diskdump</strong></span>
-</span></dt><dd>
- Like kdump compressed format, used by RedHat's diskdump. Not described here.
-</dd></dl></div></div><div class="refsect1" lang="en" xml:lang="en"><a id="_elf_core_dumps"></a><h2>ELF CORE DUMPS</h2><p>`See <span class="strong"><strong>core</strong></span>(5) for a general description about ELF core files, and
-<a class="ulink" href="http://lse.sourceforge.net/kdump/documentation/ols2oo5-kdump-paper.pdf" target="_top">http://lse.sourceforge.net/kdump/documentation/ols2oo5-kdump-paper.pdf</a> for the
-kdump-specific extensions.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_kdump_compressed_dumps"></a><h2>KDUMP COMPRESSED DUMPS</h2><div class="refsect2" lang="en" xml:lang="en"><a id="_file_structure"></a><h3>File structure</h3><pre class="literallayout"> File offset
-+------------------------------------------+ 0x0
-| main header (struct disk_dump_header) |
-|------------------------------------------+ block 1
-| sub header (struct kdump_sub_header) |
-|------------------------------------------+ block 2
-| 1st-bitmap |
-|------------------------------------------+ block 2 + X blocks
-| 2nd-bitmap | (aligned by block)
-|------------------------------------------+ block 2 + 2 * X blocks
-| page header for pfn 0 (struct page_desc) | (aligned by block)
-| page header for pfn 1 (struct page_desc) |
-| : |
-| page header for pfn Z (struct page_desc) |
-|------------------------------------------| (not aligned by block)
-| page data (pfn 0) |
-| page data (pfn 1) |
-| : |
-| page data (pfn Z) |
-+------------------------------------------+</pre></div><div class="refsect2" lang="en" xml:lang="en"><a id="_main_header"></a><h3>Main header</h3><p>The main header of the kdump compressed format is the almost same as the one of
-diskdump. This header has the following members, and the member signature and
-header_version are different from diskdump.</p><pre class="literallayout">struct disk_dump_header {
- char signature[SIG_LEN]; /* = "KDUMP " */
- int header_version; /* Dump header version */
- struct new_utsname utsname; /* copy of system_utsname */
- struct timeval timestamp; /* Time stamp */
- unsigned int status; /* Above flags */
- int block_size; /* Size of a block in byte */
- int sub_hdr_size; /* Size of arch dependent
- header in blocks */
- unsigned int bitmap_blocks; /* Size of Memory bitmap in
- block */
- unsigned int max_mapnr; /* = max_mapnr */
- unsigned int total_ram_blocks;/* Number of blocks should be
- written */
- unsigned int device_blocks; /* Number of total blocks in
- * the dump device */
- unsigned int written_blocks; /* Number of written blocks */
- unsigned int current_cpu; /* CPU# which handles dump */
- int nr_cpus; /* Number of CPUs */
- struct task_struct *tasks[0];
-};</pre></div><div class="refsect2" lang="en" xml:lang="en"><a id="_sub_header"></a><h3>Sub header</h3><p>The sub header of the kdump compressed format is original. This header
-has the member <code class="literal">phys_base</code> and <code class="literal">dump_level</code>. The member <code class="literal">phys_base</code> is for
-an x86_64 relocatable kernel, and the member dump_level has <code class="literal">-d</code> option's
-value of makedumpfile command.</p><pre class="literallayout">struct kdump_sub_header {
- unsigned long phys_base;
- int dump_level; /* header_version 1 and later */
-};</pre></div><div class="refsect2" lang="en" xml:lang="en"><a id="_1st_bitmap"></a><h3>1st-bitmap</h3><p>The bit of 1st-bitmap presents either a page on memory hole, or not. If a page
-is on memory hole, the corresponding bit is off. Otherwise, it is on.</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_2nd_bitmap"></a><h3>2nd-bitmap</h3><p>The bit of 2nd-bitmap presents either a dumpable page, or not. If a page is on
-memory hole or excluded by makedumpfile command, the corresponding bit is off.
-Otherwise, it is on.</p></div><div class="refsect2" lang="en" xml:lang="en"><a id="_page_header"></a><h3>Page header</h3><p>There are page headers corresponding to dumpable pages. This header presents
-the corresponding page information (compressed, or not. etc.)</p><pre class="literallayout">typedef struct page_desc {
- off_t offset; /* the offset of the page data*/
- unsigned int size; /* the size of this dump page */
- unsigned int flags; /* flags */
- unsigned long long page_flags; /* page flags */
-} page_desc_t;</pre></div></div><div class="refsect1" lang="en" xml:lang="en"><a id="_bugs"></a><h2>BUGS</h2><p>This manual page is incomplete.</p><p>Please report bugs and enhancement requests at <a class="ulink" href="https://bugzilla.novell.com" target="_top">https://bugzilla.novell.com</a>.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_copying"></a><h2>COPYING</h2><p>The description of the kdump compressed format was written by
-Ken'ichi Ohmichi <<a class="ulink" href="mailto:oomichi@mxs.nes.nec.co.jp" target="_top">oomichi@mxs.nes.nec.co.jp</a>>.</p><p>Rest was written by Bernhard Walle <<a class="ulink" href="mailto:bwalle@suse.de" target="_top">bwalle@suse.de</a>>.</p></div><div class="refsect1" lang="en" xml:lang="en"><a id="_see_also"></a><h2>SEE ALSO</h2><p><span class="strong"><strong>kdump</strong></span>(7), <span class="strong"><strong>makedumpfile</strong></span>(8), <span class="strong"><strong>crash</strong></span>(8), <span class="strong"><strong>gdb</strong></span>(1), <span class="strong"><strong>core</strong></span>(5)</p></div></div></body></html>
Files old/kdump-0.6.0/doc/man/vmcore.5.pdf and new/kdump-0.6.1/doc/man/vmcore.5.pdf differ
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/kdump-0.6.0/NEWS new/kdump-0.6.1/NEWS
--- old/kdump-0.6.0/NEWS 2008-08-07 11:53:43.000000000 +0200
+++ new/kdump-0.6.1/NEWS 2008-08-09 18:43:53.000000000 +0200
@@ -1,4 +1,8 @@
-0.7.0
+0.6.1
+-----
+ * add kdump(7) manual page
+
+0.6.0
-----
* add vmcore(5) manual page
* implement email support
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-commit+help@opensuse.org