Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I think the problem is that the o/p of 'locate' is effectively a bunch of strings (as opposed to eg grep -r , which is actually reading the dir nodes content ).
Try using 'grep -v' or even 'egrep -v' on the 'locate' o/p.
don't use locate for changing, user created content.
also, since you are piping locate's output to grep, i don't think the --exclude-dir option makes any sense there.
please explain what you are trying to achieve, we will help you formulate a better command.
this is completely wrong.
--exlcude-dir has only any effect if you use recursive search (grep -r), not when grepping stdin.
From the other hand grep -v <pattern> may work (as it was already suggested).
Quote:
Originally Posted by TBotNik
All,
Following up on all my open threads, looking to close/solve them all.
Yes, I would like to see a follow up from you. If it was still a problem for you, if you have already tried any suggestion posted.
As a KDE user, I normally use "KFind" which searches the entire system including any flash drives active, but kfind sometimes blows on install, so not always available.
Both "find" and "locate" are limited to the "/home" directory!
What is needed is a command line equivalent of "kfind" that will search the entire system by default.
I'll try to find the right board to post this one so the OS level gurus will create the right command for this!
If anyone has a bash script that equals "kfind"; I'll go ahead and mark this solved. Please share if you have such a script!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.