Many beginning Linux users experience difficulties getting used to the filesystem structure. Indeed, there are many files and directories, the structure of which are not as obvious as it could be. Choosing an appropriate location for a new file or directory is difficult and many choose to follow their own instincts.<\/p>\n
With more experience, the file hierarchy becomes clearer and old concepts of placing files and directories start to fade out. When it happens, finding things becomes difficult. It is than that users learn that Linux has many tools for finding things. And it is than that they become confused once again.<\/p>\n
Read on for a quick introduction into searching tools available in Linux.<\/p>\n
<\/p>\n
find<\/strong><\/p>\n Example of usage:<\/p>\n locate<\/strong><\/p>\n Once you start using While you would certainly appreciate the speed with which Example of usage:<\/p>\n whereis<\/strong><\/p>\n Example of usage:<\/p>\n which<\/strong><\/p>\n If you are trying to start some program and get a different version of it or a totally other program instead, use Example of usage:<\/p>\n rpm<\/strong> (or any other package manager for that matter)<\/p>\n RPM is a package manager. It is used to install, update and remove applications on your computer. RPM maintains its own database. RPM packages store information regarding what are they installing and where. When the package is installed, this information is added to the RPM database. When the package is removed, the information is also deleted from the database.<\/p>\n Example of usage:<\/p>\n Many beginning Linux users experience difficulties getting used to the filesystem structure. Indeed, there are many files and directories, the structure of which are not as obvious as it could be. Choosing an appropriate location for a new file or directory is difficult and many choose to follow their own instincts. With more experience, the … Continue reading Finding files in Linux<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false,"_links_to":"","_links_to_target":""},"categories":[1,6,18],"tags":[1960,616,699,1531,698,80],"keyring_services":[],"class_list":["post-9488","post","type-post","status-publish","format-standard","hentry","category-general","category-linux","category-programming","tag-command-line","tag-filesystem","tag-gnu","tag-operating-systems","tag-rpm","tag-tutorials"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tfind<\/code> is a very powerful tool to search through filesystem hierarchy. It goes from directory to directory and from file to file. It finds only stuff that is physically present on the hard disk. find<\/code> accepts a multitude of parameters. It can search for files and directories by name, path, mount point, inode number, owner, permissions, creation or modification timestamp, etc. It can perform a number of actions on the results – print them out, delete them, or pass them as parameters to external scripts.<\/p>\nfind<\/code> is one of those tools that you learn and than can’t imagine your life without. Read the manual page (man 1 find<\/code>) and than refresh your memory once in a while.<\/p>\n\r\n# Find in the current directory (recursively)\r\n# all files named core.\r\n[me@here dir]$ find . -name core\r\n<\/pre>\n
find<\/code>, you’ll notice that searching through a large directory or even a whole hard drive takes a long time. You’ll get bored and tired of waiting and will be wondering if there is any other, – faster – way. It is than that you will be glad to learn about locate<\/code>.<\/p>\nlocate<\/code> builds an index of all files and directories on the system and uses it to find things much faster than find<\/code>. This index is refreshed periodically (anywhere from 1 day to 1 month – check your cron<\/code> setup for specifics of your system).<\/p>\nlocate<\/code> finds files and directories, I should warn that it can get pretty frastrating sometimes. You know that the file or directory is there, you are certain even, and you can list it with ls<\/code>, but locate<\/code> doesn’t find it. What’s wrong? Well, it can mean only one of two things. Either the file or directory that you are looking for is new, and was created after the last update to locate<\/code> index and thus cannot be found. Or this directory is outside of those paths indexed by locate<\/code>. Usually temporary and spool directories are not index as they are meant to hold short-lived items. Check the locate<\/code> configuration file (usually \/etc\/updatedb.conf<\/code>) for specifics of your system.<\/p>\n\r\n# Find all files and directories on the \r\n# system that have exim in their name.\r\n[me@here dir]$ locate exim\r\n<\/pre>\n
whereis<\/code> looks for “tasty” stuff in the places where “tasty” stuff is usually stored. By “tasty” I mean program binaries, sources, and manuals. If you’ve used Linux even for a little while, you know that programs’ executables are usually stored in \/bin<\/code>, \/sbin<\/code>, \/usr\/bin<\/code>, \/usr\/local\/bin<\/code>, and other similar directories. There are similar places for sources (\/usr\/include<\/code>) and manuals (\/usr\/man\/<\/code>).<\/p>\nwhereis<\/code> just doesn’t forget about different locations and thus is a bit more efficient at findings interesting stuff than going through many places manually.<\/p>\n\r\n# Find binaries, sources,\r\n# and manuals for ls \r\n[me@here dir]$ where ls\r\n<\/pre>\n
which<\/code> is one of those little simple programs that can save a lot of confusion. which<\/code> tells you the full path of the program that you want to execute. For example, I can have a system-wide \/bin\/ls<\/code> and my own modified version in \/home\/leonid\/bin\/ls<\/code>. If I use just ls<\/code> on the command line, than I am not sure which copy of the program the shell is executing. I can run which ls<\/code> to make sure that the proper one will be started.<\/p>\nwhich<\/code> works in a very simple manner. It looks for the program you asked in directories listed in your path (PATH<\/code> environment variable) and outputs the full path to the first match. It uses exactly the same algorithm as shell itself uses.<\/p>\nwhich<\/code> to make sure that you are running the proper copy. Also, you can use which<\/code> to see if the program is in your PATH<\/code>. If it says it’s not, than shell won’t find it either.<\/p>\n\r\n# Find out which copy of ls\r\n# will start by shell if no full\r\n# path used\r\n[me@here dir]$ which ls\r\n<\/pre>\n
rpm<\/code> tool can be used to query RPM database for directory and file locations. Note that it does know what was actually installed by the package, but rather only what the package told it it would install.<\/p>\n\r\n# Find which binaries and\r\n# in which directories exim\r\n# package installed\r\n[me@here dir]$ rpm -ql exim | grep bin\r\n<\/pre>\n\n","protected":false},"excerpt":{"rendered":"\n