No prizes here, so I had to do it myself :-( On a Sun running 4.1.4 stock
mt identifies an Exabyte 8505 as an 8500. This is because st_conf.c and stdef.h
have entries for the 8505 with the relevant SCSI command bytes for the various
operating modes. However, both models are identified as the #defined type
ST_TYPE_EXB8500 which presumably is used by mt to key into its internal table
of drive descriptions - I copped this when I realised that the kernel bootup
message identifies the drive as st1: <Exabyte EXB-8505 8mm Helical Scan> - the
string between <> is what's in st_conf.c for the drive but that mt identifies
the drive as an Exabyte EXB-8500 8mm tape drive: . I was deluding myself
that mt somehow had accesss to the kernels table of drive types but 't'ain't
so. Interestingly, Solaris 2.5's mt identifies the 8505 as an 8500 also. And
yes, I know I'm just being picky :-)
The reason why my 4.1.3 machine just identified the 8505 as a generic SCSI tape
drive was that I was using a modified st_conf.c and stdef.h to include support
for the 8505 and I hadn't used ST_TYPE_EXB8500 - I'd picked a number and #defined
it as ST_TYPE_EXB8505 - a singularly useless exercise, as nothing else recognises
my assigned number :-(
Kindest regards,
Niall O Broin
UNIX Network Administrator nobroin@esoc.esa.de
Ground Systems Engineering Department Ph./Fax +49 6151 90 3619/2179
European Space Operations Centre, Darmstadt, Germany
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:57 CDT