[TriLUG] Help: Kernel Snafu? Used up2date to update kernel, now it panics. Probably common, but...

[William W. Ward]

Well, I made a boo boo.  I used up2date to drag down 2.4.9-34 against the
wishes of the skip list.  I checked the version of up2date, or so I thought,
and it said just "v" in response to "up2date --nox --version".  Now, Grub
lists two kernels to choose from, and the previous edition (the standard one
with the 7.2 distribution.)  The previous works fine.  But the new one
panics with "no init found" which is probably related to some modules not
playing along.

I'm currently digging through the "how to upgrade your Red Hat kernel" but I
have a couple questions I thought the group may be more enlightened on:

1.  If v2.5.4 of up2date or older editions cannot be used to update the
kernel, how can I be sure what version I'm using?  --version did not give me
a version number, just a "v" and a copyright date through 2001.  IF I have
an outdated up2date, how can I get a new one?

2.  How can I repair the kernel 2.4.9-32 so that it will operate as if it
were upgraded automatically by up2date, and how can I have my packages and
whatnot reflect properly on the Red Hat Network if I make a manual
adjustment that de-sync's it from the expected list?  I have added nothing
to the machine, and only used the errata and package updates to auto-update
the box.

Your help is appreciated,
Bill