[continued from previous message]   
      
   >     echo "Gets the serial number of a device from SMART data. Ask only   
   one disk at a time (Yotta bug)"   
   >     exit   
   > fi   
   >   
   > THEDISK=$1   
   >   
   > # Ask twice, the first one is a cached answer that has to be disregarded.   
   > smartctl -d sat -a $THEDISK | grep "Serial Number" 1>/dev/null   
   > smartctl -d sat -a $THEDISK | grep "Serial Number"   
   >   
   >   
   >   
   > Isengard:~ #   
   > ·····················++-   
   >   
      
   The log makes it sound like it is using a smaller CDB definition for some   
   commands, and then switches to the 16 byte CDB when it finds a "very big   
   device".   
      
   I found this in a Google:   
      
      "48 bits are for toys. SCSI's 16-byte CDBs use 64-bit logical block   
   addresses. This has been the case   
       since the 1990s, and implementing the read(16) and write(16) commands has   
   been mandatory for   
       DASD targets since the turn of the century. As I wrote a decade ago this   
   puts the maximum size supported   
       by the SCSI protocol in the ZiBs. - JdeBP Apr 15, 2015 at 16:11"   
      
   I'd expect both BOT and UAS to use CDBs and the SCSI stack,   
   because as far as I know, that's what is used for "foreign devices".   
   Anything which was not a ribbon cable (in the old days), or is not   
   SATA in the current era, will likely see CDBs used. They're also   
   used (Mode Sense) for optical drives.   
      
   If it supports 16 byte CDB, it should be using it always.   
      
   The advantage of BOT over UAS, was BOT was supposed to work, and   
   UAS was not supposed to work. For some definition of the correct   
   firmware version.   
      
      Paul   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)