Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
starting to use the 2.4.20 kernel yesterday and want to get rid of everything to do with old kernel to save space....got rid of source and old module directory, when does the actual kernel image stay at?? in /boot there is two files that have a .old extension but they are close to 1mb only....is the kernel that small?? Also, to make a new boot disk in slackware i just choose SYSLINUX option then point it to /boot/vmlinuz correct??? thanks
yeah the kernel is tiny... it has to be able to fit on a floppy disk after all.... any other modules compiled outside fo the kernel will be in /lib/modules/2.4.x/ which you can safely remove.
there is a list of everything in boot, everything is still using the 2.4.18 name, thats probably normal i guess?? so just the vmlinuz.old, and the System.old to go?? -thanks
I see
All files with an '@' are symbolic filelinks. They point to *.2.4.18. Just remove the symlinks (=@-files) and edit your lilo.conf:
image = /boot/vmlinuz
label = Slackware
image = /boot/vmlinuz.old
label = Old_kernel
So 'Slackware' ist your new kernel and 'Old_kernel' would boot your old kernel.
Don't forget to run 'lilo' after you edited your lilo.conf!
After you assumed that your new kernel works well, you can delete the old kernel and old kernelomdules (here too: don't forget to edit lilo.conf again!).
my kernel is 573,801. It has not been above 600K for a while.
smaller allows me to put both new and previous on diskette - I only boot from diskette.
small kernel = rebuild kernel with max use of modules and least amount of unneeded options (just say "N")
source = /usr/src/linux or /usr/src/*2.4.20 *
ok thanks i am just doing this pretty much for learning sake.....i figured everything out but one thing,
System.Old----->System.map-ide-2.4.18------not needed
vmlinuz.old------>vmlinuz-ide-2.4.18------not needed
config-------->config-ide-2.4.18----seems like not need
Where is my current kernel config file at??? the config-ide-2.4.18 is definetly from the old kernel because i even looked to see if some of the new features were in it, they werent....so i dont understand, where is the new kernel config??? -thanks
i used this guide to compile it http://p-two.net/modules.php?op=modl...=article&sid=5
I did everthing step by step except did a 'make oldconfig'. Said no to all the new things except for a module for the TI 83 graphing calculators......i looked in the 2.4.20 kernel source config and it was listed but its not in the /boot config (which still has the old kernels config), the module was made because i can load it. So i guess it really doesn't matter but should i copy it over?? or just leave it alone?? Im sure you can tell this was my first kernel compile so just trying to learn whatever i can from it and keep my system as tidy as possible. -thanks
I do prefer to have a bunch of kernels sitting in
/boot, so I can go back & forth, fool around with
configurations, which is why I don't use install
but rather manually copy my files and
symlink System.map and vmlinuz as required :}
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.