sane-tamarack(5)
sane-tamarack(5) πβ¨
π NAME π
okay so bestie, sane-tamarack is the SANE backend for Tamarack flatbed scanners β and it's from the SANE Scanner Access Now Easy side of town π«
πΈ DESCRIPTION πΈ
okay so the sane-tamarack library implements a SANE (Scanner Access Now Easy) backend that gives you access to these Tamarack flatbed scanners, no cap:
Artiscan 6000CArtiscan 8000CArtiscan 12000C
π 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. π«Ά
π FILES π
These are the literal files involved, no cap:
/etc/sane.d/tamarack.confβ the backend configuration file (see also description ofSANE_CONFIG_DIRbelow)./usr/lib64/sane/libsane-tamarack.aβ the static library implementing this backend./usr/lib64/sane/libsane-tamarack.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 *NIX systems, 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_TAMARACKβ 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, bestie:
export SANE_DEBUG_TAMARACK=4
β SEE ALSO β
go read these too, iykyk:
π AUTHOR π
Roger Wolff β ty for this iconic backend, king π«Ά
π cute sign-off: this page is dated 14 Jul 2008, and it's the sane-tamarack(5) manual page β bye bestie, slay your scans πβ¨
π¦ 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