Trying to recover HDD space after new kernel compilation
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.
Trying to recover HDD space after new kernel compilation
So I compiled my first kernel last night and it seems to be working. However I have noticed that now I have about 1.9Gb less free harddisk space.
I figured this would be in the source files and compiled objects used/made during the compilation and indeed they are taking up about 1.2Gb.
Where is the other ~700Mb going? Is that the size of an installed, compiled kernel?? If so, where can I find these files? If i can i would like to clean out some of the older kernel options so free up some space.
Yeh I figured it would all be scattered around the disk (both a boon and a bane for linux in comparison to windows).
Basically I want to scrub my disk clean of an old boot/kernel option. In what places must I look to find files associated with a kernel 2.6.x for example.
After that i plan on removing the GRUB loader entry.
Those figures seem terribly large. Are you sure you need all (or even most) of the modules you are compiling? For reference, my source directories after compilation weigh in at about 230 megabytes, and i wouldn't consider them "minimal" configurations -- they just match the hardware I am using. Don't worry about needing some oddball driver in the future. If you keep your source dir around, you can always build and install the module in a few minutes, without even a reboot.
Also, if you want help in tracking disk usage, I recommend an excellent graphical utility for KDE called Filelight. Tell it to scan a directory, and it will recurse the subdirectories and give you an attractive looking radial chart that you can zoom in and out on to quickly find exactly which folders are causing the bloat. It's so nice for what it does that it's one of the few KDE programs I use on Gnome.
Thanks for that program trashmatic, I will look into it.
Yeh, it was my first kernel compile and i did get rid of a bunch of stuff but ultimately i just wanted to get a kernel compiled to try out software suspend. I will probably recompile the kernel again in the future and dump a bunch of stuff.
Still wondering where all the kernel files are stored once installed.
You can try using Active@Undelete to recover your data. It really supports many special and effective recover algorithms and supports many file systems. Visit (URL deleted) to get more information and download it.
Last edited by mcleodnine; 10-11-2005 at 07:32 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.