{"id":7067,"date":"2014-04-09T05:06:17","date_gmt":"2014-04-08T19:06:17","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=7067"},"modified":"2014-04-09T05:06:17","modified_gmt":"2014-04-08T19:06:17","slug":"linux-find-andor-locate-filesdirectories-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/linux-find-andor-locate-filesdirectories-primer-tutorial\/","title":{"rendered":"Linux Find and\/or Locate Files\/Directories Primer Tutorial"},"content":{"rendered":"
\"Linux<\/a>

Linux Find and\/or Locate Files\/Directories Primer Tutorial<\/p><\/div>\n

Linux (or Unix) servers have two really useful commands which help the user find files and\/or directories … locate<\/a> and find<\/a>. Doubt there are many people out there who have not mislaid a computer file at some time or other. The GUI options are there, such as Windows Explorer and Mac Finder, but you tend to think, with these, of the one area or folder to search (mind you both are capable of better), whereas you often face the dilemma of having no idea where the file is. The GUIs can help here, but find, for myself, that I always jump to the command line for this, with Windows command line DIR C: [filespec] \/s or the Linux\/Unix commands for today’s tutorial … locate and find.<\/p>\n

So why confuse things with two choices? Well, locate is fast, once set up, because it sets up its own “database” of previous knowledge, and so can pluck out whatever you want really fast from then on, once you use a “sudo<\/a>” command to set up locate for future use.<\/p>\n

The strength of the Linux\/Unix find command are its switches like “-type ?” to define what type of file to find, and the way you can use “exec” in a piped scenario, to add more functionality.<\/p>\n

So some words about the syntax (and for this, found Linux<\/i> by Steve Oualline and Eric Foster-Johnson (pp 72-73) an excellent source) where you can hover or click for further information:<\/p>\n