aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/linux-libc-headers.xml
diff options
context:
space:
mode:
authorManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-05-30 13:41:04 +0000
committerManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-05-30 13:41:04 +0000
commit574b0eabcc0015a1ee7c8b7098f50e2b6b0e9005 (patch)
tree83d15d25797db1a7575a6bc2e8b8d34783f25e14 /chapter05/linux-libc-headers.xml
parentb711e1d6218396e587b111d540c8567453b21502 (diff)
Tagging corrections in chapters 5.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3730 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/linux-libc-headers.xml')
-rw-r--r--chapter05/linux-libc-headers.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter05/linux-libc-headers.xml b/chapter05/linux-libc-headers.xml
index 31f1b2b20..a74ce26e3 100644
--- a/chapter05/linux-libc-headers.xml
+++ b/chapter05/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>