ccdconfig(8) [netbsd man page]
CCDCONFIG(8) BSD System Manager's Manual CCDCONFIG(8) NAME
ccdconfig -- configuration utility for the concatenated disk driver SYNOPSIS
ccdconfig [-cv] ccd ileave [flags] dev [...] ccdconfig -C [-v] [-f config_file] ccdconfig -u [-v] ccd [...] ccdconfig -U [-v] [-f config_file] ccdconfig -g [-M core] [-N system] [ccd [...]] DESCRIPTION
ccdconfig is used to dynamically configure and unconfigure concatenated disk devices, or ccds. For more information about the ccd, see ccd(4). The options are as follows: -c Configure a ccd. This is the default behavior of ccdconfig. -C Configure all ccd devices listed in the ccd configuration file. -f config_file When configuring or unconfiguring all devices, read the file config_file instead of the default /etc/ccd.conf. -g Dump the current ccd configuration in a format suitable for use as the ccd configuration file. If no arguments are specified, every configured ccd is dumped. Otherwise, the configuration of each listed ccd is dumped. -M core Extract values associated with the name list from core instead of the default /dev/mem. -N system Extract the name list from system instead of the default /netbsd. -u Unconfigure a ccd. -U Unconfigure all ccd devices listed the ccd configuration file. -v Causes ccdconfig to be verbose. A ccd is described on the command line and in the ccd configuration file by the name of the ccd, the interleave factor, the ccd configuration flags, and a list of one or more devices. The flags may be represented as a decimal number, a hexadecimal number, a comma-separated list of strings, or the word ``none''. The flags are as follows: Symbolic Numeric Comment CCDF_UNIFORM 0x02 Use uniform interleave. The size of all components is clamped to that of the smallest component. CCDF_NOLABEL 0x04 Ignore raw disklabel. Useful when creating a new ccd. /etc/ccd.conf The file /etc/ccd.conf is used to configure ccdconfig if -C or -U is used. Each line of the configuration file contains arguments as per the -c argument: ccd ileave [flags] dev [...] A '#' is a comment, and everything to end of line is ignored. A '' at the end of a line indicates that the next line should be concatenated with the current. A '' preceding any character (other than the end of line) prevents that character's special meaning from taking effect. See EXAMPLES for an example of /etc/ccd.conf. FILES
/etc/ccd.conf - default ccd configuration file. EXAMPLES
The following command, executed from the command line, would configure ccd0 with 4 components (/dev/sd2e, /dev/sd3e, /dev/sd4e, /dev/sd5e), and an interleave factor of 32 blocks. # ccdconfig ccd0 32 0 /dev/sd2e /dev/sd3e /dev/sd4e /dev/sd5e An example /etc/ccd.conf: # # /etc/ccd.conf # Configuration file for concatenated disk devices # # ccd ileave flags component devices ccd0 16 none /dev/sd2e /dev/sd3e SEE ALSO
ccd(4), ccd.conf(5), rc(8) HISTORY
The ccdconfig command first appeared in NetBSD 1.1. BSD
October 17, 2003 BSD
Check Out this Related Man Page
sane-umax(5) SANE Scanner Access Now Easy sane-umax(5) NAME
sane-umax - SANE backend for UMAX scanners ABOUT THIS FILE
This file only is a short descripton of the umax-backend for sane! For detailled information take a look at sane-umax-doc.html (it is included in the sane source directory and in the xsane online help)! DESCRIPTION
The sane-umax library implements a SANE backend that provides acces to several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, par- allel- and USB-scanners are not (and propably will never be) supported! I suggest you hold one hand on the power-button of the scanner while you try the first scans! CONFIGURATION
The configuration file for this backend resides in /etc/sane.d/umax.conf. Its contents is a list of device names that correspond to UMAX and UMAX compatible scanners. Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below: # this is a comment # option scsi-maxqueue 4 option scsi-buffer-size-min 65536 option scsi-buffer-size-max 131072 option scan-lines 40 option preview-lines 10 option scsi-maxqueue 2 option execute-request-sense 0 option force-preview-bit-rgb 0 option slow-speed -1 option care-about-smearing -1 option calibration-full-ccd -1 option calibration-width-offset -1 option calibration-bytes-pixel -1 option exposure-time-rgb-bind -1 option invert-shading-data -1 option lamp-control-available 0 option gamma-lsb-padded 0 /dev/sge #scsi Vendor Model Type Bus Channel ID LUN # The following scanner supports lamp control option lamp-control-available 1 scsi UMAX * Scanner * * * * * # scanner on /dev/scanner does not support lamp control option lamp-control-available 0 /dev/scanner execute-request-sense: values: 0 = disabled, 1 = enabled default = 0 If set to 1 umax_do_request_sense is called in umax_do_calibration. This can hang the system (but has been enabled until this ver- sion) scsi-buffer-size-min, scsi-buffer-size-max: values: 4096-1048576 default min = 32768, max = 131072 Especially the minimum value is very important. If this value is set too small the backend is not able to send gamma tables to the scanner or to do a correct color calibration. This may result in strange color effects. If the minimum value is set too large then the backend is not able to allocate the requested scsi buffer size and aborts with out of memory error. The default is 32KB, for some scanners it should be increased to 64KB. scan-lines, preview-lines: values: 1-65535 default: scan-lines = 40, preview-lines = 10 define the maximum number of lines that are scanned into one buffer force-preview-bit-rgb: values: 0 = disabled, 1 = enabled default = 0 set preview bit in rgb real scan slow-speed, care-about-smearing: values: -1 = auto, 0 = disabled, 1 = enabled default = -1 dangerous options, needed for some scanners do not changed these options until you really know what you do, you may destroy your scanner when you define wrong values for this options calibration-full-ccd: values: -1 = auto, 0 = disabled, 1 = enabled default = -1 do calibration for each pixel of ccd instead of selected image calibration-width-offset: values: -99999 = auto, > -99999 set value add an offset width to the calculated with for image/ccd calibration-bytes-pixel: values: -1 = disabled, 0 = not set, 1 = 1 byte/pixel, 2 = 2 bytes/pixel use # bytes per pixel for calibration exposure-time-rgb-bind: values: -1 = automatically set by driver - if known, 0 = disabled (own selection for red, green and blue), 1 = enabled (same values for red, green and blue) invert-shading-data: values: -1 = automatically set by driver - if known, 0 = disabled, 1 = enabled default = -1 invert shading data before sending it back to the scanner lamp-control-available: values: 0 = automatically set by driver - if known, 1 = available default = 0 gamma-lsb-padded: values: -1 = automatically set by driver - if known, 0 = gamma data is msb padded, 1 = gamma data is lsb padded default = -1 handle-bad-sense-error: values: 0 = handle as device busy, 1 = handle as ok, 2 = handle as i/o error, 3 = ignore bad error code - continue sense handler default = 0 scsi-maxqueue: values: 1..# (maximum defined at compile time) default = 2 most scsi drivers allow internal command queueing with a depth of 2 commands. In most cases it does not mprove anything when you increase this value. When your scsi driver does not support any command queueing you can try to set this value to 1. The special device name must be a generic SCSI device or a symlink to such a device. To find out to which device your scanner is assigned and how you have to set the permissions of that device, have a look at sane-scsi. SCSI ADAPTER TIPS
The ISA-SCSI-adapters that are shipped with some Umax-scanners are not supported very well by Linux (I suggest not to use it), the PCI- SCSI-adapters that come with some Umax-scanners are not supported at all (as far as I know). On other platforms these SCSI-adapters are not supported. So you typically need to purchase another SCSI-adapter that is supported by your platform. See the relevant hardware FAQs and HOWTOs for your platform for more information. The UMAX-scanners do block the scsi-bus for a few seconds while scanning. It is not necessary to connect the scanner to its own SCSI- adapter. But if you need short response time for your SCSI-harddisk (e.g. if your computer is a file-server) or other scsi devices, I sug- gest you use an own SCSI-adapter for your UMAX-scanner. If you have any problems with your Umax scanner, check your scsi chain (cable length, termination, ...). See also: sane-scsi(5) FILES
The backend configuration file: /etc/sane.d/umax.conf The static library implementing this backend: /usr/lib64/sane/libsane-umax.a The shared library implementing this backend: /usr/lib64/sane/libsane-umax.so (present on systems that support dynamic loading) ENVIRONMENT
SANE_DEBUG_UMAX If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity: SANE_DEBUG_UMAX values Number Remark 0 print important errors (printed each time) 1 print errors 2 print sense 3 print warnings 4 print scanner-inquiry 5 print informations 6 print less important informations 7 print called procedures 8 print reader_process messages 10 print called sane-init-routines 11 print called sane-procedures 12 print sane infos 13 print sane option-control messages Example: export SANE_DEBUG_UMAX=8 BUGS
X-resolutions greater than 600 dpi sometimes make problems SEE ALSO
sane(7) AUTHOR
Oliver Rauch EMAIL-CONTACT Oliver.Rauch@Rauch-Domain.DE 14 Jul 2008 sane-umax(5)