[blfs-book] r11066 - in trunk/BOOK: . introduction/welcome postlfs/security x/installing

bdubbs at higgs.linuxfromscratch.org bdubbs at higgs.linuxfromscratch.org
Thu Mar 7 19:49:03 PST 2013


Author: bdubbs
Date: Thu Mar  7 19:49:03 2013
New Revision: 11066

Log:
Correct some font links.
Reword DRI description.
Do some general reformatting.

Modified:
   trunk/BOOK/general.ent
   trunk/BOOK/introduction/welcome/changelog.xml
   trunk/BOOK/postlfs/security/openssl.xml
   trunk/BOOK/x/installing/xorg-config.xml

Modified: trunk/BOOK/general.ent
==============================================================================
--- trunk/BOOK/general.ent	Wed Mar  6 18:30:41 2013	(r11065)
+++ trunk/BOOK/general.ent	Thu Mar  7 19:49:03 2013	(r11066)
@@ -4,12 +4,12 @@
 -->
 
 <!ENTITY day          "04">                   <!-- Always 2 digits -->
-<!ENTITY month        "06">                   <!-- Always 2 digits -->
+<!ENTITY month        "07">                   <!-- Always 2 digits -->
 <!ENTITY year         "2013">
 <!ENTITY copyrightdate "2001-&year;">
 <!ENTITY copyholder   "The BLFS Development Team">
 <!ENTITY version      "&year;-&month;-&day;">
-<!ENTITY releasedate  "March 6th, &year;">
+<!ENTITY releasedate  "March 7th, &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
 <!ENTITY lfs-version  "development">          <!-- version|testing|unstable|development] -->

Modified: trunk/BOOK/introduction/welcome/changelog.xml
==============================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml	Wed Mar  6 18:30:41 2013	(r11065)
+++ trunk/BOOK/introduction/welcome/changelog.xml	Thu Mar  7 19:49:03 2013	(r11066)
@@ -44,6 +44,20 @@
 
 -->
     <listitem>
+      <para>March 7th, 2013</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Fix link to Chineese fonts.  Fixes
+          <ulink url="&blfs-ticket-root;3821">#3821</ulink>.</para>
+        </listitem>
+        <listitem>
+          <para>[bdubbs] - Update wording of DRI detection in Xorg
+          configuration.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>March 6th, 2013</para>
       <itemizedlist>
         <listitem>

Modified: trunk/BOOK/postlfs/security/openssl.xml
==============================================================================
--- trunk/BOOK/postlfs/security/openssl.xml	Wed Mar  6 18:30:41 2013	(r11065)
+++ trunk/BOOK/postlfs/security/openssl.xml	Thu Mar  7 19:49:03 2013	(r11066)
@@ -107,7 +107,11 @@
     </para>
 
 <screen><userinput>patch -Np1 -i ../openssl-&openssl-version;-fix_manpages-1.patch &&
-./config --prefix=/usr --openssldir=/etc/ssl shared zlib-dynamic &&
+
+./config --prefix=/usr         \
+         --openssldir=/etc/ssl \
+         shared                \
+         zlib-dynamic &&
 make</userinput></screen>
 
     <para>

Modified: trunk/BOOK/x/installing/xorg-config.xml
==============================================================================
--- trunk/BOOK/x/installing/xorg-config.xml	Wed Mar  6 18:30:41 2013	(r11065)
+++ trunk/BOOK/x/installing/xorg-config.xml	Thu Mar  7 19:49:03 2013	(r11066)
@@ -47,11 +47,15 @@
 
     <para>
       To check if DRI drivers are installed properly, check the log file
-      <filename>/var/log/Xorg.0.log</filename> for statements like:
+      <filename>/var/log/Xorg.0.log</filename> for statements such as:
     </para>
 
 <screen><literal>(II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
 
+    <para>or</para>
+
+<screen><literal>(II) NOUVEAU(0): Loaded DRI module</literal></screen>
+
     <note>
       <para>
         DRI configuration may differ if you are using alternate drivers, such
@@ -66,14 +70,14 @@
       is only available to <systemitem class="username">root</systemitem> and members
       of the <systemitem class="groupname">video</systemitem> group.
     </para>
-
+<!--
     <para>
       To see if hardware acceleration is available for your driver, look in
       <filename>/var/log/Xorg.0.log</filename> for statements like:
     </para>
 
 <screen><literal>(II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
-
+-->
     <para>
       If your driver is supported, add any users that might use X to that group:
     </para>
@@ -81,8 +85,9 @@
 <screen role="root"><userinput>usermod -a -G video <replaceable><username></replaceable></userinput></screen>
 
     <para>
-      If you have installed two OpenGL demo programs when you installed
-      <xref linkend="mesalib"/>, from an X terminal, run <command>glxinfo</command>
+      Another way to determine if DRI is working properly is to use one of the
+      two optionally installed OpenGL demo programs in <xref
+      linkend="mesalib"/>. From an X terminal, run <command>glxinfo</command>
       and look for the phrase:
     </para>
 
@@ -97,23 +102,24 @@
     </para>
 
     <para>
-      If DRI2 is enabled, to confirm that DRI2 hardware acceleration is working you can
-      (still in the X terminal) run the command
-      <command>glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</command>
-      - if that reports something <emphasis>other than</emphasis>
-      <literal>Software Rasterizer</literal> then you have working acceleration for the
-      user who ran the command.
+      To confirm that DRI2 hardware acceleration is working, you can (still in
+      the X terminal) run the command <command>glxinfo | egrep "(OpenGL
+      vendor|OpenGL renderer|OpenGL version)"</command>.
+      If that reports something <emphasis>other than</emphasis>
+      <literal>Software Rasterizer</literal> then you have working
+      acceleration for the user who ran the command.
     </para>
 
     <para>
-      If your hardware does not have any DRI2 driver available, it will use Software Rasterizer
-      for Direct Rendering. In such cases, it is recommended that you use new, LLVM-accelerated,
-      Software Rasterizer called LLVMPipe. In order to build LLVMPipe just make sure that
-      <xref linkend="llvm"/> is present at MesaLib build time. Please note that all decoding is
-      done on CPU instead of GPU, so expect that things run slower. To check if you are using
-      LLVMpipe, run
-      <command>glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</command>.
-      An example output is shown below:
+      If your hardware does not have any DRI2 driver available, it will use a
+      Software Rasterizer for Direct Rendering. In such cases, you can use a new,
+      LLVM-accelerated, Software Rasterizer called LLVMPipe. In order to build
+      LLVMPipe just make sure that <xref linkend="llvm"/> is present at MesaLib
+      build time. Note that all decoding is done on the CPU instead of the GPU,
+      so the display will run slower than with hardware acceleration.  
+      To check if you are using LLVMpipe,
+      review the output ot the glxinfo command above.  An example of the
+      output using the Software Rasterizer is shown below:
     </para>
 
 <screen><computeroutput>OpenGL vendor string: VMware, Inc.
@@ -121,18 +127,19 @@
 OpenGL version string: 2.1 Mesa 9.1-devel (git-cb3b172)</computeroutput></screen>
 
     <para>
-      You can always force LLVMPipe by exporting <envar>LIBGL_ALWAYS_SOFTWARE=1</envar>
-      environment variable.
+      You can also force LLVMPipe by exporting the <envar>LIBGL_ALWAYS_SOFTWARE=1</envar>
+      environment variable when starting Xorg.
     </para>
 
     <para>
-      Again, if you have built Mesa OpenGL demos, you can also run the test program
-      <command>glxgears</command>. This program brings up a window with three gears
-      turning. The X terminal will display how many frames were drawn every five
-      seconds, so this is a reasonable benchmark. The window is scalable, and the
-      frames drawn per second is highly dependent on the size of the window. On some
-      hardware, <command>glxgears</command> will run synchronized to vertical refresh
-      and framerate will be approximately the same as the monitor refresh rate.
+      Again, if you have built the Mesa OpenGL demos, you can also run the test
+      program <command>glxgears</command>. This program brings up a window with
+      three gears turning. The X terminal will display how many frames were
+      drawn every five seconds, so this will give a rough benchmark. The window
+      is scalable, and the frames drawn per second is highly dependent on the
+      size of the window. On some hardware, <command>glxgears</command> will
+      run synchronized with the vertical refresh signal and the frame rate will
+      be approximately the same as the monitor refresh rate.
     </para>
 
     </sect2>
@@ -150,14 +157,14 @@
     <para>
       In order to use PRIME for GPU switching, make sure that you are using Linux
       Kernel 3.4 or later (recommended). You will need latest DRI and DDX drivers
-      for your hardware and <application>Xorg Server</application> 1.13 with an
-      optional patch applied.
+      for your hardware and <application>Xorg Server</application> 1.13 or later
+      with an optional patch applied.
     </para>
 
     <para>
       <application>Xorg Server</application> should load both GPU drivers automaticaly.
       In order to run a GLX application on a discrete GPU, you will need to export
-      <envar>DRI_PRIME=1</envar> environment variable. For example,
+      the <envar>DRI_PRIME=1</envar> environment variable. For example,
 
 <screen><userinput>DRI_PRIME=1 glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</userinput></screen>
 
@@ -165,48 +172,12 @@
     </para>
 
     <para>
-      If the last command reports same OpenGL renderer with and without <envar>DRI_PRIME=1</envar>,
-      you will need to check your installation.
+      If the last command reports same OpenGL renderer with and without
+      <envar>DRI_PRIME=1</envar>, you will need to check your installation.
     </para>
 
     </sect2>
 
-<!--
-    <sect2 role="configuration" id='X11R6-compat-symlink'
-         xreflabel="Creating an X11R6 Compatibility Symlink">
-
-    <title>Creating an X11R6 Compatibility Symlink</title>
-
-    <para>Until recently (relatively speaking) almost every
-    <application>X Window</application> installation you performed or came
-    across was installed in the
-    <filename class='directory'>/usr/X11R6</filename> directory. That was the
-    standard for years. Developers picked up on this and wrote their package
-    installation scripts looking for <application>X</application> in the
-    standard location. Things have changed and the trend is to now install
-    <application>X</application> in
-    <filename class='directory'>/usr</filename>. Some people want to install
-    it in a custom location.</para>
-
-    <para>Many package developers have not caught up to the change and their
-    packages are still trying to find <application>X</application> in
-    <filename class='directory'>/usr/X11R6</filename> and subsequently fail
-    when you try to build the package. Though for most packages it is not
-    difficult to 'hack' the installation script to fix the problem, that is not
-    the long term solution to the problem. Upstream developers need to modernize
-    their installation scripts and eliminate the problem altogether.</para>
-
-    <para>Until then, you can create a symbolic link to satisfy the
-    <filename class='directory'>/usr/X11R6</filename> requirement so that you
-    won't be inconvenienced with a package build failure due to this known
-    issue. If you wish to create the symlink, issue the following command as
-    the <systemitem class="username">root</systemitem>:</para>
-
-<screen role="root"><userinput>ln -vsf $XORG_PREFIX /usr/X11R6</userinput></screen>
-
-    </sect2>
--->
-
     <sect2 role="configuration" id="xft-font-protocol"  xreflabel="Xft Font Protocol">
       <title>Xft Font Protocol</title>
 
@@ -291,7 +262,7 @@
         </listitem>
         <listitem>
           <para><ulink
-          url="http://cle.linux.org.tw/fonts/FireFly">Firefly New Sung font</ulink>
+          url="http://sourceforge.jp/projects/sfnet_chinesepuppy/downloads/ChineseSupport/Fonts/fireflysung-1.3.0.tar.gz">Firefly New Sung font</ulink>
           - This font provides Chinese coverage. This font is listed in the
           aliases in the
           the <filename class="directory">/etc/fonts/fonts.d</filename>
@@ -299,7 +270,7 @@
         </listitem>
         <listitem>
           <para><ulink
-          url="http://cle.linux.org.tw/fonts/Arphic">Arphic fonts</ulink> -
+          url="http://packages.debian.org/sid/fonts-arphic-ukai">Arphic fonts</ulink> -
           A similar set of Chinese fonts to the Firefly New Sung font.
           These fonts are listed in the aliases in the
           <filename class="directory">/etc/fonts/fonts.d</filename> directory
@@ -334,9 +305,13 @@
       more information, please visit the <ulink
       url="http://unifont.org/fontguide/">Unicode Font Guide</ulink>.</para>
 
-      <para>As an example, consider the installation of the DejaVu fonts.  From
-      the unpacked source directory, run the following commands as the
-      <systemitem class="username">root</systemitem> user:</para>
+      <para>Rendered examples of many of the above fonts can be found at this
+      <ulink url="http://homepage.ntlworld.com/zarniwhoop/ttf-font-analysis/">
+      font analysis</ulink> site.</para>
+
+      <para>As a font installation example, consider the installation of the 
+      DejaVu fonts.  From the unpacked source directory, run the following 
+      commands as the <systemitem class="username">root</systemitem> user:</para>
 
 <screen role="root"><userinput>install -v -d -m755 /usr/share/fonts/dejavu &&
 install -v -m644 *.ttf /usr/share/fonts/dejavu &&
@@ -346,6 +321,7 @@
 
   <sect2 role="configuration" id='xconfig'>
     <title>Setting up Xorg Devices</title>
+
     <para>For most hardware configurations, modern Xorg will automatically
     get the server configuration correct without any user intervention. There
     are, however, some cases where auto-configuration will be incorrect.
@@ -359,6 +335,7 @@
 
     <para>A sample default XKB setup could look like the following (executed as
     the <systemitem class="username">root</systemitem> user):</para>
+
 <screen><userinput role="username">cat > /etc/X11/xorg.conf.d/xkb-defaults.conf << "EOF"
 Section "InputClass"
     Identifier "XKB Defaults"
@@ -370,6 +347,7 @@
 
   <sect3 id="xdisplay">
   <title>Fine Tuning Display Settings</title>
+  
   <para>Again, with modern Xorg, little or no additional configuration is
   necessary. If you should need extra options passed to your video driver,
   for instance, you could use something like the following (again, executed as



More information about the blfs-book mailing list