gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-05 22:04:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Text update

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@358 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-03-23 03:13:31 +00:00
parent 0375b34d45
commit 728ea56c70
3 changed files with 32 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
chapter03/creatingdirs.xml
View File

@ -2,10 +2,10 @@
<title>Creating directories</title>
<para>
Let's create the directory tree on the LFS partition according to the FHS
Let's create the directory tree on the LFS partition based on the FHS
standard, which can be found at <ulink
url="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</ulink>.
Issuing the following commands will create the necessary directories:
Issuing the following commands will create a default directory layout:
</para>
<blockquote><literallayout>
@ -36,16 +36,15 @@ Issuing the following commands will create the necessary directories:
<para>
Normally, directories are created with permission mode 755, which isn't
desired for all directories. I haven't checked if the FHS suggests
default modes for certain directories, so I'll just change the modes for
a few directories that make sense to change. The first change is a mode
0750 for the $LFS/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 stuff to the /tmp directory when
needed. The sticky (1) bit makes sure users can't delete other
users' files which they normally can do, because the directory is set in
such a way that everybody (owner, group, world) can write to that directory.
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
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 directory when
needed. The sticky bit (the first bit in the 1777 mask) makes sure
users can't delete other users files which they normally can do,
because the directory is set in such a way that everybody (owner, group,
world) can write to that directory (the 777 in the bit mask)
</para>
<blockquote><literallayout>
@ -58,8 +57,8 @@ such a way that everybody (owner, group, world) can write to that directory.
<para>
Now that the directories are created, copy the source files that were
downloaded in chapter 3 to some subdirectory under $LFS/usr/src (this
directory still needs to be created yet).
downloaded in chapter 3 to some subdirectory under $LFS/usr/src (you
will need to create the desired directory yourself).
</para>
</sect1>

12
chapter03/creatingfs.xml
View File

@ -3,11 +3,11 @@
<para>
Once the partition is created, we have to create a new file system on
that partition. To create an ext2 file system, the mke2fs command is the
correct choice. To create a reiser file system, the mkreiserfs command
should be used. The new partition is used as the only option to the
command and the file system is created. If the partition is hda11
and ext2 is to be created, the user would run:
that partition. To create an ext2 file system, use the mke2fs command.
To create a reiser file system, the mkreiserfs command should be used.
The new partition is used as the only option to the command and the file
system is created. If the partition is hda11 and ext2 is to be created,
run the following:
</para>
<blockquote><literallayout>
@ -17,7 +17,7 @@ and ext2 is to be created, the user would run:
</literallayout></blockquote>
<para>
To create a reiser file system the user would run:
To create a reiser file system, run the following:
</para>
<blockquote><literallayout>

28
chapter03/mounting.xml
View File

@ -1,15 +1,14 @@
<sect1 id="ch04-mountingpart">
<sect1 id="ch04-mounting">
<title>Mounting the new partition</title>
<para>
Now that we have created the ext2 file system, it is ready for use. All we have
to do to be able to access it (as in reading from and writing date to it) is
mounting it. If it is mounted under /mnt/lfs, this partition can be accessed
by going to the /mnt/lfs directory and then doing whatever needed to do. This
book will assume that the partition was mounted on a subdirectory
under /mnt. It doesn't matter which directory is chosen, the user just has
to make sure
that he remembers what he chose.
Now that we have created a file system, it is ready for use. All we have
to do to be able to access it (as in reading data from and writing data to
it) is mounting it. If it is mounted under /mnt/lfs, this partition can
be accessed by going to the /mnt/lfs directory and then doing whatever
needed to do. This book will assume that the partition was mounted
under /mnt/lfs. It doesn't matter which directory is chosen, the
user just has to make sure that he remembers what he chose.
</para>
<para>
@ -33,15 +32,14 @@ Now mount the LFS partition by running:
</literallayout></blockquote>
<para>
Replace <quote>xxx</quote> by the partition's designation.
Replace <quote>xxx</quote> by the partition's designation (like hda11).
</para>
<para>
This directory (/mnt/lfs) is the $LFS variable I have written about earlier.
So if the user somewhere reads to "cp inittab $LFS/etc" he actually will type
<quote>cp inittab /mnt/lfs/etc</quote>. Or if he wants to use the $LFS
environment variable, <userinput>export LFS=/mnt/lfs</userinput> has to be
executed now. </para>
This directory (/mnt/lfs) is the $LFS variable you have read about earlier.
If you were planning to make use of the $LFS environment variable,
<userinput>export LFS=/mnt/lfs</userinput> has to be executed now.
</para>
</sect1>