Is it easy to identify? Yes, but you need some understanding. Initially everyone try to find out the large files, it could be log files, etc, the other option is application/packages installed size. It would be great if yumdb supported “group” type.When you are running out of space in your system, you might want to check who’s the major contributor to get out of the issue. So only way around this I can see is to not install groups, because installing a group tells it to install whatever is in the list. Similarly, for ModemManager, it’ll be part of default group. $ sudo yum groupinfo hardware-support |grep ipw2200 I guess that makes sense, if you install a group then you’re telling it you want all of the packages there (but you shouldn’t get any deps).įor example, most systems probably have group installed, which is where ipw220-firmware comes from: I think the reason for this is that yumdb is including default and mandatory packages from when you install a group. Some people have written in to say the command shows packages that they never explicitly installed, things like ModemManager and firware packages. Yumdb search reason dep |egrep 'agg|boost-iostreams|boost-serialization|gtkglext-libs|pangox-compat' List packages which were installed as deps:

If you’re after a way to list all the packages you have explicitly installed (rather than packages that have been pulled in as a dependency) then you can do that with yumdb (thanks to Panu on #yum for the tip) which is powered by a new database added in 2009.

Yum list installed