Context Navigation

rf0f3191	r2f5db45b
14	14	/usr/bin. One reason being: the /usr partition might be on a separate
15	15	partition which has to be mounted at some point. Before that partition is
16		mounted ~~a user needs~~ and will want to have bash available (it will be hard to
	16	mounted you need and will want to have bash available (it will be hard to
17	17	execute the boot scripts without a shell for instance).</para>
18	18

chapter05/diffutils-exp.xml

-              rf0f3191
+              r2f5db45b
 replace every instance of re_max_failures it finds by re_max_failures2
 before handing the source file to the compiler itself for compilation. This
+package has problems linking statically on certain platforms (depending
+on the Glibc version used on that system) and this construction fixes
+that problem.</para>
+package has problems linking statically on systems that run an older
+Glibc version and this construction fixes that problem.</para>
 </sect2>

-              rf0f3191
+              r2f5db45b
 <para><userinput>patch -Np1 -i ../gzip-&gzip-version;.patch </userinput> This
+patch file is necessary to avoid a
+conflict of variable names with glibc when compiling and linking
+statically.</para>
+patch file is necessary to avoid a conflict of variable names with
+Glibc-2.0 systems when compiling and linking statically.</para>
 </sect2>

-              rf0f3191
+              r2f5db45b
 setting up basic networking.</para>
 <para>The software in this chapter will be linked statically. These programs
 will be reinstalled in the next chapter and linked dynamically. The
+<para>The software in this chapter will be linked statically and will be
+reinstalled in the next chapter and linked dynamically. The
 reason for the static version first is that there is a chance that our
 normal Linux system and the LFS system aren't using the same C
 Library versions. If the programs in the first part are linked against
 an older C library version, those programs might not work well on the
+LFS system.</para>
+LFS system. Another reason is to resolve circular dependencies. An
+example of such a dependency is that you need a compiler to install a
+compiler, and you're going to need a shell to install a shell and that
+copmiler.</para>
 <para>The key to learn what makes Linux tick is to know exactly what packages

rf0f3191	r2f5db45b
2	2	<title>Mounting $LFS/proc file system</title>
3	3
4		<para>In order for certain programs to function properly the proc file system
	4	<para>In order for certain programs to function properly, the proc file system
5	5	must be mounted and available from within the chroot'ed environment as
6	6	well. It's not a problem to mount the proc file system twice

-              rf0f3191
+              r2f5db45b
 <para>In order for the user and group root to be recognized and to be able to
 login, there needs to be an entry in the /etc/passwd and /etc/group file.
 Besides the group root a couple of other groups are recommended and needed by
+Besides the group root, a couple of other groups are recommended and needed by
 packages. The groups with their GID's below aren't part of any standard.
 The LSB only recommends besides a group root a group bin to be present
 with GID 1. Other group names and GID's can be chosen by the user. Well
 written packages don't depend on GID numbers but just use the group
+name, since it doesn't matter all that much what GID a group has. Since there
+aren't any standards for groups I won't follow any conventions used by
+Debian, RedHat and others. The groups added here are the groups the
+name, since it doesn't matter which GID a group has. Since there
+aren't any standards for groups The groups created here are the groups the
 MAKEDEV script (the script that creates the device files in the /dev
 directory) mentions.</para>

-              rf0f3191
+              r2f5db45b
 <para><userinput>patch -Np1 -i
 ../sh-utils-&sh-utils-version;.patch</userinput>This
+patch is needed to avoid a conflict of variable names with glibc when
+patch is needed to avoid a conflict of variable names with certain Glibc
+verions (depending on the way your distributio has patched Glibc) when
 compiling sh-utils statically.</para>

Note: See TracChangeset for help on using the changeset viewer.