1 |
swift 11/08/22 17:23:47 |
2 |
|
3 |
Modified: hb-install-x86+amd64-kernel.xml |
4 |
Log: |
5 |
Removing trailing spaces (no content change) |
6 |
|
7 |
Revision Changes Path |
8 |
1.38 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.38&view=markup |
11 |
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 |
12 |
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 |
13 |
|
14 |
Index: hb-install-x86+amd64-kernel.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml,v |
17 |
retrieving revision 1.37 |
18 |
retrieving revision 1.38 |
19 |
diff -u -r1.37 -r1.38 |
20 |
--- hb-install-x86+amd64-kernel.xml 12 Aug 2011 19:05:02 -0000 1.37 |
21 |
+++ hb-install-x86+amd64-kernel.xml 22 Aug 2011 17:23:47 -0000 1.38 |
22 |
@@ -4,7 +4,7 @@ |
23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
25 |
|
26 |
-<!-- $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 $ --> |
27 |
+<!-- $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 $ --> |
28 |
|
29 |
<sections> |
30 |
|
31 |
@@ -48,7 +48,7 @@ |
32 |
layer between the user programs and your system hardware. Gentoo provides its |
33 |
users several possible kernel sources. A full listing with description is |
34 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
35 |
-Guide</uri>. |
36 |
+Guide</uri>. |
37 |
</p> |
38 |
|
39 |
<p> |
40 |
@@ -85,8 +85,8 @@ |
41 |
|
42 |
<p> |
43 |
If you want to manually configure your kernel, continue now with <uri |
44 |
-link="#manual">Default: Manual Configuration</uri>. If you want to use |
45 |
-<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
46 |
+link="#manual">Default: Manual Configuration</uri>. If you want to use |
47 |
+<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
48 |
genkernel</uri> instead. |
49 |
</p> |
50 |
|
51 |
@@ -107,13 +107,13 @@ |
52 |
|
53 |
<p> |
54 |
However, one thing <e>is</e> true: you must know your system when you start |
55 |
-configuring a kernel manually. Most information can be gathered by emerging |
56 |
-pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
57 |
-be able to use <c>lspci</c> within the chrooted environment. You may safely |
58 |
-ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
59 |
-/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
60 |
-<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
61 |
-You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
62 |
+configuring a kernel manually. Most information can be gathered by emerging |
63 |
+pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
64 |
+be able to use <c>lspci</c> within the chrooted environment. You may safely |
65 |
+ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
66 |
+/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
67 |
+<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
68 |
+You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
69 |
uses (it might provide you with a nice hint on what to enable). |
70 |
</p> |
71 |
|
72 |
@@ -170,7 +170,7 @@ |
73 |
|
74 |
<pre caption="Selecting processor type and features"> |
75 |
Processor type and features ---> |
76 |
- [ ] Machine Check / overheating reporting |
77 |
+ [ ] Machine Check / overheating reporting |
78 |
[ ] Intel MCE Features |
79 |
[ ] AMD MCE Features |
80 |
Processor family (AMD-Opteron/Athlon64) ---> |
81 |
@@ -304,7 +304,7 @@ |
82 |
</pre> |
83 |
|
84 |
<p> |
85 |
-When you've finished configuring the kernel, continue with <uri |
86 |
+When you've finished configuring the kernel, continue with <uri |
87 |
link="#compiling">Compiling and Installing</uri>. |
88 |
</p> |
89 |
|
90 |
@@ -315,7 +315,7 @@ |
91 |
<body> |
92 |
|
93 |
<p> |
94 |
-Now that your kernel is configured, it is time to compile and install it. Exit |
95 |
+Now that your kernel is configured, it is time to compile and install it. Exit |
96 |
the configuration and start the compilation process: |
97 |
</p> |
98 |
|
99 |
@@ -352,13 +352,13 @@ |
100 |
</p> |
101 |
|
102 |
<p> |
103 |
-Now that your kernel source tree is installed, it's now time to compile your |
104 |
-kernel by using our <c>genkernel</c> script to automatically build a kernel for |
105 |
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
106 |
-way our Installation CD kernel is configured. This means that when you use |
107 |
-<c>genkernel</c> to build your kernel, your system will generally detect all |
108 |
-your hardware at boot-time, just like our Installation CD does. Because |
109 |
-genkernel doesn't require any manual kernel configuration, it is an ideal |
110 |
+Now that your kernel source tree is installed, it's now time to compile your |
111 |
+kernel by using our <c>genkernel</c> script to automatically build a kernel for |
112 |
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
113 |
+way our Installation CD kernel is configured. This means that when you use |
114 |
+<c>genkernel</c> to build your kernel, your system will generally detect all |
115 |
+your hardware at boot-time, just like our Installation CD does. Because |
116 |
+genkernel doesn't require any manual kernel configuration, it is an ideal |
117 |
solution for those users who may not be comfortable compiling their own kernels. |
118 |
</p> |
119 |
|
120 |
@@ -391,8 +391,8 @@ |
121 |
|
122 |
<p> |
123 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
124 |
-might need to manually configure your kernel using <c>genkernel --menuconfig |
125 |
-all</c> and add support for your filesystem <e>in</e> the kernel (i.e. |
126 |
+might need to manually configure your kernel using <c>genkernel --menuconfig |
127 |
+all</c> and add support for your filesystem <e>in</e> the kernel (i.e. |
128 |
<e>not</e> as a module). Users of EVMS2 or LVM2 will probably want to add |
129 |
<c>--evms2</c> or <c>--lvm2</c> as arguments as well. |
130 |
</p> |
131 |
@@ -402,11 +402,11 @@ |
132 |
</pre> |
133 |
|
134 |
<p> |
135 |
-Once <c>genkernel</c> completes, a kernel, full set of modules and |
136 |
-<e>initial ram disk</e> (initramfs) will be created. We will use the kernel |
137 |
+Once <c>genkernel</c> completes, a kernel, full set of modules and |
138 |
+<e>initial ram disk</e> (initramfs) will be created. We will use the kernel |
139 |
and initrd when configuring a boot loader later in this document. Write |
140 |
down the names of the kernel and initrd as you will need it when writing |
141 |
-the bootloader configuration file. The initrd will be started immediately after |
142 |
+the bootloader configuration file. The initrd will be started immediately after |
143 |
booting to perform hardware autodetection (just like on the Installation CD) |
144 |
before your "real" system starts up. |
145 |
</p> |