public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Saddler <nightmorph@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: xorg-config.xml
Date: Sat, 17 Feb 2007 19:12:14 +0000	[thread overview]
Message-ID: <E1HIUyk-0003r9-Jg@lark.gentoo.org> (raw)

nightmorph    07/02/17 19:12:14

  Modified:             xorg-config.xml
  Log:
  added bit about /dev/input/mice to the xorg guide, bug 167337

Revision  Changes    Path
1.21                 xml/htdocs/doc/en/xorg-config.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?r1=1.20&r2=1.21

Index: xorg-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- xorg-config.xml	29 Nov 2006 15:48:57 -0000	1.20
+++ xorg-config.xml	17 Feb 2007 19:12:14 -0000	1.21
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.20 2006/11/29 15:48:57 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.21 2007/02/17 19:12:14 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -22,8 +22,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.14</version>
-<date>2006-07-13</date>
+<version>1.15</version>
+<date>2007-02-17</date>
 
 <chapter>
 <title>What is the X Window Server?</title>
@@ -243,10 +243,12 @@
 </pre>
 
 <p>
-If all goes well, you should see a simple black and white pattern.  Verify if
-your mouse works correctly and if the resolution is good. You might not be able
-to deduce the exact resolution, but you should be able to see if it's too low.
-You can exit any time by pressing Ctrl-Alt-Backspace.
+If all goes well, you should see a simple black and white pattern. Verify if
+your mouse works correctly and if the resolution is good. If you received errors
+about "/dev/mouse", try changing your mouse device to <c>/dev/input/mice</c> in
+the "InputDevice" section of <path>xorg.conf</path>. You might not be able to
+deduce the exact resolution, but you should be able to see if it's too low. You
+can exit any time by pressing Ctrl-Alt-Backspace.
 </p>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2007-02-17 19:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 19:12 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-10  7:01 [gentoo-doc-cvs] cvs commit: xorg-config.xml Joshua Saddler
2008-05-23 19:40 Sven Vermeulen
2007-10-18 18:20 Josh Saddler
2007-10-18 18:16 Josh Saddler
2007-06-21  2:37 Josh Saddler
2007-06-09 12:40 Jan Kundrat
2006-07-13  4:29 Lukasz Damentko
2005-09-09  6:01 Shyam Mani
2005-09-09  5:57 Shyam Mani
2005-07-13 21:21 Jose Luis Rivero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1HIUyk-0003r9-Jg@lark.gentoo.org \
    --to=nightmorph@lark.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox