...but if it is, it should be documented, and it's not clear where you would
document this one, so let's call it a "surprising behavior".
I'm using the 6.0 installer to do network installs of a variety of
configurations that are somewhere between 6.0 and 6.1.
As such, I have my own comps file.
I wanted to use a different kernel in one configuration, so I moved "kernel"
from "base" to each separate configuration and then changed "kernel" to
"firewallkernel" in the one that I wanted to be different.
I stuck an RPM for firewallkernel in my RPMS directory, but it had a different
version number than the kernel RPM.
When I did the install, I got this:
* installed kernel version 2.2.12-20vircio
* installed kernel version 2.2.12-20vircio
* running: /bin/insmod /bin/insmod /modules/loop.o
* running: /sbin/mkinitrd /sbin/mkinitrd -f /boot/initrd-2.2.12-20vircio.img
--ifneeded 2.2.12-20vircio
* root is /mnt
* running: /bin/rmmod /bin/rmmod loop
where "2.2.12-20vircio" is the version number of "kernel", not of
"firewallkernel".
WHen I upped the RPM version of "kernel" to be the same as the RPM version of
"firewallkernel", it worked.
So in short, there's a rather surprising requirement that any RPM which
provides "kernel" needs to have the same version number as the RPM by that
name.
Chris
--
Chris Garrigues virCIO
http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com
+1 512 432 4046 +1 512 374 0500
4314 Avenue C
O- Austin, TX 78751-3709
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
