source: chapter10/kernel.xml@ 7b7733d

xry111/clfs-ng
Last change on this file since 7b7733d was f0ebf5c, checked in by Xi Ruoyao <xry111@…>, 15 months ago

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng
  • Property mode set to 100644
File size: 24.3 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-bootable-kernel" role="wrap">
9 <?dbhtml filename="kernel.html"?>
10
11 <sect1info condition="script">
12 <productname>kernel</productname>
13 <productnumber>&linux-version;</productnumber>
14 <address>&linux-url;</address>
15 </sect1info>
16
17 <title>Linux-&linux-version;</title>
18
19 <indexterm zone="ch-bootable-kernel">
20 <primary sortas="a-Linux">Linux</primary>
21 </indexterm>
22
23 <sect2 role="package">
24 <title/>
25
26 <para>The Linux package contains the Linux kernel.</para>
27
28 <segmentedlist>
29 <segtitle>&buildtime;</segtitle>
30 <segtitle>&diskspace;</segtitle>
31
32 <seglistitem>
33 <seg>&linux-knl-sbu;</seg>
34 <seg>&linux-knl-du;</seg>
35 </seglistitem>
36 </segmentedlist>
37
38 </sect2>
39
40 <sect2 role="installation">
41 <title>Installation of the kernel</title>
42
43 <para>Building the kernel involves a few steps&mdash;configuration,
44 compilation, and installation. Read the <filename>README</filename> file
45 in the kernel source tree for alternative methods to the way this book
46 configures the kernel.</para>
47
48 <important>
49 <para>
50 Building the linux kernel for the first time is one of the most
51 challenging tasks in LFS. Getting it right depends on the specific
52 hardware for the target system and your specific needs. There are
53 almost 12,000 configuration items that are available for the kernel
54 although only about a third of them are needed for most computers. The
55 LFS editors recommend that users not familiar with this process follow
56 the procedures below fairly closely. The objective is to get an
57 initial system to a point where you can log in at the command line when
58 you reboot later in <xref linkend="ch-finish-reboot"/>. At his point
59 optimization and customization is not a goal.
60 </para>
61
62
63 <para>
64 For general information on kernel configuration see <ulink
65 url="&hints-root;kernel-configuration.txt"/>. Additional information
66 about configuring and building the kernel can be found at <ulink
67 url="&anduin-sources;/kernel-nutshell/"/>.
68 These references are a bit
69 dated, but still give a reasonable overview of the process.
70 </para>
71
72 <para>
73 If all else fails, you can ask for help on the <ulink
74 url="https://www.linuxfromscratch.org/mail.html">lfs-support</ulink>
75 mailing list. Note that subscribing is required in order for the list
76 to avoid spam.
77 </para>
78 </important>
79
80 <para>Prepare for compilation by running the following command:</para>
81
82<screen><userinput remap="pre">make mrproper</userinput></screen>
83
84 <para>This ensures that the kernel tree is absolutely clean. The
85 kernel team recommends that this command be issued prior to each
86 kernel compilation. Do not rely on the source tree being clean after
87 un-tarring.</para>
88
89 <para>There are several ways to configure the kernel options. Usually,
90 This is done through a menu-driven interface, for example:</para>
91
92<screen role="nodump"><userinput>make menuconfig</userinput></screen>
93
94 <variablelist>
95 <title>The meaning of optional make environment variables:</title>
96
97 <varlistentry>
98 <term><parameter>LANG=&lt;host_LANG_value&gt; LC_ALL=</parameter></term>
99 <listitem>
100 <para>This establishes the locale setting to the one used on the
101 host. This may be needed for a proper menuconfig ncurses interface
102 line drawing on a UTF-8 linux text console.</para>
103
104 <para>If used, be sure to replace
105 <replaceable>&lt;host_LANG_value&gt;</replaceable> by the value of
106 the <envar>$LANG</envar> variable from your host. You can
107 alternatively use instead the host's value of <envar>$LC_ALL</envar>
108 or <envar>$LC_CTYPE</envar>.</para>
109 </listitem>
110 </varlistentry>
111
112 <varlistentry>
113 <term><command>make menuconfig</command></term>
114 <listitem>
115 <para>This launches an ncurses menu-driven interface. For other
116 (graphical) interfaces, type <command>make help</command>.</para>
117 </listitem>
118 </varlistentry>
119 </variablelist>
120
121 <!-- Support for compiling a keymap into the kernel is deliberately removed -->
122
123
124 <note>
125 <para>A good starting place for setting up the kernel configuration is to
126 run <command>make defconfig</command>. This will set the base
127 configuration to a good state that takes your current system architecture
128 into account.</para>
129
130 <para>Be sure to enable/disable/set the following features or the system might
131 not work correctly or boot at all:</para>
132
133 <screen role="nodump" revision="sysv">Processor type and features ---&gt;
134 [*] Build a relocatable kernel [CONFIG_RELOCATABLE]
135 [*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
136General setup ---&gt;
137 [ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
138 &lt; &gt; Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
139 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
140General architecture-dependent options ---&gt;
141 [*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
142 [*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
143Device Drivers ---&gt;
144 Graphics support ---&gt;
145 Frame buffer Devices ---&gt;
146 &lt;*&gt; Support for frame buffer devices ---&gt;
147 Console display driver support ---&gt;
148 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
149 Generic Driver Options ---&gt;
150 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
151 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
152 [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs [CONFIG_DEVTMPFS_MOUNT]</screen>
153
154 <screen role="nodump" revision="systemd">Processor type and features ---&gt;
155 [*] Build a relocatable kernel [CONFIG_RELOCATABLE]
156 [*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
157General setup ---&gt;
158 [ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
159 [ ] Auditing Support [CONFIG_AUDIT]
160 CPU/Task time and stats accounting ---&gt;
161 [*] Pressure stall information tracking [CONFIG_PSI]
162 [ ] Require boot parameter to enable pressure stall information tracking [CONFIG_PSI_DEFAULT_DISABLED]
163 &lt; &gt; Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
164 [*] Control Group support [CONFIG_CGROUPS] ---&gt;
165 [*] Memory controller [CONFIG_MEMCG]
166 [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]
167 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
168General architecture-dependent options ---&gt;
169 [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
170 [*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
171 [*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
172[*] Networking support ---&gt; [CONFIG_NET]
173 Networking options ---&gt;
174 [*] TCP/IP networking [CONFIG_INET]
175 &lt;*&gt; The IPv6 protocol [CONFIG_IPV6]
176Device Drivers ---&gt;
177 Generic Driver Options ---&gt;
178 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
179 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
180 [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs [CONFIG_DEVTMPFS_MOUNT]
181 Firmware Loader ---&gt;
182 [ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
183 Firmware Drivers ---&gt;
184 [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
185 Graphics support ---&gt;
186 Frame buffer Devices ---&gt;
187 &lt;*&gt; Support for frame buffer devices ---&gt;
188 Console display driver support ---&gt;
189 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
190File systems ---&gt;
191 [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
192 Pseudo filesystems ---&gt;
193 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen>
194
195 <para>Enable some additional features if you are building a 64-bit
196 system. If you are using menuconfig, enable them in the order of
197 <parameter>CONFIG_PCI_MSI</parameter> first, then
198 <parameter>CONFIG_IRQ_REMAP</parameter>, at last
199 <parameter>CONFIG_X86_X2APIC</parameter> because an option only
200 shows up after its dependencies are selected.</para>
201
202 <screen role="nodump">Processor type and features ---&gt;
203 [*] Support x2apic [CONFIG_X86_X2APIC]
204Device Drivers ---&gt;
205 [*] PCI Support ---&gt; [CONFIG_PCI]
206 [*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI]
207 [*] IOMMU Hardware Support ---&gt; [CONFIG_IOMMU_SUPPORT]
208 [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen>
209
210 <para>If you are building a 32-bit system running on a hardware
211 with RAM more than 4GB, adjust the configuration so the kernel will
212 be able to use up to 64GB physical RAM:</para>
213
214 <screen role="nodump">Processor type and features ---&gt;
215 High Memory Support ---&gt;
216 (X) 64GB [CONFIG_HIGHMEM64G]</screen>
217
218 <para>If the partition for the LFS system is in a NVME SSD (i. e. the
219 device node for the partition is <filename>/dev/nvme*</filename>
220 instead of <filename>/dev/sd*</filename>), enable NVME support or
221 the LFS system won't boot:</para>
222
223 <screen role="nodump">Device Drivers ---&gt;
224 NVME Support ---&gt;
225 &lt;*&gt; NVM Express block device [CONFIG_BLK_DEV_NVME]</screen>
226 </note>
227
228 <note revision="systemd">
229 <para>While "The IPv6 Protocol" is not strictly
230 required, it is highly recommended by the systemd developers.</para>
231 </note>
232
233 <para>There are several other options that may be desired
234 depending on the requirements for the system. For a list of options needed
235 for BLFS packages, see the <ulink
236 url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
237 Index of Kernel Settings</ulink>.</para>
238
239 <note>
240 <para>If your host hardware is using UEFI and you wish to boot the
241 LFS system with it, you should adjust some kernel configuration
242 following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
243 the BLFS page</ulink> <emphasis role='bold'>even if you'll use the
244 UEFI bootloader from the host distro</emphasis>.</para>
245 </note>
246
247 <variablelist>
248 <title>The rationale for the above configuration items:</title>
249
250 <varlistentry>
251 <term><parameter>Randomize the address of the kernel image (KASLR)</parameter></term>
252 <listitem>
253 <para>Enable ASLR for kernel image, to mitigate some attacks based
254 on fixed addresses of sensitive data or code in the kernel.</para>
255 </listitem>
256 </varlistentry>
257
258 <varlistentry>
259 <term>
260 <parameter>
261 Compile the kernel with warnings as errors
262 </parameter>
263 </term>
264 <listitem>
265 <para>This may cause building failure if the compiler and/or
266 configuration are different from those of the kernel
267 developers.</para>
268 </listitem>
269 </varlistentry>
270
271 <varlistentry>
272 <term>
273 <parameter>
274 Enable kernel headers through /sys/kernel/kheaders.tar.xz
275 </parameter>
276 </term>
277 <listitem>
278 <para>This will require <command>cpio</command> building the kernel.
279 <command>cpio</command> is not installed by LFS.</para>
280 </listitem>
281 </varlistentry>
282
283 <varlistentry>
284 <term>
285 <parameter>
286 Configure standard kernel features (expert users)
287 </parameter>
288 </term>
289 <listitem>
290 <para>This will make some options show up in the configuration
291 interface but changing those options may be dangerous. Do not use
292 this unless you know what you are doing.</para>
293 </listitem>
294 </varlistentry>
295
296 <varlistentry>
297 <term><parameter>Strong Stack Protector</parameter></term>
298 <listitem>
299 <para>Enable SSP for the kernel. We've enabled it for the entire
300 userspace with <parameter>--enable-default-ssp</parameter>
301 configuring GCC, but the kernel does not use GCC default setting
302 for SSP. We enable it explicitly here.</para>
303 </listitem>
304 </varlistentry>
305
306 <varlistentry>
307 <term><parameter>Support for uevent helper</parameter></term>
308 <listitem>
309 <para>Having this option set may interfere with device
310 management when using Udev/Eudev. </para>
311 </listitem>
312 </varlistentry>
313
314 <varlistentry>
315 <term><parameter>Maintain a devtmpfs</parameter></term>
316 <listitem>
317 <para>This will create automated device nodes which are populated by the
318 kernel, even without Udev running. Udev then runs on top of this,
319 managing permissions and adding symlinks. This configuration
320 item is required for all users of Udev/Eudev.</para>
321 </listitem>
322 </varlistentry>
323
324 <varlistentry>
325 <term><parameter>Automount devtmpfs at /dev</parameter></term>
326 <listitem>
327 <para>This will mount the kernel view of the devices on /dev
328 upon switching to root filesystem just before starting
329 init.</para>
330 </listitem>
331 </varlistentry>
332
333 <varlistentry>
334 <term><parameter>Framebuffer Console support</parameter></term>
335 <listitem>
336 <para>This is needed to display the Linux console on a frame
337 buffer device. To allow the kernel to print debug messages at an
338 early boot stage, it shouldn't be built as a kernel module
339 unless an initramfs will be used. And, if
340 <option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled,
341 it's likely <option>CONFIG_DRM_FBDEV_EMULATION</option> (Enable
342 legacy fbdev support for your modesetting driver) should be
343 enabled as well.</para>
344 </listitem>
345 </varlistentry>
346
347 <varlistentry>
348 <term><parameter>Support x2apic</parameter></term>
349 <listitem>
350 <para>Support running the interrupt controller of 64-bit x86
351 processors in x2APIC mode. x2APIC may be enabled by firmware on
352 64-bit x86 systems, and a kernel without this option enabled will
353 panic on boot if x2APIC is enabled by firmware. This option has
354 has no effect, but also does no harm if x2APIC is disabled by the
355 firmware.</para>
356 </listitem>
357 </varlistentry>
358
359 </variablelist>
360
361 <para>Alternatively, <command>make oldconfig</command> may be more
362 appropriate in some situations. See the <filename>README</filename>
363 file for more information.</para>
364
365 <para>If desired, skip kernel configuration by copying the kernel
366 config file, <filename>.config</filename>, from the host system
367 (assuming it is available) to the unpacked <filename
368 class="directory">linux-&linux-version;</filename> directory. However,
369 we do not recommend this option. It is often better to explore all the
370 configuration menus and create the kernel configuration from
371 scratch.</para>
372
373 <para>Compile the kernel image and modules:</para>
374
375<screen><userinput remap="make">make</userinput></screen>
376
377 <para>If using kernel modules, module configuration in <filename
378 class="directory">/etc/modprobe.d</filename> may be required.
379 Information pertaining to modules and kernel configuration is
380 located in <xref linkend="ch-config-udev"/> and in the kernel
381 documentation in the <filename
382 class="directory">linux-&linux-version;/Documentation</filename> directory.
383 Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
384
385 <para>Unless module support has been disabled in the kernel configuration,
386 install the modules with:</para>
387
388<screen><userinput remap="install">make modules_install</userinput></screen>
389
390 <para>After kernel compilation is complete, additional steps are
391 required to complete the installation. Some files need to be copied to
392 the <filename class="directory">/boot</filename> directory.</para>
393
394 <caution>
395 <para>As the cross-built LFS system has a separate &boot-dir;
396 partition, the files copied below should go there. The easiest way to
397 do that is to create the entry for &boot-dir; in &fstab; first (read
398 the previous section for details), then issue the following command
399 as the &root; user:</para>
400
401<screen role="nodump"><userinput>mount /boot</userinput></screen>
402
403 <para>We don't need to specify the path to the device node, as it's
404 already given in <filename>/etc/fstab</filename>.</para>
405 </caution>
406
407 <para>The path to the kernel image may vary depending on the platform being
408 used. The filename below can be changed to suit your taste, but the stem of
409 the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
410 the automatic setup of the boot process described in the next section. The
411 following command assumes an x86 architecture:</para>
412
413<screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
414
415 <para><filename>System.map</filename> is a symbol file for the kernel.
416 It maps the function entry points of every function in the kernel API,
417 as well as the addresses of the kernel data structures for the running
418 kernel. It is used as a resource when investigating kernel problems.
419 Issue the following command to install the map file:</para>
420
421<screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen>
422
423 <para>The kernel configuration file <filename>.config</filename>
424 produced by the <command>make menuconfig</command> step
425 above contains all the configuration selections for the kernel
426 that was just compiled. It is a good idea to keep this file for future
427 reference:</para>
428
429<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
430
431 <para>Install the documentation for the Linux kernel:</para>
432
433<screen><userinput remap="install">install -d /usr/share/doc/linux-&linux-version;
434cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
435
436 <para>It is important to note that the files in the kernel source
437 directory are not owned by <emphasis>root</emphasis>. Whenever a
438 package is unpacked as user <emphasis>root</emphasis> (like we did
439 inside chroot), the files have the user and group IDs of whatever
440 they were on the packager's computer. This is usually not a problem
441 for any other package to be installed because the source tree is
442 removed after the installation. However, the Linux source tree is
443 often retained for a long time. Because of this, there is a chance
444 that whatever user ID the packager used will be assigned to somebody
445 on the machine. That person would then have write access to the kernel
446 source.</para>
447
448 <note>
449 <para>In many cases, the configuration of the kernel will need to be
450 updated for packages that will be installed later in BLFS. Unlike
451 other packages, it is not necessary to remove the kernel source tree
452 after the newly built kernel is installed.</para>
453
454 <para>If the kernel source tree is going to be retained, run
455 <command>chown -R 0:0</command> on the <filename
456 class="directory">linux-&linux-version;</filename> directory to ensure
457 all files are owned by user <emphasis>root</emphasis>.</para>
458 </note>
459
460 <warning>
461 <para>Some kernel documentation recommends creating a symlink from
462 <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
463 source directory. This is specific to kernels prior to the 2.6 series and
464 <emphasis>must not</emphasis> be created on an LFS system as it can cause
465 problems for packages you may wish to build once your base LFS system is
466 complete.</para>
467 </warning>
468
469 <warning>
470 <para>The headers in the system's <filename
471 class="directory">include</filename> directory (<filename
472 class="directory">/usr/include</filename>) should
473 <emphasis>always</emphasis> be the ones against which Glibc was compiled,
474 that is, the sanitised headers installed in <xref
475 linkend="ch-tools-linux-headers"/>. Therefore, they should
476 <emphasis>never</emphasis> be replaced by either the raw kernel headers
477 or any other kernel sanitized headers.</para>
478 </warning>
479
480 </sect2>
481
482 <sect2 id="conf-modprobe" role="configuration">
483 <title>Configuring Linux Module Load Order</title>
484
485 <indexterm zone="conf-modprobe">
486 <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
487 </indexterm>
488
489 <para>Most of the time Linux modules are loaded automatically, but
490 sometimes it needs some specific direction. The program that loads
491 modules, <command>modprobe</command> or <command>insmod</command>, uses
492 <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
493 needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
494 uhci_hcd) have been built as modules, they will be loaded in the correct
495 order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
496 to avoid a warning being output at boot time.</para>
497
498 <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
499 the following:</para>
500
501<screen><userinput>install -v -m755 -d /etc/modprobe.d
502cat &gt; /etc/modprobe.d/usb.conf &lt;&lt; "EOF"
503<literal># Begin /etc/modprobe.d/usb.conf
504
505install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
506install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
507
508# End /etc/modprobe.d/usb.conf</literal>
509EOF</userinput></screen>
510
511 </sect2>
512
513 <sect2 id="contents-kernel" role="content">
514 <title>Contents of Linux</title>
515
516 <segmentedlist>
517 <segtitle>Installed files</segtitle>
518 <segtitle>Installed directories</segtitle>
519
520 <seglistitem>
521 <seg>config-&linux-version;,
522 vmlinuz-&linux-version;-lfs-&version;,
523 and System.map-&linux-version;</seg>
524 <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
525 </seglistitem>
526 </segmentedlist>
527
528 <variablelist>
529 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
530 <?dbfo list-presentation="list"?>
531 <?dbhtml list-presentation="table"?>
532
533 <varlistentry id="config">
534 <term><filename>config-&linux-version;</filename></term>
535 <listitem>
536 <para>Contains all the configuration selections for the kernel</para>
537 <indexterm zone="ch-bootable-kernel config">
538 <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
539 </indexterm>
540 </listitem>
541 </varlistentry>
542
543 <varlistentry id="lfskernel">
544 <term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
545 <listitem>
546 <para>The engine of the Linux system. When turning on the computer,
547 the kernel is the first part of the operating system that gets loaded.
548 It detects and initializes all components of the computer's hardware,
549 then makes these components available as a tree of files to the
550 software and turns a single CPU into a multitasking machine capable
551 of running scores of programs seemingly at the same time</para>
552 <indexterm zone="ch-bootable-kernel lfskernel">
553 <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
554 </indexterm>
555 </listitem>
556 </varlistentry>
557
558 <varlistentry id="System.map">
559 <term><filename>System.map-&linux-version;</filename></term>
560 <listitem>
561 <para>A list of addresses and symbols; it maps the entry points and
562 addresses of all the functions and data structures in the
563 kernel</para>
564 <indexterm zone="ch-bootable-kernel System.map">
565 <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
566 </indexterm>
567 </listitem>
568 </varlistentry>
569
570 </variablelist>
571
572 </sect2>
573
574</sect1>
Note: See TracBrowser for help on using the repository browser.