Hi y'all,
can I some how make my /usr smaller? I mean, is it normal to have 1.3 GB only in /usr on a gentoo-system with kde3.0.1 (only kadebase! no extra kde applications), mozilla and openoffice? (I remember my ms-windows life using not more than 500 MB for all this inclusive the system itself...)
/usr/portage -> 310 MB
/usr/share -> 297 MB
/usr/lib -> 186 MB
/usr/X11R6 -> 102 MB
Thanks
Felix
/usr quite big - what do I need?
Message
Some ideas ...
Here are some folders for which it is generally safe to clean:
/usr/portage/distfiles
Contains source tarballs and patches which are downloaded by Portage for all builds. It is safe to delete them, but should you recompile anything they will need to be downloaded again. Good candidates for burning to CD if you have a burner.
/var/tmp/portage
Temporary working files used during compilation process invoked by Portage.
/usr/share/doc
Generally speaking, documentation is optional and could be backed up and removed.
You can try running emerge clean to remove stale files belonging to out-of-date builds. Be advised also that CPU-optimised compiling (one of Gentoo's chief attractions) will often generate *larger* binaries. Speed in code is often gained at the expense of memory. In other words, the greater the optimisations used in make.conf, the greater in size every single binary on your system may be!
You may also consider using a different filesystem. If you are not using ReiserFS you might consider it because it is more efficient than most at packing large numbers of relatively small files, thus avoiding disk "slack".
/usr/portage/distfiles
Contains source tarballs and patches which are downloaded by Portage for all builds. It is safe to delete them, but should you recompile anything they will need to be downloaded again. Good candidates for burning to CD if you have a burner.
/var/tmp/portage
Temporary working files used during compilation process invoked by Portage.
/usr/share/doc
Generally speaking, documentation is optional and could be backed up and removed.
You can try running emerge clean to remove stale files belonging to out-of-date builds. Be advised also that CPU-optimised compiling (one of Gentoo's chief attractions) will often generate *larger* binaries. Speed in code is often gained at the expense of memory. In other words, the greater the optimisations used in make.conf, the greater in size every single binary on your system may be!
You may also consider using a different filesystem. If you are not using ReiserFS you might consider it because it is more efficient than most at packing large numbers of relatively small files, thus avoiding disk "slack".
True - and I like it to compile the code everytime I need it, but I don't need the src present on my harddisk when the bins are ready, do I?tomte wrote:under windows you didn't had the complete source code, the development headers and a complete compiler collection installed, I assume...
'bye
Felix
The archives, certainly not, but they come in handy if you want to recompile a package; how big your bandwidth might be, the server bandwidth is limited and shared by many downloading users, and recompiling without downloading is faster anyway; so if you aren't short of hd space, there's one big reason to keep the source-archives, and the smaller reason of speedf.kater wrote:True - and I like it to compile the code everytime I need it, but I don't need the src present on my harddisk when the bins are ready, do I?tomte wrote:under windows you didn't had the complete source code, the development headers and a complete compiler collection installed, I assume...
'bye
Felix
and no reason against it.regards,
tom
You could use the mount bind option in /etc/fstab to link the /usr/portage/distfiles to another partition which has more space, a normal link could also be enough.- B
Using LVM
The other option is to do what I did and do a full LVM
Check out this:
install.http://forums.gentoo.org/viewtopic.php?t=1897
Check out this:
install.http://forums.gentoo.org/viewtopic.php?t=1897