Free usb 30 software for linux

LCD2USB is a open source/open hardware project. LCD2USB was meant to be cheap and to be made of easily available parts.
It is therefore based on the Atmel AVR Mega8 CPU and does not require any difficult to obtain parts like separate USB controllers and the like. The total cost (without display and pcb) are about 5 to 10 Euros. LCD2USB currently comes with a simple demo application that works under Linux, MacOS X and Windows. I still have several spare PCBs, please email me if you are interested.
LCD2USB makes use of several projects to achieve this goal. LCD2USB is based on:
LCD4LINUX, a great framework to use small LCDs with linux, AVR-USB, a pure software implementation of USB for the AVR plattform, USBtiny, another software usb implementation for the AVR, and Peter Fleurys LCD routines for the AVR.
The hardware of the LCD2USB interface consists of the Atmel AVR Mega8 CPU, a cheap and easy to obtain microcontroller with 8 KBytes flash (of which ~3k are used in this application) and 2 KBytes RAM. The processor is surrounded by few parts, mainly connectors to interface to the PC and the LCD.
A power LED (LED1) indicates that the system is powered via USB. The system clock is derived from a 12Mhz crystal. This frequency is necessary due to the fact that the software USB implementation requires a precise timing with respect to the USB.
Enhancements:
- Added usbtiny based version due to user request
- AVR-USB version 1.07, USBtiny version 2.07

libusb is a library to provide userspace access to USB devices. libusb project supports Linux 2.6/2.4/2.2, FreeBSD/OpenBSD/NetBSD, and Darwin/MacOS X.
Operating System support
- Linux
- FreeBSD
- NetBSD
- OpenBSD
- Darwin
- MacOS X
Building:
It should be as simple as running these two commands:
./configure
make

usb-mount project provides desktop integration for systems using the hotplug scripts and the KDE desktop. It automatically mounts and unmounts USB storage partitions and modifies the users desktop, via the addition of icons representing USB storage device partitions.
The user can interact with the storage device by opening the desktop icons to reveal the folders corresponding to each partition. Each partitions mount status can be altered by using icon control options.
These scripts work for me on Fedora Core 2 and Redhat 9. Several people have reported that they can be made to function on many other Linux distributions with minor configuration changes and some editing.
To get them to work on your system you may need knowledge of Linux and shell scripting. If the scripts dont work out of the box, you should look for errors in /var/log/messages (or where ever your system log is kept). If you are not comfortable with reading logs and editing scripts - perhaps these scripts arent for you.
I no longer have any Linux systems with 2.4 kernels, I think the scripts will still work. All recent modifications have only been tested on Fedora Core 4 running kernel 2.6.
Many distributions are now adequately handling usb - so I havent spent much time improving usb-mount. If anyone wants to fork a new version, feel free. The new kernel, dbus, etc should make it quite easy to create a simpler script from scratch.
Enhancements:
- More fixes for newer kernels/distibutions that take longer to setup usb devices;
- Handle flash card readers that have more than one device (thanks to Edward);
- Ignore non usb-storage devices (thanks to Wolfgang Klein).

vp-usb-lock is a Linux kernel driver and PAM module that utilizes the PC wireless USB lock and makes it possible to use it as authentication method for your Linux box.
It is easy to install, but needs access to the sources of the kernel and PAM to build correctly. It has been tested under Fedora Core 2 with a custom made 2.6.7-1.494.2.2 kernel, but it should also work with other kernel versions and distributions.
Enhancements:
- A lock daemon was added.
- A compilation error that was introduced lately by some changes to the Linux kernel was fixed.
- Support for kernel 2.4.x versions was added.

Ukop is a free Linux program used to copy or back-up disk files to a USB stick. The project copies only new or modified files since the last backup, and is therefore quite fast.
A GUI is used to navigate the file system to include or exclude files or directories at any level. Backup jobs can be saved for later re-use.
New or deleted files are normally handled automatically, without re-editing the backup job. Files can be selectively restored using a GUI. Ownership and permissions are also restored, even if the USB stick uses a FAT file system.
ukop is a Linux utility program for copying or backing-up disk files to USB sticks or "thumb drives", which are fast, non-volatile, removable memories that function like disk drives. Ukop is a free program licensed under the GNU General Public License.
The program is taylored for use with USB sticks, but any medium supporting disk functionality (a Linux file system such as ext2 or FAT) can be used. You can also use any ordinary directory for backup storage. For DVD media please see the sister program dkop.
You can select files to be copied using a GUI. You can navigate through the file system and select files or directories to include or exclude at any level in the directory hierarchy. These choices can be saved in a backup job file to automate recurring backups. If files are added or deleted within an included or excluded directory, the next backup will include these changes automatically. You do not need to revise the backup job unless you add new directories or make new exceptions.
Two kinds of backup are available: incremental and accumulate. An incremental backup copies all disk files specified by the backup job to the USB stick, except those that are already there and have not been modified since the last backup. Also, files on the USB stick that have no corresponding disk file are deleted. When done, the USB stick will exactly match the disk. An accumulate backup is like an incremental backup, but unmatched files are NOT deleted.
USB stick media can be verified three ways: full, incremental, and thorough. A full verify reads the entire USB stick and reports any files having read errors. An incremental verify reads only those files that have been newly recorded by a preceding backup job. This is usually much faster while still offering a high level of security. A thorough verify reads every file on the USB stick and makes a bytewise comparison with the corresponding disk file. This is normally not necessary, but provided as a check that all hardware and software is working correctly.
You can report all files in a backup job, or all files on a USB stick medium. You can search for files using wildcards. You can compare a USB stick with a backup job: list all files that have been created, deleted, or modified since the USB stick backup was made.
For disaster recovery or file transfer, ukop has a file restore capability. You can select and restore USB stick files to their original directories or anywhere else. Owner and permissions are are also restored, even if the USB stick uses a FAT file system.
Speed: Incremental backup and verify can be done in a few seconds if updated files are less than a few megabytes. Otherwise the USB stick I/O speed determines the time required, and this can range from 1 to 20+ megabytes per second.
The download tar file contains the source code, a binary executable that may work out of the box, and a complete user guide, including technical information about how ukop works.
Enhancements:
- if an empty directory is deleted in the backup medium and its parent becomes empty, then delete the parent also
- if a file fails to copy, report the error in backup only, not in verify
- new technical note about file name limitations for vfat formatted media

Device::USB::FAQ Perl module contains Frequently Asked Questions for Device::USB.

This is an attempt to answer some of the frequently asked questions about the Device::USB module.

Which platforms does Device::USB support?

Device:USB supports any platform that libusb supports. This list currently includes Linux, FreeBSD, NetBSD, OpenBSD, Darwin, and MacOS X.

There is a port of the libusb library to the Windows environment called LibUsb-Win32. Because I dont have a development environment for testing this library, Device::USB does not yet support this library.

Do I have to use Device::USB as root?

By default, access to the USB devices on a Unix-based system appear to be limited to the root account. This usually causes access to most of the libusb features to fail with a permission error.

Using the Device::USB module as root avoids this feature, but is not very satisfying from a security standpoint. (See the next question for more options.)

How do I enable use of Device::USB as a non-root user?

Some of the attributes of USB devices are available to non-root users, but accessing many of the more interesting features require special privileges. According to the libusb source, the open() function requires either device nodes to be present or the usbfs file system to be mounted in specific locations. Those places in order are:

1)
/dev/bus/usb - pre-2.6.11: via devfs / post-2.6.11: via udev
2)
/proc/bus/usb - usbfs

Look in both locations on your system for which of these two methods your libusb will use.

No matter which method your system uses, you will probably want to create a separate group to control access. Run this command to add a system group:

addgroup --system usb

or

groupadd --system usb

You can then add users to that group to allow access to your usb devices.

gunzets supports Gunze touch panels under Linux and XFree86. Supported panels are the serial, PS/2, and USB devices.
All devices are supported by means of an XFree86 module, and the USB device via a kernel module as well. Both XFree version 3.3.6 and 4.x are supported, as well as kernel 2.2 and 2.4. The driver is supported by Gunze USA.
Version restrictions:
- Debouncing is only supported for XFree 4.0 (not 3.3.6).
- A bounce event breaks smoothing processing
- Support for multi-screen operation is not supported.
Compiling
In order to successfully load the module you need to have the following facilities compiled in your kernel or loaded as modules:
- usb generic support (usbcore.o)
- a usb host controller driver (usb-ohci.o o usb-uhci.o)
- support for misc devices like the ps2 mouse (misc.o)
- the input mechanism (input.o)
To compile the driver just make. If your 2.4 or 2.2 kernel headers are not available from /usr/src/linux/include then specify KERNELDIR to point to your kernel source directory, either on the make command line or in the environment. For example:
make KERNELDIR=/usr/src/linux-2.4
To load the driver, use insmod:
insmod ./gunzets.o
To use the input mechanism, specify it on the command line:
insmod ./gunzets.o use_input=1
To automatically create the entry point in /dev (needed if you are not using the input mechanism) run the gunzets_load script instead:
./gunzets_load
Instllation
To install the module to the proper places you can run make install. You may also wish to copy gunzets_load from /usr/local/bin to /etc/rc.d/init.d or /etc/init.d and create a proper symbolic link for automatic load at boot.