Shell Programming and Scripting

You have to do that on on any *nix OS, including Linux.

Just tryed on my ubuntu at home and it was working without double quotes, maybe not the correct behavior .....

Code:

snerge@sn-ubt:~$ cd /tmp
snerge@sn-ubt:/tmp$ ls
gconfd-snerge  kde-snerge  ksocket-snerge  orbit-snerge  ssh-jtGPjJ5607
snerge@sn-ubt:/tmp$ find . -name orb*
./orbit-snerge
snerge@sn-ubt:/tmp$

Snerge - is there a switch or option I can include in my example of FIND that will ignore case?

find . -name filename*

Hello kozmo,

Not that I know of, you will need to learn a little bit about regular expression

You can pass any regular expression to -name like :

Code:

find . -type f -name "[^C|c]*"

should find every file beginning with C or c ....

Have a look at man regexp and look for tutorials about regular expression.

I am no regexp guru (still learning) as it is one of the most usefull thing I have seen as a unix admin.

Do this, then try it again:

Code:

touch orbit orbison orb

yup, you're right !

find is now not even acting the way it was back when I tested/posted this, I'm running feisty fawn (herd 5). I guess they might be doing some change ..

I usually always put strings between doubles quotes, I think it is the best way to avoid funny behavior !

thanks

There is no change; it doesn't work, and has never worked. You may have been lucky, and not had any files in the current directory that match the wildcard expression.

The -name operand to find takes a single argument; if the shell expands a wildcard to more than one filename, then your find syntax is wrong.

Even if it expands the wildcard to a single filename, your command will not work as it will only match that single name.

Don't bother to quote strings. You need to quote wildcards and variables.