Submitted 03-Aug-00 by Mike & Tracy Holt:
> I had switched back to ext2 filesystem for awhile so I could test the
> latest kernel releases, but I recently switched back to reiser for speed
> and now I'm stuck not being able use the latest kernel rpms. Is there
> something really simple that I'm missing?
I use exclusively custom compiled kernels to avoid needing an initrd, but
you should be able to modprobe loop before you do the kernel update. What
is probably happening (guesswork from what I've seen) is that you are doing
an rpm -U on the kernel package. This is a big "no-no" with kernels,
especially if you use an initrd. When you "Upgrade" an rpm, the files that
were part of the old version are deleted. This:
a) can prevent you from booting into your old kernel if needed
b) removes needed modules (like loop.o) that were part of the currently
running kernel, preventing you from using them after the upgrade.
If you do rpm -i instead, both kernels are on your disk (and in the rpm
database) and the modules still exist for you to use. Then, when you are
satisfied that the new kernel works well enough, you can rpm -e
kernel-<old-version>
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
