Changeset 907238e1 for introduction/welcome/askhelp.xml
- Timestamp:
- 05/07/2005 12:42:37 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:
- fa8d573
- Parents:
- f88c4ee
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/askhelp.xml
rf88c4ee r907238e1 7 7 8 8 <sect1 id="intro-welcome-askhelp"> 9 <sect1info> 10 <othername>$LastChangedBy$</othername> 11 <date>$Date$</date> 12 </sect1info> 13 <?dbhtml filename="askhelp.html"?> 14 <title>Asking for help and the <acronym>FAQ</acronym></title> 9 <?dbhtml filename="askhelp.html"?> 15 10 16 <para>If you encounter a problem while using this book, and your problem 17 is not listed in the <acronym>FAQ</acronym> (<ulink 18 url="http://www.linuxfromscratch.org/faq"/>), you will find that most of the 19 people on Internet Relay Chat (<acronym>IRC</acronym>) and on the mailing lists 20 are willing to help you. An overview of the <acronym>LFS</acronym> mailing 21 lists can be found in <xref linkend="intro-welcome-maillists"/>. To assist us 22 in diagnosing and solving your problem, include as much relevant information as 23 possible in your request for help.</para> 11 <sect1info> 12 <othername>$LastChangedBy$</othername> 13 <date>$Date$</date> 14 </sect1info> 24 15 25 <sect2> 26 <title>Things to check prior to asking</title> 16 <title>Asking for Help and the FAQ</title> 27 17 28 <para>Before asking for help, you should review the following 29 items:</para> 18 <para>If you encounter a problem while using this book, and your problem 19 is not listed in the FAQ (<ulink url="http://www.linuxfromscratch.org/faq"/>), 20 you will find that most of the people on Internet Relay Chat (IRC) and on the 21 mailing lists are willing to help you. An overview of the LFS mailing 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 as 24 possible in your request for help.</para> 30 25 31 <itemizedlist> 32 <listitem><para>Is the hardware support compiled into the kernel or 33 available as a module to the kernel? If it is a module, is it configured 34 properly in <filename>modules.conf</filename> and has it been loaded? You 35 should use <command>lsmod</command> as root to see if it's loaded. Check the 36 <filename>sys.log</filename> or run <command>modprobe <driver> 37 </command> to review any error message. If it loads properly, you may need 38 to add the <command>modprobe</command> to your boot scripts.</para></listitem> 26 <sect2> 27 <title>Things to Check Prior to Asking</title> 39 28 40 <listitem><para>Are your permissions properly set, especially for 41 devices? <acronym>LFS</acronym> uses groups to make these settings easier, but 42 it also adds the step of adding users to groups to allow access. A simple 43 <command>moduser -G audio <user></command> may be all that's necessary 44 for that user to have access to the sound system. Any question that starts 45 out with "It works as root, but not as ..." requires a thorough review 46 of permissions prior to asking.</para></listitem> 29 <para>Before asking for help, you should review the following items:</para> 47 30 48 <listitem><para><acronym>BLFS</acronym> liberally uses <filename> 49 /opt/<package></filename>. The main objection to this centers around the 50 need to expand your environment variables for each package placed there (e.g., 51 PATH=$PATH:/opt/kde/bin). In some cases, the package will walk you 52 through the changes, but some will not. The section called "<ulink 53 url="beyond.html">Going Beyond BLFS</ulink>" is available to help you check.</para></listitem> 54 </itemizedlist></sect2> 31 <itemizedlist> 32 <listitem> 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> 40 </listitem> 41 <listitem> 42 <para>Are your permissions properly set, especially for devices? LFS 43 uses groups to make these settings easier, but it also adds the step of 44 adding users to groups to allow access. A simple <command>moduser 45 -G audio <user></command> may be all that's necessary for that 46 user to have access to the sound system. Any question that starts 47 out with "It works as root, but not as ..." requires a thorough review 48 of permissions prior to asking.</para> 49 </listitem> 50 <listitem> 51 <para>BLFS liberally uses <filename>/opt/<package></filename>. 52 The main objection to this centers around the need to expand your 53 environment variables for each package placed there (e.g., 54 PATH=$PATH:/opt/kde/bin). In some cases, the package will walk you 55 through the changes, but some will not. The section called "<ulink 56 url="beyond.html">Going Beyond BLFS</ulink>" is available to help 57 you check.</para> 58 </listitem> 59 </itemizedlist> 55 60 56 <sect2> 57 <title>Things to mention</title> 61 </sect2> 58 62 59 <para>Apart from a brief explanation of the problem you're having, the 60 essential things to include in your request are:</para>63 <sect2> 64 <title>Things to Mention</title> 61 65 62 <itemizedlist> 63 <listitem><para>the version of the book you are using (being 64 &version;),</para></listitem> 65 <listitem><para>the package or section giving you 66 problems,</para></listitem> 67 <listitem><para>the exact error message or symptom you are 68 receiving,</para></listitem> 69 <listitem><para>whether you have deviated from the book or 70 <acronym>LFS</acronym> at all.</para></listitem> 71 </itemizedlist> 66 <para>Apart from a brief explanation of the problem you're having, the 67 essential things to include in your request are:</para> 72 68 73 <para>(Note that saying that you've deviated from the book doesn't mean 74 that we won't help you. It'll just help us to see other possible causes of your problem.)</para> 69 <itemizedlist> 70 <listitem> 71 <para>the version of the book you are using (being &version;),</para> 72 </listitem> 73 <listitem> 74 <para>the package or section giving you problems,</para> 75 </listitem> 76 <listitem> 77 <para>the exact error message or symptom you are receiving,</para> 78 </listitem> 79 <listitem> 80 <para>whether you have deviated from the book or LFS at all.</para> 81 </listitem> 82 </itemizedlist> 75 83 76 <para>Expect guidance instead of specific instructions. If you are 77 instructed to read something, please do so. It generally implies that 78 the answer was way too obvious and that the question would not have been asked 79 if a little research was done prior to asking. The volunteers in the mailing 80 list prefer not to be used as an alternative to doing reasonable research on 81 your end. In addition, the quality of your experience with <acronym>BLFS 82 </acronym> is also greatly enhanced by this research, and the quality of 83 volunteers is enhanced because they don't feel that their time has been abused, 84 so they are far more likely to participate.</para> 84 <para>(Note that saying that you've deviated from the book doesn't mean 85 that we won't help you. It'll just help us to see other possible causes 86 of your problem.)</para> 85 87 86 <para>An excellent article on asking for help on the Internet in general 87 has been written by Eric S. Raymond. It is available online at <ulink 88 url="http://www.catb.org/~esr/faqs/smart-questions.html"/>. 89 Read and follow the hints in that document and you are much more likely 90 to get a response to start with and also to get the help you actually 91 need.</para> 92 </sect2> 88 <para>Expect guidance instead of specific instructions. If you are 89 instructed to read something, please do so. It generally implies that 90 the answer was way too obvious and that the question would not have 91 been asked if a little research was done prior to asking. The volunteers 92 in the mailing list prefer not to be used as an alternative to doing 93 reasonable research on your end. In addition, the quality of your 94 experience with BLFS is also greatly enhanced by this research, and 95 the quality of volunteers is enhanced because they don't feel that their 96 time has been abused, so they are far more likely to participate.</para> 97 98 <para>An excellent article on asking for help on the Internet in general 99 has been written by Eric S. Raymond. It is available online at 100 <ulink url="http://www.catb.org/~esr/faqs/smart-questions.html"/>. 101 Read and follow the hints in that document and you are much more likely 102 to get a response to start with and also to get the help you actually 103 need.</para> 104 105 </sect2> 93 106 94 107 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.