gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-01-31 11:21:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

some fixes related to removal from ch6

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1904 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Mark Hymers 2002-05-26 01:07:46 +00:00
parent cb4481bd35
commit 24bb762288
5 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/changelog.xml
View File

@ -27,6 +27,10 @@
</para></listitem>
<listitem><para>May 25th, 2002 [markh]: Chapter 6 - Some minor
corrections dealing with removing the $LFS variable where it isn't
wanted.</para></listitem>
<listitem><para>May 23rd, 2002 [gerard]: Implemented the
keep_chap5_and_chap6_sep lfs-hint. Highlights of the change: added
findutils and util-linux to chapter 5, installed everything from chapter 5

4
chapter06/chroot.xml
View File

@ -23,8 +23,8 @@ present, such as CFLAGS or CXXFLAGS, you need to set them again.</para>
install all the basic system software. You have to make sure all the
following commands in this and following chapters are run from within the
chroot'ed environment. If you ever leave this environment for any reason
(when rebooting for example) please remember to mount $LFS/proc
again and re-enter chroot before continuing with the
(when rebooting for example) you must remember to enter chroot and mount
$LFS/proc again (as will be discussed later) before continuing with the
book.</para>
<para>Note that the bash prompt will contain "I have no name!" This is

4
chapter06/creatingdirs.xml
View File

@ -25,14 +25,14 @@ 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
$LFS/root directory. This is to make sure that not just everybody can
/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>
<para><screen><userinput>cd $LFS &amp;&amp;
<para><screen><userinput>cd / &amp;&amp;
chmod 0750 root &amp;&amp;
chmod 1777 tmp var/tmp</userinput></screen></para>

12
chapter06/kernel-exp.xml
View File

@ -17,16 +17,16 @@ after untarring.</para>
<filename>include/linux/version.h</filename>, as well as the <filename
class="symlink">include/asm</filename> symlink.</para>
<para><userinput>mkdir $LFS/usr/include/asm</userinput>
and <userinput>cp include/asm/* $LFS/usr/include/asm</userinput>:
<para><userinput>mkdir /usr/include/asm</userinput>
and <userinput>cp include/asm/* /usr/include/asm</userinput>:
This copies the platform-specific assembler kernel header files to
<filename>$LFS/usr/include/asm</filename></para>
<filename>/usr/include/asm</filename></para>
<para><userinput>cp -R include/linux $LFS/usr/include</userinput>:
<para><userinput>cp -R include/linux /usr/include</userinput>:
This command copies the cross-platform kernel header files to
<filename>$LFS/usr/include</filename></para>
<filename>/usr/include</filename></para>
<para><userinput>touch $LFS/usr/include/linux/autoconf.h</userinput>: Some
<para><userinput>touch /usr/include/linux/autoconf.h</userinput>: Some
kernel header files include this <filename>autoconf.h</filename> file, but
outside the Linux source tree, that file has no meaning so we just create
an empty one so we don't get compile errors whenever it happens to be a

9
chapter06/mountproc.xml
View File

@ -7,14 +7,9 @@ system must be mounted and available from within the chroot'ed environment
as well. It's not a problem to mount the proc file system (or any other
file system for that matter) twice or even more than that.</para>
<para>If you're still logged in as user "lfs", you should log out and log
in again as user root. The reason for this is simple: only root is allowed
to mount filesystems and to run chroot.</para>
<para>The proc file system is mounted under $LFS/proc by running the
following command. We'll also chown it to user root/group root while we're
at it (the rest of the filesystem is chown'ed to root:root in a minute when
we start with chapter 6).</para>
following command. Note that we don't use the $LFS variable because we
are now in chroot.</para>
<para><screen><userinput>mount proc /proc -t proc</userinput></screen></para>