Bug 16670 - kernel installation problem
kernel installation problem
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.2
All Linux
low Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-21 06:36 EDT by thomas.mangin
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-23 12:47:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description thomas.mangin 2000-08-21 06:36:51 EDT
I wonder why you are not automaticly creating the initrd file after a 
kernel installation as it can leave the system in a reallly broken state.

kernel RPM can be installed too with a -U option, as a consequence the old 
kernel is removed and mkinitrd can not be used anymore as loop.o was 
deleted !

RPM spec files would perhaps benefit of a way to restrict install option 
(install only, update only or install & update).
Comment 1 Michael K. Johnson 2000-08-21 10:15:38 EDT
Our current source tree does a modprobe loop in the preinstall
so that the loop module will be loaded and mkinitrd will work.
Comment 2 Need Real Name 2001-02-22 18:58:27 EST
I just upgraded my kernel with rpm's -U option from both 2.2.14-5 and 2.2.16-
22smp to the 2.2.17-14smp. Immediately afterwards, an lsmod showed no loop 
module loaded.
Comment 3 Michael K. Johnson 2001-02-23 12:47:43 EST
Oops.  I only added it for the uniprocessor kernel before.  I have
just added that for the smp and enterprise kernels as well.  Will
be fixed in the next 2.2 kernel we release.  Thanks for pointing
this oversight out.
Comment 4 Michael K. Johnson 2001-12-06 12:28:20 EST
Since we have released errata kernels after my last comment, I am
closing this bug report.

Note You need to log in before you can comment on or make changes to this bug.