More info/output:

This is from one of my OS guys:

*I used 'udevinfo' to determine the serial nos. for the various tape drives
when compiling the rules file we discussed.  Here's an example for finding
the serial no. of a tape drive at '/dev/IBMtape2':*

RedHat 6

*udevadm info --attribute-walk --name /dev/IBMtape2 | grep -e serial_num -e
ww_port_name*

*
*
RedHat 5

*      udevinfo -a -p `udevinfo -q path -n /dev/IBMtape2` | grep -e
serial_num -e ww_port_name*
*
      SYSFS{ww_port_name}=="0x500507630F5B7706"
      SYSFS{serial_num}=="000007857392"

*
My other OS guy is a little more creative with scripting/awk and such:

[root@moon ~]# for ((i=0; i<17; i++)); do udevinfo -q all -n IBMtape$i; done
P: /class/lin_tape/IBMtape0
N: IBMtape0
S: lin_tape/by-serial/000007857569
P: /class/lin_tape/IBMtape1
N: IBMtape1
S: lin_tape/by-serial/000007857540
P: /class/lin_tape/IBMtape2
N: IBMtape2
S: lin_tape/by-serial/000007857392

[snippage for brevity]

HTH



On Wed, Apr 24, 2013 at 4:33 PM, Zoltan Forray <zforray AT vcu DOT edu> wrote:

> These are our /etc/udev/rules.d
>
> [root@sun rules.d]# cat 98-lin_tape.rules
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A401C",SYMLINK="lin_tape/by-serial/0000078A401C"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A3C78",SYMLINK="lin_tape/by-serial/0000078A3C78"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007857440",SYMLINK="lin_tape/by-serial/000007857440"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007857392",SYMLINK="lin_tape/by-serial/000007857392"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007868704",SYMLINK="lin_tape/by-serial/000007868704"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007868729",SYMLINK="lin_tape/by-serial/000007868729"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007857569",SYMLINK="lin_tape/by-serial/000007857569"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007857540",SYMLINK="lin_tape/by-serial/000007857540"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A08AB",SYMLINK="lin_tape/by-serial/0000078A08AB"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A073E",SYMLINK="lin_tape/by-serial/0000078A073E"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A08A1",SYMLINK="lin_tape/by-serial/0000078A08A1"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007876472",SYMLINK="lin_tape/by-serial/000007876472"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007876475",SYMLINK="lin_tape/by-serial/000007876475"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="000007876473",SYMLINK="lin_tape/by-serial/000007876473"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A4011",SYMLINK="lin_tape/by-serial/0000078A4011"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A70E8",SYMLINK="lin_tape/by-serial/0000078A70E8"
> KERNEL=="IBMtape*[!n]",
> SYSFS{serial_num}=="0000078A70E9",SYMLINK="lin_tape/by-serial/0000078A70E9"
> [root@sun rules.d]#
>
>
>
>
>
> On Wed, Apr 24, 2013 at 3:58 PM, Lee, Gary <GLEE AT bsu DOT edu> wrote:
>
>> Running tsm 5.5.4 on suse linux sles9 under vm.
>> Lin_tape version 1.19.0
>>
>> I am trying to get persistent names attached to our 3592 tape drives with
>> udev rules.
>>
>> Cannot seem to get them to recognize.
>>
>> Can supply a udevinfo output and .rules file.
>>
>> Any ideas welcome.
>>
>
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html