SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've been with Linux for 3-4 years and love it. Mainly a Slacker.
Anywhoo, I kept installing packages from SlackBuilds. But unless the bin file has the same name (IE mame) then I can't get the new installation to activate and I then can't find the file location to find what the bin file would be called. (IE advancemame)
So my question. When installing from installpkg, where do the files go? I've looked in usr/bin and //bin. No luck. I know there are sbin directories too that I'll wade through but I don't hold out a lot of hope for any results. And the Dolphin Find function is rarely of any benefit.
I know the feeling, for example the gnome-disk-utility package in Debian become palimpsest after installed.
You are looking at the right places, in some distros the binaries sometimes goes in different directories thou,
but the most used ones are: /bin , /sbin , /usr/bin , /opt , there is also some other possible places but depends
on what kind of setup is been used. If you have the program running in another machine you can check the processes
to find out the binary name.
Also commands like whereis and locate can help you find what you looking for.
As Didier says, the files in /var/log/packages contain a list of all files installed by a package. If you know what the binary is called you can find it with the `which` command. If you want to trawl though all the dirs it might be in, the $PATH variable will tell you which directories bash checks for executables when you type in a command.
Tip: omit the first slash (/) from the path otherwise it it won't be found.
Or you just use slackpkg with the file-search option instead, like
tobi ~ ☺ $ slackpkg file-search mcedit
Looking for mcedit in package list. Please wait... DONE
The list below shows the packages that contains "mcedit" file.
[ installed ] - mc-4.8.4-i486-2
You can search specific packages using "slackpkg search package".
Keep in mind that this works only with packages from the Slackware repo.