Package: kernel-package Version: 9.008.4 Severity: minor I had no kernel package installed at all, and when I installed one, I was told that we're being reinstalled AND updated. Obviously, neither is true.
| Not touching initrd symlinks since we are being reinstalled (2.6.12-10) | Not updating image symbolic links since we are being updated (2.6.12-10) (Yes, I was running the kernel that I was installing; basically, I purged and then reinstalled the package.) Full transcript: [ purge kernel stuff ] 619:[EMAIL PROTECTED]: ~] ls -la /boot total 19 drwxr-xr-x 5 root root 1024 2005-11-01 06:52 . drwxr-xr-x 24 root root 4096 2005-11-01 05:58 .. lrwxrwxrwx 1 root root 15 2005-05-25 19:35 debian.bmp -> /boot/sarge.bmp drwxr-xr-x 2 root root 1024 2005-11-01 06:52 grub drwx------ 2 root root 1024 2005-05-25 20:20 keys drwx------ 2 root root 12288 2005-05-25 17:23 lost+found 620:[EMAIL PROTECTED]: ~] sudo apt-get install linux-image-2.6.12-1-686 Reading package lists... Done Building dependency tree... Done Suggested packages: linux-doc-2.6.12 lilo The following NEW packages will be installed: linux-image-2.6.12-1-686 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/16.7MB of archives. After unpacking 48.6MB of additional disk space will be used. Selecting previously deselected package linux-image-2.6.12-1-686. (Reading database ... 104500 files and directories currently installed.) Unpacking linux-image-2.6.12-1-686 (from .../linux-image-2.6.12-1-686_2.6.12-10_i386.deb) ... You are attempting to install a kernel image (version 2.6.12-1-686) However, the directory /lib/modules/2.6.12-1-686 still exists. If this directory belongs to a previous linux-image-2.6.12-1-686 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 not tell the difference. If /lib/modules/2.6.12-1-686 belongs to a old install of linux-image-2.6.12-1-686, then 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 linux-image-2.6.12-1-686 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.6.12-1-686 out of the way, perhaps to /lib/modules/2.6.12-1-686.old or something, and then try re-installing this image. Do you want to stop now? [Y/n]n Setting up linux-image-2.6.12-1-686 (2.6.12-10) ... You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.12-1-686). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.6.12-1-686/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. Please Hit return to continue. Not touching initrd symlinks since we are being reinstalled (2.6.12-10) Not updating image symbolic links since we are being updated (2.6.12-10) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.12-1-686 Updating /boot/grub/menu.lst ... done -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]