Changeset afbe6d9
- Timestamp:
- 05/12/2005 10:07:33 PM (19 years ago)
- Branches:
- 6.1, 6.1.1
- Children:
- b9248a9
- Parents:
- e750af1
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
re750af1 rafbe6d9 13 13 mirrors via <ulink url="&lfs-root;"/>.</para> 14 14 15 <para>Below is a list of changes made since the previous release of the book ,16 first a summary, then a detailed log.</para>15 <para>Below is a list of changes made since the previous release of the book. 16 First a summary, then a detailed log.</para> 17 17 18 18 <itemizedlist> … … 84 84 </listitem> 85 85 86 <listitem><para>May 12th, 2005 [matt]: More wording and tagging improvements 87 (thanks to Peter Ennis and Tony Morgan)</para></listitem> 88 89 <listitem><para>May 12th, 2005 [matt]: Minor wording improvements (thanks to 90 Peter Ennis)</para></listitem> 91 86 92 <listitem><para>April 27th, 2005 [archaic]: Added a patch to fix 2 glibc 87 93 testsuite failures when the running kernel is 2.6.11.x.</para></listitem> … … 133 139 </listitem> 134 140 135 <listitem><para>April 4, 2005 [matt]: Fix E2fsprogs compile problem (Ken Moffat141 <listitem><para>April 4, 2005 [matt]: Fix e2fsprogs compile problem (Ken Moffat 136 142 & Greg Schafer)</para></listitem> 137 143 … … 193 199 </listitem> 194 200 195 <listitem><para>March 14, 2005 [jim]: Added /var/log/hotplugfor capturing201 <listitem><para>March 14, 2005 [jim]: Added <filename class="directory">/var/log/hotplug</filename> for capturing 196 202 of hotplug events. Added /lib/firmware for firmware loading with hotplug</para></listitem> 197 203 … … 239 245 </para></listitem> 240 246 241 <listitem><para>February 28, 2005 [matt]: Move /usr/bin/logger to /bin242 as the bootscripts need it there. Fixes bug 1035.</para>247 <listitem><para>February 28, 2005 [matt]: Move <filename>/usr/bin/logger</filename> 248 to <filename class="directory">/bin</filename> as the bootscripts need it there. Fixes bug 1035.</para> 243 249 </listitem> 244 250 … … 275 281 276 282 <listitem><para>February 19, 2005 [jeremy]: Added correction to chapter 5 277 glibc build to correctthe disabling of selinux functionality. Thanks to283 glibc build to fix the disabling of selinux functionality. Thanks to 278 284 Bobson on IRC (bobson@bobson.net) for pointing this out. Closes bugzilla 279 285 1034.</para></listitem> … … 360 366 from version 5.1.</para></listitem> 361 367 362 <listitem><para>December 20, 2004 [manuel]: Made Grub's configuration location368 <listitem><para>December 20, 2004 [manuel]: Made grub's configuration location 363 369 FHS compliant.</para></listitem> 364 370 -
chapter02/creatingfilesystem.xml
re750af1 rafbe6d9 10 10 <para>Now that a blank partition has been set up, the file system can 11 11 be created. The most widely-used system in the Linux world is the 12 second extended file system (ext2), but with thenewer high-capacity13 hard disks, thejournaling file systems are becoming increasingly14 popular. Here we will create an ext2 file system, butbuild12 second extended file system (ext2), but with newer high-capacity 13 hard disks, journaling file systems are becoming increasingly 14 popular. We will create an ext2 file system, however build 15 15 instructions for other file systems can be found at <ulink 16 16 url="&blfs-root;view/svn/postlfs/filesystems.html"><phrase … … 52 52 53 53 <para>If a swap partition was created, it will need to be initialized 54 as a swap partition too (also known as formatting, as described above 55 with <command>mke2fs</command>) by running the following. If you are using an existing 54 as a swap partition by using the command below. If you are using an existing 56 55 swap partition, there is no need to format it.</para> 57 56 -
chapter02/creatingpartition.xml
re750af1 rafbe6d9 8 8 <?dbhtml filename="creatingpartition.html"?> 9 9 10 <!--Edit Me-->11 10 <para>Like most other operating systems, LFS is usually installed on 12 a dedicated partition. If you have an empty partition or enough13 unpartitioned space on one of your hard disks to make one, using this 14 for your LFS installation is recommended.However, an LFS system (in11 a dedicated partition. The recommended approach to building an LFS 12 system is to use an available empty partition or, if you have enough 13 unpartitioned space, to create one. However, an LFS system (in 15 14 fact even multiple LFS systems) may also be installed on a partition 16 15 already occupied by another operating system and the different systems … … 20 19 explains how to implement this, whereas this book discusses the method of 21 20 using a fresh partition for the installation.</para> 22 <!--End Edit Me-->23 21 24 22 <para>A minimal system requires a partition of around 1.3 gigabytes … … 27 25 Linux system, additional software will probably be installed which 28 26 will require additional space (2 or 3 GB). The LFS system itself will 29 not take up this much space. A large portion of this required amount30 of space is to provide sufficient free temporary space. Compiling27 not take up this much room. A large portion of this requirement 28 is to provide sufficient free temporary storage. Compiling 31 29 packages can require a lot of disk space which will be reclaimed after 32 30 the package is installed.</para> … … 34 32 <para>Because there is not always enough Random Access Memory (RAM) 35 33 available for compilation processes, it is a good idea to use a small 36 disk partition as swap space. This spaceis used by the kernel to37 store seldom-used data to make room in memoryfor active processes.34 disk partition as swap space. This is used by the kernel to 35 store seldom-used data and leave more memory available for active processes. 38 36 The swap partition for an LFS system can be the same as the one used 39 by the host system, so another swap partition will not need to be40 created if your host system already has one setup.</para>37 by the host system, in which case it is not necessary to create another 38 one.</para> 41 39 42 40 <para>Start a disk partitioning program such as -
chapter05/glibc.xml
re750af1 rafbe6d9 145 145 importance, please see <xref linkend="ch-system-glibc" role="."/></para> 146 146 147 <para>In this chapter, some tests can be adversely effected by147 <para>In this chapter, some tests can be adversely affected by 148 148 existing tools or environmental issues on the host system. Glibc test 149 149 suite failures in this chapter are typically not worrisome. The Glibc -
chapter05/toolchaintechnotes.xml
re750af1 rafbe6d9 67 67 68 68 <listitem><para>Careful manipulation of <command>gcc</command>'s 69 <filename>specs</filename> file tell the compiler which target dynamic69 <filename>specs</filename> file tells the compiler which target dynamic 70 70 linker will be used</para></listitem> 71 71 </itemizedlist> … … 78 78 result in a subtly broken toolchain, where the impact of such breakage 79 79 might not show up until near the end of the build of an entire 80 distribution. A test suite failure will usually alert this error80 distribution. A test suite failure will usually highlight this error 81 81 before too much additional work is performed.</para> 82 82 -
general.ent
re750af1 rafbe6d9 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 <!ENTITY version "TESTING-20050 428">3 <!ENTITY releasedate " April 28, 2005">2 <!ENTITY version "TESTING-20050512"> 3 <!ENTITY releasedate "May 12, 2005"> 4 4 <!ENTITY milestone "6.1"> 5 5
Note:
See TracChangeset
for help on using the changeset viewer.