cvs commit: BLFS/BOOK/x/xorg xorg.ent xorg.xml

bdubbs at bdubbs at
Fri Apr 23 00:36:51 PDT 2004

bdubbs      04/04/23 01:36:51

  Modified:    BOOK     index.xml
               BOOK/introduction/welcome changelog.xml
               BOOK/x/installing xfree86-setup.xml
               BOOK/x/xorg xorg.ent xorg.xml
  Completed xorg section
  Revision  Changes    Path
  1.439     +3 -3      BLFS/BOOK/index.xml
  Index: index.xml
  RCS file: /home/cvsroot/BLFS/BOOK/index.xml,v
  retrieving revision 1.438
  retrieving revision 1.439
  diff -u -r1.438 -r1.439
  --- index.xml	22 Apr 2004 14:04:15 -0000	1.438
  +++ index.xml	23 Apr 2004 07:36:50 -0000	1.439
  @@ -2,9 +2,9 @@
   <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
   			"/usr/share/docbook/docbookx.dtd" [
  -<!ENTITY version "CVS-20040422">
  -<!ENTITY releasedate "April 22nd, 2004">
  -<!ENTITY pubdate "2004-04-22">
  +<!ENTITY version "CVS-20040423">
  +<!ENTITY releasedate "April 23rd, 2004">
  +<!ENTITY pubdate "2004-04-23">
   <!ENTITY blfs-version "cvs">
   <!ENTITY % book SYSTEM "book/book.ent">
  1.1084    +2 -0      BLFS/BOOK/introduction/welcome/changelog.xml
  Index: changelog.xml
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/changelog.xml,v
  retrieving revision 1.1083
  retrieving revision 1.1084
  diff -u -r1.1083 -r1.1084
  --- changelog.xml	22 Apr 2004 21:35:36 -0000	1.1083
  +++ changelog.xml	23 Apr 2004 07:36:50 -0000	1.1084
  @@ -11,6 +11,8 @@
  +<listitem><para>April 23rd, 2004 [bdubbs]: Completed section.</para></listitem>
   <listitem><para>April 22nd, 2004 [igor]: Moved Qt installation to
   /usr with instructions submitted by Tushar Teredesai.</para></listitem>
  1.11      +23 -22    BLFS/BOOK/x/installing/xfree86-setup.xml
  Index: xfree86-setup.xml
  RCS file: /home/cvsroot/BLFS/BOOK/x/installing/xfree86-setup.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- xfree86-setup.xml	14 Oct 2003 00:31:45 -0000	1.10
  +++ xfree86-setup.xml	23 Apr 2004 07:36:51 -0000	1.11
  @@ -1,15 +1,15 @@
   <sect1 id="x-setup">
   <?dbhtml filename="xfree86-setup.html" dir="x"?>
  -<title>XFree86 Components</title>
  +<title>X Window Components</title>
   <title>Checking Direct Rendering Infrastructure (<acronym>DRI</acronym>) Installation</title>
   <para><acronym>DRI</acronym> is a framework for allowing software to access graphics hardware
   in a safe and efficient manner.  It is installed in
  -<application>XFree86</application> by default if 
  +<application>X</application> by default if 
   you have a supported video card.  To check if <acronym>DRI</acronym> is installed properly, 
  -check the log file <filename>/var/log/XFree86.0.log</filename> for statements
  +check the log file <filename>/var/log/XFree86.0.log</filename> or
  +<filename>/var/log/Xorg.0.log</filename> for statements like:</para>
   <screen>(II) R128(0): Direct rendering enabled</screen>
  @@ -32,10 +32,10 @@
   <title>Adding <application>TrueType</application> fonts to
   <para><application>TrueType</application> font support is built into
  -<application>XFree86</application>.  The following items need to 
  +<application>X</application>.  The following items need to 
   be completed to make the fonts available.</para>
  @@ -48,19 +48,18 @@
   <application>TrueType</application> font 
  -<listitem><para>Ensure the <application>TrueType</application> module is loaded in 
  +<listitem><para>Ensure the <application>TrueType</application> module is loaded in the
  +<filename>XF86Config</filename> or <filename>xorg.conf</filename>.</para></listitem>
   <listitem><para>Ensure the <parameter>FontPath</parameter> in 
  -<filename>XF86Config</filename> contains the
  -<application>TrueType</application> font 
  +<filename>XF86Config</filename> or <filename>Xorg.conf</filename> contains the
  +<application>TrueType</application> font directory.</para></listitem>
   <sect3><title>Establish a <application>TrueType</application> font directory</title>
  -<para>The build of <application>XFree86</application> as given above
  +<para>The build of <application>X</application> as given above
   automatically creates a <application>TrueType</application>
   font directory: <filename class="directory">/usr/X11R6/lib/X11/fonts/TTF</filename>.  This
   directory already has some <application>TrueType</application> fonts and is set up correctly.
  @@ -78,7 +77,8 @@
   <screen><userinput><command>mkfontscale &&
  -<sect3><title>Ensure <application>TrueType</application> is loaded in <filename>XF86Config</filename></title> 
  +<sect3><title>Ensure <application>TrueType</application> is loaded in 
  +<filename>XF86Config</filename> or <filename>xorg.conf</filename></title> 
   <para>The "Module" section should look like:
   <screen>Section "Module"
  @@ -102,7 +102,7 @@
   cache files specified in <filename>/etc/fonts/fonts.conf</filename>, run</para>
  -<para><application>XFree86</application> will now be able to use
  +<para><application>X</application> will now be able to use
   <application>TrueType</application> fonts when it is restarted.
   You can check to see if the new fonts are available with the
   <command>xlsfonts</command>  or <command>xfontsel</command> 
  @@ -120,11 +120,11 @@
   <!-- ================================================== -->
   <title>Setting up keyboards</title>
  -<para>In this version of <application>XFree86</application>, it has been reported that non-Latin
  +<para>In this version of <application>X</application>, it has been reported that non-Latin
   keyboard layouts do not include Latin configurations as was previous
   practice. To set up a keyboard for Latin and non-Latin input, 
   change the XkbLayout keyboard driver option in the InputDevice section
  -of the <filename>XF86Config</filename> file.  For example:</para>
  +of the <filename>XF86Config</filename> or <filename>xorg.conf</filename> file.  For example:</para>
   <screen>   Section "InputDevice"
        Identifier          "Keyboard0"
  @@ -145,7 +145,8 @@
   <para><command>xdm</command> provides a graphical logon capability and is
   normally set up in <filename>/etc/inittab</filename>.  Most of the information 
   you need to customize <command>xdm</command> is found in its man page.  To 
  -execute <command>xdm</command> during bootup, change the initdefault level to 5 and add the following lines to <filename>/etc/inittab</filename>:</para>
  +execute <command>xdm</command> during bootup, change the initdefault level to 5 
  +and add the following lines to <filename>/etc/inittab</filename>:</para>
   <para><screen><userinput># Run xdm as a separate service
   x:5:respawn:/usr/X11R6/bin/xdm -nodaemon</userinput></screen></para>
  @@ -153,9 +154,9 @@
   <!-- ================================================== -->
  -<title>Using <application>XFree86</application> Resources</title>
  +<title>Using <application>X</application> Resources</title>
   <para>There are many options that can be set in
  -<application>XFree86</application> and <application>X</application> clients via
  +<application>X</application> and <application>X</application> clients via
   resources.  Typically resources are set in the <filename>~/.Xresources</filename>
  @@ -164,14 +165,14 @@
   <screen>object.subobject[.subobject...].attribute: value</screen>
  -<para>Typically, components of a resource specification are linked together 
  +<para>Components of a resource specification are linked together 
   by either <emphasis>tight</emphasis>, represented by a dot (.),
   or <emphasis>loose</emphasis>, represented by an asterisk (*),  bindings.
   A tight binding indicates that the components on either side of the dot must
   be directly next to each other as defined in a specific implementation.  An
   asterisk is a wildcard character that means that any number of levels in
   a defined hierarchy can be between the components. 
  -For example, XFree86 offers two new cursors: redglass and whiteglass.  To
  +For example, X offers two special cursors: redglass and whiteglass.  To
   use one of these resources, you need to add the following line:</para>
   <screen>Xcursor.theme: whiteglass</screen>
  @@ -192,7 +193,7 @@
   <screen><userinput><command>xrdb -load <filename></command></userinput></screen>
  -<para>To add resources to <application>XFree86</application>'s database in memory use:</para>
  +<para>To add resources to <application>X</application>'s database in memory use:</para>
   <screen><userinput><command>xrdb -merge <filename></command></userinput></screen>
   <para>The <command>xrdb</command> instruction is usually placed in 
  1.2       +1 -1      BLFS/BOOK/x/xorg/xorg.ent
  Index: xorg.ent
  RCS file: /home/cvsroot/BLFS/BOOK/x/xorg/xorg.ent,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- xorg.ent	19 Apr 2004 05:08:03 -0000	1.1
  +++ xorg.ent	23 Apr 2004 07:36:51 -0000	1.2
  @@ -9,4 +9,4 @@
   <!ENTITY xorg-download-ftp "">
   <!ENTITY xorg-size "70.3 MB">
   <!ENTITY xorg-buildsize "645 MB">
  -<!ENTITY xorg-time "tbd SBU">
  +<!ENTITY xorg-time "17.1 SBU">
  1.2       +336 -27   BLFS/BOOK/x/xorg/xorg.xml
  Index: xorg.xml
  RCS file: /home/cvsroot/BLFS/BOOK/x/xorg/xorg.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- xorg.xml	19 Apr 2004 05:08:03 -0000	1.1
  +++ xorg.xml	23 Apr 2004 07:36:51 -0000	1.2
  @@ -1,35 +1,35 @@
   <sect1 id="xorg" xreflabel=";">
   <?dbhtml filename="xorg.html" ?>
  -<title>Introduction to <application></application></title>
  +<title>Introduction to <application>Xorg</application></title>
   <note><para>There are two packages in BLFS that implement the <application>X</application> 
  -Window System: <application></application> and <application>XFree86</application>.  
  -These packages are quite similar.  In fact the base system of <application></application>
  +Window System: <application>Xorg</application> and <application>XFree86</application>.  
  +These packages are quite similar.  In fact the base system of <application>Xorg</application>
   is <application>XFree86</application>-RC2.  The primary difference as of this writing is 
   the license provisions of the packages.  For someone building a package for their own use,
   these issues are not significant.  Most large commercial distributions have decided
  -to use the  <application></application> package, but several still use 
  +to use the  <application>Xorg</application> package, but several still use 
   <para>A second reason for the forking of X packages is the stated goals of the 
   developers.  Some developers were unhappy with the administration and progress of 
  -<application>XFree86</application>.'s future plans include significant 
  +<application>XFree86</application>.  Xorg's future plans include significant 
   improvements to the internals of the system and more frequent releases.</para>
   <para><application>XFree86</application> continues to be a solid, conservitive 
   application with excellent driver support.</para>
  -<para>Both <application></application> and <application>XFree86</application>
  +<para>Both <application>Xorg</application> and <application>XFree86</application>
   can be installed in the same way, but this section will provide a slightly
   different and more current variation for installation.</para>
  -<para><application></application> is a freely redistributable open-source
  +<para><application>Xorg</application> is a freely redistributable open-source
   implementation of the <application>X</application> Window System. 
   This application  provides a client/server interface between display
   hardware (the mouse, keyboard, and video displays) and the desktop environment
  @@ -46,7 +46,7 @@
  -<sect3><title><application></application> dependencies</title>
  +<sect3><title><application>Xorg</application> Dependencies</title>
   <para><xref linkend="libpng"/>, <xref linkend="expat"/>, <xref linkend="freetype2"/> 
  @@ -69,7 +69,7 @@
  -<para>The first package contains the <application></application> libraries amd 
  +<para>The first package contains the <application>Xorg</application> libraries amd 
   support programs,  the second contains standard X programs, the third contains the 
   X server, the fourth and fifth are fonts, the sixth is normal documentation, and the seventh
   is hardcopy documentation.</para> 
  @@ -84,30 +84,339 @@
  -<title>Installation of</title>
  -<para>Under Construction</para>
  +<title>Installation of <application>Xorg</application></title>
  -<title>Command Explainations</title>
  -<para>Under Construction</para>
  +<title>Kernel Compilation Settings</title>
  +<para>If you have an Intel P6 (Pentium Pro, Pentium II and later) it is recommended
  +that you compile <acronym>MTRR</acronym> (Memory Type Range Registers) support into the kernel.
  +The kernel can map Cyrix and AMD <acronym>CPU</acronym>s to the
  +<acronym>MTRR</acronym> interface so selecting this
  +option is useful for those processors also. This option is found in the
  +"Processor type and features" menu.  It can increase performance of
  +image write operations 2.5 times or more on <acronym>PCI</acronym> or
  +<acronym>AGP</acronym> video cards.</para>
  +<para>In the "Character Devices" section, enable <acronym>AGP</acronym> Support and 
  +select the chipset support on your motherboard.  If you do not know the chipset, 
  +you may select all the chip types at the expense of extra kernel size. You can usually
  +determine your motherboard's chipset by doing:</para>
  +<screen><userinput><command>cat /proc/pci</command></userinput></screen>
  +<para>In the "Character Devices" section, <emphasis>disable</emphasis> Direct
  +Rendering Manager unless you have a Direct Rendering Infrastructure
  +supported video card.  A complete list of <acronym>DRI</acronym> supported video cards can
  +be found at <ulink url="" /> in the Status section.
  +Currently, supported cards include those from 3dfx (Voodoo, Banshee), 3Dlabs,
  +ATI (Rage Pro, Rage 128,
  +Radeon 7X00, Radeon 2), Intel (i810, i815), and Matrox (G200, G400, G450).
  +If you do enable <acronym>DRI</acronym> here, make sure you select the video card(s) you want
  +to support as a <emphasis>module</emphasis>.</para>
  +<para>Additionally NVidia provides their own closed source binary drivers,
  +which do not make use of <acronym>DRI</acronym>. If you intend to use these drivers,
  +do not enable <acronym>DRI</acronym>.</para>
  +<para>If you made any changes to the kernel configuration, recompile the kernel.</para>
  +<para>Copy <filename>/usr/src/linux/arch/i386/boot/bzImage</filename> and
  +<filename>/usr/src/linux/</filename> to
  +<filename>/boot</filename>, edit <filename>/etc/lilo.conf</filename>
  +appropriately and run <filename>lilo</filename>. If you use
  +<filename>grub</filename>, edit <filename>/boot/grub/grub.conf</filename>
  +and add the new kernel to the boot menu.
  +<note><para>If you build <application>Xorg</application> in a chroot environment, 
  +make sure the kernel version of the base system and the target system are the same.  
  +This is especially important if you enabled <acronym>DRI</acronym> support as a module as
  +instructed above.</para></note>
  +<sect3><title>Setting Up a Shadow Directory</title>  
  +<para>When building <application>Xorg</application> you should create
  +a shadow directory of symbolic links for the compiled code.  To do that, we first
  +make the <application>lndir</application>.  Starting from the 
  +<filename class='directory'>xc</filename> directory:</para>
  +<screen><userinput><command>pushd config/util &&
  +make -f Makefile.ini lndir &&
  +cp lndir /usr/bin/ &&
  +<para>Now create the shadow tree:</para>
  +<screen><userinput><command>mkdir ../xcbuild &&
  +cd ../xcbuild &&
  +lndir ../xc</command></userinput></screen>
  +<sect3><title>Creating <filename>host.def</filename></title>  
  +<para>The next step is to create the <filename>config/cf/host.def</filename> file.
  +The documentation for <application>Xorg</application> indicates that the 
  +application will build without a <filename>host.def</filename> file, but
  +the included libraries for <application>fontconfig</application> and 
  +<application>freetype2</application> do not build properly on a base LFS system so 
  +we must specify that we have those and some other libraries too.</para>
  +<note><para><filename>config/cf/host.def</filename> is a C file, not a shell 
  +script.  Be sure to make sure the comments delimited by /* ... */ are
  +balanced when modifying the file. </para></note>
  +<screen><userinput><command>cat > config/cf/host.def << "EOF"</command>
  +/* Begin Xorg host.def file */
  +/* System Related Information.  If you read and configure only one
  + * section then it should be this one.  The Intel architecture defaults are
  + * set for a i686 and higher.  Axp is for the Alpha architecture and Ppc is
  + * for the Power PC.  AMD64 is for the Opteron processor. Note that there have 
  + * been reports that the Ppc optimization line causes segmentation faults during 
  + * build.  If that happens, try building without the DefaultGcc2PpcOpt line.  ***********/
  +/* #define DefaultGcc2i386Opt -O2 -fno-strength-reduce -fno-strict-aliasing -march=i686 */
  +/* #define DefaultGccAMD64Opt -O2 -fno-strength-reduce -fno-strict-aliasing */
  +/* #define DefaultGcc2AxpOpt  -O2 -mcpu=ev6 */
  +/* #define DefaultGcc2PpcOpt  -O2 -mcpu=750 */
  +#define HasFreetype2             YES
  +#define HasFontconfig            YES
  +#define HasExpat                 YES
  +#define HasLibpng                YES
  +#define HasZlib                  YES
  + * Which drivers to build.  When building a static server, each of these
  + * will be included in it.  When building the loadable server each of these
  + * modules will be built.
  + *
  +#define XF86CardDrivers         mga glint nv tga s3virge sis rendition \
  +                                neomagic i740 tdfx savage \
  +                                cirrus vmware tseng trident chips apm \
  +                                GlideDriver fbdev i128 \
  +                                ati AgpGartDrivers DevelDrivers ark cyrix \
  +                                siliconmotion \
  +                                vesa vga XF86OSCardDrivers XF86ExtraCardDrivers
  + * Select the XInput devices you want by uncommenting this.
  + *
  +#define XInputDrivers           mouse keyboard acecad calcomp citron \
  +                                digitaledge dmc dynapro elographics \
  +                                microtouch mutouch penmount spaceorb summa \
  +                                wacom void magictouch aiptek
  + */
  +/* Most installs will only need this */
  -<para>Under Construction</para>
  +#define XInputDrivers           mouse keyboard
  +/* End Xorg host.def file */
  +<para>There are several other options that you may want to consider.  A well documented
  +example file is <filename>config/cf/</filename>.</para>
  +<title>Build Commands</title>
  +<para>Install <application>Xorg</application> by running the following commands:</para>
  +<screen><userinput><command>( make World 2>&1 | tee xorg-compile.log && exit $PIPESTATUS ) &&
  +make install &&
  +make &&
  +ln -sf ../X11R6/bin /usr/bin/X11 &&
  +ln -sf ../X11R6/lib/X11 /usr/lib/X11 &&
  +ln -sf ../X11R6/include/X11 /usr/include/X11</command></userinput></screen>
  +<title>Updating Direct Rendering Infrastructure (<acronym>DRI</acronym>)</title>
  +<para>If you have one of the supported <acronym>DRI</acronym> cards and
  +have enabled <acronym>DRI</acronym> kernel modules as explained
  +above, you now need to update the kernel modules to ensure they are compatible with the
  +current version of <application>Xorg</application>.  To do this, perform the following:</para>
  +<screen><userinput><command>cd programs/Xserver/hw/xorg/os-support/linux/drm/kernel &&
  +make  CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux  &&
  +mkdir -p /lib/modules/`uname -r`/kernel/drivers/char/drm/  &&
  +cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o \
  +    /lib/modules/`uname -r`/kernel/drivers/char/drm/  &&
  +depmod -a</command></userinput></screen>
  +<warning><para>If you recompile or upgrade your kernel, you will need to re-copy the
  +appropriate driver module(s)
  +to the kernel module library and rerun the <command>depmod -a</command> command.</para></warning>
  +<note><para>If you created <acronym>AGP</acronym> support as a module when compiling 
  +the kernel, you may have to add a line to <filename>/etc/modules.conf</filename> to ensure
  +the agpgart module is loaded.  For instance, the <acronym>AGP</acronym> version of the 
  +Radeon video card will use the <filename>radeon.o</filename> driver.  It will
  +need to have the line <screen>below radeon agpgart</screen> in
  +<filename>/etc/modules.conf</filename> to enable <acronym>DRI</acronym> support.</para></note>
  +<title>Command explanations</title>
  +<para><command>( make World 2>&1 | tee xorg-compile.log
  +   && exit $PIPESTATUS )</command>:
  +This command runs multiple makefiles to completely rebuild the system.
  +<parameter>2>&1</parameter> redirects error messages
  +to the same location as normal output. The <command>tee</command> command
  +allows viewing of the output while logging the results to a file. The parentheses
  +around the command run the entire comand in a subshell and finally the
  +<command>exit $PIPESTATUS</command> ensures the result of the <command>make</command>
  +is returned as the result and not the result of the <command>tee</command> command.</para>
  +<note><para>When rebuilding <application>Xorg</application>, a separate command that may 
  +be used if only minor changes are made to the sources is <command>make
  +Everything</command>.  This does not automatically remove generated
  +files and only rebuilds those files or programs that are out
  +of date.</para></note>
  +<para><screen><command>ln -sf ../X11R6/bin /usr/bin/X11
  +ln -sf ../X11R6/lib/X11 /usr/lib/X11
  +ln -sf ../X11R6/include/X11 /usr/include/X11</command></screen>
  +These commands are present to enable other (broken) packages to build
  +against <application>Xorg</application>.  We do this even though the i
  +Filesystem Hierarchy Standard says:
  +"In general, software must not be installed or managed via the above
  +symbolic links. They are intended for utilization by users only."</para>
  +<para><command>make  CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux</command>: This builds the
  +<application>Xorg</application> compatible kernel modules using the same compiler used to compile
  +the kernel.</para>
  +<para><command>cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o
  +/lib/modules/`uname -r`/kernel/drivers/char/drm/</command>: Put the kernel
  +module(s) where the kernel can find them. You only need to copy the driver you
  +need to support your video card.</para>
  +<para><command>depmod -a</command>: Update the modules.dep file for module
  +<title>Configuring Xorg</title>
  +<para>Edit <filename>/etc/</filename> and add
  +<filename class="directory">/usr/X11R6/lib</filename>.
  +Run</para> <screen><userinput><command>ldconfig</command></userinput></screen>
  +<para>Add <filename class='directory'>/usr/X11R6/bin</filename> to your
  +<envar>PATH</envar> environment
  +variable in <filename>.bash_profile</filename> or <filename>/etc/profile</filename>.  
  +The statement should look something like <parameter>PATH=$PATH:/usr/X11R6/bin</parameter>
  +and be placed before the <command>export PATH</command>
  +<para>Expand the <envar>PKG_CONFIG_PATH</envar> so that other packages
  +can find <application>Xorg</application> libraries. Add the following line to
  +<filename>.bash_profile</filename> for root user:</para>
  +<screen><userinput><command>export PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig</command></userinput></screen>
  +<screen><userinput><command>source ~/.bash_profile</command></userinput></screen>
  +<para>Set up your mouse:
  +<screen><userinput><command>ln -s psaux /dev/mouse</command></userinput></screen>
  +Adjust the symbolic link as necessary for other types of mice.  For instance,
  +a serial mouse on the first serial port would be linked to ttyS1.</para>
  +<para>Create the <filename>xorg.conf</filename> file with
  +<screen><userinput><command>cd ~
  +Xorg -configure</command></userinput></screen>
  +The screen will go black and you may hear some clicking of the monitor.  This
  +command will create a file, <filename></filename> in your home
  +<para>Edit <filename></filename> to suit your system.  The
  +details of the file are located in the man
  +page <command>man xorg.conf</command>.  Some things you may want to
  +do are:</para>
  +<listitem><para>Section "Files". Change the order of the font paths searched.
  +You may want to put 100dpi fonts ahead of 75dpi fonts if your system normally
  +comes up closer to 100 dots per inch.  You may want to remove some font
  +directories completely.</para></listitem>
  +<listitem><para>Section "Monitor".  Specify the <parameter>VertRefresh</parameter>
  +and <parameter>HorizSync</parameter> values if the system does not automatically
  +detect the monitor and its values.</para></listitem>
  +<listitem><para>Section "InputDevice".  You may want to change the keyboard
  +autorepeat rate by
  +adding <parameter>Option "Autorepeat" "250 30"</parameter>.</para></listitem>
  +<listitem><para>Section "Device".  You may want to set some of the options
  +available for your selected video driver.  A description of the driver
  +parameters is in the man page for your driver.</para></listitem>
  +<listitem><para>Section "Screen".  Add a DefaultDepth statement such
  +as: <parameter>DefaultDepth 16</parameter>. In the SubSection for your
  +default depth, add a modes line such
  +as: <parameter> Modes "1280x1024" "1024x768"</parameter>.
  +The first mode listed will normally be the starting
  +<para>Test the system with
  +<screen><userinput><command>Xorg -config ~/</command></userinput></screen>
  +You will only get a gray background with an X-shaped mouse cursor, but it
  +confirms the system is working.  Exit with Control-Alt-Backspace.  If the
  +system does not work, take a look
  +at <filename>/var/log/Xorg.0.log</filename> to see what went
  +<para>Move the configuration file to its final location</para>
  +<screen><userinput><command>mv ~/ /etc/X11/xorg.conf</command></userinput></screen>
  +<para>Create <filename>.xinitrc</filename>
  +<screen><userinput><command>cat > ~/.xinitrc << "EOF"</command>
  +# Begin .xinitrc file
  +xterm  -g 80x40+0+0   &
  +xclock -g 100x100-0+0 &
  +This provides an initial screen with an xterm and a clock that is managed by a
  +simple window manager, Tab Window Manager.  For details of twm, see the
  +man page.</para>
  +<para>When needed, <application>Xorg</application> creates the directory
  +<filename>/tmp/.ICE-unix</filename> if it does not exist. If this directory is
  +not owned by root, <application>Xorg</application> delays startup by a few seconds
  +and also appends a warning to the logfile. This also affects startup of other
  +applications. To improve performance, it is advisable to manually create the directory
  +before Xorg uses it. Add the file creation to <filename>/etc/sysconfig/createfiles</filename>
  +that is sourced by the
  +<filename>/etc/rc.d/init.d/cleanfs</filename> startup script.</para>
  +<screen><userinput><command>cat >> /etc/sysconfig/createfiles << "EOF"</command>
  +/tmp/.ICE-unix dir 1777 root root
  +<para>Start <application>X</application> with
  +to get basic functional <application>X</application> Window System.</para>
  +<para>At this point, you should check out the X Window Components at 
  +<xref linkend='x-setup'/>.</para>

More information about the blfs-book mailing list