1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
5 | %general-entities;
|
---|
6 |
|
---|
7 | <!ENTITY xorg-download-http "http://freedesktop.org/~xorg/X11R6.7.0/src/">
|
---|
8 | <!ENTITY xorg-download-ftp " ">
|
---|
9 | <!ENTITY xorg-size "70.3 MB">
|
---|
10 | <!ENTITY xorg-buildsize "645 MB">
|
---|
11 | <!ENTITY xorg-time "17.1 SBU">
|
---|
12 | ]>
|
---|
13 |
|
---|
14 | <sect1 id="xorg" xreflabel="X.org-&xorg-version;">
|
---|
15 | <?dbhtml filename="xorg.html"?>
|
---|
16 | <title>Xorg-&xorg-version;</title>
|
---|
17 |
|
---|
18 |
|
---|
19 | <sect2>
|
---|
20 | <title>Introduction to <application>Xorg</application></title>
|
---|
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
|
---|
29 | <application>XFree86</application>.</para>
|
---|
30 |
|
---|
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>
|
---|
35 |
|
---|
36 | <para><application>XFree86</application> continues to be a solid, conservative
|
---|
37 | application with excellent driver support.</para>
|
---|
38 |
|
---|
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 | </note>
|
---|
43 |
|
---|
44 |
|
---|
45 | <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>
|
---|
51 |
|
---|
52 | <sect3><title>Package information</title>
|
---|
53 | <itemizedlist spacing='compact'>
|
---|
54 | <listitem><para>Download (HTTP): <ulink url="&xorg-download-http;"/></para></listitem>
|
---|
55 | <listitem><para>Download (FTP): <ulink url="&xorg-download-ftp;"/></para></listitem>
|
---|
56 | <listitem><para>Download size: &xorg-size;</para></listitem>
|
---|
57 | <listitem><para>Estimated Disk space required: &xorg-buildsize;</para></listitem>
|
---|
58 | <listitem><para>Estimated build time: &xorg-time;</para></listitem></itemizedlist>
|
---|
59 | </sect3>
|
---|
60 |
|
---|
61 |
|
---|
62 | <sect3><title><application>Xorg</application> Dependencies</title>
|
---|
63 |
|
---|
64 | <sect4><title>Required</title>
|
---|
65 | <para><xref linkend="libpng"/>, <xref linkend="expat"/>, <xref linkend="freetype2"/> and
|
---|
66 | <xref linkend="fontconfig"/>.</para>
|
---|
67 | </sect4>
|
---|
68 |
|
---|
69 | <sect4><title>Optional</title>
|
---|
70 | <para><xref linkend="Linux_PAM"/>.</para>
|
---|
71 | </sect4>
|
---|
72 |
|
---|
73 | </sect3>
|
---|
74 |
|
---|
75 |
|
---|
76 | <sect3><title>Download Instructions</title>
|
---|
77 |
|
---|
78 | <para>There are several files that need to be fetched from the download location:</para>
|
---|
79 | <itemizedlist spacing='compact'>
|
---|
80 | <listitem><para><filename>X11R6.7.0-src1.tar.gz</filename></para></listitem>
|
---|
81 | <listitem><para><filename>X11R6.7.0-src2.tar.gz</filename></para></listitem>
|
---|
82 | <listitem><para><filename>X11R6.7.0-src3.tar.gz</filename></para></listitem>
|
---|
83 | <listitem><para><filename>X11R6.7.0-src4.tar.gz</filename></para></listitem>
|
---|
84 | <listitem><para><filename>X11R6.7.0-src5.tar.gz</filename></para></listitem>
|
---|
85 | <listitem><para><filename>X11R6.7.0-src6.tar.gz</filename></para></listitem>
|
---|
86 | <listitem><para><filename>X11R6.7.0-src7.tar.gz</filename></para></listitem>
|
---|
87 | </itemizedlist>
|
---|
88 |
|
---|
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
|
---|
92 | is hardcopy documentation.</para>
|
---|
93 |
|
---|
94 | <para>To check your downloads for integrity, download the <filename>md5sums</filename>
|
---|
95 | file. Then:</para>
|
---|
96 |
|
---|
97 | <screen><userinput><command>md5sum -c md5sums</command></userinput></screen>
|
---|
98 |
|
---|
99 | <para>All seven packages should give an OK status.</para>
|
---|
100 | </sect3>
|
---|
101 | </sect2>
|
---|
102 |
|
---|
103 | <sect2>
|
---|
104 | <title>Installation of <application>Xorg</application></title>
|
---|
105 |
|
---|
106 |
|
---|
107 | <sect3>
|
---|
108 | <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
|
---|
114 | "Processor type and features" menu. It can increase performance of
|
---|
115 | image write operations 2.5 times or more on <acronym>PCI</acronym> or
|
---|
116 | <acronym>AGP</acronym> video cards.</para>
|
---|
117 |
|
---|
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>
|
---|
123 |
|
---|
124 | <para>In the "Character Devices" section, <emphasis>disable</emphasis> Direct
|
---|
125 | 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 | 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>
|
---|
134 |
|
---|
135 | <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>
|
---|
152 | </sect3>
|
---|
153 |
|
---|
154 | <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
|
---|
158 | <filename class='directory'>xc</filename> directory:</para>
|
---|
159 |
|
---|
160 | <screen><userinput><command>pushd config/util &&
|
---|
161 | make -f Makefile.ini lndir &&
|
---|
162 | cp lndir /usr/bin/ &&
|
---|
163 | popd</command></userinput></screen>
|
---|
164 |
|
---|
165 | <para>Now create the shadow tree:</para>
|
---|
166 |
|
---|
167 | <screen><userinput><command>mkdir ../xcbuild &&
|
---|
168 | cd ../xcbuild &&
|
---|
169 | lndir ../xc</command></userinput></screen>
|
---|
170 | </sect3>
|
---|
171 |
|
---|
172 | <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
|
---|
175 | application 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>
|
---|
180 |
|
---|
181 | <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 |
|
---|
185 |
|
---|
186 | <screen><userinput><command>cat > config/cf/host.def << "EOF"</command>
|
---|
187 | /* Begin Xorg host.def file */
|
---|
188 |
|
---|
189 | /* System Related Information. If you read and configure only one
|
---|
190 | * section then it should be this one. The Intel architecture defaults are
|
---|
191 | * set for a i686 and higher. Axp is for the Alpha architecture and Ppc is
|
---|
192 | * for the Power PC. AMD64 is for the Opteron processor. Note that there have
|
---|
193 | * been reports that the Ppc optimization line causes segmentation faults during
|
---|
194 | * build. If that happens, try building without the DefaultGcc2PpcOpt line. ***********/
|
---|
195 |
|
---|
196 | /* #define DefaultGcc2i386Opt -O2 -fno-strength-reduce -fno-strict-aliasing -march=i686 */
|
---|
197 | /* #define DefaultGccAMD64Opt -O2 -fno-strength-reduce -fno-strict-aliasing */
|
---|
198 | /* #define DefaultGcc2AxpOpt -O2 -mcpu=ev6 */
|
---|
199 | /* #define DefaultGcc2PpcOpt -O2 -mcpu=750 */
|
---|
200 |
|
---|
201 | #define HasFreetype2 YES
|
---|
202 | #define HasFontconfig YES
|
---|
203 | #define HasExpat YES
|
---|
204 | #define HasLibpng YES
|
---|
205 | #define HasZlib YES
|
---|
206 |
|
---|
207 | /*
|
---|
208 | * Which drivers to build. When building a static server, each of these
|
---|
209 | * will be included in it. When building the loadable server each of these
|
---|
210 | * modules will be built.
|
---|
211 | *
|
---|
212 | #define XF86CardDrivers mga glint nv tga s3virge sis rendition \
|
---|
213 | neomagic i740 tdfx savage \
|
---|
214 | cirrus vmware tseng trident chips apm \
|
---|
215 | GlideDriver fbdev i128 \
|
---|
216 | ati AgpGartDrivers DevelDrivers ark cyrix \
|
---|
217 | siliconmotion \
|
---|
218 | vesa vga XF86OSCardDrivers XF86ExtraCardDrivers
|
---|
219 | */
|
---|
220 |
|
---|
221 | /*
|
---|
222 | * Select the XInput devices you want by uncommenting this.
|
---|
223 | *
|
---|
224 | #define XInputDrivers mouse keyboard acecad calcomp citron \
|
---|
225 | digitaledge dmc dynapro elographics \
|
---|
226 | microtouch mutouch penmount spaceorb summa \
|
---|
227 | wacom void magictouch aiptek
|
---|
228 | */
|
---|
229 |
|
---|
230 | /* Most installs will only need this */
|
---|
231 |
|
---|
232 | #define XInputDrivers mouse keyboard
|
---|
233 |
|
---|
234 |
|
---|
235 | /* End Xorg host.def file */
|
---|
236 | <command>EOF</command></userinput></screen>
|
---|
237 |
|
---|
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>
|
---|
240 | </sect3>
|
---|
241 |
|
---|
242 | <sect3>
|
---|
243 | <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 | make install &&
|
---|
249 | make install.man &&
|
---|
250 | ln -sf ../X11R6/bin /usr/bin/X11 &&
|
---|
251 | ln -sf ../X11R6/lib/X11 /usr/lib/X11 &&
|
---|
252 | ln -sf ../X11R6/include/X11 /usr/include/X11</command></userinput></screen>
|
---|
253 |
|
---|
254 | </sect3>
|
---|
255 |
|
---|
256 | <sect3>
|
---|
257 | <title>Updating Direct Rendering Infrastructure (<acronym>DRI</acronym>)</title>
|
---|
258 | <para>If you have one of the supported <acronym>DRI</acronym> cards and
|
---|
259 | 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>
|
---|
262 |
|
---|
263 | <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 &&
|
---|
265 | mkdir -p /lib/modules/`uname -r`/kernel/drivers/char/drm/ &&
|
---|
266 | cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o \
|
---|
267 | /lib/modules/`uname -r`/kernel/drivers/char/drm/ &&
|
---|
268 | depmod -a</command></userinput></screen>
|
---|
269 |
|
---|
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>
|
---|
280 | </sect3>
|
---|
281 | </sect2>
|
---|
282 |
|
---|
283 | <sect2>
|
---|
284 | <title>Command explanations</title>
|
---|
285 |
|
---|
286 | <para><command>( make World 2>&1 | tee xorg-compile.log
|
---|
287 | && exit $PIPESTATUS )</command>:
|
---|
288 | This command runs multiple makefiles to completely rebuild the system.
|
---|
289 | <parameter>2>&1</parameter> redirects error messages
|
---|
290 | 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>
|
---|
301 |
|
---|
302 | <para><screen><command>ln -sf ../X11R6/bin /usr/bin/X11
|
---|
303 | ln -sf ../X11R6/lib/X11 /usr/lib/X11
|
---|
304 | 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
|
---|
309 | symbolic links. They are intended for utilization by users only."</para>
|
---|
310 |
|
---|
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>
|
---|
314 |
|
---|
315 | <para><command>cp gamma.o radeon.o sis.o r128.o i810.o i830.o mga.o tdfx.o
|
---|
316 | /lib/modules/`uname -r`/kernel/drivers/char/drm/</command>: Put the kernel
|
---|
317 | module(s) where the kernel can find them. You only need to copy the driver you
|
---|
318 | need to support your video card.</para>
|
---|
319 |
|
---|
320 | <para><command>depmod -a</command>: Update the modules.dep file for module
|
---|
321 | management.</para>
|
---|
322 |
|
---|
323 | </sect2>
|
---|
324 |
|
---|
325 | <sect2>
|
---|
326 | <title>Configuring Xorg</title>
|
---|
327 |
|
---|
328 | <para>Edit <filename>/etc/ld.so.conf</filename> and add
|
---|
329 | <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>
|
---|
335 |
|
---|
336 | <para>Expand the <envar>PKG_CONFIG_PATH</envar> so that other packages
|
---|
337 | can find <application>X</application> libraries. Procedures for this are also
|
---|
338 | described in the section "<xref linkend='postlfs-config-profile'/>."</para>
|
---|
339 |
|
---|
340 | <para>Set up your mouse:
|
---|
341 | <screen><userinput><command>ln -s psaux /dev/mouse</command></userinput></screen>
|
---|
342 |
|
---|
343 | 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 ttyS1.</para>
|
---|
345 |
|
---|
346 | <para>Create the <filename>xorg.conf</filename> file with:
|
---|
347 | <screen><userinput><command>cd ~
|
---|
348 | Xorg -configure</command></userinput></screen>
|
---|
349 | The screen will go black and you may hear some clicking of the monitor. This
|
---|
350 | command will create a file, <filename>xorg.conf.new</filename> in your home
|
---|
351 | directory.</para>
|
---|
352 |
|
---|
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>
|
---|
357 |
|
---|
358 | <itemizedlist>
|
---|
359 |
|
---|
360 | <listitem><para>Section "Files". Change the order of the font paths searched.
|
---|
361 | You may want to put 100dpi fonts ahead of 75dpi fonts if your system normally
|
---|
362 | comes up closer to 100 dots per inch. You may want to remove some font
|
---|
363 | directories completely.</para></listitem>
|
---|
364 |
|
---|
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>
|
---|
368 |
|
---|
369 | <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>
|
---|
372 |
|
---|
373 | <listitem><para>Section "Device". You may want to set some of the options
|
---|
374 | available for your selected video driver. A description of the driver
|
---|
375 | parameters is in the man page for your driver.</para></listitem>
|
---|
376 |
|
---|
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>
|
---|
383 |
|
---|
384 | </itemizedlist>
|
---|
385 | <para>Test the system with:
|
---|
386 | <screen><userinput><command>X -xf86config ~/xorg.conf.new</command></userinput></screen>
|
---|
387 | You will only get a gray background with an X-shaped mouse cursor, but it
|
---|
388 | 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>
|
---|
392 |
|
---|
393 | <para>Move the configuration file to its final location:</para>
|
---|
394 | <screen><userinput><command>mv ~/xorg.conf.new /etc/X11/xorg.conf</command></userinput></screen>
|
---|
395 |
|
---|
396 | <para>Create <filename>.xinitrc</filename>:
|
---|
397 | <screen><userinput><command>cat > ~/.xinitrc << "EOF"</command>
|
---|
398 | # Begin .xinitrc file
|
---|
399 | xterm -g 80x40+0+0 &
|
---|
400 | xclock -g 100x100-0+0 &
|
---|
401 | twm
|
---|
402 | <command>EOF</command></userinput></screen>
|
---|
403 | 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 the
|
---|
405 | man page.</para>
|
---|
406 |
|
---|
407 | <note>
|
---|
408 |
|
---|
409 | <para>When needed, <application>Xorg</application> creates the directory
|
---|
410 | <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>
|
---|
417 |
|
---|
418 | <screen><userinput><command>cat >> /etc/sysconfig/createfiles << "EOF"</command>
|
---|
419 | /tmp/.ICE-unix dir 1777 root root
|
---|
420 | <command>EOF</command></userinput></screen>
|
---|
421 |
|
---|
422 | </note>
|
---|
423 |
|
---|
424 | <para>Start <application>X</application> with:
|
---|
425 | <screen><userinput><command>startx</command></userinput></screen>
|
---|
426 | to get a basic functional <application>X</application> Window System.</para>
|
---|
427 |
|
---|
428 | <para>At this point, you should check out the X Window Components at
|
---|
429 | <xref linkend='x-setup'/>.</para>
|
---|
430 |
|
---|
431 | </sect2>
|
---|
432 | </sect1>
|
---|