Attachment #275631 for bug #369841

View | Details | Raw Unified | Return to bug 369841
Collapse All | Expand All

Lines 319-325 Link Here

(-)hb-install-alpha-kernel.xml (-1 / +1 lines)
319		319
320	<p>	320	<p>
321	Once <c>genkernel</c> completes, a kernel, full set of modules and <e>initial	321	Once <c>genkernel</c> completes, a kernel, full set of modules and <e>initial
322	root disk</e> (initrd) will be created. We will use the kernel and initrd when	322	ram disk</e> (initrd) will be created. We will use the kernel and initrd when
323	configuring a boot loader later in this document. Write down the names of the	323	configuring a boot loader later in this document. Write down the names of the
324	kernel and initrd as you will need it when writing the bootloader configuration	324	kernel and initrd as you will need it when writing the bootloader configuration
325	file. The initrd will be started immediately after booting to perform hardware	325	file. The initrd will be started immediately after booting to perform hardware

Lines 108-114 Link Here

(-)hb-install-bootconfig.xml (-1 / +1 lines)
108	<p>	108	<p>
109	If you want to view the Gentoo Handbook during the installation, make sure you	109	If you want to view the Gentoo Handbook during the installation, make sure you
110	have created a user account (see <uri link="#useraccounts">Optional: User	110	have created a user account (see <uri link="#useraccounts">Optional: User
111	Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in.	111	Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal.
112	</p>	112	</p>
113		113
114	<p>	114	<p>

Lines 318-324 Link Here

(-)hb-install-hppa-kernel.xml (-1 / +1 lines)
318		318
319	<p>	319	<p>
320	Once <c>genkernel</c> completes, a kernel, full set of modules and	320	Once <c>genkernel</c> completes, a kernel, full set of modules and
321	<e>initial root disk</e> (initrd) will be created. We will use the kernel	321	<e>initial ram disk</e> (initrd) will be created. We will use the kernel
322	and initrd when configuring a boot loader later in this document. Write	322	and initrd when configuring a boot loader later in this document. Write
323	down the names of the kernel and initrd as you will need it when writing	323	down the names of the kernel and initrd as you will need it when writing
324	the bootloader configuration file. The initrd will be started immediately after	324	the bootloader configuration file. The initrd will be started immediately after

Lines 310-316 Link Here

(-)hb-install-ia64-kernel.xml (-1 / +1 lines)
310		310
311	<p>	311	<p>
312	Once <c>genkernel</c> completes, a kernel, full set of modules and	312	Once <c>genkernel</c> completes, a kernel, full set of modules and
313	<e>initial root disk</e> (initrd) will be created. We will use the kernel	313	<e>initial ram disk</e> (initrd) will be created. We will use the kernel
314	and initrd when configuring a boot loader later in this document. Write	314	and initrd when configuring a boot loader later in this document. Write
315	down the names of the kernel and initrd as you will need it when writing	315	down the names of the kernel and initrd as you will need it when writing
316	the bootloader configuration file. The initrd will be started immediately after	316	the bootloader configuration file. The initrd will be started immediately after





<p>
You should list the modules you want automatically loaded in
<path>/etc/conf.d/modules</path>. You can add extra options to
the modules too if you want.
</p>


</pre>

<p>
For instance, to automatically load the <c>3c59x.ko</c> module (which is the
driver for a specific 3Com network card family), edit the
<path>/etc/conf.d/modules</path> file and enter the module name in it.
</p>

<pre caption="Editing /etc/conf.d/modules">
# <i>nano -w /etc/conf.d/modules</i>
modules_2_6="<i>3c59x</i>"

<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>

<p>

Lines 406-412 Link Here

(-)hb-install-ppc-kernel.xml (-1 / +1 lines)
406		406
407	<p>	407	<p>
408	Once <c>genkernel</c> completes, a kernel, full set of modules and	408	Once <c>genkernel</c> completes, a kernel, full set of modules and
409	<e>initial root disk</e> (initrd) will be created. We will use the kernel	409	<e>initial ram disk</e> (initrd) will be created. We will use the kernel
410	and initrd when configuring a boot loader later in this document. Write	410	and initrd when configuring a boot loader later in this document. Write
411	down the names of the kernel and initrd as you will need them when writing	411	down the names of the kernel and initrd as you will need them when writing
412	the bootloader configuration file. The initrd will be started immediately after	412	the bootloader configuration file. The initrd will be started immediately after




Depending on your installation medium, you have a couple of tools available to
download a stage. If you have <c>links</c> available, then you can immediately
surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and 
choose a mirror close to you: type <c>links http://www.gentoo.org/main/en/mirrors.xml</c>
and press enter.
</p>

<p>

</p>

<p>
Select a mirror closeby. Usually HTTP mirrors suffice, but other protocols are
available as well. Move to the <path><keyval id="release-dir"/></path>
directory. There you should see all available stage files for your architecture
(they might be stored within subdirectories named after the individual
subarchitectures). Select one and press <c>D</c> to download. When you're
finished, press <c>Q</c> to quit the browser.
</p>

<p test="'x86'=func:keyval('arch')">

Lines 30-36 Link Here

(-)hb-install-system.xml (-1 / +9 lines)
30	our <uri link="/main/en/mirrors.xml">mirror list</uri> and search	30	our <uri link="/main/en/mirrors.xml">mirror list</uri> and search
31	for a mirror (or mirrors) close to you (as those are most frequently the	31	for a mirror (or mirrors) close to you (as those are most frequently the
32	fastest ones), but we provide a nice tool called <c>mirrorselect</c> which	32	fastest ones), but we provide a nice tool called <c>mirrorselect</c> which
33	provides you with a nice interface to select the mirrors you want.	33	provides you with a nice interface to select the mirrors you want. Just
		34	navigate to the mirrors of choice and press spacebar to select one or more
		35	mirrors.
34	</p>	36	</p>
35		37
36	<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable">	38	<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable">
Lines 89-94 Link Here
89	<body>	91	<body>
90		92
91	<p>	93	<p>
		94	In a few moments, we will change the Linux root towards the new location. To
		95	make sure that the new environment works properly, we need to make certain file
		96	systems available there as well.
		97	</p>
		98
		99	<p>
92	Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to	100	Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to
93	allow the installation to use the kernel-provided information within the	101	allow the installation to use the kernel-provided information within the
94	chrooted environment, and then mount-bind the <path>/dev</path> filesystem.	102	chrooted environment, and then mount-bind the <path>/dev</path> filesystem.

Lines 403-409 Link Here

(-)hb-install-x86+amd64-kernel.xml (-1 / +1 lines)
403		403
404	<p>	404	<p>
405	Once <c>genkernel</c> completes, a kernel, full set of modules and	405	Once <c>genkernel</c> completes, a kernel, full set of modules and
406	<e>initial root disk</e> (initrd) will be created. We will use the kernel	406	<e>initial ram disk</e> (initrd) will be created. We will use the kernel
407	and initrd when configuring a boot loader later in this document. Write	407	and initrd when configuring a boot loader later in this document. Write
408	down the names of the kernel and initrd as you will need it when writing	408	down the names of the kernel and initrd as you will need it when writing
409	the bootloader configuration file. The initrd will be started immediately after	409	the bootloader configuration file. The initrd will be started immediately after

Return to bug 369841

Lines 13-19 Link Here

(-)hb-install-kernelmodules.xml (-9 / +7 lines)
13		13
14	<p>	14	<p>
15	You should list the modules you want automatically loaded in	15	You should list the modules you want automatically loaded in
16	<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to	16	<path>/etc/conf.d/modules</path>. You can add extra options to
17	the modules too if you want.	17	the modules too if you want.
18	</p>	18	</p>
19		19
Lines 28-43 Link Here
28	</pre>	28	</pre>
29		29
30	<p>	30	<p>
31	For instance, to automatically load the <c>3c59x.ko</c> module, edit the	31	For instance, to automatically load the <c>3c59x.ko</c> module (which is the
32	<path>kernel-2.6</path> file and enter the module name in it.	32	driver for a specific 3Com network card family), edit the
		33	<path>/etc/conf.d/modules</path> file and enter the module name in it.
33	</p>	34	</p>
34		35
35	<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">	36	<pre caption="Editing /etc/conf.d/modules">
36	# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>	37	# <i>nano -w /etc/conf.d/modules</i>
37	</pre>	38	modules_2_6="<i>3c59x</i>"
38
39	<pre caption="/etc/modules.autoload.d/kernel-2.6">
40	3c59x
41	</pre>	39	</pre>
42		40
43	<p>	41	<p>

Lines 95-101 Link Here

(-)hb-install-stage.xml (-6 / +8 lines)
95	Depending on your installation medium, you have a couple of tools available to	95	Depending on your installation medium, you have a couple of tools available to
96	download a stage. If you have <c>links</c> available, then you can immediately	96	download a stage. If you have <c>links</c> available, then you can immediately
97	surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and	97	surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and
98	choose a mirror close to you.	98	choose a mirror close to you: type <c>links http://www.gentoo.org/main/en/mirrors.xml</c>
		99	and press enter.
99	</p>	100	</p>
100		101
101	<p>	102	<p>
Lines 114-124 Link Here
114	</p>	115	</p>
115		116
116	<p>	117	<p>
117	Move to the <path><keyval id="release-dir"/></path> directory. There you	118	Select a mirror closeby. Usually HTTP mirrors suffice, but other protocols are
118	should see all available stage files for your architecture (they might be	119	available as well. Move to the <path><keyval id="release-dir"/></path>
119	stored within subdirectories named after the individual subarchitectures).	120	directory. There you should see all available stage files for your architecture
120	Select one and press <c>D</c> to download. When you're finished, press <c>Q</c>	121	(they might be stored within subdirectories named after the individual
121	to quit the browser.	122	subarchitectures). Select one and press <c>D</c> to download. When you're
		123	finished, press <c>Q</c> to quit the browser.
122	</p>	124	</p>
123		125
124	<p test="'x86'=func:keyval('arch')">	126	<p test="'x86'=func:keyval('arch')">