Finders, Keepers
Caveats
Although USB/IP is pretty awesome, there are some disadvantages you may want to consider before deploying it for everyday use. For starters, as it is underused, many distributions have scatty support for the USB/IP tools usbip and usbipd. Many distros include old versions, and different versions have different parameters. Some versions don't work at all.
Secondly, you have to attach and detach devices as root, which makes it inconvenient and a bit dangerous. Also, while a device is attached, it is blocked for other clients, and you have to remember to detach it when you have finished using it.
If you have a large number of client machines, by using USB/IP, you will have to install drivers onto each and every one of them. If you want to share a printer, CUPS may be the way to go, as you only have to install and maintain drivers on the server. If your scanner plays well with SANE's network system, this would also be the best way of cutting back on installing, configuring, and maintaining drivers.
Make It Better
That said, you can make USB/IP much friendlier if, for example, you load modules at boot time both on the server and client and turn usbip into a service on the server.
USB/IP also allows you to use a Raspberry Pi as a server for devices – even if the Pi doesn't understand them. You see, many vendors with proprietary drivers only provide drivers for Intel-based machines and do not supply any for the Pi, since it is an ARM-based computer. This is the case of the printer/scanner that kicked all of this off. With USB/IP, however, you can still use the Pi as a printer/scanner server because it doesn't actually have to load any drivers: The Pi just has to forward the whole USB connection to the client machine, where the driver is installed.
Is that cool or what?
Infos
- XSane: http://xsane.org/
« Previous 1 2
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
US / Canada
UK / Australia