On Mon, 2 Aug 1999, Kai Makisara wrote:
> The Linux SCSI tape driver does not support lseek() (and I have not seen
> it on any other Unix either). The basic reason is that the data on a tape
> is addressed as blocks and so lseek() does not make sense.
So, why isn't fseek() failing with an error (I haven't tried seek()) ?
That wouldn't be the best comportment ?
The only case where fseek() or seek() can not return an error is
if the user wants to go forward: in that case, seek() can be implemented
as dummy reads, and not return an error. But if the driver doesn't
support that, shouldn't it simply return an error also ?
> forward and backward using the MTIOCTOP ioctl functions FSR and BSR. If
> the drive supports direct block addressing (which is your case), you can
> use the MTIOCTOP function MTSEEK to to position the tape and the MTIOCPOS
> ioctl to get the current position.
Thank you very much (that's probably what mt fsf|bsf|bsr|fsr is using).
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
