[EMAIL PROTECTED] (Andy Polyakov) quoted and then wrote: >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.
You are correct that ISO-9660 allows an implementation to restrict itself to Interchange Level 2, meaning files consist of a single file section. If a Linux system only handles Level 2 ISO-9660 structures, it should be documented as having that restriction. Ideally, it would detect a disc that does not conform to that restriction and issue a clear error message to the user. The restriction to 8.3 filenames would be Interchange Level 1, and is not limited to the Directory Hierarchy identified in the Primary Volume Descriptor. It also applies to any Directory Hierarchy identified by a Supplementary Volume Descriptor. Perhaps you have confused this with the restriction on valid characters outlined in section 7.4.4 of the ISO 9660 standard. So nothing in ISO 9660 differentiates between the various Directory Hierarchies regarding 8.3 filename restrictions, but perhaps some authors (or even authoring tools) follow such a restriction only for the Directory Hierarchy identified in the Primary Volume Descriptor as a pragmatic step toward compatibility with some unspecified operating system (PC DOS?). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
