Bug 54045
Summary: | kernel-enterprise doesn't update symlinks in /boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Dalbec <jpdalbec> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | shishz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-07 18:09:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Dalbec
2001-09-26 15:59:22 UTC
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? |