Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hi, new to Linux (couple months and new to this forum)
already In grub after a couple of months I have 3 versions of fedora 3.
due to kernel updates through Yum.
What steps do I need to take to clean up the older versions of the kernel as far as routine maintenance of my system.
I assume I can edit the reference to older ones out of grub.conf, but also what old kernel files can I/Do I need to clean up and get rid of?
thx , dan
experimenting with the kernel is a serious issue..........i usually have bad luck when it comes to compiling a new kernel
i don't really know how you can clean the older version............i know that each kernel version has its own two or three folders named after the version...........i guess all you do is just delete the folders........not sure though
--------------------------------------
the safest way to get around kernel problems is to make an image of your root partition, before compiling a new kernel...............you can use norton ghost for instance..............place that image in a safe partition.........then you can restore your old system withing 5 min or less, in case you damage your system
i do this for windows with ntfs partition............i don't know if norton ghost can recognize ext2/3 partitions
no, I am not compiling it myself. I am just allowing yum to do the update.
I suspect there is also probably commands to make Yum clean up the older kernel just don't know what it is.
husnos, that is such overkill to be "safe". All you need to do is save your old vmlinuz image as a seperate file before copying over the freshly compiled one. Then edit your boot manager (such as lilo) to point to each image, that way if your new one doesn't work you can fall back to the old one. Saves having to do all that extra (unnecessary) work.
Daniel49, if you look in /usr/src/ you can see each linux-x.x.x folder, as well as a linux folder symlinked to one of the versioned ones. I've safely removed an older version folder here completely and had no problems. Just make sure your new kernel is working 100% as you expect (try plugging in USB devices, test sound and graphics drivers, etc.)
inside /boot I have config-original ver
initrd-original ver
systemmap-original ver
vmlinuz-original ver (4 files)
all of the above first kernel update (4 files)
and finally all of the above 2nd kernel update. (4 files)
inside of /usr/src there are no files.
so if I delete the reference in grub to original and delete the config-orig,initrd-orig,system map-orig, and vmlinuz-orig.
that would that be safe and all the cleanup that is necessary?
last 2 updates seem stable by the way.
Originally posted by Vgui husnos, that is such overkill to be "safe". All you need to do is save your old vmlinuz image as a seperate file before copying over the freshly compiled one. Then edit your boot manager (such as lilo) to point to each image, that way if your new one doesn't work you can fall back to the old one. Saves having to do all that extra (unnecessary) work.
Hope that helps.
the thing is restoring an image located on hardrive takes less than 5 minutes.............
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.