/[gentoo]/xml/htdocs/doc/en/xorg-config.xml
Gentoo

Diff of /xml/htdocs/doc/en/xorg-config.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.23 Revision 1.24
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.23 2007/06/21 02:37:46 nightmorph Exp $ -->
4
5<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.24 2007/10/18 18:16:02 nightmorph Exp $ -->
6 4
7<guide link="/doc/en/xorg-config.xml"> 5<guide link="/doc/en/xorg-config.xml">
8
9<title>The X Server Configuration HOWTO</title> 6<title>The X Server Configuration HOWTO</title>
10 7
11<author title="Author"> 8<author title="Author">
12 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 9 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
13</author> 10</author>
233<p> 230<p>
234Be sure to read the last lines printed on your screen when Xorg has finished 231Be sure to read the last lines printed on your screen when Xorg has finished
235probing your hardware. If it tells you it failed at some point, you're forced to 232probing your hardware. If it tells you it failed at some point, you're forced to
236manually write an <path>xorg.conf</path> file. Assuming that it didn't fail, it 233manually write an <path>xorg.conf</path> file. Assuming that it didn't fail, it
237will have told you that it has written <path>/root/xorg.conf.new</path> ready 234will have told you that it has written <path>/root/xorg.conf.new</path> ready
238for you to test. So let's test :) 235for you to test. So let's test. :)
239</p> 236</p>
240 237
241<pre caption="Testing the xorg.conf.new file"> 238<pre caption="Testing the xorg.conf.new file">
242# <i>X -config /root/xorg.conf.new</i> 239# <i>X -config /root/xorg.conf.new</i>
243</pre> 240</pre>
286<body> 283<body>
287 284
288<p> 285<p>
289Let us copy over the <path>xorg.conf.new</path> to 286Let us copy over the <path>xorg.conf.new</path> to
290<path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run 287<path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run
291<c>X -config</c> -- typing just <c>X</c> or <c>startx</c> is far more easy :) 288<c>X -config</c> -- typing just <c>X</c> or <c>startx</c> is easier. :)
292</p> 289</p>
293 290
294<pre caption="Copying over xorg.conf"> 291<pre caption="Copying over xorg.conf">
295# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i> 292# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i>
296</pre> 293</pre>
317 Otherwise, it will read the value of the XSESSION variable and will execute 314 Otherwise, it will read the value of the XSESSION variable and will execute
318 one of the sessions available in <path>/etc/X11/Sessions/</path> 315 one of the sessions available in <path>/etc/X11/Sessions/</path>
319 accordingly (you can set the value of XSESSION in <path>/etc/rc.conf</path> 316 accordingly (you can set the value of XSESSION in <path>/etc/rc.conf</path>
320 to make it a default for all the users on the system). 317 to make it a default for all the users on the system).
321 </li> 318 </li>
322<li> 319 <li>
323 If all of the above fail, it will fall back to a simple window manager, 320 If all of the above fail, it will fall back to a simple window manager,
324 usually <c>twm</c>. 321 usually <c>twm</c>.
325 </li> 322 </li>
326</ul> 323</ul>
327 324
332<p> 329<p>
333If you see an ugly, loathsome, repulsive, deformed window manager, that's 330If you see an ugly, loathsome, repulsive, deformed window manager, that's
334<c>twm</c>. To finish the twm session, type in <c>exit</c> or Ctrl-D in the 331<c>twm</c>. To finish the twm session, type in <c>exit</c> or Ctrl-D in the
335upcoming xterms. You can also kill the X session using the Ctrl-Alt-Backspace 332upcoming xterms. You can also kill the X session using the Ctrl-Alt-Backspace
336combination. This will however make X exit disgracefully -- something that you 333combination. This will however make X exit disgracefully -- something that you
337might not always want. It doesn't hurt though :) 334might not always want. It doesn't hurt though. :)
338</p> 335</p>
339 336
340</body> 337</body>
341</section> 338</section>
342</chapter> 339</chapter>
393 EndSubSection 390 EndSubSection
394EndSection 391EndSection
395</pre> 392</pre>
396 393
397<p> 394<p>
398Run X (<c>startx</c>) to discover it uses the resolution you want :) 395Run X (<c>startx</c>) to discover it uses the resolution you want. :)
399</p> 396</p>
400 397
401</body> 398</body>
402</section> 399</section>
403<section> 400<section>
469 466
470<p> 467<p>
471Run <c>startx</c> and be happy about the result :) Congratulations, you now 468Run <c>startx</c> and be happy about the result :) Congratulations, you now
472(hopefully) have a working Xorg on your system. The next step is to remove this 469(hopefully) have a working Xorg on your system. The next step is to remove this
473ugly lightweight window manager and use a high-feature one (or even a desktop 470ugly lightweight window manager and use a high-feature one (or even a desktop
474environment) such as KDE or GNOME, but that's not part of this guide :) 471environment) such as KDE or GNOME, but that's not part of this guide. :)
475</p> 472</p>
476 473
477</body> 474</body>
478</section> 475</section>
479</chapter> 476</chapter>
498<p> 495<p>
499There are also many online resources on editing <path>xorg.conf</path>. We only 496There are also many online resources on editing <path>xorg.conf</path>. We only
500list few of them here, be sure to <uri link="http://www.google.com">Google</uri> 497list few of them here, be sure to <uri link="http://www.google.com">Google</uri>
501for more :) As <path>xorg.conf</path> and <path>XF86Config</path> (the 498for more :) As <path>xorg.conf</path> and <path>XF86Config</path> (the
502configuration file for the XFree86 project) use the 499configuration file for the XFree86 project) use the
503same syntaxis for most configuration options and more information about 500same syntax for most configuration options and more information about
504<path>XF86Config</path> is available, we'll list those resources as well. 501<path>XF86Config</path> is available, we'll list those resources as well.
505</p> 502</p>
506 503
507<ul> 504<ul>
508 <li> 505 <li>

Legend:
Removed from v.1.23  
changed lines
  Added in v.1.24

  ViewVC Help
Powered by ViewVC 1.1.20