Thank you, I've found the instructions that I was looking for on their
web page. You're right, I have been doing the -U to bring the new
kernels in (in my mind I thought I was keeping things cleaned up).
Anyway, I've got things running now and I'll be a little more careful
next time.
Thanks again, Mike
Anton Graham wrote:
> 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>
>
--
====================
Mike & Tracy Holt
Kirkland, WA
[EMAIL PROTECTED]
[EMAIL PROTECTED]
====================
