6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am testing shc to see if it would help with my need.
Im at a point where Im trying to compile and test the "test.ksh" file that comes in the tar ball :
shc-3.8.9> shc -v -r -f test.ksh
shc shll=ksh
shc =-c
shc =exec '%s' "$@"
shc =
shc opts=
shc: cc test.ksh.x.c -o test.ksh.x... (7 Replies)
Discussion started by: popeye
7 Replies
2. Shell Programming and Scripting
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies
3. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
4. Shell Programming and Scripting
Hi,
Can somebody tell the usage of "$_"
cd $_ ?
and ls $_ ? (4 Replies)
Discussion started by: giri_luck
4 Replies
5. Shell Programming and Scripting
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Discussion started by: Max89
1 Replies
6. HP-UX
Hi
All of my unix forum friends. I mirrored my hp-ux o/s disk with the help of LVM on a disk array. Can any one tell me the procedure if the O/S disk fails then how could i recover the system disk from mirrored disk
Regards'
Alam (5 Replies)
Discussion started by: waqaralam
5 Replies
LEARN ABOUT NETBSD
sane-find-scanner
sane-find-scanner(1) SANE Scanner Access Now Easy sane-find-scanner(1)
NAME
sane-find-scanner - find SCSI and USB scanners and their device files
SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-p] [-f] [-F filename] [devname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and USB scanners and determine their Unix device files. Its primary aim is to make
sure that scanners can be detected by SANE backends.
For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So
sane-find-scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend.
For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested.
The files are opened and the vendor and device ids are determined, if the operating system supports this feature. Currently USB scanners
are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test,
sane-find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners,
so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner also tries to find out the type of
USB chip used in the scanner. If detected, it will be printed after the vendor and product ids. sane-find-scanner will even find USB scan-
ners, that are not supported by any SANE backend.
sane-find-scanner won't find most parallel port scanners, or scanners connected to proprietary ports. Some parallel port scanners may be
detected by sane-find-scanner -p. At the time of writing this will only detect Mustek parallel port scanners.
OPTIONS
-h, -? Prints a short usage message.
-v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa-
tion and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-p Probe parallel port scanners.
-f Force opening all explicitly given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determining the
device type.
-F filename
filename is a file that contains USB descriptors in the format of /proc/bus/usb/devices as used by Linux. sane-find-scanner tries
to identify the chipset(s) of all USB scanners found in such a file. This option is useful for developers when the output of "cat
/proc/bus/usb/devices" is available but the scanner itself isn't.
devname Test device file "devname". No other devices are checked if devname is given.
EXAMPLE
sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line for every device file.
sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
sane-find-scanner -p
Probe for parallel port scanners.
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5)
AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others
SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor
and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX.
BUGS
No support for most parallel port scanners yet.
Detection of USB chipsets is limited to a few chipsets.
13 Jul 2008 sane-find-scanner(1)