whereis Command Generator
Generate whereis commands to locate a command's binary, source, and man page
Getting Started with whereis
## What is whereis?
`whereis` locates the binary, source, and manual-page files for a command in one shot. It searches a fixed set of standard directories (not `$PATH`), which makes it very fast but also means it only finds files installed in conventional locations. It is the quickest way to see everything related to an installed command.
## How to Use
1. **Set Options**: Restrict to binary / source / manual, or set custom search directories. 2. **Enter Name**: Type the command name to look up. 3. **Copy & Run**: Paste the generated command into your terminal.
The output groups results as `name: /path/to/binary /path/to/man /path/to/src`.
Common Options
### `-b` Binary only Limit results to the executable binary (or script) for the command.
### `-m` Manual only Limit results to the man page file(s).
### `-s` Source only Limit results to the source code file(s).
### `-u` Unusual entries Show only entries that are "unusual" — commands that are missing at least one of binary/source/manual. Helpful for spotting incomplete installations.
### `-B DIR`, `-M DIR`, `-S DIR` Custom search paths Restrict the binary, manual, or source search to specific directories. These must come before the command name: `whereis -B /opt/bin -f python`.
### Name (positional) The command name to search for, e.g. `ls`, `gcc`, `bash`.
▶What is the difference between whereis, which, and locate?
▶How do I see only the binary path for a command?
▶How do I find commands with missing man pages or sources?
If this tool has been helpful to you, consider buying me a coffee.
Buy me a coffee