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-kernel.xml file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.38&view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.38&content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?r1=1.37&r2=1.38 Index: hb-install-x86+amd64-kernel.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-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 --> -<!-- $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 $ --> <sections> @@ -48,7 +48,7 @@ layer between the user programs and your system hardware. Gentoo provides its users several possible kernel sources. A full listing with description is available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel -Guide</uri>. +Guide</uri>. </p> <p> @@ -85,8 +85,8 @@ <p> If you want to manually configure your kernel, continue now with <uri -link="#manual">Default: Manual Configuration</uri>. If you want to use -<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using +link="#manual">Default: Manual Configuration</uri>. If you want to use +<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using genkernel</uri> instead. </p> @@ -107,13 +107,13 @@ <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>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>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 +configuring a kernel manually. Most information can be gathered by emerging +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>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> @@ -170,7 +170,7 @@ <pre caption="Selecting processor type and features"> Processor type and features ---> - [ ] Machine Check / overheating reporting + [ ] Machine Check / overheating reporting [ ] Intel MCE Features [ ] AMD MCE Features Processor family (AMD-Opteron/Athlon64) ---> @@ -304,7 +304,7 @@ </pre> <p> -When you've finished configuring the kernel, continue with <uri +When you've finished configuring the kernel, continue with <uri link="#compiling">Compiling and Installing</uri>. </p> @@ -315,7 +315,7 @@ <body> <p> -Now that your kernel is configured, it is time to compile and install it. Exit +Now that your kernel is configured, it is time to compile and install it. Exit the configuration and start the compilation process: </p> @@ -352,13 +352,13 @@ </p> <p> -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 kernel for -you. <c>genkernel</c> works by configuring a kernel nearly identically to the -way our Installation CD kernel is configured. This means that when you use -<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 ideal +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 kernel for +you. <c>genkernel</c> works by configuring a kernel nearly identically to the +way our Installation CD kernel is configured. This means that when you use +<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 ideal solution for those users who may not be comfortable compiling their own kernels. </p> @@ -391,8 +391,8 @@ <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 --menuconfig -all</c> and add support for your filesystem <e>in</e> the kernel (i.e. +might need to manually configure your kernel using <c>genkernel --menuconfig +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 add <c>--evms2</c> or <c>--lvm2</c> as arguments as well. </p> @@ -402,11 +402,11 @@ </pre> <p> -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 kernel +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 kernel 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 immediately after +the bootloader configuration file. The initrd will be started immediately after booting to perform hardware autodetection (just like on the Installation CD) before your "real" system starts up. </p>
