Bug 67260
Summary: | new-kernel-pkg does not check mkinitrd success | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Eugene Kanter <ekanter> |
Component: | mkinitrd | Assignee: | Matt Wilson <msw> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | katzj |
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: | 2002-06-21 16:34:43 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
Eugene Kanter
2002-06-21 16:34:39 UTC
good point... new-kernel-pkg will no longer run grubby if mkinitrd returns an error More potential problems, please comment. Should mkinitrd query temporary filesystem type before it runs losetup on it? Since mkinitrd always (?) runs as root would be more appropriate to use $HOME or ~ for temporary files if losetup on /tmp or /var/tmp fails? Another question: What will happen if new-kernel-pkg will not run grubby but user typed rpm -U kernel-x.x.x ? Will new-kernel-pkg tell rpm that upgrade failed and old package can not be erased? |