Neil Bothwick wrote:
On Thu, 24 Mar 2011 22:09:27 +0100, Jarry wrote:
I know, there is "qfile" with "-o" option, but its syntax is
not clear to me. I tried "qfile -o *" but that is apparently
not the correct syntax, as all I got were a few top-level
subdirectories and nothing more...
qfile operates on the files you give it, it doesn't recurse into
directories.
Try find / -xdev -type f -exec qfile -o {} +
Naturally this returned a lot so we have to use common sense before
deleting something. That said, what about these:
/usr/bin/cc
/usr/bin/c++
/usr/bin/c89
/usr/bin/gcc
/usr/bin/gcov
/usr/bin/x86_64-pc-linux-gnu-c++
/usr/bin/python-config
A whole bunch of files in:
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/32/*
/usr/lib64/python2.6/*
Just to name a few. Naturally there are files in /root and a lot of
files that I created that also show up. Some of the files above, they
just about have to belong to something tho. I used qfile to test and it
says they don't so your command is working fine. I'm pretty sure tho
that python-config and gcc belong to their respective packages.
Question is, why does qfile think they don't?
This is the ones I tested:
root@fireball / # qfile /usr/bin/c++
root@fireball / # qfile /usr/bin/c89
root@fireball / # qfile /usr/bin/gcc
root@fireball / # qfile /usr/bin/gcov
root@fireball / # qfile /usr/bin/x86_64-pc-linux-gnu-c++
root@fireball / # qfile /usr/bin/python-config
root@fireball / # qfile /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/32/
root@fireball / # qfile
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/32/crtbeginS.o
root@fireball / # qfile /usr/lib64/python2.6/binhex.pyo
root@fireball / #
Is qfile wrong? The equery command said the same as qfile so this is
confusing.
Dale
:-) :-)
P. S. Nope, I'm not deleting those. ;-)
