From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-commits+bounces-374750-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1QvYE9-0002VO-5K
	for garchives@archives.gentoo.org; Mon, 22 Aug 2011 17:23:57 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E4B8421C0A7;
	Mon, 22 Aug 2011 17:23:49 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id 9B3A321C0A7
	for <gentoo-commits@lists.gentoo.org>; Mon, 22 Aug 2011 17:23:49 +0000 (UTC)
Received: from flycatcher.gentoo.org (flycatcher.gentoo.org [81.93.255.6])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPS id C29521B4021
	for <gentoo-commits@lists.gentoo.org>; Mon, 22 Aug 2011 17:23:48 +0000 (UTC)
Received: by flycatcher.gentoo.org (Postfix, from userid 617)
	id 87A7620051; Mon, 22 Aug 2011 17:23:47 +0000 (UTC)
From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Reply-To: gentoo-dev@lists.gentoo.org, swift@gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-kernel.xml
X-VCS-Repository: gentoo
X-VCS-Files: hb-install-x86+amd64-kernel.xml
X-VCS-Directories: xml/htdocs/doc/en/handbook
X-VCS-Committer: swift
X-VCS-Committer-Name: Sven Vermeulen
Content-Type: text/plain; charset=utf8
Message-Id: <20110822172347.87A7620051@flycatcher.gentoo.org>
Date: Mon, 22 Aug 2011 17:23:47 +0000 (UTC)
Precedence: bulk
List-Post: <mailto:gentoo-commits@lists.gentoo.org>
List-Help: <mailto:gentoo-commits+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-commits+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-commits+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-commits.gentoo.org>
X-BeenThere: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 
X-Archives-Hash: fdf5cd6c078b69022d6bcdb5f3dad4e1

swift       11/08/22 17:23:47

  Modified:             hb-install-x86+amd64-kernel.xml
  Log:
  Removing trailing spaces (no content change)

Revision  Changes    Path
1.38                 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kern=
el.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/hand=
book/hb-install-x86+amd64-kernel.xml?rev=3D1.38&view=3Dmarkup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/hand=
book/hb-install-x86+amd64-kernel.xml?rev=3D1.38&content-type=3Dtext/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/hand=
book/hb-install-x86+amd64-kernel.xml?r1=3D1.37&r2=3D1.38

Index: hb-install-x86+amd64-kernel.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+a=
md64-kernel.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-x86+amd64-kernel.xml	12 Aug 2011 19:05:02 -0000	1.37
+++ hb-install-x86+amd64-kernel.xml	22 Aug 2011 17:23:47 -0000	1.38
@@ -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 -->
=20
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-=
x86+amd64-kernel.xml,v 1.37 2011/08/12 19:05:02 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-=
x86+amd64-kernel.xml,v 1.38 2011/08/22 17:23:47 swift Exp $ -->
=20
 <sections>
=20
@@ -48,7 +48,7 @@
 layer between the user programs and your system hardware. Gentoo provide=
s its
 users several possible kernel sources. A full listing with description i=
s
 available at the <uri link=3D"/doc/en/gentoo-kernel.xml">Gentoo Kernel
-Guide</uri>.=20
+Guide</uri>.
 </p>
=20
 <p>
@@ -85,8 +85,8 @@
=20
 <p>
 If you want to manually configure your kernel, continue now with <uri
-link=3D"#manual">Default: Manual Configuration</uri>. If you want to use=
=20
-<c>genkernel</c> you should read <uri link=3D"#genkernel">Alternative: U=
sing=20
+link=3D"#manual">Default: Manual Configuration</uri>. If you want to use
+<c>genkernel</c> you should read <uri link=3D"#genkernel">Alternative: U=
sing
 genkernel</uri> instead.
 </p>
=20
@@ -107,13 +107,13 @@
=20
 <p>
 However, one thing <e>is</e> true: you must know your system when you st=
art
-configuring a kernel manually. Most information can be gathered by emerg=
ing=20
-pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will =
now=20
-be able to  use <c>lspci</c> within the chrooted environment. You may sa=
fely=20
-ignore any <e>pcilib</e> warnings (like pcilib: cannot open=20
-/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you c=
an run=20
-<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the=
 same.=20
-You can also run <c>lsmod</c> to see what kernel modules the Installatio=
n CD=20
+configuring a kernel manually. Most information can be gathered by emerg=
ing
+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 sa=
fely
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you c=
an run
+<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 Installatio=
n CD
 uses (it might provide you with a nice hint on what to enable).
 </p>
=20
@@ -170,7 +170,7 @@
=20
 <pre caption=3D"Selecting processor type and features">
 Processor type and features  --->
-   [ ] Machine Check / overheating reporting =20
+   [ ] Machine Check / overheating reporting=20
    [ ]   Intel MCE Features
    [ ]   AMD MCE Features
   Processor family (AMD-Opteron/Athlon64)  --->
@@ -304,7 +304,7 @@
 </pre>
=20
 <p>
-When you've finished configuring the kernel, continue with <uri=20
+When you've finished configuring the kernel, continue with <uri
 link=3D"#compiling">Compiling and Installing</uri>.
 </p>
=20
@@ -315,7 +315,7 @@
 <body>
=20
 <p>
-Now that your kernel is configured, it is time to compile and install it=
. Exit=20
+Now that your kernel is configured, it is time to compile and install it=
. Exit
 the configuration and start the compilation process:
 </p>
=20
@@ -352,13 +352,13 @@
 </p>
=20
 <p>
-Now that your kernel source tree is installed, it's now time to compile =
your=20
-kernel by using our <c>genkernel</c> script to automatically build a ker=
nel for=20
-you. <c>genkernel</c> works by configuring a kernel nearly identically t=
o the=20
-way our Installation CD kernel is configured. This means that when you u=
se=20
-<c>genkernel</c> to build your kernel, your system will generally detect=
 all=20
-your hardware at boot-time, just like our Installation CD does. Because=20
-genkernel doesn't require any manual kernel configuration, it is an idea=
l=20
+Now that your kernel source tree is installed, it's now time to compile =
your
+kernel by using our <c>genkernel</c> script to automatically build a ker=
nel for
+you. <c>genkernel</c> works by configuring a kernel nearly identically t=
o the
+way our Installation CD kernel is configured. This means that when you u=
se
+<c>genkernel</c> to build your kernel, your system will generally detect=
 all
+your hardware at boot-time, just like our Installation CD does. Because
+genkernel doesn't require any manual kernel configuration, it is an idea=
l
 solution for those users who may not be comfortable compiling their own =
kernels.
 </p>
=20
@@ -391,8 +391,8 @@
=20
 <p>
 Note that, if your boot partition doesn't use ext2 or ext3 as filesystem=
 you
-might need to manually configure your kernel using <c>genkernel --menuco=
nfig=20
-all</c> and add support for your filesystem <e>in</e> the kernel (i.e.=20
+might need to manually configure your kernel using <c>genkernel --menuco=
nfig
+all</c> and add support for your filesystem <e>in</e> the kernel (i.e.
 <e>not</e> as a module). Users of EVMS2 or LVM2 will probably want to ad=
d
 <c>--evms2</c> or <c>--lvm2</c> as arguments as well.
 </p>
@@ -402,11 +402,11 @@
 </pre>
=20
 <p>
-Once <c>genkernel</c> completes, a kernel, full set of modules and=20
-<e>initial ram disk</e> (initramfs) will be created. We will use the ker=
nel=20
+Once <c>genkernel</c> completes, a kernel, full set of modules and
+<e>initial ram disk</e> (initramfs) will be created. We will use the ker=
nel
 and initrd when configuring a boot loader later in this document. Write
 down the names of the kernel and initrd as you will need it when writing
-the bootloader configuration file. The initrd will be started immediatel=
y after=20
+the bootloader configuration file. The initrd will be started immediatel=
y after
 booting to perform hardware autodetection (just like on the Installation=
 CD)
 before your "real" system starts up.
 </p>