Mikhail Teterin <[EMAIL PROTECTED]> writes:
> No single file on a ISO9660 filesystem may exceed 4Gb?
The ISO 9660 file system was designed for a storage medium which had a
fixed capacity of 600 MB.
> Is there some newer, superceeding backwards-compatible standard -- all the new
> DVD devices are
> ISO9660 does not use 64-bit values. Those 8-byte values you see in
> the headers are 32-bit values stored first in little-endian format and
> second in big-endian format.
So, in my original question, the blame lies solely with
3) ISO-9660 standard
? No single file on a ISO9660 filesys
The attached patch should make the isonum functions in iso.h much
clearer. It also gets rid of the optimizated versions; I trust the
compiler to take care of that.
The inode number situation can be improved by dividing the byte offset
of the directory entry by a suitable number guaranteed not to
Bruce Evans <[EMAIL PROTECTED]> writes:
> Mostly (b). Sizes are 64 bits in the standard, but FreeBSD has always
> silently discarded the highest 32 bits and corrupted the next highest
> bit to a sign bit, so the file size limit is at most 2GB or 4GB
> (depending on whether the sign bit gets corrup
On Fri, 19 Aug 2005, Mikhail Teterin wrote:
I have a cd9660 image with several files on it. One of the files is very large
(above 4Gb). When I mount the image, the size of this file is shown as
realsize % 4Gb -- 758876749 bytes instead of 5053844045.
What should I blame:
1) The softwar
Hello!
I have a cd9660 image with several files on it. One of the files is very large
(above 4Gb). When I mount the image, the size of this file is shown as
realsize % 4Gb -- 758876749 bytes instead of 5053844045.
What should I blame:
1) The software, that created the image (modified m
