Changes in / [d9c86378:7f3f152]
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
appendices/udev-rules.xml
rd9c86378 r7f3f152 14 14 15 15 <para>The rules in this appendix are listed for convenience. Installation is 16 normally done via instructions in <xref linkend='ch-system-udev' role='.'/></para>16 normally done via instructions in <xref linkend='ch-system-udev'/>. </para> 17 17 18 18 <sect1 id="lfsrules" role="wrap"> -
chapter01/askforhelp.xml
rd9c86378 r7f3f152 16 16 instruction, we strongly discourage posting the issue directly onto 17 17 the upstream support channel before discussing via a LFS support 18 channel listed in <xref linkend="ch-intro-resources" role='.'/>18 channel listed in <xref linkend="ch-intro-resources"/>. 19 19 Doing so is often quite inefficient because the upstream 20 20 maintainers are rarely familiar with LFS building procedure. Even if -
chapter02/stages.xml
rd9c86378 r7f3f152 87 87 commands in 88 88 <xref linkend='ch-tools-bindmount'/> and 89 <xref linkend='ch-tools-kernfsmount' role='.'/></para>89 <xref linkend='ch-tools-kernfsmount'/>.</para> 90 90 </listitem> 91 91 </itemizedlist> -
chapter06/introduction.xml
rd9c86378 r7f3f152 27 27 This whole chapter must be done as user <systemitem 28 28 class="username">lfs</systemitem>, with the environment as described in 29 <xref linkend="ch-preps-settingenviron" role='.'/></para>29 <xref linkend="ch-preps-settingenviron"/>.</para> 30 30 31 31 </sect1> -
chapter07/cleanup.xml
rd9c86378 r7f3f152 92 92 </para> 93 93 <para> 94 This has been discussed in 95 <xref linkend='ch-partitioning-aboutlfs' role='.'/> 94 This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>. 96 95 </para> 97 96 </important> -
chapter08/grub.xml
rd9c86378 r7f3f152 112 112 113 113 <para>Making your LFS system bootable with GRUB will be discussed in 114 <xref linkend="ch-bootable-grub" role='.'/></para>114 <xref linkend="ch-bootable-grub"/>.</para> 115 115 116 116 </sect2> -
chapter08/shadow.xml
rd9c86378 r7f3f152 243 243 even though the account has been created correctly. That is why we 244 244 created the group <systemitem class="groupname">users</systemitem> 245 with this group ID in 246 <xref linkend='ch-tools-createfiles' role='.'/></para> 245 with this group ID in <xref linkend='ch-tools-createfiles'/>.</para> 247 246 248 247 </listitem> -
chapter09/symlinks.xml
rd9c86378 r7f3f152 40 40 wlan0; such laptops can also use this method. The command line 41 41 is in the GRUB configuration file. 42 See <xref linkend="grub-cfg" role='.'/></para>42 See <xref linkend="grub-cfg"/>.</para> 43 43 </sect3> 44 44 … … 220 220 <title>Dealing with Duplicate Devices</title> 221 221 222 <para>As explained in <xref linkend="ch-config-udev" role=','/> the223 order inwhich devices with the same function appear in222 <para>As explained in <xref linkend="ch-config-udev"/>, the order in 223 which devices with the same function appear in 224 224 <filename class="directory">/dev</filename> is essentially random. 225 225 E.g., if you have a USB web camera and a TV tuner, sometimes … … 230 230 fixable by creating udev rules to create persistent symlinks. 231 231 The case of network cards is covered separately in 232 <xref linkend="ch-config-network" role=','/> and sound card 233 configuration can be found in 234 <ulink url="&blfs-book;postlfs/devices.html">BLFS</ulink>.</para> 232 <xref linkend="ch-config-network"/>, and sound card configuration can 233 be found in <ulink url="&blfs-book;postlfs/devices.html">BLFS</ulink>.</para> 235 234 236 235 <para>For each of your devices that is likely to have this problem -
chapter09/usage.xml
rd9c86378 r7f3f152 255 255 256 256 <para>For information on kernel module loading and udev, see 257 <xref linkend="module-loading" role='.'/></para>257 <xref linkend="module-loading"/>.</para> 258 258 </sect2> 259 259 -
chapter10/kernel.xml
rd9c86378 r7f3f152 56 56 the procedures below fairly closely. The objective is to get an 57 57 initial system to a point where you can log in at the command line when 58 you reboot later in <xref linkend="ch-finish-reboot" role='.'/>59 At this pointoptimization and customization is not a goal.58 you reboot later in <xref linkend="ch-finish-reboot"/>. At this point 59 optimization and customization is not a goal. 60 60 </para> 61 61
Note:
See TracChangeset
for help on using the changeset viewer.