Ignore:
Timestamp:
07/21/2005 09:49:02 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
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
Message:

Various tagging and text modifications to the 'Conventions' and 'Asking for Help' pages

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4753 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/welcome/askhelp.xml

    re4e0cc35 r8aefeb67  
    2121  mailing lists are willing to help you. An overview of the LFS mailing
    2222  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>
     23  in diagnosing and solving your problem, include as much relevant information
     24  as possible in your request for help.</para>
    2525
    2626  <sect2>
     
    3232      <listitem>
    3333        <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 &lt;driver&gt;
    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>
    4042      </listitem>
    4143      <listitem>
     
    4345        uses groups to make these settings easier, but it also adds the step of
    4446        adding users to groups to allow access. A simple <command>moduser
    45         -G audio &lt;user&gt;</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>
     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>
    4951      </listitem>
    5052      <listitem>
    51         <para>BLFS liberally uses <filename>/opt/&lt;package&gt;</filename>.
     53        <para>BLFS liberally uses <filename
     54        class='directory'>/opt/<replaceable>[package]</replaceable></filename>.
    5255        The main objection to this centers around the need to expand your
    5356        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>
     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>
    5861      </listitem>
    5962    </itemizedlist>
     
    9295    in the mailing list prefer not to be used as an alternative to doing
    9396    reasonable research on your end.  In addition, the quality of your
    94     experience with BLFS  is also greatly enhanced by this research, and
     97    experience with BLFS is also greatly enhanced by this research, and
    9598    the quality of volunteers is enhanced because they don't feel that their
    9699    time has been abused, so they are far more likely to participate.</para>
     
    106109
    107110</sect1>
    108 
Note: See TracChangeset for help on using the changeset viewer.