From owner-freebsd-current Sat Nov 20 12:42:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 59FBC14C88 for ; Sat, 20 Nov 1999 12:42:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA23071; Sat, 20 Nov 1999 12:43:04 -0800 Date: Sat, 20 Nov 1999 12:43:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Joerg Wunsch Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 SCSI Tape Driver- Okay, Okay, you win.... In-Reply-To: <199911202021.VAA11447@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Nov 1999, J Wunsch wrote: > Matthew Jacob 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.) Sigh. Every time I've suggested this in both FreeBSD and NetBSD I've been shot down with that too. > > 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.) Yes, I've though about this. I should indeed check. But I suspect that there is breakage with a number of drives here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message