On Thu, Apr 26, 2007 at 01:16:39PM +0200, Jozef Uhliarik wrote:
Hi, I did update of UI. You can find new mock-ups on the http://en.opensuse.org/YaST/yast-kdump
We have following frames:
,---- Enable/Disable Kdump ---------------------------------, | | | (o) Enable kdump | | ( ) Disable kdump | | | .............................................................
,---- Boot Option (crashkernel) for Kdump ------------------, | | | (o) Add Boot Option | | ( ) Remove Boot Option | | | .............................................................
The frame "Boot Option (crashkernel) for Kdump" is clear it only adds or removes boot parameter "crashkernel". The change this option apply after reboot.
I interested in the frame Enable/Disable Kdump and logic for this frame. I would like only clarify from you logic for this frames and what is necessary to allow users.
1. user boots with crashkernel parameter: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - frame has selected "(o) Enable kdump" - user can disable kdump service via selecting "( ) Disable kdump"
Is it possible to disable kdump? Is it necessary to allow this operation users?
- kdump service is disabled "(o) Disable kdump" - user can enable kdump service via selecting "( ) Enable kdump"
Is it possible enable/start kdump in this case? Is it necessary to allow this operation users?
My opinion is only operation "(o) Disable kdump" and "(o) Remove Boot Option" has logic (necessary reboot) but this is question for you. :) You are expert for debugging kernel and kdump.
2. user boots WITHOUT crashkernel parameter: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ All changes in the frames "Boot Option (crashkernel) for Kdump" and "Enable/Disable Kdump" will be possible.
I prefer following operations:
i. "(o) Add Boot Option" and "(o) Enable kdump" (necessary reboot) ii. "(o) Remove Boot Option" and "(o) Disable kdump" (without reboot because kernel was sterted without "crashkernel" - present status)
Another combinations will be permitted.
If you want to add another combinations write me them please.
Hi Jozef, Looks like it is confusing for us the developers themselves. What if we just have "(o) Enable (o) Disable" option only. If the user selects "Enable" the tool can _display a message box_ conveying the user that the change will be in effect after a reboot. The config tool then puts the "crashkernel=" parameter in the kernel command line as per the memory reservation settings. And the kdump service is run while the OS is coming up through init script. I the user selects "Disable" The kdump service will be stopped and not run by defalt from the next oot onwards. Also, the next boot will not have he "crashkernel=" parameter.
Mock-ups don't include unclear widgets. If you finish, clarify or add new functionality for kdump you can write me about it and I add it into UI.
Provided some comments in the other thread. 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