[SunRescue] mt -f status vs. dmesg

[Mike Hebel]

OK.

Got the st.conf on my E450 configured correctly and re-built the kernel.

The mt -f /dev/rmt/x status for each device (0,1,2 respectively) looks
correct:

Archive Python 4mm DAT Stacker tape drive:
   sense key(0x0)= No Additional Sense   residual= 0   retries= 0
   file no= 0   block no= 0

HP DDS-3 4MM DAT tape drive:
   sense key(0x0)= No Additional Sense   residual= 0   retries= 0
   file no= 0   block no= 0

SONY AIT 8mm tape drive:
   sense key(0x0)= No Additional Sense   residual= 0   retries= 0
   file no= 0   block no= 0

But the dmesg output looks like so:

{truncated}
st11:	<Archive Python 4mm Helical Scan> st11 at pci1000,f1: target 4 lun 0
st11 is /pci at 1f,4000/scsi at 2/st at 4,0
st12:	<HP DDS-3 4MM DAT> st12 at pci1000,f1: target 5 lun 0
st12 is /pci at 1f,4000/scsi at 2/st at 5,0
st53:	<Vendor 'SONY    ' Product 'SDX-300C       '> st53 at pci1000,f7:
target 4 lun 0
st53 is /pci at 6,4000/scsi at 2,1/st at 4,0

Is this normal or should they both match?  The output from dmesg appears the
same as if I had not edited the st.conf file.

My gut feel says these should match what is in the st.conf but I'm not sure.
Can anybody confirm or deny this for me?

Thanks!

Sincerely,

Mike Hebel

BTW - A good couple of references on the st.conf file if anyone is looking
for them are Infodocs number: 21513 (Explains how exactly to configure the
st.conf file) and 18010 (Explains how to - most of the time - re-load the
tape modules without rebooting)  Both very cool docs IMHO.  You may need a
Sunsolve account to get to them though but I'm not too sure about that.