|
|
Find 'non-findable' files
The "find" command does not look for content. In fact, the "find" command can find files based on pattern matching criteria and can limit the directories it searches. Yes, the command line syntax is a bit cryptic for the "average" user, but I am not an average user (I started using Unix Version 7 in 1979).
However, I like the wildcard matching capabilities of "find" that would allow me to find all httd.conf files, including renamed backups like http.conf2, etc. (
find / -name "http.conf*" -print). And if I need to search root-owned content, just precede the command with "sudo" (e.g., sudo find ...). Cool stuff!
Find 'non-findable' files
I think you misunderstood me. I was trying to point out that FAF's search is much faster than the "find" command, at least if you are searching an entire disk. The reason is the same as for why FAF is faster than EasyFind: "find" and EasyFind perform recursive directory descent for their search, while FAF performs a flat search on directories of HFS volumes, which avoids lots of seeking. FAF finishes a search on a 2 million items volume in about 15 seconds on my Mac Pro, while find (and EasyFind) take minutes. Sure, find has other advantages, but it doesn't win in every category. Otherwise, what would be the point of me having developed it? :) |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|