Yes. Later reads/writes fails as they should.
> Stupid standards aside: what is the purpose of this? blockdevices don't
It can be used to determine the size fo the device. Seek then read, if read fails
back off. That's where I first noticed it. The IOtest program from the Cerberus suite
As to the stupidity of standards, I'm not sure how to answer that. I am not the only
one to raise this issue though.
> grow bigger if you seek beyond them..
> Did any Linux implementation ever follow the standard (as you rewrite
Yes. As far as I can tell this came in in 2.4.11. Earlier 2.4 kernels and at least 2.2.16
(I didn't check them all) don't have this problem. If it had always been this way it
probably wouldn't have come up. I'm not trying to pick nits on purpose. Something
used to work and then didn't.
> What's the behaviour of other unix systems when seeking
> beyond the end of block devices?
Unfortunately (or not), I don't have any others handy.
Remember there is no data transfer taking place to do the lseek.
There were a couple of exerpts from the standard in this thread:
-- Philip R. Auld, Ph.D. Technical Staff Egenera Corp. firstname.lastname@example.org 165 Forest St., Marlboro, MA 01752 (508)858-2600 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/