Griff Miller <com> wrote:
Pretty much. It's not the "two eofs in a row" that prevents the reads.
It's the fact that after you write *anything* on the tape, then close,
the tape drive will write a special mark on the tape (eom) after the
write. The drive will not advance past that mark.
By one eof, yes. You have to write *something* after the 'd' dataset,
and that something will take some space on the tape.
If you knew that something was there, you could backup over it, and
begin writing on top of it to get your (tiny) space back. That might be
more logic than you want over simply going to eom and writing there.
If you have your two consecutive EOFs, then you'd have to issue an extra
fsf to get past the second one, even though there is no data between
Darren Dunham com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >