I've been running 7.2 for a couple of months now (2.2.17). Yesterday,
while doing the MandrakeUpdate, it told me 2.2.19 was available and
recommended, due to a number of security issues. I did the update of the
kernel, sources, etc. Now, several hours later, I've finally managed to
restore my system to usability (back on 2.2.17). Issues that came up:
1. The kernel source tree was unusable. Attempts to do menuconfig failed
due to tk segv'ing. Attempts to do xconfig failed due to a number of
(apparently) missing config files pertaining to ipsec and other
security things.
2. I've been running 100% reiserfs since the 2nd day on 2.2.17, and was
chagrined to discover that the 2.2.19 package apparently didn't
include a 2.2.19 initrd image, and attempting to use the 2.2.17
image didn't work, since the reiserfs module wouldn't load under
the 2.2.19 kernel, so the root FS couldn't load. I managed to get
around this by uncompressing the 2.2.17 image, loopback mounting
it, copying in a 2.2.19 reiserfs module, etc...
3. Apparently as part of the rpm "upgrade", my 2.2.17 kernel source
tree was rendered unusable. i.e. makefiles, etc were removed so
that I couldn't even build a new 2.2.17 kernel or modules.
4. One of my older IDE drives started having odd messages printed
out (about timeouts and such) - never a problem under 2.2.17.
#4 may be a random (harmless?) bug. #3 might have conceivably have
been something I did wrong (don't see how, though, as all of the
2.2.17 /lib/modules stuff was also deleted as part of the "upgrade".
#2 sounds like a build booboo (if you're upgrading a system from
2.2.17 to 2.2.19, most likely the modules in the old initrd
image won't be usable by the new kernel, no?)
#1 is just plain bogus. Didn't anyone do basic regression testing
before releasing this???
