* Maneesh Soni <maneesh@in.ibm.com> [2007-06-14 11:27]:
On Thu, Jun 14, 2007 at 10:40:01AM +0200, Bernhard Walle wrote:
* Maneesh Soni <maneesh@in.ibm.com> [2007-06-14 10:31]:
This option is needed for the environments where the distribution couldnot generate the propoer initrd. I have seen cases like in a multipath IO environment, one has to create an initrd manually. So, if the uses knows how to create an initrd, they can use this option and still save the dump automatically, without too many changes in dump saving mechanisms.
In such cases, just symlink the normal kernel to a kdump kernel, create a initrd manually for that kernel and specify that kernel in the configuration. No need for an extra option.
ok.. creating symlink should work.. but by "specify that kernel in the configuration" you mean manually edit the /etc/sysconfig/kdump file? or use some facility in yast-kdump?
Would a YaST text field with the kernel configurable (KDUMP_KERNELVER) ok? Thanks, Bernhard -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org