03-14-2010
as long as nothing is mounted you are good to pull the drive.
it's all about disk cacheing.
the "safe removal" function in windows just fluches the cache and mark the file system as clean.
the same as an unmount in unix.
as for the light, windows has a driver that understand the light, and can turn it off, in unix you dont have such a nice driver.
in some versions of linux the light should turn off.
10 More Discussions You Might Find Interesting
1. Linux
Hi Folks,
I want to know how to mount usb device (cd,dvd etc) in linux,
Regards,
Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies
2. Solaris
AM TRYING TO CONNECT A USB EXTERNAL DRIVE FOR BACKUP,THE USB SLOT IS AVAILABLE,BUT I DONT KNOW IF IT IS READY WHEN I CONNECT IT,AND WHAT COMMANDS DO I NEED.
tHANKS (10 Replies)
Discussion started by: tomjones
10 Replies
3. UNIX and Linux Applications
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (0 Replies)
Discussion started by: jimthompson
0 Replies
4. UNIX for Advanced & Expert Users
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (2 Replies)
Discussion started by: jimthompson
2 Replies
5. Red Hat
Hi friends,
I wanna know how to block USB devices in my RedHat flavor Operating system.
regards,
Prakash (3 Replies)
Discussion started by: prakashkumar41
3 Replies
6. UNIX for Advanced & Expert Users
Hello all :-)
i'm not sure if its a beginner or advanced question but i have the following problem - now for some months
after building a kernel from source (2.6.36 and now 2.6.38) the /dev/sd* entries are not removed if a remove the corresponding usb disk, sd card, what ever. i'm pretty sure... (0 Replies)
Discussion started by: apfelkuchen
0 Replies
7. Debian
Hello,
I need to run an application in wine that requires write permission to a USB device. Wine users must not have root privileges. On FreeBSD this could be accomplished by adding the user to the wheel group but I am using Debian 6.0. From looking at the passwd file it is not obvious what... (6 Replies)
Discussion started by: snorkack59
6 Replies
8. UNIX for Advanced & Expert Users
In linux system when a pnp usb device is plugged in then how does the system gets a notification of it?
I mean to say in linux usb system there is usb host controller above which is host controller driver above which is usb core.
So does the host controller/usb core keeps on polling the usb bus... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
9. UNIX for Dummies Questions & Answers
Hi all
unixware 7.1.3 I'm afraid ! I connected a usb tape drive and it was automatically recognised in the device list (sdiconfig -l) and created devices in /dev/rmt (ctape1 etc.). I could successfully read and write to the device.
Then unplugged the usb cable and plugged it back in again... (0 Replies)
Discussion started by: deel
0 Replies
10. UNIX for Advanced & Expert Users
Hi,
i am developing an application on an ARM 7 architatcure with a small Linux.
i want to run tar on a usb device (~10 Mb) but it runs realy slow. the command only takes 1% of cpu usage.
is there a way to improve the tar command or is the USB-Connection the bottleneck here? (4 Replies)
Discussion started by: louisk
4 Replies
LEARN ABOUT CENTOS
sane-cardscan
sane-cardscan(5) SANE Scanner Access Now Easy sane-cardscan(5)
NAME
sane-cardscan - SANE backend for Corex CardScan usb scanners
DESCRIPTION
The sane-cardscan library implements a SANE (Scanner Access Now Easy) backend which provides access to the Corex CardScan 800c & 600c
small-format scanners.
The backend supports only grayscale and color modes and media of (theoretically) infinite length.
This backend may support other scanners. The best way to determine level of support is to get a trace of the windows driver in action, and
send it to the author.
OPTIONS
The cardscan backend supports the following options:
mode m
Selects the mode for the scan. Options are "Gray" and "Color".
CONFIGURATION FILE
The configuration file "cardscan.conf" is used to tell the backend how to look for scanners, and provide options controlling the operation
of the backend. This file is read each time the frontend asks the backend for a list of scanners, generally only when the frontend starts.
If the configuration file is missing, the backend will use a set of compiled defaults, which are identical to the default configuration
file shipped with SANE.
Scanners can be specified in the configuration file in 2 ways:
"usb 0x04c5 0x1042" (or other vendor/product ids)
Requests backend to search all usb busses in the system for a device which uses that vendor and product id. The device will then be
queried to determine if it is a cardscan scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This method is untested.
Additionally, there are two configuration options that control the protocol used by the backend:
"lines_per_block 16" (or other number from 1 to 32)
Controls the number of lines of image data which will be aquired in each pass. Older scanners will require this number set lower,
often 1.
"has_cal_buffer 1" (1 or 0)
Causes the backend to get calibration data from scanner during initialization. Older scanners do not support this request, and must
be set to 0.
ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_CARDSCAN, which enables debugging output to stderr. Valid values are:
5 Errors
10 Function trace
15 Function detail
20 Option commands
25 SCSI/USB trace
30 SCSI/USB detail
35 Useless noise
KNOWN ISSUES
The scanner does not seem to have much control possible, so the backend cannot set x/y coordinate values, resolutions, etc. These
things could be simulated in the backend, but there are plenty of command line tools.
The backend also does not send all the commands that the windows driver does, so it may not function the same.
The backend does not have the calibration or ejection options of the windows driver.
CREDITS
The hardware to build this driver was provided to the author by:
Jeff Kowalczyk <jtk a t yahoo d o t com>
SEE ALSO
sane(7), sane-usb(5)
AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
10 Feb 2010 sane-cardscan(5)