swift       05/06/05 16:36:18

  Modified:    xml/htdocs/doc/en/handbook hb-install-alpha-kernel.xml
                        hb-install-amd64-kernel.xml
                        hb-install-hppa-kernel.xml
                        hb-install-ppc-kernel.xml
                        hb-install-ppc64-kernel.xml
                        hb-install-sparc-kernel.xml
                        hb-install-x86-kernel.xml
  Log:
  Fix stupid typo

Revision  Changes    Path
1.25      +3 -3      xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml?rev=1.25&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml?rev=1.25&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml.diff?r1=1.24&r2=1.25&cvsroot=gentoo

Index: hb-install-alpha-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- hb-install-alpha-kernel.xml 2 Jun 2005 17:18:54 -0000       1.24
+++ hb-install-alpha-kernel.xml 5 Jun 2005 16:36:18 -0000       1.25
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 
1.24 2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 
1.25 2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -113,11 +113,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.25      +3 -3      xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.25&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.25&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml.diff?r1=1.24&r2=1.25&cvsroot=gentoo

Index: hb-install-amd64-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- hb-install-amd64-kernel.xml 2 Jun 2005 17:18:54 -0000       1.24
+++ hb-install-amd64-kernel.xml 5 Jun 2005 16:36:18 -0000       1.25
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v 
1.24 2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v 
1.25 2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -110,11 +110,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.21      +3 -3      xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.21&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.21&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml.diff?r1=1.20&r2=1.21&cvsroot=gentoo

Index: hb-install-hppa-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- hb-install-hppa-kernel.xml  2 Jun 2005 17:18:54 -0000       1.20
+++ hb-install-hppa-kernel.xml  5 Jun 2005 16:36:18 -0000       1.21
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v 
1.20 2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v 
1.21 2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -104,11 +104,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.27      +3 -3      xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.27&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.27&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml.diff?r1=1.26&r2=1.27&cvsroot=gentoo

Index: hb-install-ppc-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- hb-install-ppc-kernel.xml   2 Jun 2005 17:18:54 -0000       1.26
+++ hb-install-ppc-kernel.xml   5 Jun 2005 16:36:18 -0000       1.27
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.26 
2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.27 
2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -116,11 +116,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.14      +3 -3      xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.14&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.14&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml.diff?r1=1.13&r2=1.14&cvsroot=gentoo

Index: hb-install-ppc64-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- hb-install-ppc64-kernel.xml 2 Jun 2005 17:18:54 -0000       1.13
+++ hb-install-ppc64-kernel.xml 5 Jun 2005 16:36:18 -0000       1.14
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v 
1.13 2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v 
1.14 2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -104,11 +104,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.17      +3 -3      xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml?rev=1.17&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml?rev=1.17&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml.diff?r1=1.16&r2=1.17&cvsroot=gentoo

Index: hb-install-sparc-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-sparc-kernel.xml 2 Jun 2005 17:18:54 -0000       1.16
+++ hb-install-sparc-kernel.xml 5 Jun 2005 16:36:18 -0000       1.17
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v 
1.16 2005/06/02 17:18:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v 
1.17 2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -105,11 +105,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



1.48      +3 -3      xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml?rev=1.48&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml?rev=1.48&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml.diff?r1=1.47&r2=1.48&cvsroot=gentoo

Index: hb-install-x86-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- hb-install-x86-kernel.xml   4 Jun 2005 13:31:28 -0000       1.47
+++ hb-install-x86-kernel.xml   5 Jun 2005 16:36:18 -0000       1.48
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml,v 1.47 
2005/06/04 13:31:28 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-kernel.xml,v 1.48 
2005/06/05 16:36:18 swift Exp $ -->
 
 <sections>
 
@@ -113,11 +113,11 @@
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
 configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now 
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
 be able to  use <c>lspci</c> within the chrooted environment. You may safely 
 ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
 /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
-<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. 
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
 You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
 uses (it might provide you with a nice hint on what to enable).
 </p>



-- 
[email protected] mailing list

Reply via email to