Nick,
did anyone ever reply to you on this one? (I haven't seen one here but you may have got one off-list).
Keith
On Fri, 16 Jan 2004 12:10:35 +0000 Nick Heppleston nickheppleston@gmx.co.uk wrote:
Morning all, Hope you can help. Started playing with Debian after deciding it was time I got upto speed with it. I've just gone for an 'apt-get update' and 'apt-get upgrade' and received the following warning (see below).
Could anyone help decipher it for me. As far as I can see i'm running kernel 2.4.18-1-386 already, so how come the apt-get upgrade command wants to upgrade my kernel to the current version?
Any help would be greatly appreciated.
Cheers, Nick
<snip> You are attempting to install a kernel image (version 2.4.18-1-386) However, the directory /lib/modules/2.4.18-1-386 still exists. If this directory belongs to a previous kernel-image-2.4.18-1-386 package, and if you have deselected some modules, or installed standalone modules packages, this could be bad. However, if this directory exists because you are also installing some stand alone modules right now, and they got unpacked before I did, then this is pretty benign. Unfortunately, I can't tell the difference.
If /lib/modules/2.4.18-1-386 belongs to a old install of kenel-image-2.4.18-1-386, this is your last chance to abort the installation of this kernel image (nothing has been changed yet).
If this directory is because of stand alone modules being installed right now, or if it does belong to an older kernel-image-2.4.18-1-386 package but you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question.
Otherwise, I suggest you move /lib/modules/2.4.18-1-386 out of the way, perhaps to /lib/modules/2.4.18-1-386.old or something, and then try re-installing this image.
</snip>
-- Nick Heppleston 07989 581766 | nickheppleston@gmx.co.uk
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!