On Mon, 23 Nov 2015 07:42:48 -0600, Dale wrote: > > As with everything Gentoo, it is 100% safe to look at the output and > > make your own decisions. Generally, if its in /lib or /usr/lib it's > > usually fair game, but not if it's in /etc.
> I have some in lib directories. I skipped the ones in /etc and home > directories. This is a example: > > /lib64/firmware/LICENCE.iwlwifi_firmware > /lib64/firmware/liquidio/lio_410nv_nic.bin > /lib64/firmware/liquidio/lio_210nv_nic.bin > /lib64/firmware/liquidio/lio_210sv_nic.bin > /lib64/firmware/iwlwifi-6000g2b-6.ucode > /lib64/firmware/LICENCE.atheros_firmware > /lib64/firmware/TDA7706_OM_v2.5.1_boot.txt > /lib64/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq > /lib64/firmware/intel/fw_sst_22a8.bin How did they get there? Did you manually install some firmware or drivers? To be safe, run qfile on each of them, they may be recorded as having been installed to /lib instead of /lib64 or vice-versa. If you think they are no longer needed, move them elsewhere, reboot and see what breaks. > /lib64/modules/3.2.11-gentoo/modules.isapnpmap > /lib64/modules/3.2.11-gentoo/modules.ieee1394map > /lib64/modules/3.2.11-gentoo/modules.pcimap > /lib64/modules/3.2.11-gentoo/modules.order > /lib64/modules/3.2.11-gentoo/modules.symbols.bin > /lib64/modules/4.1.2-gentoo/modules.dep You should rarely delete anything in /lib/modules. These files are created during the kernel build/install process. > That is just a small snippet. There are so many, it seems odd that that > many would be left behind but equery shows they belong to nothing for > the ones I tested on. > > Thought it better to ask first. ;-) May just leave it alone. If disk space is not critical, that is the easiest option. -- Neil Bothwick The trouble with life is that you are halfway through it before you realize it's a "do it yourself" thing.
pgpSFBCB1AUoD.pgp
Description: OpenPGP digital signature
