From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Description of problem: Since the kernel-kdump (or whatever is the package needed for kdump) is not installed by network installer, there shouldn't be any Snnkdump scripts in /etc/rc.d/rcn.d/. Those scripts should probably be a part of kernel-kdump package. Version-Release number of selected component (if applicable): kernel-2.6.14-1.1632_FC5 How reproducible: Always Steps to Reproduce: 1. Install FC5 from network (development repo) 2. Boot 3. Look at boot-time messages Actual Results: Error below. Expected Results: No errors. Additional info: Starting kdump: No kdump kernel image found. Tried to locate /boot/vmlinux-2.6.14-1.1632_FC5kdump
Until this is taken care of, would you recommend to install the kdump kernel, or rename S20kdump files to K99kdump? I've done anything w/ kdump, and i'd rather not have stuff that could introduce fragility. Not sure if kdump would be in fragile or anti-fragile category, despite its apparent value in debugging kernel panics. Would kdump kernel make file system corruption recoveries easier, for instance, or would it just tell me "This is why file system is now corrupted: ..."?
The init script is part of the kexec-tools package. Running the init script when the kdump kernel isn't found is not going to destabilize your machine. The init script will eventually go away, replaced by logic in mkinitrd. As such, just chkconfig off kdump and you should be fine. I'll let Thomas decide whether to change the default to off.
kexec-tools 1.101 resolves this issue by now reporting a warning instead of an error in case the kdump kernel image cannot be found.