Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6269461

Document default jre/jdk on Linux JDS/SuSE (as is done for Solaris)


    • Type: Bug
    • Status: Closed
    • Priority: P4
    • Resolution: Not an Issue
    • Affects Version/s: 5.0
    • Fix Version/s: None
    • Component/s: docs
    • Labels:
    • Subcomponent:
    • CPU:
    • OS:


      The JDK documentation includes a description of the default version of
      Java for Solaris (http://java.sun.com/j2se/1.5.0/install-solaris.html#default),
      but not for Linux JDS/SuSE -- a similar write-up needs to be made for it,
      on the Linux (or JDS) installation page, I suppose.

      ###@###.### wrote:
      > Thanks! For Solaris, /usr/java seems to be the right thing to
      > do *and* it's documented well in the web page you provide. Yeah!
      > This means I should be able to always say JAVA_HOME=/usr/java for
      > the Solaris spec files and get at least some version of the JDK.
      > Now that the Solaris question has been answered, it's off to
      > the same question for Cinnabar (JDS/Suse).
      > Cinnabar (JDS/Suse) seems to ship *almost* everything under
      > /usr/bin that I need: javac, rmic, etc. Someone went through
      > the task of making these symbolic links to /usr/java/j2redefault
      > and /usr/java/jdk1.5.0_[latest rev here], depending upon whether
      > they are JDK-ish or JRE-ish binaries.
      > But, /usr/bin doesn't have javah or idlj, which I need. So,
      > JAVA_HOME=/usr/bin on Cinnabar is close but not quite there.
      > I've dug around on Cinnabar, but I cannot seem to find anything
      > quite so consistent as there is on Solaris.
      > Am I missing something on Cinnabar?
      > Thanks again! Your time spent here could potentially prevent
      > needless hours of running through the Sun process to update
      > various spec files just to point to a new JDK rev.
      > Will

      ###@###.### wrote:
      You may want to read RFE 6211006. If you don't want to read it, here's a brief rundown...

      Starting with Mustang b36 the Java RPM packages will create/maintain two links in /usr/java. One link, named latest, will point to the latest (i.e. highest version number) of Java installed on the system. The other link, named default, will point to the latest link, but it can be changed by the SysAdmin. This means that on Linux, /usr/java/default is equivalent to /usr/java on Solaris.

      In addition, several other links will be created in /usr/bin. If the JRE package is installed, links for java and javaws that point through /usr/java/default are added to /usr/bin. If the JDK package is installed, then links for javac, jar, and javadoc are also installed.

      The JDS supplied link you mention was added by JDS against the advice of Java. It may conflict with the links Java is creating. Other packages, such as GNU Java may also create links in /usr/bin that conflict with or override the Java links. Also, the Java packages are only linking a small subset of Java tools to /usr/bin. Basically, the tools we are adding to /usr/bin are what we expect are the most common tools, that the average user needs to run from the command line. Non-average users will still need to modify PATH and/or JAVA_HOME to get full access to all the Java tools.

      If you are writing specs that can depend on Java 1.6.0+, then you should use JAVA_HOME=/usr/java/default, and that should solve all your problems.

      Good luck,


      When both the JDK and JRE packages are installed on the system, /usr/java/latest will point to JDK. Otherwise, it will point to whichever package is installed.

      ###@###.### 2005-05-12 17:02:35 GMT




            • Assignee:
              sharonz Sharon Zakhour (Inactive)
              dkramersunw Douglas Kramer (Inactive)
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: