Bug 27318
Summary: | After Updating Kernel with up2date, system never gets past | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jonathan J. Miner <miner> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-13 20:16:54 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
Jonathan J. Miner
2001-02-13 02:25:54 UTC
This is a problem in up2date Actually, what happened was that up2date did an upgrade so the old kernel was deleted, and didn't create a ramdisk or update lilo. Of course, it is my fault for doing this and not paying attention to these issues, but if it's going to be available via up2date, there should be some warning. It's available via up2date so that those who download via up2date without doing an upgrade can get it. |