From: "Lukasz Damentko" <rane@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: nvidia-guide.xml
Date: Wed, 26 Jul 2006 09:50:06 +0000 [thread overview]
Message-ID: <20060726095006.A7E6364363@smtp.gentoo.org> (raw)
rane 06/07/26 09:50:06
Modified: nvidia-guide.xml
Log:
there's nothing like /dev/nvidia, adding missing asterisks, thanks to kucrut for reporting
Revision Changes Path
1.30 xml/htdocs/doc/en/nvidia-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/nvidia-guide.xml?r1=1.29&r2=1.30
Index: nvidia-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- nvidia-guide.xml 26 May 2006 20:38:25 -0000 1.29
+++ nvidia-guide.xml 26 Jul 2006 09:50:06 -0000 1.30
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.29 2006/05/26 20:38:25 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/nvidia-guide.xml,v 1.30 2006/07/26 09:50:06 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/nvidia-guide.xml">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.25</version>
-<date>2006-05-26</date>
+<version>1.26</version>
+<date>2006-07-25</date>
<chapter>
<title>Introduction</title>
@@ -511,7 +511,7 @@
</pre>
<p>
-If your <path>/dev/nvidia</path> devices are still missing every time you
+If your <path>/dev/nvidia*</path> devices are still missing every time you
reboot, then it is most likely because udev is not automatically creating the
proper device nodes. You can fix this by re-running <c>NVmakedevices.sh</c>,
and then editing <path>/etc/conf.d/rc</path> as shown:
@@ -522,7 +522,7 @@
</pre>
<p>
-This will preserve your <path>/dev/nvidia</path> nodes even if you reboot.
+This will preserve your <path>/dev/nvidia*</path> nodes even if you reboot.
</p>
<note>
@@ -530,7 +530,7 @@
<c>nvidia-glx</c> from the 8xxx series. At the time of this writing, both are
still marked ~arch. These drivers no longer rely on hotplug or udev to create
the proper device nodes, so you won't need to run <c>NVmakedevices.sh</c>.
-Instead, the X driver itself will create your <path>/dev/nvidia</path> files
+Instead, the X driver itself will create your <path>/dev/nvidia*</path> files
when you start X. However, this will require you to use a recent kernel (2.6.14
and greater).
</note>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-07-26 9:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 9:50 Lukasz Damentko [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-14 5:12 [gentoo-doc-cvs] cvs commit: nvidia-guide.xml Joshua Saddler
2008-03-06 8:50 Joshua Saddler
2007-11-15 20:22 Josh Saddler
2007-07-31 21:07 Josh Saddler
2007-07-22 7:32 Josh Saddler
2007-03-24 1:04 Josh Saddler
2007-02-08 15:50 Josh Saddler
2007-02-08 3:41 Josh Saddler
2007-02-08 0:09 Dimitry Bradt
2006-11-29 15:57 Josh Saddler
2006-10-24 2:24 Josh Saddler
2006-09-02 10:19 Josh Saddler
2006-05-26 20:38 Josh Saddler
2006-05-02 17:39 Josh Saddler
2006-03-28 12:33 Xavier Neys
2006-03-05 12:02 Josh Saddler
2006-03-04 6:35 Shyam Mani
2006-01-25 21:41 Jan Kundrat
2006-01-21 12:54 swift
2006-01-13 16:06 Xavier Neys
2005-10-25 17:27 swift
2005-10-21 20:35 swift
2005-10-05 0:03 Lukasz Damentko
2005-09-11 20:19 Jan Kundrat
2005-07-15 5:10 Shyam Mani
2005-07-06 8:05 Shyam Mani
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=20060726095006.A7E6364363@smtp.gentoo.org \
--to=rane@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