mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
You
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@333 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
9fffe5fee8
commit
ab8b3526fa
@ -40,7 +40,7 @@ desired for all directories. I haven't checked the FHS if they suggest
|
|||||||
default modes for certain directories, so I'll just change the modes for
|
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
|
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
|
0750 for the $LFS/root directory. This is to make sure that not just
|
||||||
everybody can enter the /root directory (the same you would do with
|
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
|
/home/username directories). The second change is a mode 1777 for the tmp
|
||||||
directories. This way every user can write stuff to the /tmp directory if
|
directories. This way every user can write stuff to the /tmp directory if
|
||||||
they need to. The sticky (1) bit makes sure users can't delete other
|
they need to. The sticky (1) bit makes sure users can't delete other
|
||||||
@ -57,9 +57,9 @@ such a way that every body (owner, group, world) can write to that directory.
|
|||||||
</literallayout></blockquote>
|
</literallayout></blockquote>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Now that the directories are created, copy the source files you have
|
Now that the directories are created, copy the source files that were
|
||||||
downloaded in chapter 3 to some subdirectory under $LFS/usr/src (you will
|
downloaded in chapter 3 to some subdirectory under $LFS/usr/src (this
|
||||||
need to create this subdirectory yourself).
|
directory needs to be created yet).
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
@ -3,12 +3,13 @@
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
Once the partition is created, we have to create a new file system on
|
Once the partition is created, we have to create a new file system on
|
||||||
that partition. If you want to create an ext2 file system, use the mke2fs
|
that partition. To create an ext2 file system, the mke2fs command is the
|
||||||
command. If you want to create a reiser file system, use the mkreiserfs
|
correct choice. To create a reiser file system, the mkreiserfs command
|
||||||
command. If you want to create a different kind of file system, use the
|
should be used. To create a different kind of file system, the
|
||||||
appropriate command. Enter the new partition as the only option to the
|
appropriate command needs to be executed. The new partition used
|
||||||
command and the file system will be created. If your partition is hda2
|
as the only option to the
|
||||||
and you want ext2 you would run:
|
command and the file system will be created. If the partition is hda2
|
||||||
|
and ext2 is to be creaed, the user would run:
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<blockquote><literallayout>
|
<blockquote><literallayout>
|
||||||
@ -18,7 +19,7 @@ and you want ext2 you would run:
|
|||||||
</literallayout></blockquote>
|
</literallayout></blockquote>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
If you want reiserfs you would run:
|
To use reiserfs the user would run:
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<blockquote><literallayout>
|
<blockquote><literallayout>
|
||||||
|
@ -4,18 +4,19 @@
|
|||||||
<para>
|
<para>
|
||||||
Before we can build our new Linux system, we need to have an empty Linux
|
Before we can build our new Linux system, we need to have an empty Linux
|
||||||
partition on which we can build our new system. I recommend a partition size
|
partition on which we can build our new system. I recommend a partition size
|
||||||
of around 750 MB. This gives you enough space to store all the tarballs and
|
of around 750 MB. This gives enough space to store all the tarballs and
|
||||||
to compile all packages without worrying running out of the necessary
|
to compile all packages without worrying running out of the necessary
|
||||||
temporary disk space. If you already have a Linux Native partition available,
|
temporary disk space. If a Linux Native partition is already available,
|
||||||
you can skip this subsection.
|
this subsection can be skipped.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Start the cfdisk program (or another fdisk like program you prefer) with the
|
The cfdisk program (or another fdisk like program the user prefers) is
|
||||||
appropriate hard disk as the option (like /dev/hda if you want to create a
|
started with the
|
||||||
new partition on the primary master IDE disk). Create a Linux Native
|
appropriate hard disk as the option (like /dev/hda if he wants to create a
|
||||||
partition, write the partition table and exit the cfdisk program. Remember
|
new partition on the primary master IDE disk). He creates a Linux Native
|
||||||
what your new partition's designation is. It could be something
|
partition, writes the partition table and exits the cfdisk program.
|
||||||
|
The new partition's designation should be remembered. It could be something
|
||||||
like hda11 (as it is in my case). This newly created partition will be
|
like hda11 (as it is in my case). This newly created partition will be
|
||||||
referred to as the LFS partition in this book.
|
referred to as the LFS partition in this book.
|
||||||
</para>
|
</para>
|
||||||
|
@ -4,11 +4,12 @@
|
|||||||
<para>
|
<para>
|
||||||
Now that we have created the ext2 file system, it is ready for use. All we have
|
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
|
to do to be able to access it (as in reading from and writing date to it) is
|
||||||
mounting it. If you mount it under /mnt/lfs, you can access this partition
|
mounting it. If it is mounted under /mnt/lfs, this partition can be accessed
|
||||||
by going to the /mnt/lfs directory and then do whatever you need to do. This
|
by going to the /mnt/lfs directory and then doing whatever needed to do. This
|
||||||
book will assume that you have mounted the partition on a subdirectory
|
book will assume that the partition was mounted on a subdirectory
|
||||||
under /mnt. It doesn't matter which directory you choose, just make sure
|
under /mnt. It doesn't matter which directory is chosen, the user just has
|
||||||
you remember what you chose.
|
to make sure
|
||||||
|
that he remembers what he chose.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -32,16 +33,15 @@ Now mount the LFS partition by running:
|
|||||||
</literallayout></blockquote>
|
</literallayout></blockquote>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Replace <quote>xxx</quote> by your partition's designation.
|
Replace <quote>xxx</quote> by the partition's designation.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This directory (/mnt/lfs) is the $LFS variable you have read about earlier.
|
This directory (/mnt/lfs) is the $LFS variable I have written about earlier.
|
||||||
So if you read somewhere to "cp inittab $LFS/etc" you actually will type
|
So if the user somewhere reads to "cp inittab $LFS/etc" he actually will type
|
||||||
<quote>cp inittab /mnt/lfs/etc</quote>. Or if you want to use the $LFS
|
<quote>cp inittab /mnt/lfs/etc</quote>. Or if he wants to use the $LFS
|
||||||
environment variable, execute <userinput>export LFS=/mnt/lfs</userinput>
|
environment variable, <userinput>export LFS=/mnt/lfs</userinput> has to be
|
||||||
now.
|
executed now. </para>
|
||||||
</para>
|
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user