From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (Windows NT 5.0; U) Description of problem: The kernel-enterprise postinstall script doesn't update the module-info, System.map, and vmlinuz symlinks in /boot after installation. The normal kernel package does this. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Install kernel-enterprise RPM. 2.ls -l /boot 3. Actual Results: Symlinks still point to previous kernel version. Expected Results: Symlinks should be updated to point to new kernel version. Additional info: More of a random question, really: is there any reason not to have an 'initrd' symlink on systems with an initrd?
I'd argue that this is a bug in the normal package; these symlinks are made at boot time to point to the currently running kernel; all tools expect those files to point to the RUNNING kernel... a symlink to the initrd isn't useful (at least I never found any good use for it; if you know of any I'm curious ;)
I can see why System.map needs to match the running kernel. What uses module-info? depmod? I always understood the vmlinuz symlink to be a convenience so you didn't have to keep changing lilo.conf every time you upgraded the kernel. I suggested an initrd symlink in the same spirit. Is there another reason for vmlinuz?