In message <20031012220230.GA20939@panzer.kdm.org>, "Kenneth D. Merry" writes:
>Back when the cd(4) driver used the old slice code, it had a function,
>cdfirsttrackisdata(), that figured out whether the first track was an audio
>or data track. It would set the flags in the disk structure accordingly to
>tell the slice code whether or not to attempt to read a disklabel from the
>The code in -stable still works that way.
>My guess is that we need something similar again to tell GEOM not to
>attempt to read the first sector of the CD when it's not a data CD.
Or do what the atapi-cd code does: indicate the true sector size
(2352 bytes) and use whatever "read audio" command is appropriate
for that situation.
I'm somewhat  unhappy that the atapi-cd and the scsi_cd present
multitrack CD's in two different ways, and from a POLA  perspective
I must say that the /dev/acd%dt%02d devices do make a lot of sense.
 Not "terribly" because I seldomly use it myself, but the
inconsistency still bothers me.
 Your POLA may vary.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.