From owner-freebsd-arch Tue Dec 21 9: 3:59 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 5DA8E14F28 for ; Tue, 21 Dec 1999 09:03:55 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id SAA22443 for ; Tue, 21 Dec 1999 18:03:51 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA27375 for freebsd-arch@freebsd.org; Tue, 21 Dec 1999 18:03:51 +0100 (MET) Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 18D7C14F28 for ; Tue, 21 Dec 1999 09:03:35 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id QAA21135; Tue, 21 Dec 1999 16:57:48 GMT (envelope-from rb) Message-Id: <3.0.6.32.19991221165541.007b7480@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 21 Dec 1999 16:55:41 +0000 To: Stephen McKay , Bruce Evans From: Bob Bishop Subject: Re: filemarks? Cc: Matthew Jacob , "Rodney W. Grimes" , freebsd-arch@freebsd.org, Greg Lehey , Thomas David Rivers , Joerg Wunsch , Hauke Fath , syssgm@detir.qld.gov.au In-Reply-To: <199912211014.UAA21880@nymph.detir.qld.gov.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:14 PM 12/21/99 +1000, Stephen McKay wrote: >[...] >We should consider the nature of programs that will write to tape. How >should "cat" work when writing a tape? I expect it would write until >physical end of media with this model and run the 1/2" tape right off the >reel. That would be fine by me since "cat" is not a normal tape writing >program. On 1/2" tape, EOT was a reflective marker on the back of the tape. You were supposed to have something like 30ft of tape after the marker, at least 10ft of which had to be writeable. So the drive could complete the block being written at EOT, and still write two tape marks thereafter (but data writes would fail IIRC). Only a broken drive (not unknown) would let you run the tape off the reel. ISTR (and you will appreciate this is a while ago) that drivers would return the block size for the block written over EOT and zero for any subsequent data write attempt. Closing the file wrote two tape marks. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message