>I have added what I've been sent as entries to cmtp.conf (sp? sorry I'm
I may have missed the beginning of this thread so I'm not exactly clear
what you're tyring to accomplish.
Who sent you those cmtp.conf updates? I don't know where the idea
originated that it's possible to add entries to cmtp.conf for new tape
drives on Solaris x86 . That's a feature of the SPARC st driver not the
x86 cmtp or sctp drivers. There currently isn't any method for a user
to add a new tape drive to cmtp (or sctp). Currently, the table of
known drives is compiled into sctp and can only be modified via a Driver
Quote:>sending this from a non-Solaris OS at present) and still see an 8500
>when I do mt status.
The mt program has a bug. It doesn't accurately report the drive type.
If you hooked up the drive and did a reconfigure reboot the drive should
be usable. If it's not a support model you won't be able to use any
of its "optional" features.
Quote:>Can I change this? Is it in fact getting it all wrong?
Mt is getting it wrong. Sorry, you can't change mt, cmtp or sctp.
Quote:>I have managed to both read and write tars and dumps so far, so I am at
>least talking to the drive.
All SCSI-2 compatable drives should work in their default states/modes
without adding their configurations to the Solaris x86 sctp driver. You
only have to add the tape drive to the configuration table if you
need/want to use any of the optional SCSI-2 features such as variable
length records, backspace record/file, alternate densities, unload the
tape, etc. The default configuration is sort of like the very old
Archive Viper QIC-150 drive.
Use a tape drive which is on the Solaris x86 2.4 Hardware Compatibility
List or wait for the Driver Update that adds whatever drive you're
trying to use.