[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: finding .m files using 'locate'
From: |
Mike Miller |
Subject: |
Re: finding .m files using 'locate' |
Date: |
Fri, 15 Jul 2005 22:24:00 -0500 (CDT) |
On Fri, 15 Jul 2005, Henry F. Mollet wrote:
Thank you. I'm beginning to understand. It implies that a fink
installation makes it easier to find octave and octave-forge .m files.
What is the difference between locate and find? If both are to be used
in the terminal window why would I use locate, which requires the data
base to be brought up to date, when find will do the same thing all the
time?
'find' doesn't do quite the same thing as 'locate', but I would say that
the major reason for using 'locate' with its 'locatedb' is that 'locate'
is very fast. The database stores an index of all files on the system, so
'locate' uses that database instead of having to read all the filenames on
the system like 'find'. Compare them sometime and you will see - 'locate'
can be hundreds of times faster than 'find.' A 'find' command can take
many minutes to complete.
Mike
-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.octave.org
How to fund new projects: http://www.octave.org/funding.html
Subscription information: http://www.octave.org/archive.html
-------------------------------------------------------------
- Re: finding .m files using 'locate', (continued)
- Re: finding .m files using 'locate', Przemek Klosowski, 2005/07/18
- Re: finding .m files using 'locate', Mike Miller, 2005/07/19
- Re: finding .m files using 'locate', Mike Miller, 2005/07/19
- SV: finding .m files using 'locate', Peter J. Acklam, 2005/07/19
- Re: SV: finding .m files using 'locate', Mike Miller, 2005/07/19
- Re: finding .m files using 'locate', Peter J. Acklam, 2005/07/19
Re: finding .m files using 'locate', Michael W. Martin, 2005/07/15