On Fri, 13 Aug 2010 20:41:14 +0200, Merciadri Luca wrote:
> Well, you're right.
>
> But I've found
>
> ==
> /usr/lib/jvm/java-6-sun/sun-java6-6-12/jdk1.6.0_12/jre/bin# ls -al
> total 756
> drwxr-xr-x 2 root root 4096 2009-08-29 23:03 .
> drwxr-xr-x 6 root root 4096 2009-08-29 23:03 ..
> lrwxrwxrwx 1 root root 10 2009-08-29 23:03 ControlPanel -> ./jcontrol
> -rwxr-xr-x 1 root root 47308 2009-08-29 23:03 java
> <----------------------------------------
(...)
Sure, Sun's java "bin" is in your system and you can launch any java
application by calling the full path ("/usr/lib/jvm/java-6-sun/sun-
java6-6-12/jdk1.6.0_12/jre/bin/java -jar ...") , is just that "update-
alternatives" cannot auto-link for "java -jar ..." to your current Sun
binary, which was installed from "outside".
> What do you suggest now?
If you are asking how to force "update-alternatives" to "detect" the
installed Sun's Java binary, dunno.
No information about this in the man page? :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.08.13.19.08...@gmail.com
