Maneesh Soni wrote:
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.
Yes, this would be even better. Less fantasy, more reality :) User doesn't need to tune everything, some features might be a bit complicated inside the logic layer but UI should be simple as possible. Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic