aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/linux-libc-headers.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter06/linux-libc-headers.xml')
-rw-r--r--chapter06/linux-libc-headers.xml23
1 files changed, 22 insertions, 1 deletions
diff --git a/chapter06/linux-libc-headers.xml b/chapter06/linux-libc-headers.xml
index 487f09798..64d1e93bb 100644
--- a/chapter06/linux-libc-headers.xml
+++ b/chapter06/linux-libc-headers.xml
@@ -25,7 +25,7 @@
<title>Installation of Linux-Libc-Headers</title>
<para>For years it has been common practice to use so-called <quote>raw</quote>
-kernel headers (straight from a kernel tarball) in /usr/include, but over the
+kernel headers (straight from a kernel tarball) in <filename class="directory">/usr/include</filename>, but over the
last few years, the kernel developers have taken a strong stance that such
things should not be done. Thus was born the linux-libc-headers project,
designed to maintain an API stable version of the Linux headers.</para>
@@ -46,4 +46,25 @@ find /usr/include/{asm,linux} -type f -exec chmod 644 {} \;</userinput></screen>
</sect2>
+
+<sect2 id="contents-linux-libc-headers" role="content"><title>Contents of Linux-Libc-Headers</title>
+
+<segmentedlist>
+<segtitle>Installed headers</segtitle>
+<seglistitem><seg>/usr/include/{asm,linux}/*.h</seg></seglistitem>
+</segmentedlist>
+
+<variablelist><title>Short description</title>
+
+<varlistentry id="linux-libc-headers">
+<term><filename class="headerfile">/usr/include/{asm,linux}/*.h</filename></term>
+<listitem>
+<indexterm zone="ch-system-linux-libc-headers linux-libc-headers"><primary sortas="e-/usr/include/{asm,linux}/*.h">/usr/include/{asm,linux}/*.h</primary></indexterm>
+<para>This files are the Linux headers API.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
</sect1>