Quote:
Originally Posted by Deixus
|
Well the idea is to find your actual "javaws' executable then find the package from which it came.
The following example is from my system which runs Debian:
First you find the actual "javaws":
Code:
$which javaws
/usr/bin/javaws
laca@laca-desktop:~$ ls -al /usr/bin/javaws
lrwxrwxrwx 1 root root 24 May 2 2016 /usr/bin/javaws -> /etc/alternatives/javaws
Then you will have to find the exact executable - because java and it's companion packages are using the "alternatives" system that permits you to have multiple executables of different versions installed in parallel and you can select which one launches "javaws" in this case. Basically you have to find the REAL executable at the end of a possible chain of links.
Code:
laca@laca-desktop:~$ ls -al /etc/alternatives/javaws
lrwxrwxrwx 1 root root 48 May 2 2016 /etc/alternatives/javaws -> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws
$ ls -al /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws
-rwxr-xr-x 1 root root 2756 Jan 14 17:46 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws
Now that we found the REAL executable, we will do a reverse search for it's "parent" package:
Code:
laca@laca-desktop:~$ dpkg --search /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws
icedtea-netx:amd64: /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws
Now we will look at the package version:
Code:
$apt-cache policy icedtea-netx
icedtea-netx:
Installed: 1.6.2-3.1
Candidate: 1.6.2-3.1
Version table:
*** 1.6.2-3.1 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
2 http://ftp.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status