diff options
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/changingowner.xml | 14 | ||||
| -rw-r--r-- | chapter06/chroot.xml | 2 | ||||
| -rw-r--r-- | chapter06/config-shadowpwd.xml | 12 | ||||
| -rw-r--r-- | chapter06/config-vim.xml | 4 | ||||
| -rw-r--r-- | chapter06/creatingdirs.xml | 10 | ||||
| -rw-r--r-- | chapter06/glibc-exp.xml | 5 | ||||
| -rw-r--r-- | chapter06/kernel-exp-headers.xml | 2 | ||||
| -rw-r--r-- | chapter06/makedev-exp.xml | 6 | ||||
| -rw-r--r-- | chapter06/makedev-inst.xml | 6 | ||||
| -rw-r--r-- | chapter06/nettools-inst.xml | 4 | ||||
| -rw-r--r-- | chapter06/psmisc-inst.xml | 8 |
11 files changed, 36 insertions, 37 deletions
diff --git a/chapter06/changingowner.xml b/chapter06/changingowner.xml index 092bf073e..f0bdee09e 100644 --- a/chapter06/changingowner.xml +++ b/chapter06/changingowner.xml @@ -1,16 +1,16 @@ <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> diff --git a/chapter06/chroot.xml b/chapter06/chroot.xml index 43eb646d9..b9f20b3f8 100644 --- a/chapter06/chroot.xml +++ b/chapter06/chroot.xml @@ -11,7 +11,7 @@ command.</para> <para>Enter the following commands to enter the chroot'ed environment. From this point on there's no need to use the $LFS variable anymore, because everything a user does will be restricted to the LFS partition (since / is -actually /mnt/lfs but the shell doesn't know that).</para> +actually /mnt/lfs, but the shell doesn't know that).</para> <para><screen>&c6-chrootcmd;</screen></para> diff --git a/chapter06/config-shadowpwd.xml b/chapter06/config-shadowpwd.xml index 6c9c3d876..4f0e84e61 100644 --- a/chapter06/config-shadowpwd.xml +++ b/chapter06/config-shadowpwd.xml @@ -1,12 +1,12 @@ <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> <para>To enable shadow'ed passwords, run the following command:</para> diff --git a/chapter06/config-vim.xml b/chapter06/config-vim.xml index ee4124a2f..e750963d6 100644 --- a/chapter06/config-vim.xml +++ b/chapter06/config-vim.xml @@ -1,8 +1,8 @@ <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> <para><screen><userinput>cat > /root/.vimrc << "EOF"</userinput> diff --git a/chapter06/creatingdirs.xml b/chapter06/creatingdirs.xml index 09b94e5f3..1eb8a5d2c 100644 --- a/chapter06/creatingdirs.xml +++ b/chapter06/creatingdirs.xml @@ -26,11 +26,11 @@ ln -s ../var/tmp /usr</userinput></screen></para> <para>Normally, directories are created with permission mode 755, which isn't 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 && chmod 1777 /tmp /var/tmp</userinput></screen></para> diff --git a/chapter06/glibc-exp.xml b/chapter06/glibc-exp.xml index 6efbae47a..c3e474308 100644 --- a/chapter06/glibc-exp.xml +++ b/chapter06/glibc-exp.xml @@ -36,9 +36,8 @@ been installed yet.</para> <para><userinput>exec /bin/bash:</userinput>This command will 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> diff --git a/chapter06/kernel-exp-headers.xml b/chapter06/kernel-exp-headers.xml index de1256f3c..525fe0f6b 100644 --- a/chapter06/kernel-exp-headers.xml +++ b/chapter06/kernel-exp-headers.xml @@ -1,7 +1,7 @@ <sect2> <title>Why we copy the kernel headers and don't symlink them</title> -<para>In the past, it was common practice for people to symlink the +<para>In the past it was common practice for people to symlink the /usr/include/linux and asm directories to /usr/src/linux/include/linux and asm respectively. This is a <emphasis>bad</emphasis> idea as this extract from a post by Linus Torvalds to the Linux Kernel diff --git a/chapter06/makedev-exp.xml b/chapter06/makedev-exp.xml index 377fc42f9..95e0242d0 100644 --- a/chapter06/makedev-exp.xml +++ b/chapter06/makedev-exp.xml @@ -1,11 +1,11 @@ <sect2> <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 <device>. -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> </sect2> diff --git a/chapter06/makedev-inst.xml b/chapter06/makedev-inst.xml index 6797a057d..c8654578c 100644 --- a/chapter06/makedev-inst.xml +++ b/chapter06/makedev-inst.xml @@ -26,9 +26,9 @@ ensure you have the devices you need. If you are sure you are going to use devpts however, the other command makes sure that you don't create a 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> diff --git a/chapter06/nettools-inst.xml b/chapter06/nettools-inst.xml index 585fa4f05..c1f671f51 100644 --- a/chapter06/nettools-inst.xml +++ b/chapter06/nettools-inst.xml @@ -21,8 +21,8 @@ have enabled in your kernel.</para> <para>The default answers will enable the tools from this package to work 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> diff --git a/chapter06/psmisc-inst.xml b/chapter06/psmisc-inst.xml index 32193ace9..a349a4e9b 100644 --- a/chapter06/psmisc-inst.xml +++ b/chapter06/psmisc-inst.xml @@ -9,17 +9,17 @@ make install</userinput></screen></para> <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> |