Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'd be really surprised if "find" didn't work in AIX. It is one of the basic tools of Unix/Linux.
Anyway usually "missing conjunction" is just a cute way to tell you to put your search pattern in quotes:
find / -name *suze* = Missing conjuntion (not just on AIX)
find / -name "*suze*" = Any file with suze embedded in its name.
I've never figured out exactly what makes find complain about missing conjunction but long ago figured out the quotes told it to shut up about it. It has to do with the metacharacters but on occasion find blithely does the search without the quotes so go figure.
Yes, find does work in AIX but usually when I try to find a file (for example, .bashrc) , I do the following :
find /dir -name .bashrc - print
but since in the script it was taking the filename(s) from the variable $files (which has more than 1 filename in it, many files infact), it failed. Hopefully anyone out there might know a
way how I can get find to find multiple files at one go?
Of course | has special meaning to the shell so its possible you'd need to escape it (put backslash in front of each occurrence). Just try it as aboove first.
Also remember grep (and egrep which is same as grep -E) matches any part of something so you don't need everything you have above. For example:
would find all of start_kde, kde, .kde, .kde/Autostart, .kderc from your original list so there's no reason to include all of those - just kde. NOTE: It will also find anything else that had kde in it such as other files under .kde/. To restrict it you'd have to use the end of line ($) special character for each:
kde$ start_kde$ .,kde/Autostart$ .kderc$
Even there the kde$ would find BOTH kde and .kde so you'd have to prepend it with start of line (^) special character - be careful on that though as doing a find usually prepends your search path so you'd have to put the start of line in front of the path.
Example: If "find ." it would put "./" in front of all entries so you'd have to do:
Last edited by MensaWater; 12-05-2005 at 09:21 AM.