2007-02-09 21:09:34 +00:00
|
|
|
.TH MKDUMRD 8 "Fri Feb 9 2007"
|
|
|
|
|
.SH NAME
|
|
|
|
|
mkdumprd \- creates initial ramdisk images for kdump crash recovery
|
|
|
|
|
.SH SYNOPSIS
|
2012-06-06 08:24:37 +00:00
|
|
|
\fBmkdumprd\fR [OPTION]
|
2007-02-09 21:09:34 +00:00
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
\fBmkdumprd\fR creates an initial ram file system for use in conjunction with
|
|
|
|
|
the booting of a kernel within the kdump framework for crash recovery.
|
|
|
|
|
\fBmkdumprds\fR purpose is to create an initial ram filesystem capable of copying
|
|
|
|
|
the crashed systems vmcore image to a location specified in \fI/etc/kdump.conf
|
|
|
|
|
|
|
|
|
|
\fBmkdumprd\fR interrogates the running system to understand what modules need to
|
|
|
|
|
be loaded in the initramfs (based on configuration retrieved from
|
|
|
|
|
\fI/etc/kdump.conf)\fR
|
|
|
|
|
|
2012-06-06 08:24:37 +00:00
|
|
|
\fBmkdumprd\fR add a new \fBdracut\fR module 99kdumpbase and use \fBdracut\fR
|
|
|
|
|
utility to generate the initramfs.
|
|
|
|
|
|
2007-02-09 21:09:34 +00:00
|
|
|
\fBmkdumprd\fR was not intended for casual use outside of the service
|
|
|
|
|
initialization script for the kdump utility, and should not be run manually. If
|
|
|
|
|
you require a custom kdump initramfs image, it is suggested that you use the
|
2011-04-26 13:48:49 +00:00
|
|
|
kdump service infrastructure to create one, and then manually unpack, modify and
|
2007-02-09 21:09:34 +00:00
|
|
|
repack the image.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.SH OPTIONS
|
|
|
|
|
.TP
|
2012-06-06 08:24:37 +00:00
|
|
|
All options here are passed to dracut directly, please refer \fBdracut\fR docs
|
|
|
|
|
for the info.
|
2007-02-09 21:09:34 +00:00
|
|
|
|
|
|
|
|
.SH "SEE ALSO"
|
2013-02-16 06:51:49 +00:00
|
|
|
.BR dracut (8)
|
