From owner-freebsd-scsi Fri Dec 17 3:16:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from meloghost.melog.de (meloghost.melog.de [193.155.17.3]) by hub.freebsd.org (Postfix) with ESMTP id 2DE6F14FCD for ; Fri, 17 Dec 1999 03:16:42 -0800 (PST) (envelope-from hf@Melog.DE) Received: from janus (janus.melog.de [193.155.17.21]) by meloghost.melog.de (8.9.3/8.9.3) with ESMTP id MAA24457; Fri, 17 Dec 1999 12:16:24 +0100 Message-Id: <4.2.2.19991217120438.00c89250@meloghost.melog.de> X-Sender: hf@meloghost.melog.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 17 Dec 1999 12:16:38 +0100 To: mjacob@feral.com From: Hauke Fath Subject: Re: filemarks? Cc: Hauke Fath , Joerg Wunsch , freebsd-scsi@FreeBSD.ORG In-Reply-To: References: <4.2.2.19991216175352.00b83250@meloghost.melog.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:34 16.12.99 -0800, Matthew Jacob wrote: >In my opinion, oft stated, it's only devices that cannot determine >physical eot that need two filemarks. As far as I know, only 1/2" Reel >tape drives have this property. Sounds quite sane to me. Better to quirk half-inch reel tape than the rest of the tape world. ;) What were the counter arguments? Like you said, userland does not (should not) care about the details of EOD detection. How does an application learn about EOD? By an error code? A while back, I saw you advocating fixed block sizes for QIC drives. Can you explain your reasons? I have seen many problems with this default (interoperability) and have hacked the NetBSD st.c to default to variable blocksize. hauke -- Hauke Fath Tangro Software Components GmbH D-69115 Heidelberg hf@Tangro.DE Ruf +49-6221-13336-35, Fax -21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message