There are several reasons I'm sceptical. Firstly a 64bit aware bash opens
a file redirection to a 32bit app which then blows up mysteriously...
The "file smaller than 2Gb" is unenforcable because other processors
may also be altering an object, this object might also change remotely
on a networked fs.
Obviously certain operations should fail - an lseek(), any attempt to
go past 2^31 bits on an fs that isnt 64bit aware (again this is hard
as two people may be writing). An mmap() of a small chunk that overlaps
2^32 is possibly a nasty one to handle but its just a "catch all cases"
thing.
The big problem is the EOVERFLOW blowing up apps it doesnt need to