swift       08/05/23 19:44:06

  Modified:             udev-guide.xml
  Log:
  Coding style

Revision  Changes    Path
1.45                 xml/htdocs/doc/en/udev-guide.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.45&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.45&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.44&r2=1.45

Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- udev-guide.xml      30 Oct 2007 20:31:27 -0000      1.44
+++ udev-guide.xml      23 May 2008 19:44:06 -0000      1.45
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.44 
2007/10/30 20:31:27 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.45 
2008/05/23 19:44:06 swift Exp $ -->
 
 <guide link="/doc/en/udev-guide.xml">
 <title>Gentoo udev Guide</title>
@@ -53,7 +53,7 @@
 Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... 
What
 is the first device? And for how long? What will the other devices be named 
when
 the first one disappears? How will that affect ongoing transactions? Wouldn't 
it
-be fun that a printing job is suddenly moved from your supernew laserprinter 
to 
+be fun that a printing job is suddenly moved from your supernew laserprinter to
 your almost-dead matrix printer because your mom decided to pull the plug of 
the
 laserprinter which happened to be the first printer?
 </p>
@@ -117,7 +117,7 @@
 </p>
 
 <p>
-The <e>bus device number</e> step checks the device bus number. For 
+The <e>bus device number</e> step checks the device bus number. For
 non-hot-swappable environments this procedure is sufficient to
 identify a hardware device. For instance PCI bus numbers rarely change in the
 lifetime of a system. Again, if namedev finds a match between this position and
@@ -134,12 +134,12 @@
 <p>
 The fourth step, <e>statically given name</e>, is a simple string replacement.
 When the kernel name (the default name) matches a given replacement string, the
-substitute name will be used. 
+substitute name will be used.
 </p>
 
 <p>
-The final step (<e>kernel provided name</e>) is a catch-all: this one takes 
-the default name provided by the kernel. In the majority of cases this is 
+The final step (<e>kernel provided name</e>) is a catch-all: this one takes
+the default name provided by the kernel. In the majority of cases this is
 sufficient as it matches the device naming used on current Linux systems.
 </p>
 
@@ -221,8 +221,8 @@
 If you want to use the udev-tweaks Gentoo added to make your life
 comfortable, then read no more. Gentoo will use udev but keep a static
 <path>/dev</path> so that you will never have any missing device nodes.
-The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs 
-when you boot up. 
+The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs
+when you boot up.
 </p>
 
 <p>
@@ -232,7 +232,7 @@
 </p>
 
 <p>
-We'll deactivate the rules that save the device file nodes: edit the 
+We'll deactivate the rules that save the device file nodes: edit the
 <c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it to
 <c>no</c>:
 </p>
@@ -243,7 +243,7 @@
 
 <p>
 If you have included devfs support in your kernel, you can deactivate it in
-the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter. 
+the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter.
 If you want to use devfs and deactivate udev, add <c>gentoo=noudev</c> as 
kernel
 parameter.
 </p>
@@ -336,7 +336,7 @@
 <body>
 
 <p>
-Even though our intention is to have a consistent naming scheme between both 
+Even though our intention is to have a consistent naming scheme between both
 dynamical device management solutions, sometimes naming differences do occur.
 </p>
 
@@ -497,7 +497,7 @@
 </p>
 
 <p>
-<uri 
link="http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html";>Decibel's
 
+<uri 
link="http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html";>Decibel's
 UDEV Primer</uri> is an in-depth document about udev and Gentoo.
 </p>
 



-- 
[email protected] mailing list

Reply via email to