Search results
Results from the WOW.Com Content Network
The where command does what you want and goes back at least to the resource kit for Windows 98, and is included by default in Server 2003, Vista, and newer: C:\>where csc. C:\Windows\Microsoft.NET\Framework\v3.5\csc.exe. C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe. If executed with no arguments (on Vista), it results in one of my ...
whereis (1) - locate the binary, source, and manual page files for a command. Basically, whereis searches for "possibly useful" files, while which only searches for executables. I rarely use whereis. On the other hand, which is very useful, specially in scripts. which is the answer for the following question: Where does this command come from?
From which/whereis differences. which (1) - shows the full path of (shell) commands. whereis (1) - locate the binary, source, and manual page files for a command. I'd use which as it shows you where just the binary is as I assume that is all you need. However Java could be installed somewhere else and which would not report it as it only ...
whereis and which only search specific locations. man whereis: The whereis utility checks the standard binary directories for the specified programs, printing out the paths of any it finds. man which: The which utility takes a list of command names and searches the path for each executable file that would be run had these commands actually been ...
I'm trying to install the whereis command on alpine linux 3.5. Actually I'm running the following command:
The whereis utility checks the standard binary directories for the specified programs, printing out the paths of any it finds. The path searched is the string returned by the sysctl (8) utility for the ``user.cs_path'' string. Contrary to that, which is the tool commonly used to check where a binary is for your user's path.
If you're just looking to have the same functionality without invoking cmd, you can call where.exe from powershell, as long as C:\Windows\System32 is in your path. The command where (without the .exe) is aliased to Where-Object, so just specify the full name. PS C:\Users\alec> where. cmdlet Where-Object at command pipeline position 1.
EDIT: I should have added, if you can't use the WHERE command from the command prompt, check your PATH variable. (Just use the "path" command.) Make sure C:\Windows\System32 is in your path. That's where "where.exe" is located. WHERE is the command you're looking for!
19. It's WHERE to find any files in your path. On XP/2003 and earlier, you need to add it from the Resource Kit, but it a standard command in Vista onwards. By the way, where | clip will put the path into the clipboard, which is useful. Use where.exe in Windows PowerShell otherwise it conflicts with the built-in where command.
For the last part of your question, why folders are found as binaries, I speculate that whereis finds everything as binary in the specified folders, even _un_executable (empty) files: $ touch /usr/share/foo $ whereis foo foo: /usr/share/foo What's the intention of that -- I don't know. But all in all I think whereis is a little