Ambrogio wrote:
Hi all,
yesterday I was able to update my Fedora Core 5.
For first I updated yum
May 08 12:28:41 Updated: yum.noarch 2.6.1-0.fc5
After that I run the yum update --exclude=openoff* and in the log I
found:
May 08 13:44:00 Installed: kernel-devel.x86_64 2.6.16-1.2111_FC5
May 08 13:45:04 Installed: kernel.x86_64 2.6.16-1.2111_FC5
In the same time yum removed the older kernel.
The query in the rpm database first of update was
kernel-2.6.16-1.2080_FC5.x86_64.rpm
kernel-2.6.16-1.2096_FC5.x86_64.rpm
kernel-devel-2.6.16-1.2080_FC5.x86_64.rpm
kernel-devel-2.6.16-1.2096_FC5.x86_64.rpm
and after the update is
kernel-devel-2.6.16-1.2111_FC5
kernel-2.6.16-1.2111_FC5
kernel-devel-2.6.16-1.2096_FC5
kernel-2.6.16-1.2096_FC5
The problem is that grub.conf is unchanged, and in the /boot directory I
don't find nothing about the 2111 kernel, but I find all about the 2080
that I think are to be removed.
Someone is in the same situation?
The rpm -e of all about the 2111 and the rpm -I of the last kernel is a
good solution?
Tnx
Ambrogio
P.S.
Why yum is removing the older kernel?
High jacking a thread here... Thats one of the reasons I don't like yum
putzing with my grub.conf.
At home, I've been building the latest Linus or Greg KH kernels from
scratch, and I've found that there does not seem to be a maximum number
of entries in my grub.conf, so I only clean house when the /boot
partition is pretty well filled up, meaning there are probably 20+
entries in my grub.conf at any one time.
To me, editing grub.conf is a no-brainer, and it stays a heck of a lot
neater appearing than when yum does it.
So my question then is: Can yum be told to dl and install the new
kernels but leave grub.conf alone, and not remove the older kernel?
--
Cheers, Gene
