Changeset b71fa50 for final-system/common
- Timestamp:
- Jun 21, 2006, 2:53:33 PM (19 years ago)
- Children:
- 73c89fd
- Parents:
- 9fcb5e4
- Location:
- final-system/common
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
final-system/common/coreutils.xml
r9fcb5e4 rb71fa50 81 81 ln -svf ../../bin/install /usr/bin</userinput></screen> 82 82 83 <para os="t">Some of the scripts in the LFS-Bootscripts package depend on83 <para os="t">Some of the scripts in the CLFS-Bootscripts package depend on 84 84 <command>head</command> and <command>sleep</command>. As <filename 85 85 class="directory">/usr</filename> may not be available during the early -
final-system/common/e2fsprogs.xml
r9fcb5e4 rb71fa50 70 70 Management System (EVMS) plugin. This plugin is not up-to-date with 71 71 the latest EVMS internal interfaces and EVMS is not installed as part 72 of a base LFS system, so the plugin is not required. See the EVMS72 of a base CLFS system, so the plugin is not required. See the EVMS 73 73 website at <ulink url="http://evms.sourceforge.net/"/> for more 74 74 information regarding EVMS.</para> -
final-system/common/glibc.xml
r9fcb5e4 rb71fa50 125 125 </listitem> 126 126 <listitem> 127 <para>If you have mounted the LFS partition with the127 <para>If you have mounted the CLFS partition with the 128 128 <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test 129 129 will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>, 130 130 do not use the <parameter>noatime</parameter> option while building 131 LFS.</para>131 CLFS.</para> 132 132 </listitem> 133 133 <listitem> … … 186 186 <para>Some locales installed by the <command>make 187 187 localedata/install-locales</command> command above are not properly 188 supported by some applications that are in the LFS and BLFS books. Because188 supported by some applications that are in the CLFS and BLFS books. Because 189 189 of the various problems that arise due to application programmers making 190 assumptions that break in such locales, LFS should not be used in locales190 assumptions that break in such locales, CLFS should not be used in locales 191 191 that utilize multibyte character sets (including UTF-8) or right-to-left 192 192 writing order. Numerous unofficial and unstable patches are required to 193 fix these problems, and it has been decided by the LFS developers not to193 fix these problems, and it has been decided by the CLFS developers not to 194 194 support such complex locales at this time. This applies to the ja_JP and 195 195 fa_IR locales as well—they have been installed only for GCC and -
final-system/common/inetutils.xml
r9fcb5e4 rb71fa50 79 79 <para>This disables the installation of the various network 80 80 servers included as part of the Inetutils package. These servers are 81 deemed not appropriate in a basic LFS system. Some are insecure by81 deemed not appropriate in a basic CLFS system. Some are insecure by 82 82 nature and are only considered safe on trusted networks. More 83 83 information can be found at <ulink -
final-system/common/iproute2.xml
r9fcb5e4 rb71fa50 49 49 <filename class="directory">/sbin</filename>. This is the correct 50 50 location according to the FHS, because some of the IPRoute2 binaries 51 are used by the LFS-Bootscripts package.</para>51 are used by the CLFS-Bootscripts package.</para> 52 52 </listitem> 53 53 </varlistentry> -
final-system/common/kbd.xml
r9fcb5e4 rb71fa50 296 296 <listitem> 297 297 <para>Puts the keyboard and console in UNICODE mode. Never use it on 298 LFS, because applications are not configured to support UNICODE.</para>298 CLFS, because applications are not configured to support UNICODE.</para> 299 299 <indexterm zone="ch-system-kbd unicode_start"> 300 300 <primary sortas="b-unicode_start">unicode_start</primary> -
final-system/common/man.xml
r9fcb5e4 rb71fa50 103 103 non-ISO 8859-1 locales. Also, it does not work with multibyte 104 104 character sets. The first problem does not currently have a solution. 105 The second issue is not of concern because the LFS installation does105 The second issue is not of concern because the CLFS installation does 106 106 not support multibyte character sets.</para> 107 107 -
final-system/common/psmisc.xml
r9fcb5e4 rb71fa50 40 40 <filename class="directory">/usr/bin</filename>. This is the 41 41 correct location according to the FHS, because some of the Psmisc 42 binaries are used by the LFS-Bootscripts package.</para>42 binaries are used by the CLFS-Bootscripts package.</para> 43 43 </listitem> 44 44 </varlistentry> -
final-system/common/sysvinit.xml
r9fcb5e4 rb71fa50 98 98 character set to a user-defined one, which can be modified by running 99 99 the <command>setfont</command> program. The <command>console</command> 100 initscript from the LFS-Bootscripts package calls the100 initscript from the CLFS-Bootscripts package calls the 101 101 <command>setfont</command> program during system startup. Sending this 102 102 escape sequence is necessary for people who use non-ISO 8859-1 screen -
final-system/common/udev.xml
r9fcb5e4 rb71fa50 177 177 <para>Simulates a <command>udev</command> run for the given device, 178 178 and prints out the name of the node the real <command>udev</command> 179 would have created or (not in LFS) the name of the renamed network179 would have created or (not in CLFS) the name of the renamed network 180 180 interface</para> 181 181 <indexterm zone="ch-system-udev udevtest"> -
final-system/common/util-linux.xml
r9fcb5e4 rb71fa50 91 91 <para os="g">Install the package and move the <command>logger</command> binary 92 92 to <filename class="directory">/bin</filename> as it is needed by the 93 LFS-Bootscripts package:</para>93 CLFS-Bootscripts package:</para> 94 94 95 95 <screen os="h"><userinput>make HAVE_KILL=yes HAVE_SLN=yes install -
final-system/common/vim.xml
r9fcb5e4 rb71fa50 100 100 <screen os="o"><userinput>ln -sv ../vim/vim&vim-version2;/doc /usr/share/doc/vim-&vim-version;</userinput></screen> 101 101 102 <para os="p">If an X Window System is going to be installed on the LFS102 <para os="p">If an X Window System is going to be installed on the CLFS 103 103 system, you may want to recompile Vim after installing X. Vim 104 104 comes with a GUI version of the editor that requires X and some … … 376 376 necessary to highlight in <command>vim</command>. This script 377 377 requires the old Unix <command>spell</command> command, which 378 is provided neither in LFS nor in BLFS</para>378 is provided neither in CLFS nor in BLFS</para> 379 379 <indexterm zone="ch-system-vim vimspell.sh"> 380 380 <primary sortas="b-vimspell.sh">vimspell.sh</primary>
Note:
See TracChangeset
for help on using the changeset viewer.