Matthew Jacob <[EMAIL PROTECTED]> wrote:
> Too many people have objected. I didn't make my case clearly enough,
> but because enough people of have raised issues, the default won't
> be changed.
Too bad. I think your idea was absoultely right, and i'm rather tired
myself to have to `fix' it for every new tape drive we encounter. All
the current tape drives do support a form of physical EOD marks, where
you can't read on once you've hit EOD.
The driver could easily have faked the double-filemark at EOT, so the
API wouldn't have changed at all. (Just as you see the EOD from the
tape, finish the current transfer and return a "short read", and being
asked a second time, return a null read. Upon further attempts,
return an error.)
Btw., Matt, couldn't modepage 0x10, field "EOD defined" be used in
order to decide whether a tape drive supports a physical EOD notation,
and thus doesn't require two filemarks at EOD? If i read the standard
correctly, those fields should be set to 3 for a tape drive that
doesn't support physical EOD. (I can't verify, i don't have any such
drive.)
--
cheers, J"org
[EMAIL PROTECTED] -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
