Changeset d5d9ceb


Ignore:
Timestamp:
07/25/2004 11:35:18 PM (20 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
df4e00d
Parents:
cadb42f
Message:

Added instructions to comment out linux/config.h from the source video driver files and made various fixes to Xorg

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

Files:
3 edited

Legend:

Unmodified
Added
Removed

  • introduction/welcome/changelog.xml

    rcadb42f rd5d9ceb  
    2424<listitem><para>July 25th, 2004 [randy]: Added instructions to remove
    2525linux/config.h includes from source video driver files and made various
    26 fixes to XFree86.</para></listitem>
     26fixes to XFree86 and Xorg.</para></listitem>
    2727
    2828<listitem><para>July 24th, 2004 [randy]: Added instructions to install

  • x/installing/xfree86.xml

    rcadb42f rd5d9ceb  
    527527to get a basic functional <application>X</application> Window System.</para>
    528528
     529<para>At this point, you should check out <xref linkend='x-setup'/>.</para>
     530
    529531</sect2>
    530532

  • x/installing/xorg.xml

    rcadb42f rd5d9ceb  
    2020<title>Introduction to <application>Xorg</application></title>
    2121
    22 <note><para>There are two packages in BLFS that implement the <application>X</application>
    23 Window System: <application>Xorg</application> and <application>XFree86</application>. 
    24 These packages are quite similar.  In fact, the base system of <application>Xorg</application>
    25 is <application>XFree86</application>-RC2.  The primary difference as of this writing is
    26 the license provisions of the packages.  For someone building a package for their own use,
    27 these issues are not significant.  Most large commercial distributions have decided
    28 to use the  <application>Xorg</application> package, but several still use
     22<note><para>There are two packages in <acronym>BLFS</acronym> that implement
     23the <application>X</application> Window System: <application>Xorg</application>
     24and <application>XFree86</application>. These packages are quite similar. In
     25fact, the base system of <application>Xorg</application> is
     26<application>XFree86</application>-RC2. The primary difference as of this
     27writing is the license provisions of the packages.  For someone building a
     28package for their own use, these issues are not significant.  Most large
     29commercial distributions have decided to use the 
     30<application>Xorg</application> package, but several still use
    2931<application>XFree86</application>.</para>
    3032
    31 <para>A second reason for the forking of X packages is the stated goals of the
    32 developers.  Some developers were unhappy with the administration and progress of
    33 <application>XFree86</application>.  Xorg's future plans include significant
    34 improvements to the internals of the system and more frequent releases.</para>
     33<para>A second reason for the forking of <application>X</application> packages
     34is the stated goals of the developers. Some developers were unhappy with the
     35administration and progress of <application>XFree86</application>. X.org's
     36future plans include significant improvements to the internals of the system
     37and more frequent releases.</para>
    3538
    3639<para><application>XFree86</application> continues to be a solid, conservative
    3740application with excellent driver support.</para>
    3841
    39 <para>Both <application>Xorg</application> and <application>XFree86</application>
    40 can be installed in the same way, but this section will provide a slightly
    41 different and more current variation for installation.</para>
     42<para>Both <application>Xorg</application> and
     43<application>XFree86</application> can be installed in the same way, but this
     44section will provide a slightly different and more current variation for
     45installation.</para>
    4246</note>
    4347
    44 
    4548<para><application>Xorg</application> is a freely redistributable open-source
    46 implementation of the <application>X</application> Window System.
    47 This application  provides a client/server interface between display
    48 hardware (the mouse, keyboard, and video displays) and the desktop environment,
    49 while also providing both the windowing infrastructure and a standardized
    50 application interface (<acronym>API</acronym>).</para>
     49implementation of the <application>X</application> Window System. This
     50application provides a client/server interface between display hardware (the
     51mouse, keyboard, and video displays) and the desktop environment, while also
     52providing both the windowing infrastructure and a standardized application
     53interface (<acronym>API</acronym>).</para>
    5154 
    5255<sect3><title>Package information</title>
    … …  
    5962</sect3>
    6063 
    61  
    6264<sect3><title><application>Xorg</application> Dependencies</title>
    6365 
    6466<sect4><title>Required</title>
    65 <para><xref linkend="libpng"/>, <xref linkend="expat"/>, <xref linkend="freetype2"/> and
    66 <xref linkend="fontconfig"/>.</para>
     67<para><xref linkend="libpng"/>, <xref linkend="expat"/>,
     68<xref linkend="freetype2"/> and <xref linkend="fontconfig"/>.</para>
    6769</sect4>
    6870
    … …  
    7375</sect3>
    7476 
    75  
    7677<sect3><title>Download Instructions</title>
    7778 
    78 <para>There are several files that need to be fetched from the download location:</para>
     79<para>There are several files that need to be fetched from the download
     80location:</para>
    7981<itemizedlist spacing='compact'>
    8082<listitem><para><filename>X11R6.7.0-src1.tar.gz</filename></para></listitem>
    … …  
    8789</itemizedlist>
    8890
    89 <para>The first package contains the <application>Xorg</application> libraries and
    90 support programs,  the second contains standard X programs, the third contains the
    91 X server, the fourth and fifth are fonts, the sixth is normal documentation, and the seventh
     91<para>The first package contains the <application>Xorg</application> libraries
     92and support programs, the second contains standard <application>X</application>
     93programs, the third contains the <application>X</application> server, the
     94fourth and fifth are fonts, the sixth is normal documentation, and the seventh
    9295is hardcopy documentation.</para>
    9396 
    94 <para>To check your downloads for integrity, download the <filename>md5sums</filename>
    95 file. Then:</para>
     97<para>To check your downloads for integrity, download the
     98<filename>md5sums</filename> file. Then:</para>
    9699 
    97100<screen><userinput><command>md5sum -c md5sums</command></userinput></screen>
    … …  
    104107<title>Installation of <application>Xorg</application></title>
    105108
    106 
    107109<sect3>
    108110<title>Kernel Compilation Settings</title>
    109 <para>If you have an Intel P6 (Pentium Pro, Pentium II and later), it is recommended
    110 that you compile <acronym>MTRR</acronym> (Memory Type Range Registers) support into the kernel.
    111 The kernel can map Cyrix and AMD <acronym>CPU</acronym>s to the
    112 <acronym>MTRR</acronym> interface, so selecting this
    113 option is useful for those processors also. This option is found in the
     111<para>If you have an Intel P6 (Pentium Pro, Pentium II and later), it is
     112recommended that you compile <acronym>MTRR</acronym> (Memory Type Range
     113Registers) support into the kernel. The kernel can map Cyrix and AMD
     114<acronym>CPU</acronym>s to the <acronym>MTRR</acronym> interface, so selecting
     115this option is useful for those processors also. This option is found in the
    114116"Processor type and features" menu.  It can increase performance of
    115117image write operations 2.5 times or more on <acronym>PCI</acronym> or
    116118<acronym>AGP</acronym> video cards.</para>
    117119 
    118 <para>In the "Character Devices" section, enable <acronym>AGP</acronym> Support and
    119 select the chipset support on your motherboard.  If you do not know the chipset,
    120 you may select all the chip types at the expense of extra kernel size. You can usually
    121 determine your motherboard's chipset by doing:</para>
    122 <screen><userinput><command>cat /proc/pci</command></userinput></screen>
     120<para>In the "Character Devices" section, enable <acronym>AGP</acronym> Support
     121and select the chipset support on your motherboard. If you do not know the
     122chipset, you may select all the chip types at the expense of extra kernel size.
     123You can usually determine your motherboard's chipset by running the command
     124<command>lspci</command>, a program from the <xref linkend="pciutils"/>
     125package.</para>
    123126 
    124127<para>In the "Character Devices" section, <emphasis>disable</emphasis> Direct
    125128Rendering Manager unless you have a Direct Rendering Infrastructure
    126 (<acronym>DRI</acronym>)
    127 supported video card.  A complete list of <acronym>DRI</acronym> supported video cards can
    128 be found at <ulink url="http://dri.sourceforge.net" /> in the Status section.
     129(<acronym>DRI</acronym>) supported video card.  A complete list of
     130<acronym>DRI</acronym> supported video cards can be found at
     131<ulink url="http://dri.sourceforge.net" /> in the Status section.
    129132Currently, supported cards include those from 3dfx (Voodoo, Banshee), 3Dlabs,
    130 ATI (Rage Pro, Rage 128,
    131 Radeon 7X00, Radeon 2), Intel (i810, i815), and Matrox (G200, G400, G450).
    132 If you do enable <acronym>DRI</acronym> here, make sure you select the video card(s) you want
    133 to support as a <emphasis>module</emphasis>.</para>
     133ATI (Rage Pro, Rage 128, Radeon 7X00, Radeon 2), Intel (i810, i815), and
     134Matrox (G200, G400, G450). If you do enable <acronym>DRI</acronym> here, make
     135sure you select the video card(s) you want to support as a
     136<emphasis>module</emphasis>.</para>
    134137 
    135138<para>Additionally NVidia provides their own closed source binary drivers,
    136 which do not make use of <acronym>DRI</acronym>. If you intend to use these drivers,
    137 do not enable <acronym>DRI</acronym>.</para>
    138  
    139 <para>If you made any changes to the kernel configuration, recompile the kernel.</para>
    140  
    141 <para>Copy the <filename>arch/i386/boot/bzImage</filename> and <filename>System.map</filename>
    142 from the kernel build directory to <filename class='directory'>/boot</filename>.
    143 Edit <filename>/boot/grub/grub.conf</filename> and add the new kernel to the
    144 boot menu.
    145 (If you use lilo, edit <filename>/etc/lilo.conf</filename> and run <filename>lilo</filename>.)
    146 </para>
    147  
    148 <note><para>If you build <application>Xorg</application> in a chroot environment,
    149 make sure the kernel version of the base system and the target system are the same. 
    150 This is especially important if you enabled <acronym>DRI</acronym> support as a module as
    151 instructed above.</para></note>
     139which do not make use of <acronym>DRI</acronym>. If you intend to use these
     140drivers, do not enable <acronym>DRI</acronym>.</para>
     141 
     142<para>If you made any changes to the kernel configuration, recompile the
     143kernel.</para>
     144 
     145<para>Copy the <filename>arch/i386/boot/bzImage</filename> and
     146<filename>System.map</filename> from the kernel build directory to
     147<filename class='directory'>/boot</filename>. Edit
     148<filename>/boot/grub/menu.lst</filename> and add the new kernel to the boot
     149menu. (If you use lilo, edit <filename>/etc/lilo.conf</filename> and run
     150<command>lilo</command>.)</para>
     151 
     152<note><para>If you build <application>Xorg</application> in a
     153<command>chroot</command> environment, make sure the kernel version of the base
     154system and the target system are the same. This is especially important if you
     155enabled <acronym>DRI</acronym> support as a module as instructed above.</para>
     156</note>
    152157</sect3>
    153158
    154159<sect3><title>Setting Up a Shadow Directory</title> 
    155 <para>When building <application>Xorg</application>, you should create
    156 a shadow directory of symbolic links for the compiled code.  To do that, we first
    157 make the <application>lndir</application>.  Starting from the
     160<para>When building <application>Xorg</application>, you should create a shadow
     161directory of symbolic links for the compiled code.  To do that, first make
     162<command>lndir</command>.  Starting from the
    158163<filename class='directory'>xc</filename> directory:</para>
    159164
    … …  
    171176
    172177<sect3><title>Creating <filename>host.def</filename></title> 
    173 <para>The next step is to create the <filename>config/cf/host.def</filename> file.
    174 The documentation for <application>Xorg</application> indicates that the
     178<para>The next step is to create the <filename>config/cf/host.def</filename>
     179file. The documentation for <application>Xorg</application> indicates that the
    175180application will build without a <filename>host.def</filename> file, but
    176 the included libraries for <application>fontconfig</application> and
    177 <application>freetype2</application> do not build properly on a base LFS system.
    178 Therefore, you must specify that these libraries, as well as others, should be
    179 imported from the system.</para>
     181the included libraries for <application>Fontconfig</application> and
     182<application>FreeType2</application> do not build properly on a base
     183<acronym>LFS</acronym> system. Therefore, you must specify that these
     184libraries, as well as others, should be imported from the system.</para>
    180185
    181186<note><para><filename>config/cf/host.def</filename> is a C file, not a shell
    182 script.  Ensure the comments delimited by /* ... */ are
    183 balanced when modifying the file. </para></note>
    184 
     187script.  Ensure the comments delimited by <userinput>/*</userinput> ...
     188<userinput>*/</userinput> are balanced when modifying the file.</para></note>
    185189
    186190<screen><userinput><command>cat &gt; config/cf/host.def &lt;&lt; "EOF"</command>
    … …  
    236240<command>EOF</command></userinput></screen>
    237241
    238 <para>There are several other options that you may want to consider.  A well documented
    239 example file is <filename>config/cf/xorgsite.cf</filename>.</para>
     242<para>There are several other options that you may want to consider.  A well
     243documented example file is <filename>config/cf/xorgsite.cf</filename>.</para>
    240244</sect3>
    241245
    242246<sect3>
    243247<title>Build Commands</title>
    244 <para>Install <application>Xorg</application> by running the following commands:</para>
    245  
    246  
    247 <screen><userinput><command>( make World 2&gt;&amp;1 | tee xorg-compile.log &amp;&amp; exit $PIPESTATUS ) &amp;&amp;
     248<para>Install <application>Xorg</application> by running the following
     249commands:</para>
     250 
     251<screen><userinput><command>sed -i -e "s@#include &lt;linux/config.h&gt;@/* #include &lt;linux/config.h&gt; */@" \
     252`grep -lr linux/config.h *` &amp;&amp;
     253( make World 2&gt;&amp;1 | tee xorg-compile.log &amp;&amp; exit $PIPESTATUS ) &amp;&amp;
    248254make install &amp;&amp;
    249255make install.man &amp;&amp;
    … …  
    258264<para>If you have one of the supported <acronym>DRI</acronym> cards and
    259265have enabled <acronym>DRI</acronym> kernel modules as explained
    260 above, you now need to update the kernel modules to ensure they are compatible with the
    261 current version of <application>Xorg</application>.  To do this, perform the following:</para>
     266above, you now need to update the kernel modules to ensure they are compatible
     267with the current version of <application>Xorg</application>. To do this,
     268perform the following:</para>
    262269 
    263270<screen><userinput><command>cd programs/Xserver/hw/xfree86/os-support/linux/drm/kernel &amp;&amp;
    264 make  CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux  &amp;&amp;
     271make -f Makefile.linux  &amp;&amp;
    265272mkdir -p /lib/modules/`uname -r`/kernel/drivers/char/drm/  &amp;&amp;
    266273cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o \
    … …  
    268275depmod -a</command></userinput></screen>
    269276 
    270 <warning><para>If you recompile or upgrade your kernel, you will need to re-copy the
    271 appropriate driver module(s)
    272 to the kernel module library and rerun the <command>depmod -a</command> command.</para></warning>
    273  
    274 <note><para>If you created <acronym>AGP</acronym> support as a module when compiling
    275 the kernel, you may have to add a line to <filename>/etc/modules.conf</filename> to ensure
    276 the agpgart module is loaded.  For instance, the <acronym>AGP</acronym> version of the
    277 Radeon video card will use the <filename>radeon.o</filename> driver.  It will
    278 need to have the line <screen>below radeon agpgart</screen> in
    279 <filename>/etc/modules.conf</filename> to enable <acronym>DRI</acronym> support.</para></note>
     277<warning><para>If you recompile or upgrade your kernel, you will need to
     278re-copy the appropriate driver module(s) to the kernel module library and rerun
     279the <command>depmod -a</command> command.</para></warning>
     280 
     281<note><para>If you created <acronym>AGP</acronym> support as a module when
     282compiling the kernel, you may have to add a line to
     283<filename>/etc/modules.conf</filename> to ensure the agpgart module is loaded.
     284For instance, the <acronym>AGP</acronym> version of the Radeon video card will
     285use the <filename>radeon.o</filename> driver. It will need to have the line
     286<screen>below radeon agpgart</screen> in <filename>/etc/modules.conf</filename>
     287to enable <acronym>DRI</acronym> support.</para></note>
    280288</sect3>
    281289</sect2>
    … …  
    284292<title>Command explanations</title>
    285293 
     294<para><command>sed -i -e "s@#include &lt;linux/config.h&gt;@...</command>: The
     295<application>Linux-Libc-Headers</application> package installed in
     296<acronym>LFS</acronym> installs a
     297<filename>/usr/include/linux/config.h</filename> file which is not compatible
     298with userspace applications. The recommended fix for applications including
     299this file is to remove it (see <ulink
     300url="http://ep09.pld-linux.org/~mmazur/linux-libc-headers/doc/FAQ">
     301linux-libc-headers FAQ</ulink>). The <command>sed</command> uses
     302<command>grep -lr</command> to replace all occurences. If you desire, just
     303remove (comment) the line in the appropriate video driver file if you
     304customized <filename>host.def</filename>.
     305</para>
     306
    286307<para><command>( make World 2&gt;&amp;1 | tee xorg-compile.log
    287308   &amp;&amp; exit $PIPESTATUS )</command>:
    288 This command runs multiple makefiles to completely rebuild the system.
    289 <parameter>2&gt;&amp;1</parameter> redirects error messages
     309This command runs multiple <filename>Makefile</filename>s to completely rebuild
     310the system. <parameter>2&gt;&amp;1</parameter> redirects error messages
    290311to the same location as standard output. The <command>tee</command> command
    291 allows viewing of the output while logging the results to a file. The parentheses
    292 around the command runs the entire comand in a subshell and finally the
    293 <command>exit $PIPESTATUS</command> ensures the result of the <command>make</command>
    294 is returned as the result and not the result of the <command>tee</command> command.</para>
    295  
    296 <note><para>When rebuilding <application>Xorg</application>, a separate command that may
    297 be used if only minor changes are made to the sources is <command>make
    298 Everything</command>.  This does not automatically remove generated
    299 files and only rebuilds those files or programs that are out
    300 of date.</para></note>
     312allows viewing of the output while logging the results to a file. The
     313parentheses around the command runs the entire comand in a subshell and finally
     314the <command>exit $PIPESTATUS</command> ensures the result of the
     315<command>make</command> is returned as the result and not the result of the
     316<command>tee</command> command.</para>
     317 
     318<note><para>When rebuilding <application>Xorg</application>, a separate command
     319that may be used if only minor changes are made to the sources is
     320<command>make Everything</command>. This does not automatically remove generated
     321files and only rebuilds those files or programs that are out of date.</para>
     322</note>
    301323 
    302324<para><screen><command>ln -sf ../X11R6/bin /usr/bin/X11
    303325ln -sf ../X11R6/lib/X11 /usr/lib/X11
    304326ln -sf ../X11R6/include/X11 /usr/include/X11</command></screen>
    305 These commands are present to enable other (broken) packages to build
    306 against <application>Xorg</application>.  We do this even though the
    307 Filesystem Hierarchy Standard says:
    308 "In general, software must not be installed or managed via the above
     327These commands are present to enable other (broken) packages to build against
     328<application>Xorg</application>, even though the Filesystem Hierarchy Standard
     329says: "In general, software must not be installed or managed via the above
    309330symbolic links. They are intended for utilization by users only."</para>
    310331 
    311 <para><command>make  CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux</command>: This builds the
    312 <application>Xorg</application> compatible kernel modules using the same compiler used to compile
    313 the kernel.</para>
     332<!-- <para><command>make  CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux</command>:
     333This builds the <application>Xorg</application> compatible kernel modules using
     334the same compiler used to compile the kernel.</para> -->
    314335 
    315336<para><command>cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o
    … …  
    328349<para>Edit <filename>/etc/ld.so.conf</filename> and add
    329350<filename class="directory">/usr/X11R6/lib</filename>.
    330 Run:</para> <screen><userinput><command>ldconfig</command></userinput></screen>
    331  
    332 <para>Ensure <filename class='directory'>/usr/X11R6/bin</filename> is added to your
    333 <envar>PATH</envar> environment variable. Instructions for doing this are described
    334 in the section "<xref linkend='postlfs-config-profile'/>."</para>
     351Run:</para>
     352<screen><userinput><command>ldconfig</command></userinput></screen>
     353 
     354<para>Ensure <filename class='directory'>/usr/X11R6/bin</filename> is added to
     355your <envar>PATH</envar> environment variable. Instructions for doing this are
     356described in the section "<xref linkend='postlfs-config-profile'/>."</para>
    335357 
    336358<para>Expand the <envar>PKG_CONFIG_PATH</envar> so that other packages
    … …  
    342364 
    343365Adjust the symbolic link as necessary for other types of mice.  For instance,
    344 a serial mouse on the first serial port would be linked to ttyS1.</para>
     366a serial mouse on the first serial port would be linked to ttyS0.</para>
    345367 
    346368<para>Create the <filename>xorg.conf</filename> file with:
    … …  
    351373directory.</para>
    352374 
    353 <para>Edit <filename>xorg.conf.new</filename> to suit your system.  The
    354 details of the file are located in the man
    355 page <command>man xorg.conf</command>.  Some things you may want to
    356 do are:</para>
     375<para>Edit <filename>xorg.conf.new</filename> to suit your system.  The details
     376of the file are located in the man page <command>man xorg.conf</command>. Some
     377things you may want to do are:</para>
    357378 
    358379<itemizedlist>
    … …  
    363384directories completely.</para></listitem>
    364385 
    365 <listitem><para>Section "Monitor".  Specify the <parameter>VertRefresh</parameter>
    366 and <parameter>HorizSync</parameter> values if the system does not automatically
    367 detect the monitor and its values.</para></listitem>
     386<listitem><para>Section "Monitor".  Specify the
     387<parameter>VertRefresh</parameter> and <parameter>HorizSync</parameter> values
     388if the system does not automatically detect the monitor and its values.</para>
     389</listitem>
    368390 
    369391<listitem><para>Section "InputDevice".  You may want to change the keyboard
    370 autorepeat rate by
    371 adding <parameter>Option "Autorepeat" "250 30"</parameter>.</para></listitem>
     392autorepeat rate by adding <parameter>Option "Autorepeat" "250 30"</parameter>.
     393</para></listitem>
    372394 
    373395<listitem><para>Section "Device".  You may want to set some of the options
    … …  
    375397parameters is in the man page for your driver.</para></listitem>
    376398 
    377 <listitem><para>Section "Screen".  Add a DefaultDepth statement such
    378 as: <parameter>DefaultDepth 16</parameter>. In the SubSection for your
    379 default depth, add a modes line such
    380 as: <parameter> Modes "1280x1024" "1024x768"</parameter>.
    381 The first mode listed will normally be the starting
    382 resolution.</para></listitem>
     399<listitem><para>Section "Screen".  Add a DefaultDepth statement such as:
     400<parameter>DefaultDepth 16</parameter>. In the SubSection for your default
     401depth, add a modes line such as:
     402<parameter> Modes "1280x1024" "1024x768"</parameter>. The first mode listed
     403will normally be the starting resolution.</para></listitem>
    383404 
    384405</itemizedlist>
     406
    385407<para>Test the system with:
    386408<screen><userinput><command>X -xf86config ~/xorg.conf.new</command></userinput></screen>
    387409You will only get a gray background with an X-shaped mouse cursor, but it
    388410confirms the system is working.  Exit with Control-Alt-Backspace.  If the
    389 system does not work, take a look
    390 at <filename>/var/log/Xorg.0.log</filename> to see what went
    391 wrong.</para>
     411system does not work, take a look at <filename>/var/log/Xorg.0.log</filename>
     412to see what went wrong.</para>
    392413 
    393414<para>Move the configuration file to its final location:</para>
    … …  
    402423<command>EOF</command></userinput></screen>
    403424This provides an initial screen with an xterm and a clock that is managed by a
    404 simple window manager, Tab Window Manager.  For details of twm, see the
    405 man page.</para>
     425simple window manager, Tab Window Manager.  For details of
     426<command>twm</command>, see the man page.</para>
    406427 
    407428<note>
    408  
    409429<para>When needed, <application>Xorg</application> creates the directory
    410430<filename>/tmp/.ICE-unix</filename> if it does not exist. If this directory is
    411 not owned by root, <application>Xorg</application> delays startup by a few seconds
    412 and also appends a warning to the logfile. This also affects startup of other
    413 applications. To improve performance, it is advisable to manually create the directory
    414 before Xorg uses it. Add the file creation to <filename>/etc/sysconfig/createfiles</filename>
    415 that is sourced by the
    416 <filename>/etc/rc.d/init.d/cleanfs</filename> startup script.</para>
     431not owned by root, <application>Xorg</application> delays startup by a few
     432seconds and also appends a warning to the logfile. This also affects startup of
     433other applications. To improve performance, it is advisable to manually create
     434the directory before <application>Xorg</application> uses it. Add the file
     435creation to <filename>/etc/sysconfig/createfiles</filename> that is sourced by
     436the <filename>/etc/rc.d/init.d/cleanfs</filename> startup script.</para>
    417437 
    418438<screen><userinput><command>cat &gt;&gt; /etc/sysconfig/createfiles &lt;&lt; "EOF"</command>
    419439/tmp/.ICE-unix dir 1777 root root
    420440<command>EOF</command></userinput></screen>
    421  
    422441</note>
    423  
     442
    424443<para>Start <application>X</application> with:
    425444<screen><userinput><command>startx</command></userinput></screen>
    426445to get a basic functional <application>X</application> Window System.</para>
    427446
    428 <para>At this point, you should check out
    429 <xref linkend='x-setup'/>.</para>
     447<para>At this point, you should check out <xref linkend='x-setup'/>.</para>
     448
     449<para>For a list of the package contents and a description of the commands,
     450see the sections in <xref linkend='xfree86'/>.</para>
    430451
    431452</sect2>
     453
    432454</sect1>
Note: See TracChangeset for help on using the changeset viewer.