Linux mystery showdown: which vs. whereis vs. whatis
It is possible that you have used the commands which, whereis, and whatis multiple times on Linux.. All three commands are used to find information about other Linux commands. These commands look similar, but they do have some differences.
#The following is a detailed comparison of which, whereis and whatis commands on Linux.
which command
Some commands have multiple executable files in different directories. The Shell will search for executable files in the folder specified by the PATH environment variable to run the corresponding command.
To find the directories contained in the PATH environment variable, run the following command in a Linux terminal:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ echo $PATH
Tip: You can also manually add directory to your PATH environment variable.
As soon as the first executable path is found in Linux, the shell will execute it immediately. Using the which command you can determine the path to the executable file.
It can be useful in this situation: when two identical programs with different versions are installed on your system, or two software with the same name but different programs are installed. Using the which command you can find out which one will be executed first.
The following is the syntax of the which command:
which [选项] [命令]
For example, to check the actual path of the tar command, you can enter:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ which tar
This command will display the first executable path of the tar command in PATH, which is located in /usr/bin. Every time you run the tar command, the binary file located in the /usr/bin directory is executed by the shell, and this is what it means.
To display all available executable paths for a command, use the which command with the -a option:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ which -a tar
You can also display multiple commands at the same time The executable path is as follows:
which [命令1] [命令2] [命令3]
whereis command
whereis command can display the executable files, source code files and manual page files related to the specified command path of. Unlike the which command, it searches not only $PATH for executable files, but also $MANPATH and other predefined locations.
Without any command line options, the whereis command displays the binary files, source files, and manual page files for the command:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whereis tar
To display only the binary files path, use the -b option:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whereis -b tar
To display only source files, use the -s flag:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whereis -s tar
To display only manual pages, use the -m option:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whereis -m tar
whatis command
The whatis command provides a one-line description of a given Linux command. It gets this information from the command's man page.
For example, to find out what the tar command does, run:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whatis tar
You can also find information about multiple commands at the same time, for example:
┌──(linuxmi㉿linuxmi)-[~/www.linuxmi.com]└─$ whatis ls cp mkdir cat head
#What is the difference between which, whereis and whatis?
If you need to find the executable path of a command in the shell, try using the which command. Use the whereis command to find source files, binaries, and man pages for a command. The
whereis command lists all binary executable files, while the which command displays only the first executable file that is executed when the command is entered in the shell.
which command searches in the PATH variable, while whereis command searches in standard Linux directories, including $PATH and $MANPATH.
Finally, the whatis command will extract a short description from the command's man page.
Find information about Linux commands
The which, whereis and whatis commands can help you find information about other Linux commands, such as the full path of the executable file, binary files, source files, manual pages, and the function of the command .
In addition to whatis command, you can also use other commands such as apropos, man, info and help to get detailed information and better understanding about Linux commands and their functions.
The above is the detailed content of Linux mystery showdown: which vs. whereis vs. whatis. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
