Bug 87398 - new-kernel-pkg removes kernel when installing new one
Summary: new-kernel-pkg removes kernel when installing new one
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-26 17:18 UTC by Andrew Gormanly
Modified: 2007-04-18 16:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-06-11 03:48:19 UTC

Attachments (Terms of Use)

Description Andrew Gormanly 2003-03-26 17:18:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When installing a new kernel with e.g. 'rpm -ivh kernel-2.4.18-27.8.0',
/sbin/new-kernel-pkg removes the old kernel installed on the system.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm -ivh kernel-2.4.18-27.8.0
2. reboot a bit later

Actual Results:  The old kernel is gone.

Expected Results:  The two kernel RPMs should be installed at the same time, as
before (RH 4.2 - 7.3).

Additional info:

Lines 75-79 of /sbin/new-kernel-pkg are below.  79 is the offending line for
grub; there's a similar one for lilo.

        title="Red Hat Linux ($version)"
        /sbin/grubby --add-kernel=$bootPrefix/vmlinuz-$version $INITRD    \
                     --copy-default --title "$title"                \
                     --args="root=$rootdevice"                      \

This could really screw things up if the new kernel were broken.

Comment 1 Jeremy Katz 2003-03-28 00:05:47 UTC
That line out of new-kernel-pkg removes any old kernels from the config title
which would have used the exact same title (which is based on the kernel
version).  Are you sure you used -i instead of -U or -F?

Comment 2 Jeremy Katz 2003-06-11 03:48:19 UTC
Closing due to lack of activity.  Please reopen if you have further information
to add.

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