diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index 70ccf3a63..aa9244fc1 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -76,6 +76,10 @@ first a summary, then a detailed log.
+June 19, 2004 [matt]: chapter05 - hostreqs. Provide clearer
+information regarding determining whether the host kernel is suitable for
+passing glibcs testsuite
+
June 19, 2004 [matt]: chapter06 - creatingdirs. Use
`install -d` instead of `mkdir` (fixes bug #821)
diff --git a/chapter05/hostreqs.xml b/chapter05/hostreqs.xml
index d970ef56a..fb34e8db7 100644
--- a/chapter05/hostreqs.xml
+++ b/chapter05/hostreqs.xml
@@ -19,12 +19,19 @@ recently has support for this file system been implemented in most of the kernel
drivers, however. We must be sure that all the critical system devices get
created properly.
-As for obtaining such a kernel, let's hope you distributor has provided
-a 2.6 kernel package for you. If so, install it. If not, you'll have to compile
-it yourself. If you're forced into a situation where you need to compile it
-yourself, it is highly recommended that you compile your kernel in a monolithic
-manner, as you probably don't want to go fiddling with your hosts module
-utilities. Supposing you don't want to listen, open up the module-init-tools
-tarball and check out the README on how to get module support for 2.6.
+In order to check that your host kernel meets the requirements outlined
+above, you can run the following command:
+
+cat /proc/version
+
+This will produce output similar to:
+
+Linux version 2.6.2 (user@host) (gcc version 3.4.0) #1 Tue Apr 20 21:22:18 GMT 2004
+
+If the results of the above command state that your host kernel wasn't
+compiled using a GCC-3.0 (or later) compiler, you will need to compile one
+yourself, and reboot your host to use the newly compiled kernel. Instructions
+for compiling the kernel and configuring the bootloader (assuming your host uses
+GRUB) are given in .