Context Navigation

-              rf50aec7
+              ra2cd10f
 <sect1 id="ch06-changingowner">
 <title>Changing ownership of the LFS partition</title>
+<title>Changing ownership</title>
 <?dbhtml filename="changingowner.html" dir="chapter06"?>
 <para>Now we're in chroot, it is a good time to change the ownership of
 all files and directories that were installed in chapter 5 back to root.
 Run the following commands to do so:</para>
+<para>Now we're in chroot, it is time to change the ownership of
+the files and directories that were installed in chapter 5 to root.
+Run the following command to do so:</para>
 <para><screen><userinput>chown -R 0:0 /</userinput></screen></para>
 <para>This command will change the ownership of the root partition to
 root. 0:0 is used instead of the usual root:root, because the username
 root can't be resolved because glibc is not yet installed.</para>
+<para>This command changes the ownership of the root partition to
+root. The command uses 0:0 instead of root:root, because the user name
+"root" can't be resolved, as glibc is not installed yet.</para>
 </sect1>

chapter06/chroot.xml

rf50aec7	ra2cd10f
12	12	this point on there's no need to use the $LFS variable anymore, because
13	13	everything a user does will be restricted to the LFS partition (since / is
14		actually /mnt/lfs but the shell doesn't know that).</para>
	14	actually /mnt/lfs, but the shell doesn't know that).</para>
15	15
16	16	<para><screen>&c6-chrootcmd;</screen></para>

chapter06/config-shadowpwd.xml

-              rf50aec7
+              ra2cd10f
 <sect2><title>Configuring Shadow Password Suite</title>
 <para>This package contains the utilities to modify user's passwords, add new
 users/groups, delete users/groups and more. We're not going to explain
 what 'password shadowing' means. All about that can be read in the doc/HOWTO
+<para>This package contains utilities to modify users's passwords, add
+or delete users and groups, and the like. We're not going to explain
+what 'password shadowing' means. A full explanation can be found in the doc/HOWTO
 file within the unpacked shadow password suite's source tree. There's one
 thing you should keep in mind, if you decide to use shadow support, that
 programs that need to verify passwords (examples are xdm, ftp daemons,
 pop3 daemons, etc) need to be 'shadow-compliant', e.g. they need to
+thing to keep in mind if you decide to use shadow support: that
+programs that need to verify passwords (for example xdm, ftp daemons,
+pop3 daemons) need to be 'shadow-compliant', that is they need to
 be able to work with shadow'ed passwords.</para>

chapter06/config-vim.xml

-              rf50aec7
+              ra2cd10f
 <sect2><title>Configuring Vim</title>
 <para>By default Vim runs in vi compatible mode. Some people might like this,
+<para>By default vim runs in vi compatible mode. Some people might like this,
 but we have a high preference to run vim in vim mode (else we wouldn't
 have included Vim in this book but the original Vi). Create the
+have included vim in this book, but the original vi). Create the
 <filename>/root/.vimrc</filename> by running the following:</para>

chapter06/creatingdirs.xml

-              rf50aec7
+              ra2cd10f
 desired for all directories. The first change is a mode 0750 for the
 /root directory. This is to make sure that not just everybody can
 enter the /root directory (the same a user would do with /home/username
 directories). The second change is a mode 1777 for the tmp
 directories. This way, any user can write data to the /tmp or /var/tmp
 directory but cannot remove another user's files (the latter is caused
 by the so-called "sticky bit" - bit 1 of the 1777 bit mask).</para>
+enter the /root directory (the same a user would do with his /home/username
+directory). The second change is a mode 1777 for the tmp
+directories. In this way any user can write to the /tmp and /var/tmp
+directories, but cannot remove other users's files from them (the latter is prohibited
+by the so-called "sticky bit" -- bit 1 in the 1777 bit mask).</para>
 <para><screen><userinput>chmod 0750 /root &amp;&amp;

chapter06/glibc-exp.xml

-              rf50aec7
+              ra2cd10f
 start a new bash shell which will replace the current shell. This is
 done to get rid of the "I have no name!" message in the command
+prompt, which was caused by bash's inability to resolve a userid to
+a username (which in turn was caused by the missing Glibc
+installation).</para>
+prompt, which was caused by bash's inability to resolve a user ID to
+a user name (which in turn was caused by the absence of Glibc).</para>
 </sect2>

chapter06/kernel-exp-headers.xml

rf50aec7	ra2cd10f
2	2	<title>Why we copy the kernel headers and don't symlink them</title>
3	3
4		<para>In the past, it was common practice for people to symlink the
	4	<para>In the past it was common practice for people to symlink the
5	5	/usr/include/linux and asm directories to /usr/src/linux/include/linux
6	6	and asm respectively. This is a <emphasis>bad</emphasis> idea as

chapter06/makedev-exp.xml

-              rf50aec7
+              ra2cd10f
 <title>Command explanations</title>
 <para><userinput>./MAKEDEV -v generic:</userinput> This creates generic
 devices. Normally, these devices are all the devices you need. It's possible
+<para><userinput>./MAKEDEV -v generic:</userinput> This creates a whole
+bunch of generic devices. Normally, these are all the devices you need. It's possible
 that you are missing some special devices that are needed for your hardware
 configuration. Create them with ./MAKEDEV -v &lt;device&gt;.
 The <userinput>generic-nopty</userinput> option does a similar job but skips
+The <userinput>generic-nopty</userinput> option does a similar job, but skips
 some devices which are not needed if you are using devpts.</para>

chapter06/makedev-inst.xml

-              rf50aec7
+              ra2cd10f
 set of devices which you don't require.</para>
 <para>MAKEDEV will create hda[1-20] to hdh[1-20] and such but keep in mind
 that you may not be able to use all of those devices due to kernel
 limitations regarding the max. number of partitions.</para>
+<para>MAKEDEV will create hda[1-20] to hdh[1-20] and such, but keep in mind
+that you may not be able to use all of these devices due to kernel
+limits on the maximum number of partitions.</para>
 </sect2>

chapter06/nettools-inst.xml

-              rf50aec7
+              ra2cd10f
 with the most common protocols such as TCP, PPP and a bunch of others. You
 still need to actually enable these protocols in the kernel. What you do
 here is merely telling the programs to be able to use those protocols but
 it's up to the kernel to make it available to the system.</para>
+here is merely telling the programs to be able to use those protocols, but
+it's up to the kernel to make them available to the system.</para>
 </sect2>

chapter06/psmisc-inst.xml

-              rf50aec7
+              ra2cd10f
 <para>Psmisc installs the
 <filename>/usr/share/man/man1/pidof.1</filename> man page, but Psmisc's
 pidof program isn't installed by default. Generally that isn't a problem
 because we install the sysvinit package later on which provides us with
+pidof program isn't installed by default. Generally this isn't a problem,
+because we install the Sysvinit package later on which provides
 a better pidof program.</para>
 <para>It's up to you now to decide if you are going to use the sysvinit
+<para>It's up to you now to decide if you are going to use the Sysvinit
 package which provides a pidof program, or not. If you are going to, you
 should remove Psmisc's pidof man page by running:</para>
 …
 <para><screen><userinput>rm /usr/share/man/man1/pidof.1</userinput></screen></para>
 <para>If you're not going to use sysvinit, you should complete this
+<para>If you're not going to use Sysvinit, you should complete this
 package's installation by creating the <filename>/bin/pidof</filename>
 symlink by running:</para>

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

Context Navigation

Changeset a2cd10f for chapter06

Legend:

Download in other formats: