On Thu, Jun 14, 2007 at 09:50:19AM +0200, Bernhard Walle wrote:

Hi,

Thanks for your suggestions!

* Maneesh Soni [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

On Thu, Jun 14, 2007 at 10:40:01AM +0200, Bernhard Walle wrote:

* Maneesh Soni [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? 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

On Thu, Jun 14, 2007 at 01:55:28PM +0200, Bernhard Walle wrote:

* Maneesh Soni [2007-06-14 11:27]:

...

On Thu, Jun 14, 2007 at 10:40:01AM +0200, Bernhard Walle wrote:

...

* Maneesh Soni [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?

I think so. As you said it should be useful to set KDUMP_KERNELVER. 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

On Thu, Jun 14, 2007 at 11:39:04AM +0200, Jozef Uhliarik wrote:

Hello Maneesh

see my comments below please.

...

Hi Jozef

There are few more changes which I think would be good to have. Please let me know if these are possible to make or not.

1. Start-up ----------- Please move the "kdump memory" settings from "Dumping" screen to "Start up". As, IMHO, the start-up setting should have the minimum things which are absolutely necessary for enabling kdump service. Without reserving memory one cannot enable kdump.

Yes, I will do it.

Great.. thanks.

...

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. Secondly, for NFS, I think "Share" is not needed.

Yes of course. I did some changes but I forgot update screen shots. :(

"Raw Disk" is in "Expert Settings" and doesn't include "Directory for saving Dumps" now.

Bernahrd has clarified the Raw Disk option to me. I think lets leave it in "Dump Target Settings" and as Bernhard says, we do need the option to specify the ultimate directory where the dump will be saved eventually.

...

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.

I try to replace "No. of Old Dumps" but it depend on space.

hmm.. actually I think this is one of the options which may not be used too often.

Custom kdump kernel initrd is for discussion with Mr. Walle.

...

4. Dump-filtering ----------------- I think we should either merge this with "Dump Target Settings" or if there is not much space left there, then a separate screen.

Please let me know if these make sense or not.

"Dump filtering" has different UI and name ("Dump Level) now. My opinion is that it is not good idea merge it with "Dump Target Settings". There is problem with space. I prefer separate screen for this option.

ok..

I will update screen shots today or tomorrow. I will inform you about it. I hope that it will be better. :)

Thanks again.. I appreciate it. 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

* Jozef Uhliarik [2007-06-15 13:15]:

you can find new screen shots in http://en.opensuse.org/YaST/yast-kdump

Some remarks: - Dump Level It's not clear if a [X] means if that pages are included or excluded. Please add some label about this (not in tooltip or in help text). - Dump Target This is wrong. The saving target is _independent_ of the partition (initrd based saving). Because pictures say more then words, I made some drawings at http://www.bwalle.de/temp/kdump/index.html. I hope it's clear now what I want. Please make the combo box for the partition editable. The user should be able to enter any string he wants additional to use an item from the combo box. Please also display the Linux partition naming in brackets or whatever way you like. And make clear that the user doesn't have any port here, or enter the default port (-> /etc/services). Also, make sure that only numbers are allowed here, a spin box would be an option. - Expert Settings The user should not be able to choose the initrd but the kernel. The naming scheme is: /boot/vmlinu[zx]-[.gz] The user should only enter kernel_string in the GUI. If you implement a file dialog, strip out the rest and give a warning if the scheme doesn't match. The initrd is _always_ /boot/initrd- If the user wants to reuse a kernel, he can symlink. I think users that have the experience how to build a custom initrd know how to use symlink properly. :-) Thanks, Bernhard -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Hello, * Maneesh Soni [2007-06-15 20:20]:

On Fri, Jun 15, 2007 at 01:15:14PM +0200, Jozef Uhliarik wrote:

...

you can find new screen shots in http://en.opensuse.org/YaST/yast-kdump

"Dump Level" is new version of "Dump filtering".

Best regards

Thanks for doing this again. It is coming in right shape.

I think we're getting very close to the best, ultimate kdump configuration tool. :-)

| | | +-- Kdump kernel Run level ---------------------------------+ | | | +--------------------+--+ | | | | |1 - Single User Mode| V| [] Enable Immediate Reboot | | | | +--------------------+--+ After Saving the dump | | | | | | | +-----------------------------------------------------------+ | | |

If we move this to the expert dialog, we should make sure that we have network if the user chooses a network dump target. Maybe just a dialog that asks the user if he wants to change the runlevel? Or changing the runlevel automatically? Thanks, Bernhard -- SUSE LINUX Products GmbH Tel. +49 (911) 74053-0 Maxfeldstr. 5 GF: Markus Rex 90409 Nürnberg, Germany HRB 16746 (AG Nürnberg) OpenPGP DDAF6454: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Hello, New screen shots are available. You can find it there http://en.opensuse.org/YaST/yast-kdump I didn't apply your hints and comments exactly. You can find there some differences. Maybe you don't agree with me and maybe you want to change something else. Please write me your comments. Best regards Jozef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

hello,

In http://en.opensuse.org/Image:Kdump_dump_expert_08.jpg: Please change "custom kernel initrd" to "custom kernel" since there's only a KDUMP_KERNELVER variable in /etc/sysconfig/kdump.

O.K. I will do it.

In http://en.opensuse.org/Image:Kdump_dump_target_nfs_08.jpg: The list of disks shouldn't be grayed out if the checkbox is set.

yes my fault :( I will correct it. Best regards Jozef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Hello,

In dump filtering screen (http://en.opensuse.org/Image:Kdump_dump_filtering_08.jpg) the header should say "Exclude from dumping" instead. As these options will make selected type of pages filtered out of the dump.

I know that man page says X = exclude... My implementation is reversed. X = include... It is not typical operation (for user): "select the pages which can not be in dump." Finally: I read/save the value correctly. It is only reversed UI implementation. If you wish exact solution similar with man page I can modify it. It is not a lot of work. Best regards Jozef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Dňa Po 9. Júl 2007 11:11 Bernhard Walle napísal:

* Jozef Uhliarik [2007-07-09 11:15]:

...

It is not typical operation (for user): "select the pages which can not be in dump."

It's ok for me, but I would select all per default. The user can unselect it then on demand.

O.K. :) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org