Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

26 files changed, 54 insertions, 54 deletions

diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml
index 726a54161..3e3a82dc9 100644
--- a/chapter06/aboutdebug.xml
+++ b/chapter06/aboutdebug.xml
@@ -2,7 +2,7 @@
 <title>About debugging symbols</title>
 <?dbhtml filename="aboutdebug.html" dir="chapter06"?>
 
-<para>Most programs and libraries are by default compiled with debugging
+<para>Most programs and libraries are, by default, compiled with debugging
 symbols included (with gcc option -g).</para>
 
 <para>When debugging a program or library that was compiled with debugging
@@ -43,7 +43,7 @@ Wildcards can be used to treat multiple files (use something like
 
 <para>For your convenience, Chapter 9 includes one simple command to strip
 all debugging symbols from all programs and libraries on your system.
-Additional information on optimization you can find in the hint at
+Additional information on optimization can be found in the hint at
 <ulink url="&hints-root;optimization.txt"/>.</para>
 
 </sect1>
diff --git a/chapter06/binutils-exp.xml b/chapter06/binutils-exp.xml
index 7e8711e2c..4d875e0d5 100644
--- a/chapter06/binutils-exp.xml
+++ b/chapter06/binutils-exp.xml
@@ -2,7 +2,7 @@
 <title>Command explanations</title>
 
 <para><userinput>tooldir=/usr:</userinput> Normally, the tooldir (the
-directory where the executables from binutils end up in) is set to
+directory where the executables from binutils end up) is set to
 $(exec_prefix)/$(target_alias) which expands into, for example, 
 /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
 need this target specific directory in /usr. That setup would be used
diff --git a/chapter06/binutils-inst.xml b/chapter06/binutils-inst.xml
index 970d734cf..3ccc05b91 100644
--- a/chapter06/binutils-inst.xml
+++ b/chapter06/binutils-inst.xml
@@ -2,9 +2,9 @@
 
 <para>This package is known to behave badly when you have changed its
 default optimization flags (including the -march and -mcpu options). Binutils
-is best left alone.  Therefore, if you have defined any environment variables
+is best left alone. Therefore, if you have defined any environment variables
 that override default optimizations, such as CFLAGS and CXXFLAGS, we
-recommend unsetting or modifying them when building binutils.  You have
+recommend unsetting or modifying them when building binutils. You have
 been warned.</para>
 
 <para>Install Binutils by running the following commands:</para>
diff --git a/chapter06/bzip2-exp.xml b/chapter06/bzip2-exp.xml
index 90ec45942..9a2f7132f 100644
--- a/chapter06/bzip2-exp.xml
+++ b/chapter06/bzip2-exp.xml
@@ -3,7 +3,7 @@
 
 <para><userinput>make -f Makefile-libbz2_so:</userinput> This will cause bzip2
 to be built using a different Makefile file, in this case the
-Makefile-libbz2_so file which creates a dynamic libbz2.so library and
+Makefile-libbz2_so file, which creates a dynamic libbz2.so library and
 links the bzip2 utilities against it.</para>
 
 </sect2>
diff --git a/chapter06/bzip2-inst.xml b/chapter06/bzip2-inst.xml
index ac95299a4..c3519fe86 100644
--- a/chapter06/bzip2-inst.xml
+++ b/chapter06/bzip2-inst.xml
@@ -16,7 +16,7 @@ mv /usr/bin/{bzip2recover,bzless,bzmore} /bin &amp;&amp;
 ln -s bzip2 /bin/bunzip2 &amp;&amp;
 ln -s bzip2 /bin/bzcat</userinput></screen></para>
 
-<para>Although it's not strictly a part of a basic LFS system it's worth
+<para>Although it's not strictly a part of a basic LFS system, it's worth
 mentioning that a patch for Tar can be downloaded which enables the tar
 program to compress and uncompress using bzip2/bunzip2 easily. With a
 plain tar, you have to use constructions like
diff --git a/chapter06/chroot.xml b/chapter06/chroot.xml
index dd220020a..ad297a215 100644
--- a/chapter06/chroot.xml
+++ b/chapter06/chroot.xml
@@ -1,14 +1,14 @@
 <sect1 id="ch06-chroot">
-<title>Entering the chroot'ed environment</title>
+<title>Entering the chroot environment</title>
 <?dbhtml filename="chroot.html" dir="chapter06"?>
 
-<para>It is time to enter the chroot'ed environment in order to begin installing
+<para>It is time to enter the chroot environment in order to begin installing
 the packages we need. Before you can chroot, however, you need to become
 <emphasis>root</emphasis>, since only <emphasis>root</emphasis>
 can execute the <userinput>chroot</userinput> command.</para>
 
 <para>Become <emphasis>root</emphasis> and run the following command
-to enter the chroot'ed environment:</para>
+to enter the chroot environment:</para>
 
 <para><screen><userinput>chroot $LFS /static/bin/env -i \
 &nbsp;&nbsp;&nbsp;&nbsp;HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
@@ -17,20 +17,20 @@ to enter the chroot'ed environment:</para>
 </para>
 
 <para>The <userinput>-i</userinput> option given to the
-<userinput>env</userinput> command will clear all variables of the chroot'ed
+<userinput>env</userinput> command will clear all variables of the chroot
 environment. After that, only the HOME, TERM, PS1 and PATH variables are
 set again. The TERM=$TERM construct will set the TERM variable inside chroot
 to the same value as outside chroot; this variable is needed for programs
 like vim and less to operate properly. If you need other variables present,
 such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para>
 
-<para>From this point on there's no need anymore to use the $LFS variable,
+<para>From this point on there's no need anymore to use the LFS variable,
 because everything you do will be restricted to the LFS file system -- since
 what the shell thinks is <filename class="directory">/</filename> is actually
 <filename class="directory">/mnt/lfs</filename>.</para>
 
 <para>You have to make sure all the commands in the rest of this chapter and
-in the following chapters are run from within the chroot'ed environment.
+in the following chapters are run from within the chroot environment.
 If you ever leave this environment for any reason (rebooting for example),
 you must remember to again enter chroot and mount proc (discussed later)
 before continuing with the installations.</para>
diff --git a/chapter06/creatingdirs.xml b/chapter06/creatingdirs.xml
index 0b149bfb2..36f8fae5b 100644
--- a/chapter06/creatingdirs.xml
+++ b/chapter06/creatingdirs.xml
@@ -2,7 +2,7 @@
 <title>Creating directories</title>
 <?dbhtml filename="creatingdirs.html" dir="chapter06"?>
 
-<para>Let's now create some structure in our LFS file system, let's create
+<para>Let's now create some structure in our LFS file system. Let's create
 a directory tree. Issuing the following commands will create a more or less
 standard tree:</para>
  
@@ -22,7 +22,7 @@ mkdir /opt/{bin,doc,include,info} &amp;&amp;
 mkdir -p /opt/{lib,man/man{1,2,3,4,5,6,7,8}} &amp;&amp;
 ln -s ../var/tmp /usr</userinput></screen></para>
 
-<para>Directories are by default created with permission mode 755, but this
+<para>Directories are, by default, created with permission mode 755, but this
 isn't desirable for all directories. We will make two changes: one to the home
 directory of root, and another to the directories for temporary files.</para>
 
@@ -31,11 +31,11 @@ chmod 1777 /tmp /var/tmp</userinput></screen></para>
 
 <para>The first mode change ensures that not just everybody can enter the
 <filename class="directory">/root</filename> directory -- the same
-a normal user would do with his or her home directory.
+as a normal user would do with his or her home directory.
 The second mode change makes sure that any user can write to the
 <filename class="directory">/tmp</filename> and
 <filename class="directory">/var/tmp</filename> directories, but
-cannot remove other users's files from them. The latter is prohibited
+cannot remove other users' files from them. The latter is prohibited
 by the so-called "sticky bit" -- the highest bit in the 1777 bit mask.</para>
 
 <para>Now that the directories are created, move the source tarballs that
@@ -53,7 +53,7 @@ tree this standard stipulates the existence of
 <filename class="directory">/usr/share/games</filename>, but we don't
 much like these for a base system. However, feel free to make your system
 FHS-compliant. As to the structure of the
-<filename class="directory">/usr/local/share</filename> subdirectory the FHS
+<filename class="directory">/usr/local/share</filename> subdirectory, the FHS
 isn't precise, so we created here the directories that we think are needed.</para>
 
 </sect2>
diff --git a/chapter06/e2fsprogs-exp.xml b/chapter06/e2fsprogs-exp.xml
index 69c097125..ad326915f 100644
--- a/chapter06/e2fsprogs-exp.xml
+++ b/chapter06/e2fsprogs-exp.xml
@@ -4,10 +4,10 @@
 <para><userinput>--with-root-prefix="":</userinput> The
 reason for supplying this option is because of the setup of the
 e2fsprogs Makefile. Some programs are essential for system use when,
-for example, /usr isn't mounted (like the e2fsck program).  These 
-programs and libraries therefore belong in directories like /lib and 
+for example, /usr isn't mounted (like the e2fsck program). These 
+programs and libraries, therefore, belong in directories like /lib and 
 /sbin. If this option isn't passed to E2fsprogs's configure, it places 
-these programs in /usr which  is not what we want.</para>
+these programs in /usr, which is not what we want.</para>
 
 <para><userinput>--enable-elf-shlibs:</userinput> This creates shared
 libraries that some programs in this package can make use of.</para>
diff --git a/chapter06/findutils-inst.xml b/chapter06/findutils-inst.xml
index b32686595..889d0ef36 100644
--- a/chapter06/findutils-inst.xml
+++ b/chapter06/findutils-inst.xml
@@ -18,7 +18,7 @@ make libexecdir=/usr/bin install</userinput></screen></para>
 
 <para>By default, the location of the updatedb database is in /usr/var.
 If you would rather be FHS compliant, you may wish to use another
-location.  The following commands use the database file 
+location. The following commands use the database file 
 <filename>/var/lib/misc/locatedb</filename> which is FHS compliant.</para>
 
 <para><screen><userinput>patch -Np1 -i ../findutils-&findutils-patch-version;.patch &amp;&amp;
diff --git a/chapter06/gcc-inst.xml b/chapter06/gcc-inst.xml
index 3a3b4b2c5..73c72211c 100644
--- a/chapter06/gcc-inst.xml
+++ b/chapter06/gcc-inst.xml
@@ -7,9 +7,9 @@ commands.</para>
 
 <para>This package is known to behave badly when you have changed its
 default optimization flags (including the -march and -mcpu options). GCC is
-best left alone.  Therefore, if you have defined any environment variables
+best left alone. Therefore, if you have defined any environment variables
 that override default optimizations, such as CFLAGS and CXXFLAGS, we
-recommend unsetting or modifying them when building Gcc.  You have
+recommend unsetting or modifying them when building Gcc. You have
 been warned.</para>
 
 <para>Install GCC by running the following commands. These commands will build
diff --git a/chapter06/glibc-exp.xml b/chapter06/glibc-exp.xml
index e9066c270..7495f80d6 100644
--- a/chapter06/glibc-exp.xml
+++ b/chapter06/glibc-exp.xml
@@ -30,7 +30,7 @@ of libraries with profiling information. This command may be omitted if
 you plan to do profiling.</para>
 
 <para><userinput>--enable-add-ons:</userinput> This enables the add-on that
-we install with Glibc: linuxthreads</para>
+we install with Glibc, linuxthreads</para>
 
 <para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
 pt_chown program to be installed in the /usr/bin directory.</para>
diff --git a/chapter06/glibc-inst.xml b/chapter06/glibc-inst.xml
index d122aba01..7b512cd60 100644
--- a/chapter06/glibc-inst.xml
+++ b/chapter06/glibc-inst.xml
@@ -12,9 +12,9 @@ would do.</para>
 
 <para>This package is known to behave badly when you have changed its
 default optimization flags (including the -march and -mcpu options). Glibc
-is best left alone.  Therefore, if you have defined any environment variables
+is best left alone. Therefore, if you have defined any environment variables
 that override default optimizations, such as CFLAGS and CXXFLAGS, we
-recommend unsetting or modifying them when building Glibc.  You have
+recommend unsetting or modifying them when building Glibc. You have
 been warned.</para>
 
 <para>Also, don't pass the --enable-kernel option to the configure
@@ -40,8 +40,8 @@ exec /static/bin/bash --login</userinput></screen></para>
 
 <para>An alternative to running <userinput>make
 localedata/install-locales</userinput> is to only install those locales
-which you need or want.  This can be achieved using the localedef
-command.  Information on this can be found in the INSTALL
+which you need or want. This can be achieved using the localedef
+command. Information on this can be found in the INSTALL
 file in the glibc-&glibc-version; tree. One thing to note is that the
 <userinput>localedef</userinput> program assumes that the <filename
 class="directory">/usr/lib/locale</filename> directory exists, so you need
@@ -49,7 +49,7 @@ to create it first.</para>
 
 <para>The Linux Threads man pages are not going to be installed at this
 point because it requires a working Perl installation. We'll install Perl
-later on in this chapter so we'll come back to the Linux Threads man page
+later on in this chapter, so we'll come back to the Linux Threads man page
 installation after that.</para>
 
 <para>During the configure stage you will see the following warning:</para>
diff --git a/chapter06/groff-exp.xml b/chapter06/groff-exp.xml
index 2db6716bc..00e9d727d 100644
--- a/chapter06/groff-exp.xml
+++ b/chapter06/groff-exp.xml
@@ -2,7 +2,7 @@
 <title>Command explanations</title>
 
 <para><userinput>make PROCESSEDEXAMPLEFILES="":</userinput> Groff has a few
-extra dependencies that we don't install with LFS. This option disable the
+extra dependencies that we don't install with LFS. This option disables the
 need for those tools.</para>
 
 <para><userinput>ln -s ...</userinput>: These symlinks are needed for some
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index dfe834c24..68456fc4e 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -3,7 +3,7 @@
 <?dbhtml filename="introduction.html" dir="chapter06"?>
 
 <para>In this chapter we enter the building site, and start
-constructing our LFS system in earnest.  That is, we chroot into
+constructing our LFS system in earnest. That is, we chroot into
 our temporary mini Linux system, create some auxiliary things,
 and then start installing all the packages, one by one.</para>
  
@@ -21,13 +21,13 @@ take a look at the optimization hint at
 Compiler optimizations can make a program run faster, but they
 may also cause compilation difficulties. If a package refuses
 to compile when using optimization, try to compile it without
-optimization and see if  the problem goes away.</para>
+optimization and see if the problem goes away.</para>
 
 <para>The order in which packages are installed in this chapter has
 to be strictly followed, to ensure that no program gets a path referring
 to <filename class="directory">/static</filename> hard-wired into it.
 For the same reason, <emphasis>do not </emphasis> compile packages
-in parallel.  Compiling in parallel may save you some time (especially on
+in parallel. Compiling in parallel may save you some time (especially on
 dual-CPU machines), but it could result in a program containing a
 hard-wired path to <filename class="directory">/static</filename>,
 which will cause the program to stop working when the static directory
diff --git a/chapter06/kbd-exp.xml b/chapter06/kbd-exp.xml
index f6ca100e2..e8d9e7fee 100644
--- a/chapter06/kbd-exp.xml
+++ b/chapter06/kbd-exp.xml
@@ -3,11 +3,11 @@
 
 <para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>:
 This patch fixes two problems. The first one is the <userinput>loadkeys -d</userinput>
-behaviour which is broken in current kbd versions. It is necessary to fix this,
+behaviour, which is broken in current kbd versions. It is necessary to fix this,
 because the boot scripts rely on a proper <userinput>loadkeys -d</userinput>.
-The second part of the patch changes a Makefile so some utilities (setlogcons,
-setvesablank and getunimap) that are not installed by default, are installed as
-well.</para>
+The second part of the patch changes a Makefile so some utilities that are
+not installed by default (setlogcons, setvesablank and getunimap) are also
+installed.</para>
 
 </sect2>
 
diff --git a/chapter06/kernel-exp-headers.xml b/chapter06/kernel-exp-headers.xml
index 4e42a1549..4c37a00e0 100644
--- a/chapter06/kernel-exp-headers.xml
+++ b/chapter06/kernel-exp-headers.xml
@@ -26,7 +26,7 @@ sources should go into "/usr/src/linux" even though that hasn't been
 true in a _loong_ time.</screen>
 
 <para>The essential part is where Linus states that the header files should be
-<emphasis>the ones which glibc was compiled against</emphasis>.  These are
+<emphasis>the ones which glibc was compiled against</emphasis>. These are
 the headers that should be used when you later compile other packages, as they
 are the ones that match the object-code library files. By copying the headers,
 we ensure that they remain available if later you upgrade your kernel.</para>
diff --git a/chapter06/kernel-exp.xml b/chapter06/kernel-exp.xml
index ed087d4f0..21bfabd20 100644
--- a/chapter06/kernel-exp.xml
+++ b/chapter06/kernel-exp.xml
@@ -8,7 +8,7 @@ for that. At the end we remove it again.</para>
 
 <para><userinput>make mrproper</userinput>: This ensures that the kernel
 tree is absolutely clean. The kernel team recommends that this command be
-issued prior to <emphasis>each</emphasis> kernel compilation, and that you
+issued prior to <emphasis>each</emphasis> kernel compilation and that you
 shouldn't rely on the source tree being clean after untarring.</para>
 
 <para><userinput>make include/linux/version.h</userinput> and
diff --git a/chapter06/lilo-inst.xml b/chapter06/lilo-inst.xml
index 55d3389a8..1ea435aa0 100644
--- a/chapter06/lilo-inst.xml
+++ b/chapter06/lilo-inst.xml
@@ -21,7 +21,7 @@ update. Don't do this, as it has no use: the /etc/lilo.conf isn't present
 yet. We will complete the installation of lilo in Chapter 8.</para>
 
 <para>The standard LILO prompt, or menu, may be replaced by the
-LFS logo, or any logo you like. Martin Imobersteg has written a
+LFS logo or any logo you like. Martin Imobersteg has written a
 hint about this, which is located at 
 <ulink url="&hints-root;bootlogo.txt"/>.</para>
 
diff --git a/chapter06/makedev-exp.xml b/chapter06/makedev-exp.xml
index aa8e4b05d..f41589da6 100644
--- a/chapter06/makedev-exp.xml
+++ b/chapter06/makedev-exp.xml
@@ -4,9 +4,9 @@
 <para><userinput>./MAKEDEV -v generic:</userinput> This creates a whole
 bunch of devices. Normally, these are all the devices you will need. But it
 is possible that some special devices needed for your hardware configuration
-are missing. Create these with ./MAKEDEV -v &lt;device&gt;.  
+are missing. Create these with ./MAKEDEV -v &lt;device&gt;.
 The <userinput>generic-nopty</userinput> option mostly creates the same
-devices as <userinput>generic-nopty</userinput>, but skips those that aren't
+devices as <userinput>generic</userinput>, but skips those that aren't
 needed if you are using devpts.</para>
 
 </sect2>
diff --git a/chapter06/makedev-inst.xml b/chapter06/makedev-inst.xml
index 3b93899d7..d9ec9b784 100644
--- a/chapter06/makedev-inst.xml
+++ b/chapter06/makedev-inst.xml
@@ -1,8 +1,8 @@
 <sect2>
 <title>Creating devices</title>
 
-<para>(Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
-a directory for you to cd into, as the file only contains a script.)</para>
+<para>Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
+a directory for you to cd into, as the file only contains a script.</para>
 
 <para>Prepare for the creation of the device files by running the
 following commands:</para>
diff --git a/chapter06/man-inst.xml b/chapter06/man-inst.xml
index acd96c4a2..350228636 100644
--- a/chapter06/man-inst.xml
+++ b/chapter06/man-inst.xml
@@ -17,7 +17,7 @@ edit the man.conf file and add the <userinput>-c</userinput> argument
 to nroff.</para>
 
 <para>You may want to take a look at the man hint 
-at <ulink url="&hints-root;man.txt"/> which deals with formatting 
+at <ulink url="&hints-root;man.txt"/>, which deals with formatting 
 and compression issues for man pages.</para>
 
 </sect2>
diff --git a/chapter06/mountproc.xml b/chapter06/mountproc.xml
index 2eee7bf87..0993103ca 100644
--- a/chapter06/mountproc.xml
+++ b/chapter06/mountproc.xml
@@ -3,7 +3,7 @@
 <?dbhtml filename="proc.html" dir="chapter06"?>
 
 <para>In order for certain programs to function properly, the proc file
-system must be available within the chroot'ed environment.
+system must be available within the chroot environment.
 As a file system can be mounted as many times and in as many places
 as you like, it's not a problem that the proc file system is already
 mounted on your host system -- especially so because proc is a
@@ -21,7 +21,7 @@ command, such as these:</para>
 <blockquote><screen>warning: can't open /etc/fstab: No such file or directory
 not enough memory</screen></blockquote>
 
-<para>Ignore these, they're just caused due to the fact that the system
+<para>Ignore these, they're just due to the fact that the system
 isn't installed completely yet and some files are missing. The mount itself
 will be successful and that's all we care about at this point.</para>
 
diff --git a/chapter06/ncurses-exp.xml b/chapter06/ncurses-exp.xml
index ed43190e0..79b1303e4 100644
--- a/chapter06/ncurses-exp.xml
+++ b/chapter06/ncurses-exp.xml
@@ -9,11 +9,11 @@ constructions that are no longer valid in the new C++ standard.</para>
 shared ncurses library files.</para>
 
 <para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
-executable.  Ncurses install routine doesn't set the permissions
+executable. Ncurses's install routine doesn't set the permissions
 properly so we do it manually instead.</para>
 
 <para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some
-programs try to link using -lcurses instead of -lncurses.  This symlink
+programs try to link using -lcurses instead of -lncurses. This symlink
 ensures that such programs will link without errors.</para>
 
 </sect2>
diff --git a/chapter06/nettools-inst.xml b/chapter06/nettools-inst.xml
index c1f671f51..2a00423bf 100644
--- a/chapter06/nettools-inst.xml
+++ b/chapter06/nettools-inst.xml
@@ -14,7 +14,7 @@ make update</userinput></screen></para>
 
 <para>If you don't know what to answer to all the questions asked during
 the <userinput>make</userinput> phase, then just accept the defaults, which
-will be just in fine in the majority of the cases. What you are asked here
+will be just fine in the majority of the cases. What you are asked here
 are a bunch of questions relating to the kind of network protocols that you
 have enabled in your kernel.</para>
 
diff --git a/chapter06/perl-inst.xml b/chapter06/perl-inst.xml
index 66b067ed2..eefcfc8cd 100644
--- a/chapter06/perl-inst.xml
+++ b/chapter06/perl-inst.xml
@@ -8,7 +8,7 @@ make &amp;&amp;
 make install</userinput></screen></para>
 
 <para>If you want more control over the way perl sets itself up to be
-build, you can run the interactive <userinput>Configure</userinput> script
+built, you can run the interactive <userinput>Configure</userinput> script
 and modify the way perl is built. If you think you can live with the
 (sensible) defaults perl auto-detects, then just use the commands listed
 above.</para>
diff --git a/chapter06/pwdgroup.xml b/chapter06/pwdgroup.xml
index f9c648b8c..0568c1e7b 100644
--- a/chapter06/pwdgroup.xml
+++ b/chapter06/pwdgroup.xml
@@ -35,8 +35,8 @@ audio:x:11:
 
 <para>The created groups aren't part of any standard -- they are the groups
 that the MAKEDEV script in the next section uses.
-Besides the group "root", the LSB recommends only a group "bin" with a GID
-of 1 to be present. All other group names and GIDs can be chosen freely by
+Besides the group "root", the LSB recommends only a group "bin", with a GID
+of 1, be present. All other group names and GIDs can be chosen freely by
 the user, as well-written packages don't depend on GID numbers but use the
 group's name.</para>