vapier      06/08/21 10:21:57

  Modified:             home-router-howto.xml
  Log:
  add missing spaces

Revision  Changes    Path
1.49                 xml/htdocs/doc/en/home-router-howto.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.49&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.49&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.48&r2=1.49

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- home-router-howto.xml       12 Aug 2006 12:18:55 -0000      1.48
+++ home-router-howto.xml       21 Aug 2006 10:21:57 -0000      1.49
@@ -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/home-router-howto.xml,v 
1.48 2006/08/12 12:18:55 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 
1.49 2006/08/21 10:21:57 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -104,9 +104,9 @@
 
 <p>
 If you do not see your two cards showing up and you're not sure what kind of
-cards you have, try running <c>lspci | grep Ethernet</c>. You can get that from
-<c>emerge pciutils</c>. Once you have this information, go into your kernel and
-add support for the correct drivers.
+cards you have, try running <c>lspci | grep Ethernet</c>.  You can get that
+from <c>emerge pciutils</c>.  Once you have this information, go into your
+kernel and add support for the correct drivers.
 </p>
 
 <p>
@@ -965,11 +965,11 @@
 </pre>
 
 <p>
-The trick is to know where dhcpd is sending its output. Simply browse to
-<path>/var/log</path> and read the log files. Since the exact log file depends
+The trick is to know where dhcpd is sending its output.  Simply browse to
+<path>/var/log</path> and read the log files.  Since the exact log file depends
 on the package you are using as a syslog, try running <c>grep -Rl dhcpd
-/var/log</c> to narrow down the possibilities. Chances are you made a typo in
-your config file. You could also try running <c>dhcpd -d -f</c> (short for
+/var/log</c> to narrow down the possibilities.  Chances are you made a typo in
+your config file.  You could also try running <c>dhcpd -d -f</c> (short for
 debug / foreground) and debug the error based upon the output.
 </p>
 



-- 
[email protected] mailing list

Reply via email to