Changeset d5d9ceb for x/installing
- Timestamp:
- 07/25/2004 11:35:18 PM (20 years ago)
- 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
- Location:
- x/installing
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
x/installing/xfree86.xml
rcadb42f rd5d9ceb 527 527 to get a basic functional <application>X</application> Window System.</para> 528 528 529 <para>At this point, you should check out <xref linkend='x-setup'/>.</para> 530 529 531 </sect2> 530 532 -
x/installing/xorg.xml
rcadb42f rd5d9ceb 20 20 <title>Introduction to <application>Xorg</application></title> 21 21 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 23 the <application>X</application> Window System: <application>Xorg</application> 24 and <application>XFree86</application>. These packages are quite similar. In 25 fact, the base system of <application>Xorg</application> is 26 <application>XFree86</application>-RC2. The primary difference as of this 27 writing is the license provisions of the packages. For someone building a 28 package for their own use, these issues are not significant. Most large 29 commercial distributions have decided to use the 30 <application>Xorg</application> package, but several still use 29 31 <application>XFree86</application>.</para> 30 32 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 34 is the stated goals of the developers. Some developers were unhappy with the 35 administration and progress of <application>XFree86</application>. X.org's 36 future plans include significant improvements to the internals of the system 37 and more frequent releases.</para> 35 38 36 39 <para><application>XFree86</application> continues to be a solid, conservative 37 40 application with excellent driver support.</para> 38 41 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 44 section will provide a slightly different and more current variation for 45 installation.</para> 42 46 </note> 43 47 44 45 48 <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 applicationinterface (<acronym>API</acronym>).</para>49 implementation of the <application>X</application> Window System. This 50 application provides a client/server interface between display hardware (the 51 mouse, keyboard, and video displays) and the desktop environment, while also 52 providing both the windowing infrastructure and a standardized application 53 interface (<acronym>API</acronym>).</para> 51 54 52 55 <sect3><title>Package information</title> … … 59 62 </sect3> 60 63 61 62 64 <sect3><title><application>Xorg</application> Dependencies</title> 63 65 64 66 <sect4><title>Required</title> 65 <para><xref linkend="libpng"/>, <xref linkend="expat"/>, <xref linkend="freetype2"/> and66 <xref linkend="f ontconfig"/>.</para>67 <para><xref linkend="libpng"/>, <xref linkend="expat"/>, 68 <xref linkend="freetype2"/> and <xref linkend="fontconfig"/>.</para> 67 69 </sect4> 68 70 … … 73 75 </sect3> 74 76 75 76 77 <sect3><title>Download Instructions</title> 77 78 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 80 location:</para> 79 81 <itemizedlist spacing='compact'> 80 82 <listitem><para><filename>X11R6.7.0-src1.tar.gz</filename></para></listitem> … … 87 89 </itemizedlist> 88 90 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 92 and support programs, the second contains standard <application>X</application> 93 programs, the third contains the <application>X</application> server, the 94 fourth and fifth are fonts, the sixth is normal documentation, and the seventh 92 95 is hardcopy documentation.</para> 93 96 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> 96 99 97 100 <screen><userinput><command>md5sum -c md5sums</command></userinput></screen> … … 104 107 <title>Installation of <application>Xorg</application></title> 105 108 106 107 109 <sect3> 108 110 <title>Kernel Compilation Settings</title> 109 <para>If you have an Intel P6 (Pentium Pro, Pentium II and later), it is recommended110 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 this113 option is useful for those processors also. This option is found in the111 <para>If you have an Intel P6 (Pentium Pro, Pentium II and later), it is 112 recommended that you compile <acronym>MTRR</acronym> (Memory Type Range 113 Registers) support into the kernel. The kernel can map Cyrix and AMD 114 <acronym>CPU</acronym>s to the <acronym>MTRR</acronym> interface, so selecting 115 this option is useful for those processors also. This option is found in the 114 116 "Processor type and features" menu. It can increase performance of 115 117 image write operations 2.5 times or more on <acronym>PCI</acronym> or 116 118 <acronym>AGP</acronym> video cards.</para> 117 119 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 121 and select the chipset support on your motherboard. If you do not know the 122 chipset, you may select all the chip types at the expense of extra kernel size. 123 You can usually determine your motherboard's chipset by running the command 124 <command>lspci</command>, a program from the <xref linkend="pciutils"/> 125 package.</para> 123 126 124 127 <para>In the "Character Devices" section, <emphasis>disable</emphasis> Direct 125 128 Rendering 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. 129 132 Currently, 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>133 ATI (Rage Pro, Rage 128, Radeon 7X00, Radeon 2), Intel (i810, i815), and 134 Matrox (G200, G400, G450). If you do enable <acronym>DRI</acronym> here, make 135 sure you select the video card(s) you want to support as a 136 <emphasis>module</emphasis>.</para> 134 137 135 138 <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> 139 which do not make use of <acronym>DRI</acronym>. If you intend to use these 140 drivers, do not enable <acronym>DRI</acronym>.</para> 141 142 <para>If you made any changes to the kernel configuration, recompile the 143 kernel.</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 149 menu. (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 154 system and the target system are the same. This is especially important if you 155 enabled <acronym>DRI</acronym> support as a module as instructed above.</para> 156 </note> 152 157 </sect3> 153 158 154 159 <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 the160 <para>When building <application>Xorg</application>, you should create a shadow 161 directory of symbolic links for the compiled code. To do that, first make 162 <command>lndir</command>. Starting from the 158 163 <filename class='directory'>xc</filename> directory:</para> 159 164 … … 171 176 172 177 <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 the178 <para>The next step is to create the <filename>config/cf/host.def</filename> 179 file. The documentation for <application>Xorg</application> indicates that the 175 180 application will build without a <filename>host.def</filename> file, but 176 the included libraries for <application> fontconfig</application> and177 <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>181 the 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 184 libraries, as well as others, should be imported from the system.</para> 180 185 181 186 <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 187 script. Ensure the comments delimited by <userinput>/*</userinput> ... 188 <userinput>*/</userinput> are balanced when modifying the file.</para></note> 185 189 186 190 <screen><userinput><command>cat > config/cf/host.def << "EOF"</command> … … 236 240 <command>EOF</command></userinput></screen> 237 241 238 <para>There are several other options that you may want to consider. A well documented239 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 243 documented example file is <filename>config/cf/xorgsite.cf</filename>.</para> 240 244 </sect3> 241 245 242 246 <sect3> 243 247 <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>&1 | tee xorg-compile.log && exit $PIPESTATUS ) && 248 <para>Install <application>Xorg</application> by running the following 249 commands:</para> 250 251 <screen><userinput><command>sed -i -e "s@#include <linux/config.h>@/* #include <linux/config.h> */@" \ 252 `grep -lr linux/config.h *` && 253 ( make World 2>&1 | tee xorg-compile.log && exit $PIPESTATUS ) && 248 254 make install && 249 255 make install.man && … … 258 264 <para>If you have one of the supported <acronym>DRI</acronym> cards and 259 265 have 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> 266 above, you now need to update the kernel modules to ensure they are compatible 267 with the current version of <application>Xorg</application>. To do this, 268 perform the following:</para> 262 269 263 270 <screen><userinput><command>cd programs/Xserver/hw/xfree86/os-support/linux/drm/kernel && 264 make CC=/opt/gcc-2.95.3/bin/gcc-f Makefile.linux &&271 make -f Makefile.linux && 265 272 mkdir -p /lib/modules/`uname -r`/kernel/drivers/char/drm/ && 266 273 cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o \ … … 268 275 depmod -a</command></userinput></screen> 269 276 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 278 re-copy the appropriate driver module(s) to the kernel module library and rerun 279 the <command>depmod -a</command> command.</para></warning> 280 281 <note><para>If you created <acronym>AGP</acronym> support as a module when 282 compiling the kernel, you may have to add a line to 283 <filename>/etc/modules.conf</filename> to ensure the agpgart module is loaded. 284 For instance, the <acronym>AGP</acronym> version of the Radeon video card will 285 use 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> 287 to enable <acronym>DRI</acronym> support.</para></note> 280 288 </sect3> 281 289 </sect2> … … 284 292 <title>Command explanations</title> 285 293 294 <para><command>sed -i -e "s@#include <linux/config.h>@...</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 298 with userspace applications. The recommended fix for applications including 299 this file is to remove it (see <ulink 300 url="http://ep09.pld-linux.org/~mmazur/linux-libc-headers/doc/FAQ"> 301 linux-libc-headers FAQ</ulink>). The <command>sed</command> uses 302 <command>grep -lr</command> to replace all occurences. If you desire, just 303 remove (comment) the line in the appropriate video driver file if you 304 customized <filename>host.def</filename>. 305 </para> 306 286 307 <para><command>( make World 2>&1 | tee xorg-compile.log 287 308 && exit $PIPESTATUS )</command>: 288 This command runs multiple makefiles to completely rebuild the system.289 <parameter>2>&1</parameter> redirects error messages309 This command runs multiple <filename>Makefile</filename>s to completely rebuild 310 the system. <parameter>2>&1</parameter> redirects error messages 290 311 to 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> 312 allows viewing of the output while logging the results to a file. The 313 parentheses around the command runs the entire comand in a subshell and finally 314 the <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 319 that may be used if only minor changes are made to the sources is 320 <command>make Everything</command>. This does not automatically remove generated 321 files and only rebuilds those files or programs that are out of date.</para> 322 </note> 301 323 302 324 <para><screen><command>ln -sf ../X11R6/bin /usr/bin/X11 303 325 ln -sf ../X11R6/lib/X11 /usr/lib/X11 304 326 ln -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 327 These commands are present to enable other (broken) packages to build against 328 <application>Xorg</application>, even though the Filesystem Hierarchy Standard 329 says: "In general, software must not be installed or managed via the above 309 330 symbolic links. They are intended for utilization by users only."</para> 310 331 311 < para><command>make CC=/opt/gcc-2.95.3/bin/gcc -f Makefile.linux</command>: This builds the312 <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>: 333 This builds the <application>Xorg</application> compatible kernel modules using 334 the same compiler used to compile the kernel.</para> --> 314 335 315 336 <para><command>cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o … … 328 349 <para>Edit <filename>/etc/ld.so.conf</filename> and add 329 350 <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> 351 Run:</para> 352 <screen><userinput><command>ldconfig</command></userinput></screen> 353 354 <para>Ensure <filename class='directory'>/usr/X11R6/bin</filename> is added to 355 your <envar>PATH</envar> environment variable. Instructions for doing this are 356 described in the section "<xref linkend='postlfs-config-profile'/>."</para> 335 357 336 358 <para>Expand the <envar>PKG_CONFIG_PATH</envar> so that other packages … … 342 364 343 365 Adjust 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 ttyS 1.</para>366 a serial mouse on the first serial port would be linked to ttyS0.</para> 345 367 346 368 <para>Create the <filename>xorg.conf</filename> file with: … … 351 373 directory.</para> 352 374 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 376 of the file are located in the man page <command>man xorg.conf</command>. Some 377 things you may want to do are:</para> 357 378 358 379 <itemizedlist> … … 363 384 directories completely.</para></listitem> 364 385 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 388 if the system does not automatically detect the monitor and its values.</para> 389 </listitem> 368 390 369 391 <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>392 autorepeat rate by adding <parameter>Option "Autorepeat" "250 30"</parameter>. 393 </para></listitem> 372 394 373 395 <listitem><para>Section "Device". You may want to set some of the options … … 375 397 parameters is in the man page for your driver.</para></listitem> 376 398 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 401 depth, add a modes line such as: 402 <parameter> Modes "1280x1024" "1024x768"</parameter>. The first mode listed 403 will normally be the starting resolution.</para></listitem> 383 404 384 405 </itemizedlist> 406 385 407 <para>Test the system with: 386 408 <screen><userinput><command>X -xf86config ~/xorg.conf.new</command></userinput></screen> 387 409 You will only get a gray background with an X-shaped mouse cursor, but it 388 410 confirms 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> 411 system does not work, take a look at <filename>/var/log/Xorg.0.log</filename> 412 to see what went wrong.</para> 392 413 393 414 <para>Move the configuration file to its final location:</para> … … 402 423 <command>EOF</command></userinput></screen> 403 424 This 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 the405 man page.</para>425 simple window manager, Tab Window Manager. For details of 426 <command>twm</command>, see the man page.</para> 406 427 407 428 <note> 408 409 429 <para>When needed, <application>Xorg</application> creates the directory 410 430 <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 seconds412 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>431 not owned by root, <application>Xorg</application> delays startup by a few 432 seconds and also appends a warning to the logfile. This also affects startup of 433 other applications. To improve performance, it is advisable to manually create 434 the directory before <application>Xorg</application> uses it. Add the file 435 creation to <filename>/etc/sysconfig/createfiles</filename> that is sourced by 436 the <filename>/etc/rc.d/init.d/cleanfs</filename> startup script.</para> 417 437 418 438 <screen><userinput><command>cat >> /etc/sysconfig/createfiles << "EOF"</command> 419 439 /tmp/.ICE-unix dir 1777 root root 420 440 <command>EOF</command></userinput></screen> 421 422 441 </note> 423 442 424 443 <para>Start <application>X</application> with: 425 444 <screen><userinput><command>startx</command></userinput></screen> 426 445 to get a basic functional <application>X</application> Window System.</para> 427 446 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, 450 see the sections in <xref linkend='xfree86'/>.</para> 430 451 431 452 </sect2> 453 432 454 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.