Index: general.ent
===================================================================
--- general.ent	(revision 108024113c4547b611576149c47cfdd0744a4ae0)
+++ general.ent	(revision d4277d4911ffdc99984998fc33603e62b5f1b502)
@@ -1,7 +1,7 @@
-<!ENTITY day          "30">
+<!ENTITY day          "31">
 <!ENTITY month        "01">
 <!ENTITY year         "2006">
 <!ENTITY version      "svn-&year;&month;&day;">
-<!ENTITY releasedate  "January &day;th, &year;">
+<!ENTITY releasedate  "January &day;st, &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
Index: general/prog/jdk.xml
===================================================================
--- general/prog/jdk.xml	(revision 108024113c4547b611576149c47cfdd0744a4ae0)
+++ general/prog/jdk.xml	(revision d4277d4911ffdc99984998fc33603e62b5f1b502)
@@ -83,9 +83,7 @@
 
       <!-- Commented out right now as there is no md5sums file on Anduin
-
       <listitem>
         <para>Download MD5 sum (source): <ulink url="&jdk-source-md5sum;"/></para>
       </listitem>
-
       -->
 
@@ -169,4 +167,17 @@
     either or both.</para>
 
+    <tip>
+      <para>The <command>./jdk-&jdk-bin-string;-linux-i?86.bin</command>
+      command below unpacks the distribution into a
+      <filename class='directory'>jdk&jdk-bin-version;</filename> directory.
+      You will be required to view, and then accept (by entering a
+      <keycap>y</keycap> keypress), a license agreement before any files are
+      unpacked. If you are scripting (automating) the build, you'll need to
+      account for this. There is information about automating build commands
+      in the <xref linkend="automating-builds"/> section of Chapter 2. Towards
+      the end of this section, specific information for automating this type of
+      installation is discussed.</para>
+    </tip>
+
     <para>Install the precompiled <application>JDK</application> with the
     following commands:</para>
@@ -174,7 +185,5 @@
 <screen><userinput>sed -i "s:^PATH=.*::" jdk-&jdk-bin-string;-linux-i?86.bin &amp;&amp;
 chmod -v +x jdk-&jdk-bin-string;-linux-i?86.bin &amp;&amp;
-mkdir -v -p bin &amp;&amp;
-ln -v -sf /bin/true bin/more &amp;&amp;
-yes | PATH=$PWD/bin:$PATH ./jdk-&jdk-bin-string;-linux-i?86.bin &amp;&amp;
+./jdk-&jdk-bin-string;-linux-i?86.bin &amp;&amp;
 cd jdk&jdk-bin-version;</userinput></screen>
 
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision 108024113c4547b611576149c47cfdd0744a4ae0)
+++ introduction/welcome/changelog.xml	(revision d4277d4911ffdc99984998fc33603e62b5f1b502)
@@ -43,4 +43,16 @@
 
     <listitem>
+      <para>January 31st, 2006</para>
+      <itemizedlist>
+        <listitem>
+          <para>[randy] - Removed the piping of 'yes' commands from the
+          installation of the packages containing Sun license agreements
+          (JDK binary, FOP and FreeTTS) and instead provided a note to
+          reference the text about automating builds.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>January 30th, 2006</para>
       <itemizedlist>
Index: multimedia/audioutils/freetts.xml
===================================================================
--- multimedia/audioutils/freetts.xml	(revision 108024113c4547b611576149c47cfdd0744a4ae0)
+++ multimedia/audioutils/freetts.xml	(revision d4277d4911ffdc99984998fc33603e62b5f1b502)
@@ -110,9 +110,21 @@
     -x {META-INF/*,freetts-&freetts-version;/{acknowledgments.txt,license.terms}}</userinput></screen>
 
+    <tip>
+      <para>The <command>sh jsapi.sh</command> command below installs the Java
+      Speech API components into the <application>FreeTTS</application> source
+      tree. You will be required to view, and then accept (by entering a
+      <keycap>y</keycap> keypress), a license agreement before the installation
+      will continue. If you are scripting (automating) the build, you'll need
+      to account for this. There is information about automating build commands
+      in the <xref linkend="automating-builds"/> section of Chapter 2. Towards
+      the end of this section, specific information for automating this type of
+      installation is discussed.</para>
+    </tip>
+
     <para>Install <application>FreeTTS</application> by running the following
     commands:</para>
 
 <screen><userinput>cd lib &amp;&amp;
-yes | sh jsapi.sh &amp;&amp;
+sh jsapi.sh &amp;&amp;
 cd .. &amp;&amp;
 ant</userinput></screen>
@@ -151,11 +163,7 @@
     <title>Command Explanations</title>
 
-    <para><command>yes | sh jsapi.sh</command>: This command installs the
-    <application>Java Speech API</application> into the
-    <application>FreeTTS</application> source tree. <command>yes</command>
-    is piped so that this command can be scripted and will automatically
-    agree to the JSAPI license terms. You can view the license you are
-    agreeing to at
-    <ulink url="&files-anduin;/jsapi-license.txt"/>.</para>
+    <para><command>sh jsapi.sh</command>: This command installs the
+    <application>Java Speech API</application> components into the
+    <application>FreeTTS</application> source tree.</para>
 
     <para><command>ant</command>: <application>FreeTTS</application> uses the
Index: pst/ps/fop.xml
===================================================================
--- pst/ps/fop.xml	(revision 108024113c4547b611576149c47cfdd0744a4ae0)
+++ pst/ps/fop.xml	(revision d4277d4911ffdc99984998fc33603e62b5f1b502)
@@ -129,4 +129,17 @@
       <title>Installing JAI</title>
 
+      <tip>
+        <para>The
+        <command>$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin</command>
+        command below installs the JAI components in the JDK tree. You will be
+        required to view, and then accept (by entering a <keycap>y</keycap>
+        keypress), a license agreement before the installation will continue.
+        If you are scripting (automating) the build, you'll need to account for
+        this. There is information about automating build commands in the
+        <xref linkend="automating-builds"/> section of Chapter 2. Towards the
+        end of this section, specific information for automating this type of
+        installation is discussed.</para>
+      </tip>
+
       <para>Install the JAI components by running the following commands as
       the <systemitem class="username">root</systemitem> user while in the
@@ -138,5 +151,5 @@
 FOP_BUILD_DIR=$(pwd) &amp;&amp;
 cd $JAVA_HOME &amp;&amp;
-yes | $FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin &amp;&amp;
+$FOP_BUILD_DIR/../jai-1_1_2_01-lib-linux-i586-jdk.bin &amp;&amp;
 cd $FOP_BUILD_DIR</userinput></screen>
 
@@ -250,12 +263,10 @@
     syntax.</para>
 
-    <para><command>yes | $FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This
+    <para><command>$FOP_BUILD_DIR/../jai-...-jdk.bin</command>: This
     command installs the <application>JAI</application> components
-    into the <application>JDK</application> file structure. The
-    <command>yes</command> command is piped through so that you don't have to
-    scroll through four pages of the license agreement and automatically responds
-    <quote>yes</quote> to the agreement. <envar>$FOP_BUILD_DIR</envar> is used as
-    a reference point to the source executable and as a method to return back to
-    the <application>FOP</application> source tree.</para>
+    into the <application>JDK</application> file structure.
+    <envar>$FOP_BUILD_DIR</envar> is used as a reference point to the source
+    executable and as a method to return back to the
+    <application>FOP</application> source tree.</para>
 
     <para><command>sed -i "s/build/lib/" ...</command>: These commands modify
