Tracy Johnson writes:
>
> I think there is an artificial limit which about 2.1GB as seen by
> these files I created in vi:
>
>  CODE  ------------LOGICAL RECORD-----------  ----SPACE----  FILENAME
>          SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX
>
>            1B  BA        1402 2147483647   1       16  1  *  part
>            1B  BA        8876 2147483647   1       48  1  *  part0001.html
>            1B  BA        9739 2147483647   1       48  2  *  part0002.html
>            1B  BA       10014 2147483647   1       48  2  *  part0003.html
>            1B  BA       10497 2147483647   1       48  2  *  part0004.html
>            1B  BA       24856 2147483647   1      112  2  *  part0005.html
>            1B  BA       18930 2147483647   1       80  2  *  part0006.html
>            1B  BA       15294 2147483647   1       64  2  *  part0007.html
>            1B  BA        8362 2147483647   1       48  2  *  part0008.html
>            1B  BA       10370 2147483647   1       48  2  *  part0009.html
>
...

Hmm, artificial limit... well, kind of, but not really. The maximum file
size of a byte stream file (as shown above) is 2,147,483,647 bytes, or 2**31
- 1 which is the maximum positive integer size with 32-bit words. According
to the POSIX.1 specification that MPE/iX was originally developed to, this
was indeed the physically largest file that could be supported, as the
lseek(), stat() and fstat() interfaces all defined file offsets or file
sizes in terms of a signed 32-bit integer. Later POSIX extensions have been
added to provide 64-bit support, which is what is needed to move beyond the
2GB (2.1GB only if you're selling disks) file limit.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *