mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-19 03:39:20 +01:00
Applied Billy's grammatical patch.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2317 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
b8b390a5c1
commit
91b45adcd6
@ -2,10 +2,10 @@
|
|||||||
<title>blfs-book</title>
|
<title>blfs-book</title>
|
||||||
|
|
||||||
<para>The blfs-book list is used for coordinating
|
<para>The blfs-book list is used for coordinating
|
||||||
the BLFS Book's maintenance.
|
the BLFS book's maintenance.
|
||||||
Traffic on it is mostly Bugzilla and CVS commit messages.
|
Traffic on it is mostly Bugzilla and CVS commit messages.
|
||||||
It is important that all development discussion
|
It is important that all development discussion
|
||||||
of interest to the Book's users take place on blfs-dev, not here.</para>
|
of interest to the book's users take place on blfs-dev, not here.</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<sect2>
|
<sect2>
|
||||||
<title>blfs-dev</title>
|
<title>blfs-dev</title>
|
||||||
|
|
||||||
<para>The blfs-dev list is for discussion of BLFS Book development.</para>
|
<para>The blfs-dev list is for discussion of BLFS book development.</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
@ -50,7 +50,7 @@ computer normally.</para>
|
|||||||
|
|
||||||
<para>When all the software from Chapter 6 is installed, Chapters 7, 8 and 9
|
<para>When all the software from Chapter 6 is installed, Chapters 7, 8 and 9
|
||||||
will help us finalize our installation. We will set up our boot
|
will help us finalize our installation. We will set up our boot
|
||||||
scripts in Chapter 7. In Chapter 8 we will build our final linux kernel and
|
scripts in Chapter 7. In Chapter 8 we will build our final Linux kernel and
|
||||||
set up the Linux boot loader. Chapter 9 has some pointers to help you after
|
set up the Linux boot loader. Chapter 9 has some pointers to help you after
|
||||||
you finish the book. Then finally, you reboot your system and boot into your
|
you finish the book. Then finally, you reboot your system and boot into your
|
||||||
new LFS system, and start to really use it.</para>
|
new LFS system, and start to really use it.</para>
|
||||||
|
@ -1,10 +1,10 @@
|
|||||||
<sect2>
|
<sect2>
|
||||||
<title>lfs-book</title>
|
<title>lfs-book</title>
|
||||||
|
|
||||||
<para>The lfs-book list is used for coordinating the LFS Book's maintenance.
|
<para>The lfs-book list is used for coordinating the LFS book's maintenance.
|
||||||
Traffic on it is mostly Bugzilla and CVS commit messages.
|
Traffic on it is mostly Bugzilla and CVS commit messages.
|
||||||
It is important that all development discussion
|
It is important that all development discussion
|
||||||
of interest to the Book's users take place on lfs-dev, not here.</para>
|
of interest to the book's users take place on lfs-dev, not here.</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
<sect2>
|
<sect2>
|
||||||
<title>lfs-dev</title>
|
<title>lfs-dev</title>
|
||||||
|
|
||||||
<para>The lfs-dev list is for discussion of LFS Book development.</para>
|
<para>The lfs-dev list is for discussion of LFS book development.</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
@ -34,7 +34,7 @@ than likely result in all kinds of compile time problems.</para>
|
|||||||
|
|
||||||
<para><screen><userinput>make</userinput></screen></para>
|
<para><screen><userinput>make</userinput></screen></para>
|
||||||
|
|
||||||
<para>And finsh off installing the package:</para>
|
<para>And finish off installing the package:</para>
|
||||||
|
|
||||||
<para><screen><userinput>make install</userinput></screen></para>
|
<para><screen><userinput>make install</userinput></screen></para>
|
||||||
|
|
||||||
|
@ -7,9 +7,9 @@ file within the unpacked shadow password suite's source tree. There's one
|
|||||||
thing to keep in mind if you decide to use shadow support: that
|
thing to keep in mind if you decide to use shadow support: that
|
||||||
programs that need to verify passwords (for example xdm, ftp daemons,
|
programs that need to verify passwords (for example xdm, ftp daemons,
|
||||||
pop3 daemons) need to be 'shadow-compliant', that is they need to
|
pop3 daemons) need to be 'shadow-compliant', that is they need to
|
||||||
be able to work with shadow'ed passwords.</para>
|
be able to work with shadowed passwords.</para>
|
||||||
|
|
||||||
<para>To enable shadow'ed passwords, run the following command:</para>
|
<para>To enable shadowed passwords, run the following command:</para>
|
||||||
|
|
||||||
<para><screen><userinput>/usr/sbin/pwconv</userinput></screen></para>
|
<para><screen><userinput>/usr/sbin/pwconv</userinput></screen></para>
|
||||||
|
|
||||||
|
@ -2,11 +2,11 @@
|
|||||||
<title>Command explanations</title>
|
<title>Command explanations</title>
|
||||||
|
|
||||||
<para><userinput>--enable-threads=posix:</userinput> This enables C++
|
<para><userinput>--enable-threads=posix:</userinput> This enables C++
|
||||||
exception handling for multithreaded code.</para>
|
exception handling for multi-threaded code.</para>
|
||||||
|
|
||||||
<para><userinput>--enable-__cxa_atexit:</userinput> This option will result
|
<para><userinput>--enable-__cxa_atexit:</userinput> This option will result
|
||||||
in C++ shared libraries and C++ programs that are interoperable with other
|
in C++ shared libraries and C++ programs that are interoperable with other
|
||||||
linux distributions.</para>
|
Linux distributions.</para>
|
||||||
|
|
||||||
<para><userinput>--enable-clocale=gnu:</userinput> There is a risk that
|
<para><userinput>--enable-clocale=gnu:</userinput> There is a risk that
|
||||||
some people will build ABI incompatible C++ libraries if they didn't install
|
some people will build ABI incompatible C++ libraries if they didn't install
|
||||||
|
@ -4,8 +4,8 @@
|
|||||||
|
|
||||||
<!ENTITY book SYSTEM "book/book.xml">
|
<!ENTITY book SYSTEM "book/book.xml">
|
||||||
|
|
||||||
<!ENTITY version "20030111">
|
<!ENTITY version "20030113">
|
||||||
<!ENTITY releasedate "January 11th, 2003">
|
<!ENTITY releasedate "January 13th, 2003">
|
||||||
|
|
||||||
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
|
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
|
||||||
<!ENTITY http-root "http://ftp.linuxfromscratch.org">
|
<!ENTITY http-root "http://ftp.linuxfromscratch.org">
|
||||||
|
@ -4,7 +4,7 @@
|
|||||||
|
|
||||||
<para>If you do not wish to build your own Linux system from scratch, then
|
<para>If you do not wish to build your own Linux system from scratch, then
|
||||||
you probably don't want to read this book. Our goal is to build a complete
|
you probably don't want to read this book. Our goal is to build a complete
|
||||||
and useable foundation system. If you only want to know what happens while
|
and usable foundation system. If you only want to know what happens while
|
||||||
your computer boots, then we recommend the
|
your computer boots, then we recommend the
|
||||||
<quote>From Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare
|
<quote>From Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare
|
||||||
system which is similar to that of this book, but it focuses strictly on
|
system which is similar to that of this book, but it focuses strictly on
|
||||||
|
@ -36,7 +36,7 @@ other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
|
|||||||
This allows you to review it, to omit unwanted ingredients, and to
|
This allows you to review it, to omit unwanted ingredients, and to
|
||||||
add your own ingredients which enhance the flavor of your burger. When you
|
add your own ingredients which enhance the flavor of your burger. When you
|
||||||
are satisfied with the recipe, you go on to preparing it. You make it just
|
are satisfied with the recipe, you go on to preparing it. You make it just
|
||||||
the way you like it: broil it, bake it, deep-fry it, barbeque it, or eat it
|
the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
|
||||||
tar-tar (raw).</para>
|
tar-tar (raw).</para>
|
||||||
|
|
||||||
<para>Another analogy that we can use is that of comparing LFS with a
|
<para>Another analogy that we can use is that of comparing LFS with a
|
||||||
|
Loading…
Reference in New Issue
Block a user