On Thu, Jun 14, 2007 at 09:50:19AM +0200, Bernhard Walle wrote:
Hi,
Thanks for your suggestions!
* Maneesh Soni <maneesh@in.ibm.com> [2007-06-14 09:39]:
2. Save Dump Image ----------------- IMHO, we can rename the tittle to something like "Dump Target Settings". The other options looks great. Only a couple of issues, firstly, in case of "Raw Disk", I think the "Directory for saving Dumps" is not needed.
It is. The raw disk is used to save the dump away in the initrd. Without any filtering (makedumpfile), just raw. After the first reboot (where a power off can be in between, i.e. some fixing of the file system from a resue system), the kdump script saves the dump away from the raw disk to the specified directory.
ok.. I see it now. Thanks for the clarification.
Secondly, for NFS, I think "Share" is not needed.
That's true. It was my fault. I'll change it in my backend scripts.
3. Expert Settings ------------------ IMHO, this tab should contain all the settings which normally user will not change. Apart from kdump kernel command like options, we can move the setting wrt "No. of Old Dumps" from "Dumping" screen to expert settings. Also can we put one more option to use a custom kdump kernel initrd which can be used save/process the dump.
Well, it it _really_ needed that you can specify a custom initrd here? We already have initrd based kdump saving (see above), and implementing too much logic can also be confusing.
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. Thanks Maneesh -- Maneesh Soni Linux Technology Center, IBM India Systems and Technology Lab, Bangalore, India -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org