| 1 |
More specifically, when 'find'ing files I've found quoting wildcards |
| 2 |
usually works, like: |
| 3 |
|
| 4 |
from current dir: |
| 5 |
|
| 6 |
find . -name "*file*" -print > foo |
| 7 |
|
| 8 |
from /: |
| 9 |
|
| 10 |
find / -name "*file*" -print > foo |
| 11 |
|
| 12 |
or "file*" / "*file" depending on name structure.. |
| 13 |
Nick |
| 14 |
|
| 15 |
Ciaran McCreesh wrote: |
| 16 |
> Just to warn you... New findutils releases are starting to get a lot |
| 17 |
> more picky about being given correct arguments. The correct way to |
| 18 |
> invoke find to avoid problems is as follows: |
| 19 |
> |
| 20 |
> find [paths] [options] [rules] [actions] |
| 21 |
> |
| 22 |
> The [paths] part is mandatory, and the [options] (such as -maxdepth) |
| 23 |
> should come *before* any [rules]. |
| 24 |
> |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives