From: Stephen Samuel <samuel@bcgreen.com>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: newbie <linux-newbie@vger.kernel.org>
Subject: Re: Locate Vs Find
Date: Wed, 01 Dec 2004 21:07:51 -0800 [thread overview]
Message-ID: <41AEA327.6010007@bcgreen.com> (raw)
In-Reply-To: <20041122165244.62360.qmail@web52904.mail.yahoo.com>
Locate only finds files by looking up the name in a database.
Once a day it regenerates the database.
If you're just looking for a filename, and you don't mind it being
anywhere up to 24 hours old (sometimes more, but rarely), then
ocate is a FAR faster way to do things.
Find, on the other hand can do WAY more tests than just
the filename, and it can do way more things with a file it
finds than just print it. The find command syntax is
actually a primative programming language. and you can
take actions based on the file type file syatem type
mtime, ctime atime file size, owner etc. etc.
Most, recent, versions of find can even tar up certain
matched files.
'Man find` for nore info on what find is capable of.
Ankit Jain wrote:
> Which is more efficient? /if both perform the same
> work and are not different then why shoudl we have 2 ?
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-12-02 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 16:52 Locate Vs Find Ankit Jain
2004-11-23 4:43 ` Jagadeesh Bhaskar P
2004-11-25 21:00 ` lindax newbie
2004-11-28 14:13 ` J.
2004-12-02 5:07 ` Stephen Samuel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41AEA327.6010007@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=ankitjain1580@yahoo.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox