DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just did an 'aptitude dist-upgrade' command and everytime a new kernel is released, it keeps wanting to install the 486 version(linux-image-2.6.22-1-486). I don't want that version I want the k7 version, I have been manually installing the k7.
I tried the 'aptitude hold linux-image-2.6.22-1-486' command but everytime I do dist-upgrade, it keeps saying the 486 image will be installed.
What am I doing wrong and what is the correct way to hold or stop Sid from installing the 486 kernel image?
You may have the wrong virtual package installed. linux-image-2.6-486 always depends on the latest 486 kernel image, and when the virtual package is upgraded, it automatically pulls in the next 486 image.
So, remove linux-image-2.6-486 and install linux-image-2.6-k7 and future dist-upgrades should pull in the latest k7 image instead.
You can quickly check what kernels are installed, then remove the ones you do not need. Such as the 486 kernel image.
aptitude search linux-image | grep -F 'i '
Code:
it-etch:~# aptitude search linux-image | grep -F 'i '
i linux-image-2.6-686 - Linux kernel 2.6 image on PPro/Celeron/PII
i linux-image-2.6.18-4-686 - Linux 2.6.18 image on PPro/Celeron/PII/PII
it-etch:~#
So, remove linux-image-2.6-486 and install linux-image-2.6-k7 and future dist-upgrades should pull in the latest k7 image instead.
I would be concerned about the order of this process. Granted, I've not done this, as I use custom compiled kernels, but wouldn't it be best to install the k7 image and boot to it before removing the 486 image?
You definitely should not remove the kernel you are currently using. On the plus side, I think that apt-get or aptitude might not actually let you do that. Still, don't try. It's also not a terrible idea to leave an extra kernel installed until you are very sure that you're happy with the new one. I often have four or five installed and in my GRUB menu list. It shouldn't hurt you, but you may have to be careful when you boot to make sure to boot the one you mean to rather than just the first one in the list.
The packages I mentioned are virtual packages and are the cause of the original problem, removing them should do no harm. But I was talking about apt-get, aptitude may very well try to remove the actual image (automatically installed by the virtual package) too. Better safe than sorry, do not attempt it in that order.
PS: You can remove the running kernel via apt, but not without a (humourous?) warning.
---------
You are running a kernel (version version) and attempting to remove the same version. This is a potentially disastrous action. Not only will /boot/vmlinuz-version be removed, making it impossible to boot it, (you will have to take action to change your boot loader to boot a new kernel), it will also remove all modules under the directory /lib/modules/version. Just having a copy of the kernel image is not enough, you will have to replace the modules too.
I repeat, this is very dangerous. If at all in doubt, answer Yes. If you know exactly what you are doing, and are prepared to hose your system, then answer No.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.