Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi, and welcome to LQ
The answer is it depends. How did you install the file?
With rpm, by compiling the source, by using another installer...
Anyway, the file-structure in unix is a little bit odd. Especially if you come from a Windows background. The program files may go in many different locations, and not under a specific directory.
Executables go under /usr/bin or /usr/local/bin
libraries under /usr/lib or /usr/local/lib
other files go to /usr/share/
etc
Some applications that have their own installer may be installed under a directory and create links to the directories mentioned earlier.
If you installed from an rpm package, you can use the the command:
rpm -q --filesbypkg realvnc
That is assuming that realvnc is the name of the package under Mandriva. If you are uncertain on the name of the package, you can first use:
rpm -q --all | grep vnc
to display all packages containing the string "vnc".
A program normally used by root, installed by a distro package may go under /usr/sbin/.
You can also use MCC to list all of the files in a package. kpackage if it is installed will also list the files.
It is possible that you installed a source package by mistake. You can install a source package by cd'ing to /usr/src/redhat/SPECS and entering the command:
rpmbuild -bi realvnc.spec
What I like about source packages is that the document sources are often included, and after patching, ( rpmbuild -bp realvnc.spec ) there may be a make target for pdf, or ps (in the BUILD directory).
You can use: rpm -q --filesbypkg vnc
The version numbers after the name are not needed.
You can view information about the package with:
rpm -q --info vnc
Also look for the README file, and any documentation. Sometimes a number of commands are included. Make note of them and the manpages. Some may be useful!
[root@localhost Download]# rpm -q --filesbypkg vnc-4_1_1-1
package vnc-4_1_1-1 is not installed
[root@localhost Download]#
[root@localhost Download]# rpm -q --info vnc
package vnc is not installed
[root@localhost Download]#
[root@localhost Download]# rpm -q --filesbypkg vnc
package vnc is not installed
[root@localhost Download]#
[root@localhost Download]# rpm -q --all | grep vnc
tightvnc-1.2.9-6mdk
tightvnc-server-1.2.9-1
[root@localhost Download]#
tightvnc is the one that comes with it, i can get it to remote contorl my windows pc, but i can't get the windows pc to remote control this one, this is why i am trying to install real vnc, as that is what the windows machine has.
There is a tightvnc package. It installs it's executables in /usr/X11R6/bin/.
Try rpm -q tightvnc. If you know where a particular file is you can enter "rpm -q --whatprovides <full path to file/filename>"
example:
rpm -q --whatprovides /etc/xinetd.d/vnc
tightvnc-1.2.9-186
If you installed a package from a tarball, it probably won't show up. Some tarballs have "make rpm" targets. There also is a wrapper program that does the "./configure" and "make" targets and then produces an rpm. These techniques could be used in the future to allow you to have tarball installed applications show up in the rpm database.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.