Changeset df15e9f for general

Timestamp:

05/09/2015 02:18:12 PM (9 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

d9d5a5f

Parents:

b5c1d05

Message:

Improve wording and explanations for OpenJDK tests and cacerts generation. Adapted
from an HTML patch by Paul Rogers.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@15947 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• general/prog/openjdk.xml (modified) (9 diffs)

general/prog/openjdk.xml

@@ -248 +248 @@
       <listitem>
         <para>
-          Optional test harness: <ulink url="&jtreg-download;"/>
+          Recommended test harness: <ulink url="&jtreg-download;"/>
         </para>
       </listitem>
@@ -305 +305 @@
 
     <para>
-      If you have downloaded the test harness, unpack it too:
+      If you have downloaded the recommended test harness, unpack it too:
     </para>
 
@@ -361 +361 @@
 </userinput></screen>
 
-    <para>
-      It seems that the test infrastructure of OpenJDK is a work in
-      progress, so that testing the newly built JVM involves several steps.
+    <warning>
+      <para>
+        Although the test infrastructure of <application>OpenJDK</application>
+        is not easy to use, it is recommended to run the tests in order to
+        make sure that the JVM runs fine. A malfunctionning JVM may have
+        catastrophic consequences in term of security.
+      </para>
+    </warning>
+    <note>
+      <para>
+        Testing will involve the interplay of pairs of JVMs using the
+        networking interface, so networking must be started.  If it
+        isn't, not only will these tests fail, but the test cleanup
+        will leave orphaned JVMs running.  There will be many of
+        them.  Rebooting may be the easiest recovery.
+      </para>
+    </note>
+
+    <para>
+      Testing the newly built JVM involves several steps.
       First, it is better to run the test suite in a frame buffer on a
       different display, using Xvfb:
@@ -440 +457 @@
       <ulink url="http://download.java.net/openjdk/testresults/8/">these
       results</ulink>, although they usually are run on a newer version.
-      There are a few failures, the number of which depends on various
+      Some failures can be expected, the number of which depends on various
       conditions, like whether the computer is connected to network. Also, some
       tests may timeout if the machine is under load.
@@ -557 +574 @@
 
     <para>
-      <option>--with-jobs=N</option>: Allows to set the number
+      <option>--with-jobs=N</option>: Allows setting the number
       of jobs for <command>make</command> equal to N. The default is the
       result of a calculation involving the available memory and the number
@@ -567 +584 @@
     <para>
       <option>--with-cacerts-file=...</option>: Specifies where to find a
-      <filename>cacerts</filename> file. Otherwise, an empty one is created.
+      <filename>cacerts</filename> file, typically <filename>
+      /opt/jdk/jre/lib/security</filename>. Otherwise, an empty one is created.
       You can get it from an earlier version of the package, or use the
       script below to generate one.
     </para>
+
     <para>
       <command>make DEBUG_BINARIES=true all</command>: The build fails
@@ -577 +596 @@
 
     <para>
-      <command>find ... -iname '*.jar' -exec chmod a+r {} \;</command>
-      and following line: Fix permission in some library files, in order to
-      allow all users to access them.
-    </para>
-
-    <para>
-      <command>find ... -iname '*.diz' -delete</command>: This command and the
-      the next one remove redundant files.
+      <command>find ... -iname '*.diz' -delete</command>: This command
+      removes redundant files.
     </para>
 
@@ -613 +626 @@
 
       <para>
-        Use the following procedure to install the
-        <filename>cacerts</filename> or to generate a new one if
-        <xref linkend="cacerts"/> have been updated. First, if it is not
-        already present, generate the <command>mkcacerts</command> script
+        <application>OpenJDK</application> uses its own format for the
+        CA certificates. Those certificates are located in a file named <filename>
+        /opt/jdk/jre/lib/security/cacerts</filename>. That file may be generated
+        from the one installed using the instructions on the <xref
+        linkend="cacerts"/> page, using the following procedure.
+        First, generate the <command>mkcacerts</command> script
         as the <systemitem class="username">root</systemitem> user:
       </para>
@@ -846 +861 @@
   </note>
 
-    <para>If you need to generate a <filename>cacerts</filename> file,
-    and there is already one in
-    <filename class="directory">/opt/jdk/jre/lib/security</filename>, it
-    is better to make a backup. Then, you can create a new one, as the
-    <systemitem class="username">root</systemitem> user:</para>
-
-<screen role="root"><userinput>/opt/jdk/bin/mkcacerts            \
-        -d "/etc/ssl/certs/"      \
-        -k "/opt/jdk/bin/keytool" \
-        -s "/usr/bin/openssl"     \
+    <para>
+      Generate the <application>OpenJDK</application> <filename>cacerts</filename>
+      file as the <systemitem class="username">root</systemitem> user:
+    </para>
+
+<screen role="root"><userinput>if [ -f /opt/jdk/jre/lib/security/cacerts ]; then
+  mv /opt/jdk/jre/lib/security/cacerts \
+     /opt/jdk/jre/lib/security/cacerts.bak
+fi &amp;&amp;
+/opt/jdk/bin/mkcacerts                 \
+        -d "/etc/ssl/certs/"           \
+        -k "/opt/jdk/bin/keytool"      \
+        -s "/usr/bin/openssl"          \
         -o "/opt/jdk/jre/lib/security/cacerts"</userinput></screen>