josejx      07/04/02 01:57:59

  Modified:             hb-install-ppc-kernel.xml
  Log:
  Removed extra --usepkg from draft docs.

Revision  Changes    Path
1.34                 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.34&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.34&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?r1=1.33&r2=1.34

Index: hb-install-ppc-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- hb-install-ppc-kernel.xml   2 Apr 2007 00:48:30 -0000       1.33
+++ hb-install-ppc-kernel.xml   2 Apr 2007 01:57:59 -0000       1.34
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v
 1.33 2007/04/02 00:48:30 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v
 1.34 2007/04/02 01:57:59 josejx Exp $ -->
 
 <sections>
 
@@ -98,7 +98,7 @@
 <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 --usepkg pciutils</c>) which contains the program 
+pciutils (<c>emerge pciutils</c>) which contains the program 
 <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 (such as pcilib:
 cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,



-- 
[email protected] mailing list

Reply via email to