Mick <[email protected]> wrote: > > > If you call cdrecord (release 3.00): > > > cdrecord -scanbus > > > > > > or > > > > > > cdrecord -checkdrive > > > > > > and it finds a drive, then there is a bug in k3b. > > > > al...@isba ~ $ cdrecord --checkdrive > > Cdrecord-ProDVD-ProBD-Clone 3.00 (x86_64-unknown-linux-gnu) Copyright (C) > > 1995-2010 Jörg Schilling > > Linux sg driver version: 3.5.27 > > Using libscg version 'schily-0.9'. > > No target specified, trying to find one... > > Using dev=1000,0,0. > > This looks fishy ... > > On mine it is: Using dev=1,0,0.
This is the result of having a non-orthogonal driver model for SCSI devices in Linux. Some drivers are fully integrated into the SCSI sub-system and receive low SCSI bus numbers from libscg and other drivers are separated and are mapped to high SCSI bus numbers. Some drivers are even accessible from two or more competing drivers. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
