https://bugzilla.novell.com/show_bug.cgi?id=300124#c5 --- Comment #5 from Olaf Dabrunz <odabrunz@novell.com> 2007-08-28 12:28:28 MST --- Ah, the code is run in the running system. Are the following steps followed to save the changed parameter: When this function is called, the bootloader configuration must have been read in (Bootloader::Read()). Then the kernel commandline parameter can be changed. Afterwards, the bootloader configuration must be written again (Bootloader::Write()). Does the module actually make the user aware that his bootloader configuration will be rewritten, that possibly the initrds will be recreated (with the current implementation, if at all, then for all kernels in the bootloader configuration), and that the stage1 bootloader code may be re-installed on his disk(s)? Also, please note that Bootloader::setKernelParam (Bootloader::getDefaultSection (), "crashkernel", crash_value); will set this parameter on the default section, which may be any section, e.g. containing a XEN kernel or even memtest86 or any other kernel of the user's choice. bwalle@, what happens if the user removes RAM from the system so that a previously set "crashkernel" value would need to allocate too much RAM during next boot and the system cannot start up? Does the kernel ignore this value then, does it stop booting or does it crash? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.