Install-Size wrong and how to find the true install size. Debian.
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.
Install-Size wrong and how to find the true install size. Debian.
How can I tell how much space is needed when installing say science-mathematics with # apt-get install science-mathematics
If I do
# apt-cache show science-mathematics
it says, Installed-Size: 60; clearly this is wrong even if it was kilobytes.
So my questions are,
why is it wrong?
And,
How would you find out before installing?
Is there another way? as I know I could kick off an install and then I'm prompted for yes or no, but I would like to know if its possible before getting that far.
There's just guesstimates once your disk gets close to full.
I use 'df -h', and that gives you a general idea of how much space is left on a partition. Bear in mind a portion of the disk is left for root, so a user runs out of space when the disk is less than full.
Bear in mind also that logs need to be written. As you get close to full, delete a bit to make space, etc, the amount of fragmentation goes up enormously so disk speeds slow.
An IT manager friend of mine had a rule of thumb of minimum 10% free disk space to keep windows from crashing. Not a bad one. It's the time to start doing something.
If things get desperate, you can always pull a 'rm -rf' on /usr/share/doc, /usr/doc,
thanks for the response. I know all about disk space and thoughtless data retention policies. I just wanted a quick way of finding out how much space a package would take up when installed. it looks like the installed size figure is pretty useless. I guess the answer is to start an install and answer no if there is not enough space. I'm using LVM so I can grow and shrink files stems if needed. I think I am looking at meta packages, which might explain it. Also fs type and block size makes it a guesstimate only. it just puzzled me why use an installed-size value that's really no good.
You're right it's a meta-package, it exists only to pull in other packages, hence the small installed size. When you install it through apt-get you are shown how much all the packages you are about to install will take up (or free) in MB terms.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.