neysx       05/07/21 15:30:05

  Modified:    xml/htdocs/doc/en devfs-guide.xml
  Log:
  #99799 devfs obsolete in kernels >= 2.6.13

Revision  Changes    Path
1.12      +6 -6      xml/htdocs/doc/en/devfs-guide.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/devfs-guide.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/devfs-guide.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/devfs-guide.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo

Index: devfs-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- devfs-guide.xml     18 Jul 2005 10:03:44 -0000      1.11
+++ devfs-guide.xml     21 Jul 2005 15:30:05 -0000      1.12
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.11 
2005/07/18 10:03:44 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.12 
2005/07/21 15:30:05 neysx Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -21,8 +21,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.5</version>
-<date>2005-07-18</date>
+<version>0.6</version>
+<date>2005-07-21</date>
 
 <chapter>
 <title>What is devfs?</title>
@@ -31,9 +31,9 @@
 <body>
 
 <warn>
-devfs is <e>obsolete</e> and will eventually be removed from the stable 2.6
-tree. Users on 2.6 kernels are hereby advised to switch to udev. For further
-information on udev, please refer to the <uri
+devfs is <e>obsolete</e> and has been removed from the stable 2.6 tree in the
+2.6.13 release. Users on 2.6 kernels are hereby advised to switch to udev. For
+further information on udev, please refer to the <uri
 link="/doc/en/udev-guide.xml">Gentoo udev Guide</uri>.
 </warn>
 



-- 
[email protected] mailing list

Reply via email to