sane-ricoh(5)
hey bestie π welcome to the sane-ricoh(5) main-character moment β this is the manual page for the SANE backend for Ricoh flatbed scanners. ok so itβs short, but weβre gonna read every crumb, no cap. π
πΈ NAME πΈ
sane-ricohβ SANE backend for Ricoh flatbed scanners.
π¦ DESCRIPTION π¦
The sane-ricoh library implements a SANE (Scanner Access Now Easy) backend that provides access to the following Ricoh flatbed scanners:
IS50IS60
π DEVICE NAMES π
This backend expects device names of the form:
special
Where special is the path-name for the special device that corresponds to a SCSI scanner. The special device name must be a generic SCSI device or a symlink to such a device. The program sane-find-scanner(1) helps to find out the correct device. Under Linux, such a device name could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for details.
bestie, this is the literal vibe check: special has to be a generic SCSI device or a symlink to one. slay that detail. π
π¦ FILES π¦
/etc/sane.d/ricoh.confβ the backend configuration file (see also description ofSANE_CONFIG_DIRbelow π)./usr/lib64/sane/libsane-ricoh.aβ the static library implementing this backend./usr/lib64/sane/libsane-ricoh.soβ the shared library implementing this backend (present on systems that support dynamic loading).
πΈ ENVIRONMENT πΈ
SANE_CONFIG_DIRβ this environment variable specifies the list of directories that may contain the configuration file. On*NIXsystems, the directories are separated by a colon (:), under OS/2, they are separated by a semi-colon (;). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in/etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, settingSANE_CONFIG_DIRto"/tmp/config:"would result in directoriestmp/config,., and/etc/sane.dbeing searched (in this order).SANE_DEBUG_RICOHβ if the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output.
Example:
export SANE_DEBUG_RICOH=4
π₯ SEE ALSO π₯
π AUTHOR π
Feico W. Dillema β show some love, bestie π.
k bye bestie π β this was sane-ricoh(5), dated 14 Jul 2008, coming at you from the SANE Scanner Access Now Easy side of the manual-page universe. periodt. π«Ά
π¦ where this page comes from
- centos-stream 10: sane-backends 1.2.1-10.el10 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- fedora 43: sane-backends 1.4.0-4.fc43 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- fedora 44: sane-backends 1.4.0-6.fc44 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms