SlackwareThis Forum is for the discussion of Slackware 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.
What I'd like to do is remove the generic kernel and leave the huge kernel and the current kernel. I looked around and everything is usually for Ubuntu based distros or Fedora and Redhat. I'd like some information on how to add and remove kernels easily for the future as well.
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-huge-3.14.13
root = /dev/sdb1
label = 31413
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb1
label = Linux
read-only
# Linux bootable partition config ends
I colored the sections corresponding to the kernel entries. Basically you delete any entry that you don't want, then run lilo to take change in account.
Be carefull when editing this file as some error (kernel names for example) could make the system unbootable, nothing that can not be fixed though
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-huge-3.14.13
root = /dev/sdb1
label = 31413
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb1
label = Linux
read-only
# Linux bootable partition config ends
I colored the sections corresponding to the kernel entries. Basically you delete any entry that you don't want, then run lilo to take change in account.
Be carefull when editing this file as some error (kernel names for example) could make the system unbootable, nothing that can not be fixed though
I meant deleting a kernel from the system fully. Not the entry if that helps to simplify
As root you use removepkg to remove kernel-generic-version and kernel-modules-version, delete the unneeded part of lilo.conf, run lilo, and you should be good.
Don't remove the 'kernel-modules' package unless you're also uninstalling the corresponding 'huge' kernel. The 'huge' kernel isn't completely monolithic: it shares some of the same modules with the 'generic' kernel.
As for removing just the 'kernel-generic' package on its own, I wouldn't bother. As Kenobi would say, "This little one isn't worth your effort.".
Don't remove the 'kernel-modules' package unless you're also uninstalling the corresponding 'huge' kernel. The 'huge' kernel isn't completely monolithic: it shares some of the same modules with the 'generic' kernel.
As for removing just the 'kernel-generic' package on its own, I wouldn't bother. As Kenobi would say, "This little one isn't worth your effort.".
Thanks for pointing this out. I didn't realize huge used modules (I've never used huge myself).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.