lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200609261525.k8QFP6j4022389@turing-police.cc.vt.edu>
Date:	Tue, 26 Sep 2006 11:25:06 -0400
From:	Valdis.Kletnieks@...edu
To:	linux-kernel@...r.kernel.org
Subject: Stupid kexec/kdump question...

OK, I'm running a Fedora Core 6 (rawhide actually) box with -18-mm1 kernel.
I've installed kexec-tools and similar, and am trying to get the kernels
built following the hints in Documentation/kdump/kdump.txt, but a few
questions arise:

1) Other than the fact that the Fedora userspace looks for a ${kernelvers}kdump
kernel, is there any reason the kdump kernel has to match the running one, or
can an older kernel be used?

2) I'm presuming that a massively stripped down kernel (no sound support,
no netfilter, no etc) that just has what's needed to mount the dump location
is sufficient?

3) The docs recommend 'crashkernel=64M@...', but that's 8% of my memory.
What will happen if I try '16M@...' instead?  Just slower copying due to
a smaller buffer cache space, or something more evil?


Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ