Code: Select all
whereis <program>
Code: Select all
whereis <program>
Code: Select all
dpkg --get-selections > Installed_Package_List
Code: Select all
echo $PATH
Code: Select all
#!/bin/bash
#
if [ $# -lt 1 ]
then
echo Usage: `basename $0` pattern
exit 1
fi
echo $PATH | sed 's/^/ls -A /' | sed 's/:/ |grep '$1'; ls -A /g' | sed 's/$/ |grep '$1'/' | bash | sort
exit 0
Code: Select all
$
$ W dvd
convxdvd
dvd+rw-booktype
dvd+rw-format
dvd+rw-mediainfo
dvd-ram-control
$
$ W dpkg
dpkg
dpkg-architecture
dpkg-buildflags
...lots more
Code: Select all
$ which dpkg-architecture
/usr/bin/dpkg-architecture
Then again, you'd need a password with sudo rights to be able to do that. So it's not like any stranger who is near your computer can do such a thing.Instigator wrote:feels like its very easy to install a program and hide it and the user never know its there?
Fine. The same challenge exists on Windows as well.Instigator wrote:that means you need to know each of their names? what about programs not listed in the menus? - is there a command to list every installed program? like for example tor isn't listed in menus and installed.
You are absolutely free to set up any hypothesis in the world, even if it turns out to be pretty wrong in the end.Why can't he just browse to /usr/share/applications? Coming from windows, that is what I would consider the equivalent to the C:\Program Files directory.
Do it the other way round: Try to search in Windows for paths, that you have in Linux. You will obviously already fail at the beginning.0ddity wrote:Coming from windows, that is what I would consider the equivalent to the C:\Program Files directory.
Code: Select all
man hier
Code: Select all
DOS='C:${PWD//\//\\\}>'
PS1="\[\033[00m\]\[\033[00m\]\[\033[01;39m\]$DOS\[\033[00m\]"
But the menu entries do exactly that. They are links to the programs in the folders where they are. Can you explain your reasoning?Instigator wrote:I just want to be able to run my programs from the folders they are in not the menus
And you can. You just don't know where they are "at". Just like DOS, you likely have a "$PATH" environment variable in your "shell".Instigator wrote:thanks for all the posts ill read these at work tomorrow and see what sense i can make of it all.
I just want to be able to run my programs from the folders they are in not the menus
Code: Select all
whereis -b tcpdump
Code: Select all
whereis -b tcpdump
tcpdump: /usr/sbin/tcpdump
man whereis
and I know that tcpdump is a binary, Code: Select all
find / -name tcpdump -type f | grep bin
/usr/sbin/tcpdump
Code: Select all
man locate
Code: Select all
updatedb
Code: Select all
locate tcpdump | grep bin
Thanks Karl. You rock.karlchen wrote:Oh, just in case no-one should have mentioned so in this thread before:
/usr/bin is the place where you will find representations of almost all installed applications.
Representation means:
+ Frequently the (only) executable file of an application / commandline tool is located here
+ Frequently the start script which launches an application is located here
+ Frequently a symbolic link to either of the 2 items named above is located here.
Cheers,
Karl
No problem. Open a terminal or the command-line window (alt-F2) and enter the command-name. Usually the start binaries or links to them are stored in /usr/bin (already mentioned by karlchen), so entering the name is enough (e.g. firefox).Instigator wrote:I just want to be able to run my programs from the folders they are in not the menus
Right, but even more importantly: Linux and (Unix, primarily used as server-OS, where you hardly find multiple user accounts) never assumed, that system (inclusive program) file and user data have to get mixed. In the days of Windows 9x you could find them partly even inside the Windows folder (brrr )Hoser Rob wrote:Linux has never assumed that you're the only user on the computer.
This helps immensely. You might also get a copy with a DVD of a new installation to try as well!Habitual wrote:The problem, or a contributing factor among new users is the tendency to associate every thing on the system as the OSs. "in Mint 17.3" for example. ", but this sometimes is the only frame of reference they have.
"How does Linux do it?" I always found a better question than "If Windows does it this way, it should follow Linux does too.". Wrong.
You need to learn the Linux FileSystem, not where the heck the non-existent equivalent to C:\PROGRAM FILES\
"is".
Open a terminal and issue:And then "surf" on over to http://tldp.org/ and search for filesystem and learn at your own pace.Code: Select all
man hier
Think of Windows as a set of Standard wrenches in a toolbox.
Think of Linux as a set of Metric wrenches in a toolbox.
A good mechanic doesn't spend much time on what made the differences, he just knows there is one and he has to adjust.
Don't mistake motion for effort, son.
Buy a Linux book, Hard Copy, Tree "Killing" book on Linux.
Anything published in the last 15 years (not a stretch) devotes the first 5 or 6 chapters to "introductory topics"
such as the filesystem.
Learn those 5 or 6 chapters well.
Now, Go Fish.
Who ya calling "Hannibal"?