From owner-freebsd-hackers Tue Sep 9 11:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26790 for hackers-outgoing; Tue, 9 Sep 1997 11:51:17 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26780 for ; Tue, 9 Sep 1997 11:51:13 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA29705; Tue, 9 Sep 1997 11:49:20 -0700 (MST) From: Terry Lambert Message-Id: <199709091849.LAA29705@usr04.primenet.com> Subject: Re: Tape question To: joerg_wunsch@interface-business.de Date: Tue, 9 Sep 1997 18:49:20 +0000 (GMT) Cc: hackers@FreeBSD.ORG, handy@sag.space.lockheed.com In-Reply-To: <19970909162235.DF18120@ida.interface-business.de> from "J Wunsch" at Sep 9, 97 04:22:35 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I once wrote: > > > This must be a problem with the Exabyte then. It works fine for me, > > with a Tandberg TDC4222, and a QIC-525 cartridge (QIC-150, of course, > > doesn't work since it's fixed-length blocking). > > I've verified with this test program that it works on a DAT drive as > well, with the ahc(4) driver in this case (and on 2.2-stable). I'm *really* not trying to be contentious here, but I have to ask... How did you verify that the BSD device driver was not padding records on write? AFAIK, the only way to do that is with a machine that you know doesn't do it writing the test tapes. Like a SunOS box. That said, Sun is well known to rewrite proms for no good reason (ie: Toshiba 3401B CDROMs and CDROMs as boot devices). Maybe we are both looking in the wrong place for the problem? I've done it before... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.