Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.wizards
Subject: Re: read(2) won't move TK50 past tape file mark
Keywords: ultrix tk50 unix tapes
Message-ID: <7001@cbmvax.UUCP>
Date: 27 May 89 14:42:15 GMT
References: <466@polyof.UUCP> <187@larry.sal.wisc.edu> <2721@helios.ee.lbl.gov> <6975@cbmvax.UUCP> <190@larry.sal.wisc.edu> <6982@cbmvax.UUCP> <191@larry.sal.wisc.edu> <6999@cbmvax.UUCP> <2738@helios.ee.lbl.gov>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 18

In article <2738@helios.ee.lbl.gov> envbvs@epb2 (Brian V. Smith) writes:
> In article <6999@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
> >
> >Completely different controller/driver no?
> 
> But the same manual entry/system call.  If there is supposed to be a
> difference in the different controllers/drivers/tape drives then it should
> be stated.  It simply looks like a bug.

Yes, of course it's a bug.  Inconsistancies are bugs.  You now have an
explanation, a work-around and a valid problem description.  If you consider
it a bug, the next step is to file an "SPR" with DEC or otherwise follow up
the problem through DEC software support channels.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)