pool/kexec-tools
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/kexec-tools?expand=0&rev=19

Browse Source
This commit is contained in:
OBS User unknown 2007-04-13 14:35:12 +00:00 committed by Git OBS Bridge
parent 95b3d1f646
commit 4fcc54c939
4 changed files with 32 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.SUSE
View File

@ -257,19 +257,22 @@ root file system is corrupted.
- KDUMP_DUMPDEV
Specifies the dump device that is used for saving the dump in the kdump
kernel. You don't need to specify a dump device here. Then the dump is
written to KDUMP_SAVEDIR when booting from the kdump kernel.
Specifies the dump device that is used for saving the dump with the kdump
kernel. The dump device normally is a disk partition. You don't need to
specify a dump device here. Then the dump is written to KDUMP_SAVEDIR when
booting from the kdump kernel.
If KDUMP_DUMPDEV points to a device file, the dump is written to that
device when booting from the kdump kernel. The advantage over is that
you don't have to mount the root file system (which may be corrupted!)
just to write the dump. On the first normal boot which is able to
successfully mount the root file system, the dump is saved to
If KDUMP_DUMPDEV points to a device file, the dump is written to that device
when running the kdump kernel. The advantage over writing the dump to
disk immediately is that you don't have to mount the root file system (which
may be corrupted!) just to write the dump. So if the root file system is
corrupted, you have the chance to fix the file system manually and reboot the
system without loosing the dump information. On the first normal boot which
is able to successfully mount the root file system, the dump is saved to
KDUMP_SAVEDIR as usual.
Important: The KDUMP_DUMPDEV is overwritten by kdump, so don't use it
for saving any data. Also don't use the currently used swap partition.
Important: The KDUMP_DUMPDEV is overwritten by kdump, so don't use it for
saving any data. Also don't use the currently used swap partition.
- KDUMP_KEEP_OLD_DUMPS

5
kexec-tools.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Fri Apr 13 13:55:45 CEST 2007 - bwalle@suse.de
- improved documentation of KDUMP_DUMPDEV (#264050)
-------------------------------------------------------------------
Mon Apr 2 12:24:46 CEST 2007 - rguenther@suse.de

4
kexec-tools.spec
View File

@ -19,7 +19,7 @@ Requires: %insserv_prereq %fillup_prereq
Autoreqprov: on
Summary: Tools for fast kernel loading
Version: 1.101
Release: 90
Release: 92
Source: %{name}-%{package_version}.tar.bz2
Source1: kdump
Source2: sysconfig.kdump
@ -124,6 +124,8 @@ true # ignore errors
%{_sbindir}/kdump-helper
%changelog
* Fri Apr 13 2007 - bwalle@suse.de
- improved documentation of KDUMP_DUMPDEV (#264050)
* Mon Apr 02 2007 - rguenther@suse.de
- add zlib-devel BuildRequires
* Tue Mar 20 2007 - bwalle@suse.de

18
sysconfig.kdump
View File

@ -112,15 +112,19 @@ KDUMP_FREE_DISK_SIZE=64
## Type: string
## Default: ""
#
# Specifies the dump device that is used for saving the dump in the kdump
# kernel. You don't need to specify a dump device here. Then the dump is
# written to KDUMP_SAVEDIR when booting from the kdump kernel.
# Specifies the dump device that is used for saving the dump with the kdump
# kernel. The dump device normally is a disk partition. You don't need to
# specify a dump device here. Then the dump is written to KDUMP_SAVEDIR when
# booting from the kdump kernel.
#
# If KDUMP_DUMPDEV points to a device file, the dump is written to that device
# when booting from the kdump kernel. The advantage over is that you don't have
# to mount the root file system (which may be corrupted!) just to write the
# dump. On the first normal boot which is able to successfully mount the root
# file system, the dump is saved to KDUMP_SAVEDIR as usual.
# when running the kdump kernel. The advantage over writing the dump to
# disk immediately is that you don't have to mount the root file system (which
# may be corrupted!) just to write the dump. So if the root file system is
# corrupted, you have the chance to fix the file system manually and reboot the
# system without loosing the dump information. On the first normal boot which
# is able to successfully mount the root file system, the dump is saved to
# KDUMP_SAVEDIR as usual.
#
# Important: The KDUMP_DUMPDEV is overwritten by kdump, so don't use it for
# saving any data. Also don't use the currently used swap partition.