Changeset 37f01429


Ignore:
Timestamp:
12/26/2013 01:17:22 AM (10 years ago)
Author:
Fernando de Oliveira <fernando@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 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:
6a16bc6
Parents:
19023c19
Message:

SANE-1.0.24: rephrase some paragraphs.

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pst/scanning/sane.xml

    r19023c19 r37f01429  
    157157
    158158  <sect2 role="kernel" id='sane-kernel'>
    159     <title>Kernel Configuration</title>
     159    <title>Kernel Configuration, Drivers and Additional Packages</title>
    160160
    161161    <indexterm zone="sane sane-kernel">
     
    168168    use enhanced EPP modes) and perhaps <ulink
    169169    url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>, and a USB
    170     scanner will need the <xref linkend="libusb"/> package. Ensure you have
    171     the necessary drivers properly configured to access the devices.</para>
     170    scanner will need the <xref linkend="libusb"/> package. For HP devices, you
     171    may need <ulink
     172    url="http://sourceforge.net/projects/hplip/files/hplip/">hplip</ulink>.
     173    Ensure you have the necessary drivers properly configured to access
     174    the devices.</para>
    172175
    173176  </sect2>
     
    248251
    249252      <para>With the scanner on, run <command>scanimage -L</command> and the
    250       name and location of the device will appear, if the installation was
    251       successful.</para>
     253      name and location of the device should appear. Of course, you need the
     254      device drivers configured, in order to run this test.</para>
    252255
    253256    </sect3>
Note: See TracChangeset for help on using the changeset viewer.