Changeset 8aefeb67
- Timestamp:
- 07/21/2005 09:49:02 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 4382a36
- Parents:
- e4e0cc35
- Location:
- introduction/welcome
- Files:
-
- 2 edited
-
askhelp.xml (modified) (5 diffs)
-
conventions.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/askhelp.xml
re4e0cc35 r8aefeb67 21 21 mailing lists are willing to help you. An overview of the LFS mailing 22 22 lists can be found in <xref linkend="intro-welcome-maillists"/>. To assist us 23 in diagnosing and solving your problem, include as much relevant information as24 possible in your request for help.</para>23 in diagnosing and solving your problem, include as much relevant information 24 as possible in your request for help.</para> 25 25 26 26 <sect2> … … 32 32 <listitem> 33 33 <para>Is the hardware support compiled into the kernel or 34 available as a module to the kernel? If it is a module, is it configured 35 properly in <filename>modules.conf</filename> and has it been loaded? You 36 should use <command>lsmod</command> as root to see if it's loaded. Check the 37 <filename>sys.log</filename> or run <command>modprobe <driver> 38 </command> to review any error message. If it loads properly, you may need 39 to add the <command>modprobe</command> to your boot scripts.</para> 34 available as a module to the kernel? If it is a module, is it 35 configured properly in <filename>modules.conf</filename> and has it 36 been loaded? You should use <command>lsmod</command> as the 37 <systemitem class='username'>root</systemitem> user to see if it's 38 loaded. Check the <filename>syslog.log</filename> or run 39 <command>modprobe <replaceable>[driver]</replaceable></command> to 40 review any error message. If it loads properly, you may need to add 41 the <command>modprobe</command> command to your boot scripts.</para> 40 42 </listitem> 41 43 <listitem> … … 43 45 uses groups to make these settings easier, but it also adds the step of 44 46 adding users to groups to allow access. A simple <command>moduser 45 -G audio <user></command> may be all that's necessary for that46 user to have access to the sound system. Any question that starts47 out with "It works as root, but not as ..." requires a thorough review48 of permissions prior to asking.</para>47 -G audio <replaceable>[user]</replaceable></command> may be all that's 48 necessary for that user to have access to the sound system. Any question 49 that starts out with <quote>It works as root, but not as ...</quote> 50 requires a thorough review of permissions prior to asking.</para> 49 51 </listitem> 50 52 <listitem> 51 <para>BLFS liberally uses <filename>/opt/<package></filename>. 53 <para>BLFS liberally uses <filename 54 class='directory'>/opt/<replaceable>[package]</replaceable></filename>. 52 55 The main objection to this centers around the need to expand your 53 56 environment variables for each package placed there (e.g., 54 PATH=$PATH:/opt/kde/bin). In some cases, the package will walk you55 through the changes, but some will not. The section called "<ulink56 url="beyond.html">Going Beyond BLFS</ulink>" is available to help57 you check.</para>57 PATH=$PATH:/opt/kde/bin). In most cases, the package instructions will 58 walk you through the changes, but some will not. The section called 59 <quote><ulink url="beyond.html">Going Beyond BLFS</ulink></quote> is 60 available to help you check.</para> 58 61 </listitem> 59 62 </itemizedlist> … … 92 95 in the mailing list prefer not to be used as an alternative to doing 93 96 reasonable research on your end. In addition, the quality of your 94 experience with BLFS 97 experience with BLFS is also greatly enhanced by this research, and 95 98 the quality of volunteers is enhanced because they don't feel that their 96 99 time has been abused, so they are far more likely to participate.</para> … … 106 109 107 110 </sect1> 108 -
introduction/welcome/conventions.xml
re4e0cc35 r8aefeb67 22 22 23 23 <blockquote> 24 <para>This form of text is designed to be typed exactly 25 as seen unless otherwise noted in the surrounding text. It is also used26 in the explanation sections to identifyreferences to specific commands.</para>24 <para>This form of text is designed to be typed exactly as seen unless 25 otherwise noted in the surrounding text. It is also used to identify 26 references to specific commands.</para> 27 27 </blockquote> 28 28 … … 59 59 60 60 <blockquote> 61 <para>This type of section is used mainly when creating 62 configurationfiles. The first command (in bold) tells the system to create61 <para>This type of section is used mainly when creating configuration 62 files. The first command (in bold) tells the system to create 63 63 the file <filename>$LFS/etc/group</filename> from whatever is typed on the 64 64 following lines until the sequence EOF is encountered. … … 70 70 <blockquote> 71 71 <para>This form of text is used to encapsulate text that should be 72 modified and is not to be typed as seen or copy and pasted.</para> 72 modified and is not to be typed as seen, or copy and pasted. Note that 73 the square brackets are not part of the text, but should be substituted 74 for as well.</para> 75 </blockquote> 76 77 <para><systemitem class='username'>root</systemitem></para> 78 79 <blockquote> 80 <para>This form of text is used to show a specific system user reference 81 in the instructions.</para> 73 82 </blockquote> 74 83
Note:
See TracChangeset
for help on using the changeset viewer.
