Changeset 0d84af1
- Timestamp:
- 12/28/2017 03:52:38 AM (6 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/parallelism, xry111/pip3, xry111/rust-wip-20221008
- Children:
- 25332b5
- Parents:
- 9fde3e9
- Files:
-
- 29 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/gcc-pass1.xml
r9fde3e9 r0d84af1 85 85 First we copy the files <filename>gcc/config/linux.h</filename>, 86 86 <filename>gcc/config/i386/linux.h</filename>, and 87 <filename>gcc/config/i368/linux64.h</filename> .to a file of87 <filename>gcc/config/i368/linux64.h</filename> to a file of 88 88 the same name but with an added suffix of <quote>.orig</quote>. Then the 89 89 first sed expression prepends <quote>/tools</quote> to every instance of … … 186 186 <term><parameter>--with-native-system-header-dir=/tools/include</parameter></term> 187 187 <listitem> 188 <para>By default GCC searches <filename>/usr/include</filename> for system 189 headers. In conjunction with the sysroot switch, this would translate normally 190 to <filename>$LFS/usr/include</filename>. However the headers that will be installed 191 in the next two sections will go to <filename>$LFS/tools/include</filename>. This 192 switch ensures that gcc will find them correctly. In the second pass of GCC, this 193 same switch will ensure that no headers from the host system are found.</para> 188 <para>By default GCC searches <filename>/usr/include</filename> for 189 system headers. In conjunction with the sysroot switch, this would 190 normally translate to <filename>$LFS/usr/include</filename>. However 191 the headers that will be installed in the next two sections will go 192 to <filename>$LFS/tools/include</filename>. This switch ensures that 193 gcc will find them correctly. In the second pass of GCC, this same 194 switch will ensure that no headers from the host system are 195 found.</para> 194 196 </listitem> 195 197 </varlistentry> -
chapter05/generalinstructions.xml
r9fde3e9 r0d84af1 49 49 <listitem> 50 50 51 <para>Finally, two lastimportant items must be emphasized:</para>51 <para>Finally, two important items must be emphasized:</para> 52 52 53 53 <important> -
chapter06/adjusting.xml
r9fde3e9 r0d84af1 111 111 steps to find out where the problem is and correct it. The most likely 112 112 reason is that something went wrong with the specs file adjustment. Any 113 issues will need to be resolved before continuing onwith the process.</para>113 issues will need to be resolved before continuing with the process.</para> 114 114 115 115 <para os="u">Once everything is working correctly, clean up the test files:</para> -
chapter06/bc.xml
r9fde3e9 r0d84af1 129 129 <term><command>bc</command></term> 130 130 <listitem> 131 <para> is acommand line calculator</para>131 <para>A command line calculator</para> 132 132 <indexterm zone="ch-system-bc bc"> 133 133 <primary sortas="b-bc">bc</primary> … … 139 139 <term><command>dc</command></term> 140 140 <listitem> 141 <para> is areverse-polish command line calculator</para>141 <para>A reverse-polish command line calculator</para> 142 142 <indexterm zone="ch-system-bc dc"> 143 143 <primary sortas="b-dc">dc</primary> -
chapter06/dbus.xml
r9fde3e9 r0d84af1 126 126 <term><command>dbus-cleanup-sockets</command></term> 127 127 <listitem> 128 <para> is used to clean up leftover sockets in a directory</para>128 <para>Used to clean up leftover sockets in a directory</para> 129 129 <indexterm zone="ch-system-dbus dbus-cleanup-sockets"> 130 130 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary> … … 136 136 <term><command>dbus-daemon</command></term> 137 137 <listitem> 138 <para> is the D-Bus message bus daemon</para>138 <para>The D-Bus message bus daemon</para> 139 139 <indexterm zone="ch-system-dbus dbus-daemon"> 140 140 <primary sortas="b-dbus-daemon">dbus-daemon</primary> … … 146 146 <term><command>dbus-launch</command></term> 147 147 <listitem> 148 <para> starts <command>dbus-daemon</command> from a shell148 <para>Starts <command>dbus-daemon</command> from a shell 149 149 script</para> 150 150 <indexterm zone="ch-system-dbus dbus-launch"> … … 157 157 <term><command>dbus-monitor</command></term> 158 158 <listitem> 159 <para> monitors messages passing through a D-Bus message bus</para>159 <para>Monitors messages passing through a D-Bus message bus</para> 160 160 <indexterm zone="ch-system-dbus dbus-monitor"> 161 161 <primary sortas="b-dbus-monitor">dbus-monitor</primary> … … 167 167 <term><command>dbus-run-session</command></term> 168 168 <listitem> 169 <para> starts a session bus instance of <command>dbus-daemon</command>169 <para>Starts a session bus instance of <command>dbus-daemon</command> 170 170 from a shell script and starts a specified program in that 171 171 session</para> … … 179 179 <term><command>dbus-send</command></term> 180 180 <listitem> 181 <para> sends a message to a D-Bus message bus</para>181 <para>Sends a message to a D-Bus message bus</para> 182 182 <indexterm zone="ch-system-dbus dbus-send"> 183 183 <primary sortas="b-dbus-send">dbus-send</primary> … … 189 189 <term><command>dbus-test-tool</command></term> 190 190 <listitem> 191 <para> is atool to help packages test192 <application>D-Bus</application> .</para>191 <para>A tool to help packages test 192 <application>D-Bus</application></para> 193 193 <indexterm zone="ch-system-dbus dbus-test-tool"> 194 194 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary> … … 201 201 <term><command>dbus-update-activation-environment</command></term> 202 202 <listitem> 203 <para> updates environment variables that will be set for204 <application>D-Bus</application> session services .</para>203 <para>Updates environment variables that will be set for 204 <application>D-Bus</application> session services</para> 205 205 <indexterm zone="ch-system-dbus dbus-update-activation-environment"> 206 206 <primary sortas="b-dbus-update-activation-environment">dbus-update-activation-environment</primary> … … 212 212 <term><command>dbus-uuidgen</command></term> 213 213 <listitem> 214 <para> generates a universally unique ID</para>214 <para>Generates a universally unique ID</para> 215 215 <indexterm zone="ch-system-dbus dbus-uuidgen"> 216 216 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary> … … 222 222 <term><filename class="libraryfile">libdbus-1</filename></term> 223 223 <listitem> 224 <para> contains API functions used to communicate with the D-Bus224 <para>Contains API functions used to communicate with the D-Bus 225 225 message bus</para> 226 226 <indexterm zone="ch-system-dbus libdbus-1"> -
chapter06/expat.xml
r9fde3e9 r0d84af1 92 92 <term><command>xmlwf </command></term> 93 93 <listitem> 94 <para> is a non-validating utility to check whether or not94 <para>Is a non-validating utility to check whether or not 95 95 XML documents are well formed</para> 96 96 <indexterm zone="ch-system-expat xmlwf"> … … 103 103 <term><filename class="libraryfile">libexpat</filename></term> 104 104 <listitem> 105 <para> contains API functions for parsing XML</para>105 <para>Contains API functions for parsing XML</para> 106 106 <indexterm zone="ch-system-expat libexpat"> 107 107 <primary sortas="c-libexpat">libexpat</primary> -
chapter06/gcc.xml
r9fde3e9 r0d84af1 220 220 different than the above, depending on your architecture.</para> 221 221 222 <!-- This appears to be obsolete 223 222 224 <note><para>As of version 4.3.0, GCC now unconditionally installs the 223 225 <filename>limits.h</filename> file into the private 224 226 <filename class="directory">include-fixed</filename> directory, and that 225 227 directory is required to be in place.</para></note> 228 --> 226 229 227 230 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" -
chapter06/glibc.xml
r9fde3e9 r0d84af1 51 51 of achieving a clean build.</para></note> 52 52 53 <para>Some of the Glibc programs use non-FHS compilant53 <para>Some of the Glibc programs use the non-FHS compilant 54 54 <filename class="directory">/var/db</filename> directory to store 55 55 their runtime data. Apply the following patch to make such programs … … 124 124 <term><parameter>--enable-stack-protector=strong</parameter></term> 125 125 <listitem> 126 <para>This option increases system security by adding a known canary 127 (a random integer) to the stack during a function preamble, and checks 128 it when the function returns. If it changed, there was a stack 129 overflow, and the program aborts.</para> 126 <para>This option increases system security by adding 127 extra code to check for buffer overflows, such as stack 128 smashing attacks.</para> 130 129 </listitem> 131 130 </varlistentry> … … 150 149 </important> 151 150 152 <para>Generally a few tests do not pass , but you can generally ignore153 a ny of the test failures listed below. Now test the build results:</para>151 <para>Generally a few tests do not pass. The test failures listed below 152 are usually safe to ignore.</para> 154 153 155 154 <screen><userinput remap="test">make check</userinput></screen> -
chapter06/introduction.xml
r9fde3e9 r0d84af1 69 69 70 70 <para>In the procedures in Chapter 6, we remove or disable installation of 71 most static libraries. In a few cases, especially glibc and gcc, the use 72 of static libraries remains essential to the general package building 73 process. Usually this is done by passing a 71 most static libraries. Usually this is done by passing a 74 72 <option>--disable-static</option> option to <command>configure</command>. 75 In other cases, alternate means are needed.</para> 73 In other cases, alternate means are needed. In a few cases, especially 74 glibc and gcc, the use of static libraries remains essential to the general 75 package building process. </para> 76 76 77 77 <para>For a more complete discussion of libraries, see the discussion -
chapter06/libcap.xml
r9fde3e9 r0d84af1 141 141 </varlistentry> 142 142 143 <varlistentry id="setcap"> 144 <term><command>setcap</command></term> 145 <listitem> 146 <para>Sets file capabilities</para> 147 <indexterm zone="ch-system-libcap setcap"> 148 <primary sortas="b-setcap">setcap</primary> 149 </indexterm> 150 </listitem> 151 </varlistentry> 152 143 153 <varlistentry id="libcap"> 144 154 <term><filename class="libraryfile">libcap</filename></term> … … 152 162 </varlistentry> 153 163 154 <varlistentry id="setcap">155 <term><command>setcap</command></term>156 <listitem>157 <para>Sets file capabilities</para>158 <indexterm zone="ch-system-libcap setcap">159 <primary sortas="b-setcap">setcap</primary>160 </indexterm>161 </listitem>162 </varlistentry>163 164 165 164 </variablelist> 166 165 -
chapter06/m4.xml
r9fde3e9 r0d84af1 79 79 <term><command>m4 </command></term> 80 80 <listitem> 81 <para> copies the given files while expanding the macros that they81 <para>Copies the given files while expanding the macros that they 82 82 contain [These macros are either built-in or user-defined and can 83 83 take any number of arguments. Besides performing macro expansion, -
chapter06/perl.xml
r9fde3e9 r0d84af1 243 243 <listitem> 244 244 <para>Shell script for examining installed Perl modules, 245 and can evencreate a tarball from an installed module</para>245 and can create a tarball from an installed module</para> 246 246 <indexterm zone="ch-system-perl instmodsh"> 247 247 <primary sortas="b-instmodsh">instmodsh</primary> -
chapter06/pkgconfig.xml
r9fde3e9 r0d84af1 107 107 <term><command>pkg-config </command></term> 108 108 <listitem> 109 <para> returns meta information for the specified library or package109 <para>Returns meta information for the specified library or package 110 110 </para> 111 111 <indexterm zone="ch-system-pkgconfig pkgconfig"> -
chapter06/procps.xml
r9fde3e9 r0d84af1 41 41 <title>Installation of Procps-ng</title> 42 42 43 <para> Now prepare procps-ng for compilation:</para>43 <para>Prepare procps-ng for compilation:</para> 44 44 45 45 <screen revision="sysv"><userinput remap="configure">./configure --prefix=/usr \ … … 194 194 <term><command>slabtop</command></term> 195 195 <listitem> 196 <para>Displays detailed kernel sla pcache information in real time</para>196 <para>Displays detailed kernel slab cache information in real time</para> 197 197 <indexterm zone="ch-system-procps slabtop"> 198 198 <primary sortas="b-slabtop">slabtop</primary> -
chapter06/readline.xml
r9fde3e9 r0d84af1 125 125 <term><filename class="libraryfile">libreadline</filename></term> 126 126 <listitem> 127 <para> Aids in the consistency of user interface across discrete128 programs that need to provide a command line interface</para>127 <para>Provides a set of commands for manipulating text entered in an 128 interactive session of a program.</para> 129 129 <indexterm zone="ch-system-readline libreadline"> 130 130 <primary sortas="c-libreadline">libreadline</primary> -
chapter06/shadow.xml
r9fde3e9 r0d84af1 77 77 </note> 78 78 79 <para>Make a minor change to make the default useradd consistent with the LFS80 groups file:</para>79 <para>Make a minor change to make the first group number generated 80 by useradd 1000:</para> 81 81 82 82 <screen><userinput remap="pre">sed -i 's/1000/999/' etc/useradd</userinput></screen> -
chapter06/systemd.xml
r9fde3e9 r0d84af1 124 124 125 125 <varlistentry> 126 <term><parameter>-Dldconfig=no</parameter></term> 127 <listitem> 128 <para>This switch prevents installation of a systemd 129 unit that runs <command>ldconfig</command> at 130 boot, making the boot time longer. Remove it if the 131 described feature is desired, even though it's not 132 useful for source distributions such as LFS.</para> 126 <term><parameter>-Dldconfig=false</parameter></term> 127 <listitem> 128 <para>This switch prevents installation of a systemd unit that runs 129 <command>ldconfig</command> at boot, which is not useful for source 130 distributions such as LFS and makes the boot time longer. Remove it 131 if the described feature is desired.</para> 133 132 </listitem> 134 133 </varlistentry> … … 159 158 <filename>/etc/group</filename> and 160 159 <filename>/etc/passwd</filename> files. Both files 161 were created earl yin this chapter.</para>160 were created earlier in this chapter.</para> 162 161 </listitem> 163 162 </varlistentry> … … 251 250 <term><command>bootctl</command></term> 252 251 <listitem> 253 <para> used to query the firmware and boot manager settings</para>252 <para>Used to query the firmware and boot manager settings</para> 254 253 <indexterm zone="ch-system-systemd bootctl"> 255 254 <primary sortas="b-bootctl">bootctl</primary> … … 307 306 <listitem> 308 307 <para>The first process to be started when the kernel has initialized 309 the hardware which takes over the boot process and starts all the310 proces es it is instructed to</para>308 the hardware which takes over the boot process and starts all 309 processes according to its configuration files</para> 311 310 <indexterm zone="ch-system-systemd init"> 312 311 <primary sortas="b-init">init</primary> … … 318 317 <term><command>journalctl</command></term> 319 318 <listitem> 320 <para>Used to query the contents of the systemd Journal</para>319 <para>Used to query the contents of the systemd journal</para> 321 320 <indexterm zone="ch-system-systemd journalctl"> 322 321 <primary sortas="b-journalctl">journalctl</primary> … … 559 558 <term><command>systemd-mount</command></term> 560 559 <listitem> 561 <para> is atool to temporarily mount or auto-mount a drive.</para>560 <para>A tool to temporarily mount or auto-mount a drive.</para> 562 561 <indexterm zone="ch-system-systemd systemd-mount"> 563 562 <primary sortas="b-systemd-mount">systemd-mount</primary> … … 633 632 <term><command>systemd-socket-activate</command></term> 634 633 <listitem> 635 <para> is atool to listen on socket devices and launch a process upon634 <para>A tool to listen on socket devices and launch a process upon 636 635 connection.</para> 637 636 <indexterm zone="ch-system-systemd systemd-socket-activate"> … … 689 688 <term><command>udevadm</command></term> 690 689 <listitem> 691 <para>Generic Udev administration tool: controls the udevd daemon,690 <para>Generic udev administration tool: controls the udevd daemon, 692 691 provides info from the Udev database, monitors uevents, waits for 693 uevents to finish, tests Udev configuration, and triggers uevents692 uevents to finish, tests udev configuration, and triggers uevents 694 693 for a given device</para> 695 694 <indexterm zone="ch-system-systemd udevadm"> … … 702 701 <term><filename class="libraryfile">libsystemd</filename></term> 703 702 <listitem> 704 <para> systemd utility library</para>703 <para>The main systemd utility library</para> 705 704 <indexterm zone="ch-system-systemd libsystemd"> 706 705 <primary sortas="c-libsystemd">libsystemd</primary> -
chapter06/util-linux.xml
r9fde3e9 r0d84af1 1125 1125 <listitem> 1126 1126 <para>A daemon used by the UUID library to generate time-based 1127 UUIDs in a secure and gu ranteed-unique fashion</para>1127 UUIDs in a secure and guaranteed-unique fashion</para> 1128 1128 <indexterm zone="ch-system-util-linux uuidd"> 1129 1129 <primary sortas="b-uuidd">uuidd</primary> -
chapter06/vim.xml
r9fde3e9 r0d84af1 71 71 <screen><userinput remap="test">make -j1 test &> vim-test.log</userinput></screen> 72 72 73 <para>However, this test suite outputs a lot of binary data to the screen, 74 which can cause issues with the settings of the current terminal. This can 75 be resolved by redirecting the output to a log file. A successful test 76 will result in the words "ALL DONE" at completion.</para> 73 <para>The test suite outputs a lot of binary data to the screen. This can 74 cause issues with the settings of the current terminal. The problem can be 75 avoided by redirecting the output to a log file as shown above. A 76 successful test will result in the words "ALL DONE" in the log file 77 at completion.</para> 77 78 78 79 <para>Install the package:</para> … … 273 274 <listitem> 274 275 <para>Edits two or three versions of a file with <command>vim</command> 275 and show differences</para>276 and shows differences</para> 276 277 <indexterm zone="ch-system-vim vimdiff"> 277 278 <primary sortas="b-vimdiff">vimdiff</primary> -
chapter07/clock.xml
r9fde3e9 r0d84af1 66 66 <screen role="nodump"><userinput>timedatectl set-timezone TIMEZONE</userinput></screen> 67 67 68 <para>You can get list of available time zones by running:</para>68 <para>You can get a list of available time zones by running:</para> 69 69 70 70 <screen role="nodump"><userinput>timedatectl list-timezones</userinput></screen> 71 71 72 <note><para>Please note that <command>timedatectl</command> command can72 <note><para>Please note that the <command>timedatectl</command> command can 73 73 be used only on a system booted with systemd.</para></note> 74 74 -
chapter07/consoled.xml
r9fde3e9 r0d84af1 87 87 <screen role="nodump"><userinput>localectl set-keymap MAP</userinput></screen> 88 88 89 <note><para>Please note that <command>localectl</command> command can90 be used 89 <note><para>Please note that the <command>localectl</command> command can 90 be used only on a system booted with systemd.</para></note> 91 91 92 92 <para>You can also use <command>localectl</command> utility with the … … 132 132 </variablelist> 133 133 134 <note><para>Using any of the parameters listed above requires 134 <note><para>Using any of the parameters listed above requires the 135 135 XKeyboard Config package from BLFS.</para></note> 136 136 -
chapter07/inputrc.xml
r9fde3e9 r0d84af1 16 16 17 17 <para>The <filename>inputrc</filename> file is the configuration file for 18 Readline library, which provides editing capabilities while the user is18 then Readline library, which provides editing capabilities while the user is 19 19 entering a line from the terminal. It works by tranlating keyboard inputs 20 20 into specific actions. Readline is used by Bash and most other shells as -
chapter07/locale.xml
r9fde3e9 r0d84af1 119 119 EOF</userinput></screen> 120 120 121 <para>Note that you can modify <filename>/etc/locale.conf</filename> with 122 systemd <command>localectl</command> utility. To use <command>localectl</command>123 for the example above, run:</para>121 <para>Note that you can modify <filename>/etc/locale.conf</filename> with the 122 systemd <command>localectl</command> utility. To use 123 <command>localectl</command> for the example above, run:</para> 124 124 125 125 <screen role="nodump"><userinput>localectl set-locale LANG="<replaceable><ll>_<CC>.<charmap><@modifiers></replaceable>"</userinput></screen> … … 133 133 <screen role="nodump"><userinput>localectl set-locale LANG="en_US.UTF-8" LC_CTYPE="en_US"</userinput></screen> 134 134 135 <note><para>Please note that <command>localectl</command> command can136 be used 135 <note><para>Please note that the <command>localectl</command> command can 136 be used only on a system booted with systemd.</para></note> 137 137 138 138 <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the recommended -
chapter07/systemd-custom.xml
r9fde3e9 r0d84af1 22 22 entries commented out with the default settings indicated. This file is 23 23 where the log level may be changed as well as some basic logging settings. 24 See <filename>systemd-system.conf(5)</filename> manual page for details on25 each configuration option.</para>24 See the <filename>systemd-system.conf(5)</filename> manual page for details 25 on each configuration option.</para> 26 26 27 27 </sect2> … … 213 213 <title>Long Running Processes</title> 214 214 215 <para>Beginning with systemd-230, all user processes are killed when a 216 user session is ended, even if nohup is used, or the process uses217 <function>daemon()</function> or <function>setsid()</function> . This is a218 deliberate change from a historically permissive environment to a more219 restrictive one. The new behavior may cause issues if you depend on long220 running programs (e.g., <command>screen</command> or221 <command>tmux</command>) to remain active after ending your user 222 session. There are three ways to enable lingering processes to remain after223 a usersession is ended.</para>215 <para>Beginning with systemd-230, all user processes are killed when a user 216 session is ended, even if nohup is used, or the process uses the 217 <function>daemon()</function> or <function>setsid()</function> functions. 218 This is a deliberate change from a historically permissive environment to a 219 more restrictive one. The new behavior may cause issues if you depend on 220 long running programs (e.g., <command>screen</command> or 221 <command>tmux</command>) to remain active after ending your user session. 222 There are three ways to enable lingering processes to remain after a user 223 session is ended.</para> 224 224 225 225 <itemizedlist> 226 226 <listitem> 227 227 <para> 228 <emphasis>Enable process lingering for only needed users</emphasis>:229 normal users have permission to enable process lingering228 <emphasis>Enable process lingering for only selected users</emphasis>: 229 Normal users have permission to enable process lingering 230 230 with the command <command>loginctl enable-linger</command> for their 231 231 own user. System administrators can use the same command with a … … 245 245 <para> 246 246 <emphasis>Enable system-wide process lingering</emphasis>: 247 you can set <parameter>KillUserProcesses=no</parameter> in247 You can set <parameter>KillUserProcesses=no</parameter> in 248 248 <filename>/etc/logind.conf</filename> to enable process lingering 249 249 globally for all users. This has the benefit of leaving the old -
chapter07/udev.xml
r9fde3e9 r0d84af1 210 210 intended to load it</title> 211 211 212 <para>If the <quote>wrapper</quote> module only enhances the functionality 213 provided by some other module (e.g., <emphasis>snd-pcm-oss</emphasis> 214 enhances the functionality of <emphasis>snd-pcm</emphasis> by making the 215 sound cards available to OSS applications), configure 216 <command>modprobe</command> to load the wrapper after Udev loads the 217 wrapped module. To do this, add a <quote>softdep</quote> line in any 212 <para>If the <quote>wrapper</quote> module only enhances the 213 functionality provided by some other module (e.g., 214 <emphasis>snd-pcm-oss</emphasis> enhances the functionality of 215 <emphasis>snd-pcm</emphasis> by making the sound cards available to OSS 216 applications), configure <command>modprobe</command> to load the wrapper 217 after Udev loads the wrapped module. To do this, add a 218 <quote>softdep</quote> line to the corresponding 218 219 <filename>/etc/modprobe.d/<replaceable><filename></replaceable>.conf</filename> 219 220 file. For example:</para> -
chapter08/kernel.xml
r9fde3e9 r0d84af1 73 73 into account.</para> 74 74 75 <para>Be sure to enable or disable following features or the system might75 <para>Be sure to enable or disable the following features or the system might 76 76 not work correctly or boot at all:</para> 77 77 … … 218 218 219 219 <caution> 220 <para>If the host system has a separate /boot partition, the 221 files copied below should go there. The easiest way to do that222 is to bind /boot on the host to /mnt/lfs/boot before proceeding.223 As the rootuser in the <emphasis>host system</emphasis>:</para>220 <para>If the host system has a separate /boot partition, the files copied 221 below should go there. The easiest way to do that is to bind /boot on the 222 host (outside chroot) to /mnt/lfs/boot before proceeding. As the root 223 user in the <emphasis>host system</emphasis>:</para> 224 224 225 225 <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> … … 232 232 following command assumes an x86 architecture:</para> 233 233 234 <screen revision="sysv"><userinput remap="install">cp - v arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>235 236 <screen revision="systemd"><userinput remap="install">cp - v arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen>234 <screen revision="sysv"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> 235 236 <screen revision="systemd"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen> 237 237 238 238 <para><filename>System.map</filename> is a symbol file for the kernel. … … 242 242 Issue the following command to install the map file:</para> 243 243 244 <screen><userinput remap="install">cp - v System.map /boot/System.map-&linux-version;</userinput></screen>244 <screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen> 245 245 246 246 <para>The kernel configuration file <filename>.config</filename> … … 250 250 reference:</para> 251 251 252 <screen><userinput remap="install">cp - v .config /boot/config-&linux-version;</userinput></screen>252 <screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen> 253 253 254 254 <para>Install the documentation for the Linux kernel:</para> -
general.ent
r9fde3e9 r0d84af1 1 <!ENTITY version "SVN-2017122 6">1 <!ENTITY version "SVN-20171227"> 2 2 <!ENTITY short-version "svn"> <!-- Used below in &blfs-book; 3 3 Change to x.y for release but not -rc releases --> 4 4 <!ENTITY generic-version "development"> <!-- Use "development" or "x.y[-pre{x}]" --> 5 5 6 <!ENTITY versiond "2017122 6-systemd">6 <!ENTITY versiond "20171227-systemd"> 7 7 <!ENTITY short-versiond "systemd"> 8 8 <!ENTITY generic-versiond "systemd"> 9 9 10 <!ENTITY releasedate "December 2 6, 2017">10 <!ENTITY releasedate "December 27, 2017"> 11 11 12 12 <!ENTITY copyrightdate "1999-2017"><!-- jhalfs needs a literal dash, not – --> -
prologue/architecture.xml
r9fde3e9 r0d84af1 23 23 <para>Some other facts about 64-bit systems need to be added here. When 24 24 compared to a 32-bit system, the sizes of executable programs are slightly 25 larger and the execution speeds are only slightly faster. For example, in a26 test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics 27 were measured:</para>25 larger and the execution speeds of arbitrary programs are only slightly faster. 26 For example, in a test build of LFS-6.5 on a Core2Duo CPU based system, the 27 following statistics were measured:</para> 28 28 29 29 <screen><computeroutput>Architecture Build Time Build Size … … 35 35 minimal. Of course, if you have more than 4GB of RAM or want to manipulate 36 36 data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para> 37 38 <note><para>The above discussion is only appropriate when comparing 39 builds on the same hardware. Modern 64-bit systems are considerably 40 faster than older 64-bit systems and the LFS authors recommend building 41 on a 64-bit system when given a choice.</para></note> 37 42 38 43 <para>The default 64-bit build that results from LFS is considered a "pure" -
prologue/audience.xml
r9fde3e9 r0d84af1 46 46 <para>The goal of Linux From Scratch is to build a complete and usable 47 47 foundation-level system. If you do not wish to build your own Linux system 48 from scratch, you may n ot entirelybenefit from the information in this48 from scratch, you may nevertheless benefit from the information in this 49 49 book.</para> 50 50
Note:
See TracChangeset
for help on using the changeset viewer.