en/handbook/hb-install-ia64-kernel.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- 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-ia64-kernel.xml,v 1.9 2007/07/27 18:38:09 swift Exp $ -->

<sections>

<version>8.3</version>
<date>2007-07-29</date>

<section>
<title>Timezone</title>
<body>

<p>
You first need to select your timezone so that your system knows where it is
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
The core around which all distributions are built is the Linux kernel. It is the
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>. 
</p>

<p>
For IA64 systems, we will use <c>gentoo-sources</c> (contains additional patches
for performance and stability).
</p>

<p>
Now install it using <c>emerge</c>.
</p>

<pre caption="Installing a kernel source">
# <i>emerge gentoo-sources</i>
</pre>

<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
Your version may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root   root    12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
</pre>

<p>
Now it is time to configure and compile your kernel source. You can use
<c>genkernel</c> for this, which will build a generic kernel as used by the
Installation CD. We explain the "manual" configuration first though, as it is
the best way to optimize your environment.
</p>

<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 
genkernel</uri> instead.
</p>

</body>
</subsection>
</section>
<section id="manual">
<title>Default: Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
couple of kernels you don't even remember that it was difficult ;)
</p>

<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 
uses (it might provide you with a nice hint on what to enable).
</p>

<p>
Now go to your kernel source directory and execute <c>make menuconfig</c>. This
will fire up an ncurses-based configuration menu.
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>
</pre>

<p>
You will be greeted with several configuration sections. We'll first list some
options you must activate (otherwise Gentoo will not function, or not function
properly without additional tweaks).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
First of all, activate the use of development and experimental code/drivers.
You need this, otherwise some very important code/drivers won't show up:
</p>

<pre caption="Selecting experimental code/drivers, General setup">
Code maturity level options ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
General setup  ---&gt;
  [*] Support for hot-pluggable devices
</pre>

<p>
Make sure that every driver that is vital to the booting of your system (such as
SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module,
otherwise your system will not be able to boot completely.
</p>

<p>
Now select the correct system type and processor type. If you don't know what
kind of IA64 system type you have, <c>DIG-compliant</c> is a good default
choice. If you are installing on an SGI system make sure you select the
SGI system type, your kernel may just lock up and refuse to boot otherwise.
</p>

<pre caption="Selecting correct system type">
System type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>DIG-compliant</i>
Processor type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>Itanium 2</i>
</pre>

<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
file system</c>.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [*] Virtual memory file system support (former shm fs)

<comment>(Select one or more of the following options as needed by your system)</comment>
  &lt;*&gt; Reiserfs support
  &lt;*&gt; Ext3 journalling file system support
  &lt;*&gt; JFS filesystem support
  &lt;*&gt; Second extended fs support
  &lt;*&gt; XFS filesystem support

<comment>(Be sure to enable VFAT support for the EFI partition)</comment>
DOS/FAT/NT Filesystems  --->
  &lt;*&gt; VFAT (Windows-95) fs support
</pre>

<p>
Do not forget to enable DMA for your drives:
</p>

<pre caption="Activating DMA">
Device Drivers ---&gt;
  ATA/ATAPI/MFM/RLL support ---&gt;
    [*] Generic PCI bus-master DMA support
</pre>

<p>
If you are using PPPoE to connect to the Internet or you are using a dial-up
modem, you will need the following options in the kernel:
</p>

<pre caption="Selecting PPPoE necessary drivers">
Device Drivers ---&gt;
  Networking Support ---&gt;
    &lt;*&gt; PPP (point-to-point protocol) support
    &lt;*&gt;   PPP support for async serial ports
    &lt;*&gt;   PPP support for sync tty ports
</pre>

<p>
The two compression options won't harm but are not definitely needed, neither
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
when configured to do kernel mode PPPoE.
</p>

<p>
If you require it, don't forget to include support in the kernel for your
ethernet card.
</p>

<p>
If you have an Intel CPU that supports HyperThreading (tm), or you have a
multi-CPU system, you should activate "Symmetric multi-processing support":
</p>

<pre caption="Activating SMP support">
Processor type and features  ---&gt;
  [*] Symmetric multi-processing support
</pre>

<p>
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
those as well:
</p>

<pre caption="Activating USB Support for Input Devices">
Device Drivers ---&gt;
  USB Support ---&gt;
    &lt;*&gt;   USB Human Interface Device (full HID) support
</pre>

<p>
When you've finished configuring the kernel, continue with <uri 
link="#compiling">Compiling and Installing</uri>.
</p>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration and start the compilation process:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel
choice and remember it as you will need it later on when you configure your
bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
name and version of your kernel.
</p>

<pre caption="Installing the kernel">
# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
</pre>

<p>
Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="genkernel">
<title>Alternative: Using genkernel</title>
<body>

<p>
If you are reading this section, you have chosen to use our <c>genkernel</c>
script to configure your kernel for you.
</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 
solution for those users who may not be comfortable compiling their own kernels.
</p>

<p>
Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
</p>

<pre caption="Emerging genkernel">
# <i>emerge genkernel</i>
</pre>

<p>
Now, compile your kernel sources by running <c>genkernel --udev all</c>.
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all 
hardware, this compilation will take quite a while to finish!
</p>

<note>
Users of EVMS2 or LVM2 will probably want to add
<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
</note>

<pre caption="Running genkernel">
# <i>genkernel --udev all</i>
</pre>

<p>
Once <c>genkernel</c> completes, a kernel, full set of modules and 
<e>initial root disk</e> (initrd) 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 
booting to perform hardware autodetection (just like on the Installation CD)
before your "real" system starts up.
</p>

<pre caption="Checking the created kernel image name and initrd">
# <i>ls /boot/kernel* /boot/initramfs*</i>
</pre>

</body>
</section>
<section id="kernel_modules">
<title>Kernel Modules</title>
<subsection>
<title>Configuring the Modules</title>
<body>

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

<p>
To view all available modules, run the following command:
</p>

<pre caption="Viewing all available modules">
# <i>modprobe -l</i>
</pre>

<p>
For instance, to automatically load the <c>3c59x.o</c> module, edit the
<path>kernel-2.6</path> file and enter the module name in it.
</p>

<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>

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

<p>
Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 
your System</uri>.
</p>

</body>
</subsection>
</section>
</sections>
1	<?xml version='1.0' encoding='UTF-8'?>
2	<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4	<!-- The content of this document is licensed under the CC-BY-SA license -->
5	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6
7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.9 2007/07/27 18:38:09 swift Exp $ -->
8
9	<sections>
10
11	<version>8.3</version>
12	<date>2007-07-29</date>
13
14	<section>
15	<title>Timezone</title>
16	<body>
17
18	<p>
19	You first need to select your timezone so that your system knows where it is
20	located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
21	it to <path>/etc/localtime</path>. Please avoid the
22	<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
23	indicate the expected zones. For instance, <path>GMT-8</path> is in fact
24	GMT+8.
25	</p>
26
27	<pre caption="Setting the timezone information">
28	# <i>ls /usr/share/zoneinfo</i>
29	<comment>(Suppose you want to use GMT)</comment>
30	# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
31	</pre>
32
33	</body>
34	</section>
35	<section>
36	<title>Installing the Sources</title>
37	<subsection>
38	<title>Choosing a Kernel</title>
39	<body>
40
41	<p>
42	The core around which all distributions are built is the Linux kernel. It is the
43	layer between the user programs and your system hardware. Gentoo provides its
44	users several possible kernel sources. A full listing with description is
45	available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
46	Guide</uri>.
47	</p>
48
49	<p>
50	For IA64 systems, we will use <c>gentoo-sources</c> (contains additional patches
51	for performance and stability).
52	</p>
53
54	<p>
55	Now install it using <c>emerge</c>.
56	</p>
57
58	<pre caption="Installing a kernel source">
59	# <i>emerge gentoo-sources</i>
60	</pre>
61
62	<p>
63	When you take a look in <path>/usr/src</path> you should see a symlink called
64	<path>linux</path> pointing to your kernel source. In this case, the installed
65	kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
66	Your version may be different, so keep this in mind.
67	</p>
68
69	<pre caption="Viewing the kernel source symlink">
70	# <i>ls -l /usr/src/linux</i>
71	lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/>
72	</pre>
73
74	<p>
75	Now it is time to configure and compile your kernel source. You can use
76	<c>genkernel</c> for this, which will build a generic kernel as used by the
77	Installation CD. We explain the "manual" configuration first though, as it is
78	the best way to optimize your environment.
79	</p>
80
81	<p>
82	If you want to manually configure your kernel, continue now with <uri
83	link="#manual">Default: Manual Configuration</uri>. If you want to use
84	<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
85	genkernel</uri> instead.
86	</p>
87
88	</body>
89	</subsection>
90	</section>
91	<section id="manual">
92	<title>Default: Manual Configuration</title>
93	<subsection>
94	<title>Introduction</title>
95	<body>
96
97	<p>
98	Manually configuring a kernel is often seen as the most difficult procedure a
99	Linux user ever has to perform. Nothing is less true -- after configuring a
100	couple of kernels you don't even remember that it was difficult ;)
101	</p>
102
103	<p>
104	However, one thing <e>is</e> true: you must know your system when you start
105	configuring a kernel manually. Most information can be gathered by emerging
106	pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now
107	be able to use <c>lspci</c> within the chrooted environment. You may safely
108	ignore any <e>pcilib</e> warnings (like pcilib: cannot open
109	/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
110	<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same.
111	You can also run <c>lsmod</c> to see what kernel modules the Installation CD
112	uses (it might provide you with a nice hint on what to enable).
113	</p>
114
115	<p>
116	Now go to your kernel source directory and execute <c>make menuconfig</c>. This
117	will fire up an ncurses-based configuration menu.
118	</p>
119
120	<pre caption="Invoking menuconfig">
121	# <i>cd /usr/src/linux</i>
122	# <i>make menuconfig</i>
123	</pre>
124
125	<p>
126	You will be greeted with several configuration sections. We'll first list some
127	options you must activate (otherwise Gentoo will not function, or not function
128	properly without additional tweaks).
129	</p>
130
131	</body>
132	</subsection>
133	<subsection>
134	<title>Activating Required Options</title>
135	<body>
136
137	<p>
138	First of all, activate the use of development and experimental code/drivers.
139	You need this, otherwise some very important code/drivers won't show up:
140	</p>
141
142	<pre caption="Selecting experimental code/drivers, General setup">
143	Code maturity level options --->
144	[*] Prompt for development and/or incomplete code/drivers
145	General setup --->
146	[*] Support for hot-pluggable devices
147	</pre>
148
149	<p>
150	Make sure that every driver that is vital to the booting of your system (such as
151	SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module,
152	otherwise your system will not be able to boot completely.
153	</p>
154
155	<p>
156	Now select the correct system type and processor type. If you don't know what
157	kind of IA64 system type you have, <c>DIG-compliant</c> is a good default
158	choice. If you are installing on an SGI system make sure you select the
159	SGI system type, your kernel may just lock up and refuse to boot otherwise.
160	</p>
161
162	<pre caption="Selecting correct system type">
163	System type --->
164	<comment>(Change according to your system)</comment>
165	<i>DIG-compliant</i>
166	Processor type --->
167	<comment>(Change according to your system)</comment>
168	<i>Itanium 2</i>
169	</pre>
170
171	<p>
172	Now go to <c>File Systems</c> and select support for the filesystems you use.
173	<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
174	able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
175	file system</c>.
176	</p>
177
178	<pre caption="Selecting necessary file systems">
179	File systems --->
180	Pseudo Filesystems --->
181	[*] /proc file system support
182	[*] Virtual memory file system support (former shm fs)
183
184	<comment>(Select one or more of the following options as needed by your system)</comment>
185	<*> Reiserfs support
186	<*> Ext3 journalling file system support
187	<*> JFS filesystem support
188	<*> Second extended fs support
189	<*> XFS filesystem support
190
191	<comment>(Be sure to enable VFAT support for the EFI partition)</comment>
192	DOS/FAT/NT Filesystems --->
193	<*> VFAT (Windows-95) fs support
194	</pre>
195
196	<p>
197	Do not forget to enable DMA for your drives:
198	</p>
199
200	<pre caption="Activating DMA">
201	Device Drivers --->
202	ATA/ATAPI/MFM/RLL support --->
203	[*] Generic PCI bus-master DMA support
204	</pre>
205
206	<p>
207	If you are using PPPoE to connect to the Internet or you are using a dial-up
208	modem, you will need the following options in the kernel:
209	</p>
210
211	<pre caption="Selecting PPPoE necessary drivers">
212	Device Drivers --->
213	Networking Support --->
214	<*> PPP (point-to-point protocol) support
215	<*> PPP support for async serial ports
216	<*> PPP support for sync tty ports
217	</pre>
218
219	<p>
220	The two compression options won't harm but are not definitely needed, neither
221	does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
222	when configured to do kernel mode PPPoE.
223	</p>
224
225	<p>
226	If you require it, don't forget to include support in the kernel for your
227	ethernet card.
228	</p>
229
230	<p>
231	If you have an Intel CPU that supports HyperThreading (tm), or you have a
232	multi-CPU system, you should activate "Symmetric multi-processing support":
233	</p>
234
235	<pre caption="Activating SMP support">
236	Processor type and features --->
237	[*] Symmetric multi-processing support
238	</pre>
239
240	<p>
241	If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
242	those as well:
243	</p>
244
245	<pre caption="Activating USB Support for Input Devices">
246	Device Drivers --->
247	USB Support --->
248	<*> USB Human Interface Device (full HID) support
249	</pre>
250
251	<p>
252	When you've finished configuring the kernel, continue with <uri
253	link="#compiling">Compiling and Installing</uri>.
254	</p>
255
256	</body>
257	</subsection>
258	<subsection id="compiling">
259	<title>Compiling and Installing</title>
260	<body>
261
262	<p>
263	Now that your kernel is configured, it is time to compile and install it. Exit
264	the configuration and start the compilation process:
265	</p>
266
267	<pre caption="Compiling the kernel">
268	# <i>make && make modules_install</i>
269	</pre>
270
271	<p>
272	When the kernel has finished compiling, copy the kernel image to
273	<path>/boot</path>. Use whatever name you feel is appropriate for your kernel
274	choice and remember it as you will need it later on when you configure your
275	bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
276	name and version of your kernel.
277	</p>
278
279	<pre caption="Installing the kernel">
280	# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
281	</pre>
282
283	<p>
284	Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
285	</p>
286
287	</body>
288	</subsection>
289	</section>
290	<section id="genkernel">
291	<title>Alternative: Using genkernel</title>
292	<body>
293
294	<p>
295	If you are reading this section, you have chosen to use our <c>genkernel</c>
296	script to configure your kernel for you.
297	</p>
298
299	<p>
300	Now that your kernel source tree is installed, it's now time to compile your
301	kernel by using our <c>genkernel</c> script to automatically build a kernel for
302	you. <c>genkernel</c> works by configuring a kernel nearly identically to the
303	way our Installation CD kernel is configured. This means that when you use
304	<c>genkernel</c> to build your kernel, your system will generally detect all
305	your hardware at boot-time, just like our Installation CD does. Because
306	genkernel doesn't require any manual kernel configuration, it is an ideal
307	solution for those users who may not be comfortable compiling their own kernels.
308	</p>
309
310	<p>
311	Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
312	</p>
313
314	<pre caption="Emerging genkernel">
315	# <i>emerge genkernel</i>
316	</pre>
317
318	<p>
319	Now, compile your kernel sources by running <c>genkernel --udev all</c>.
320	Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all
321	hardware, this compilation will take quite a while to finish!
322	</p>
323
324	<note>
325	Users of EVMS2 or LVM2 will probably want to add
326	<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
327	</note>
328
329	<pre caption="Running genkernel">
330	# <i>genkernel --udev all</i>
331	</pre>
332
333	<p>
334	Once <c>genkernel</c> completes, a kernel, full set of modules and
335	<e>initial root disk</e> (initrd) will be created. We will use the kernel
336	and initrd when configuring a boot loader later in this document. Write
337	down the names of the kernel and initrd as you will need it when writing
338	the bootloader configuration file. The initrd will be started immediately after
339	booting to perform hardware autodetection (just like on the Installation CD)
340	before your "real" system starts up.
341	</p>
342
343	<pre caption="Checking the created kernel image name and initrd">
344	# <i>ls /boot/kernel* /boot/initramfs*</i>
345	</pre>
346
347	</body>
348	</section>
349	<section id="kernel_modules">
350	<title>Kernel Modules</title>
351	<subsection>
352	<title>Configuring the Modules</title>
353	<body>
354
355	<p>
356	You should list the modules you want automatically loaded in
357	<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
358	the modules too if you want.
359	</p>
360
361	<p>
362	To view all available modules, run the following command:
363	</p>
364
365	<pre caption="Viewing all available modules">
366	# <i>modprobe -l</i>
367	</pre>
368
369	<p>
370	For instance, to automatically load the <c>3c59x.o</c> module, edit the
371	<path>kernel-2.6</path> file and enter the module name in it.
372	</p>
373
374	<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
375	# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
376	</pre>
377
378	<pre caption="/etc/modules.autoload.d/kernel-2.6">
379	3c59x
380	</pre>
381
382	<p>
383	Continue the installation with <uri link="?part=1&chap=8">Configuring
384	your System</uri>.
385	</p>
386
387	</body>
388	</subsection>
389	</section>
390	</sections>