Subject: Re: st driver (was Re: restore doesn't report filesystems on null
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Greywolf <firstname.lastname@example.org>
Date: 01/23/2000 16:43:43
On Sun, 23 Jan 2000, der Mouse wrote:
# >> [dump and restore vs empty hostnames]
# > Even if I *do* have a table of contents, it's kind of painful due to
# > the st driver not working properly (it counts the EOF mark as a
# > separate file, but that's another can of worms).
# Are you sure this is a bug in the driver? Often - I see this with tar,
# for example - the program reading from the tape reads the last record
# of the tape file and exits, not even attempting to read further. Then,
# of course, a following open and read hits the tape mark immediately,
# beacuse it wasn't read and thus wasn't consumed before.
# I don't know dump format well enough to know how plausible this is in
# that case. But if this is what's happening, it's not a driver bug.
It seems to happen in dd as well. This indicates to me that the extra EOF
marker is exactly that (extra), and since the driver handles the EOF writing
(the programs should NOT explicitly be writing EOF marks unless they're
doing something extra special), that classifies it to me as a (dr. evil
impression -- don't forget the finger-quotes!) "DRIVER BUG".
"I didn't get where I am today without using NetBSD."