Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!epb2!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.unix.wizards
Subject: Re: read(2) won't move TK50 past tape file mark
Keywords: ultrix tk50 unix tapes
Message-ID: <2738@helios.ee.lbl.gov>
Date: 27 May 89 02:58:03 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>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2 (Brian V. Smith)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 18

In article <6999@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
>In article <191@larry.sal.wisc.edu> jwp@larry.sal.wisc.edu.UUCP (Jeffrey W Percival) writes:
>> 
>> I should have also mentioned:  the sticky EOF occurs on the MVII TK50's,
>> but *not* on the 6250-BPI reel-to-reel drives on the very same machines.
>> 
>> So it's not even a workstation/microvax difference, but a difference
>> between units on the same machine!  Nice portability, eh?
>
>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.
_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
We don't need no signatures!