Sponsored Content
Full Discussion: Device serial number
Operating Systems Linux Device serial number Post 302259969 by noratx on Wednesday 19th of November 2008 10:56:42 AM
Old 11-19-2008
Device serial number

Hey!

I'm trying to figure out a sollution for a problem I have at my company with an Iomega MiniMax 500 GB USB disk.

If i run cat /proc/bus/usb/devices
I get this information:

Code:
T:  Bus=01 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#=  5 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=059b ProdID=0373 Rev= 1.00
S:  Manufacturer=Iomega
S:  Product=External HD
S:  SerialNumber=9675FFFFFFFF
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms

We have 13 of this disks, and 2 disks which gives the exact same SerialNumber.

The problems here now, is that our operations with this disks, require us to be able to destinguish these disks by the serialnumber to identify which disk is connected where (We send an empry disc to one facility, they fill it up with data, send it back to us, we archive the data, send it to another facility, they archive the data, they send it back to us and we empty the disk and restart the process.) We need to follow the disks to know in what facility/what country it is connected and so on.

According to Iomega, they could not give us any support for this for some reason.

So, what I need to know, is there a way to either change the serial, or to "work around" it.
The exact usage of the serial is to create a one-to-one relationship between the serial and an logical name.
(In this case, the serial 9675FFFFFFFF should have a one-to-one relationship to the name "IOMEGA-USB-008").

I started to think that we maybe could work around the problem by "inventing" an own serial, like "serial+randomnumber=result | md5sum $result | awk -F '{print $1}'" (now this is not a working code, only a thought about how to work around the problem).
But I don't think this would work since it would not be possible to re-create the same self-invented serial number due to the random numbers.

So, as I have come to a total breakdown in finding out a sollution to this problem.. can any of you shed some light over my problem?

Many thanks in advance,
/Rickard
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

serial number for E3500

just wanted to know the serial number of my machine E3500 with Solaris 8 installed.Does any one who what's the command that i can use when the OS is running?( not with the Banner Command!) (3 Replies)
Discussion started by: i2admin
3 Replies

2. Shell Programming and Scripting

Tape Serial Number

Hello Experts, I've got a shell script that makes the backup of the files that i want. I also have this script showing the amount of files backed up and in witch folders they are. It's only missing one thing. I got all the information beeing stored in a text file and all i've got to do is to... (6 Replies)
Discussion started by: jorge.ferreira
6 Replies

3. UNIX for Dummies Questions & Answers

serial port device path

hi. Im trying to install a switch. And the manual says i should type a command including a SerialPortDevicePath. which is the filepath to serial port used for connection. However.. nothing about how to find this info. Could anyone help me where to find this path? thx mr.T (6 Replies)
Discussion started by: tyskertøs
6 Replies

4. Programming

Accessing device with Prolific USB-serial controller.

I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac. After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies

5. Solaris

Serial number

Hi Solarizer ;) I have face the difficulties of gathering information about the serial number of sun machine. i think its can do so easy while the machine is just one or two. But i have to administrate hundreds of sun machine. Any body knows how to gather this information by the command ? ... (4 Replies)
Discussion started by: tpx99
4 Replies

6. Ubuntu

Ubuntu 9.04 Serial application to telnet to serial device

Hello! I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies

7. Programming

Problem with read data from serial device

I have problem with C programming. I want to send & receive data through serial communication. I send data(command) to device to get data from device but when receive data, it can't get altogether of data. It get only some data. What should I do to get altogether of data? If all of... (7 Replies)
Discussion started by: noppon_s
7 Replies

8. SCO

Modifying serial printers device

I am trying to change one of my serial printers from /dev/ttyr002 to /dev/ttyr014: lpstat -s device for check3: /dev/ttyr002 device for check4: /dev/ttyr002 I changed the tty setting for check3 in: /etc/printcap /var/spool/lp/admins/lp/printers/check3 to /dev/ttyr014 Then I get:... (4 Replies)
Discussion started by: herot
4 Replies

9. Shell Programming and Scripting

Read line from serial device with BASH

I'm new to Linux (Ubuntu 16.04), and very new to BASH scripting. I have a Numato 8-channel USB GPIO device, which is a DAQ that appears in the system as a serial port. In Linux it appears as ttyACM0. I can easily manipulate a GPO with, for example: echo "gpio set 7" > /dev/ttyACM0 ...followed... (12 Replies)
Discussion started by: Chalk-X
12 Replies
Device::USB::FAQ(3pm)					User Contributed Perl Documentation				     Device::USB::FAQ(3pm)

NAME
Device::USB::FAQ - Frequently Asked Questions for Device::USB SYNOPSIS
perldoc Device::USB::FAQ DESCRIPTION
This is an attempt to answer some of the frequently asked questions about the Device::USB module QUESTIONS
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 don't 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. DEVFS / HOTPLUG TODO UDEV If you use Debian/Ubuntu, look in the /etc/udev/permissions.rules file. If you want to allow global access to all usb devices, make this change: Change this: SUBSYSTEM=="usb_device", MODE="0664" To this: SUBSYSTEM=="usb_device", MODE="0664", GROUP="usb" After you reboot, all usb devices will inherit the mode and group specified. If you want to only change permissions for certain devices, you can add this on one line and adjust the product and vendor IDs: SUBSYSTEM=="usb_device", GROUP="usb", SYSFS{idVendor}=="1234", SYSFS{idProduct}=="1234" USBFS The usbfs defaults to root as the user and group. This can be changed in the /etc/fstab by adding the following on one line: none /proc/bus/usb usbfs noauto, listuid=0,listgid=118,listmode=0664, busuid=0,busgid=118,busmode=0775, devuid=0,devgid=118,devmode=0664 0 0 The value 118 in the above should be replaced with the group id of your usb group (created above). The list* values are to allow listing devices, the bus* is to control access to the bus directories and the dev* values control access to the device files. This approach does not allow the kind of granular permission that the udev approach gives, so it is all or nothing unless permissions are changed programmatically. If your /etc/fstab file already has a line for /proc/bus/usb, add the options above to the line that is already there rather than adding the new line. For example, you would change usbfs /proc/bus/usb usbfs noauto 0 0 to usbfs /proc/bus/usb usbfs noauto, listuid=0,listgid=118,listmode=0664, busuid=0,busgid=118,busmode=0775, devuid=0,devgid=118,devmode=0664 0 0 Once again, this needs to be all on one line with the "" characters removed. SEE ALSO
Device::USB and the "libusb" library site at <http://libusb.sourceforge.net/>. AUTHOR
G. Wade Johnson (wade at anomaly dot org) Paul Archer (paul at paularcher dot org) Houston Perl Mongers Group ACKNOWLEDGEMENTS
Thanks go to various users who submitted questions and answers for the list. In particular, Anthony L. Awtrey who contributed the first FAQ answer. COPYRIGHT &; LICENSE Copyright 2006 Houston Perl Mongers This document is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2006-09-03 Device::USB::FAQ(3pm)
All times are GMT -4. The time now is 01:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy