> Is the myth that Linux can't handle files over 2GB still alive? No.
> Perhaps > the application was compiled without support for large files... It's not an application issue (the check performed by mkisofs is artificial, it's not some kind of wrap-around bug, it won't treat e.g. 4GB+1 bytes large file as 1 byte), nor some *common/general* kernel deficiency. It's Linux isofs filesystem driver implementation issue. I also want to remind that I was answering a particular question and the question was about 4.3GB file. Once again, if you break 2GB-2 bytes barrier (actually alpha mkisofs versions do it already), it's still only part of requires solution, as you would need mkisofs to implement support for multi-extent files to break the 4GB-1 byte barrier. As for "...only if you need to have your files read on a Linux system." ISO9660 is about data interchange, isn't it? You don't know in advance where it will have to be read and therefore want your recordings to be normalized to some least common denominator. ISO9660 by itself sets perfect example for such denominator by insisting on that stupid 8.3 directory structure being present. In either case, as you can't patch all Linux kernels in the world over one night, you better be aware of this issue and stick to 2GB-2 bytes boundary. It's unfortunate, but practical choice. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
