On Monday 15 April 2002 01:22 am, Alexander Skwar wrote:
>> But mkisofs objects to 19 of the file names being longer than the
>> maximum of 37 characters supported by ISO 9660 and mkisofs -U.
> Hm, did you also try to make a pure rockridge CD?
Even the 37 characters is a violation of ISO-9660; what's happened is that
there is no more physical space on the CD for names that long. Quote from man
mkisofs:
-max-iso9660-filenames
Allow 37 chars in iso9660 filenames. This option
forces the -N option as the extra name space is
taken from the space reserved for ISO-9660 version
numbers.
This violates the ISO9660 standard, but it happens
to work on many systems. Although a conforming
application needs to provide a buffer space of at
least 37 characters, disks created with this option
may cause a buffer overflow in the reading operat�
ing system. Use with extreme care.
Even with RR and/or Joliet, there is no guarantee that the CDs will be
portable. Even as things stand _now_ there is no such guarantee, since in
theory the CD should conform to 8.3;N uppercase only.
OTOH, I don't know of anything that breaks because of it. Does anyone else?
Does, say, Solaris, HP-UX, Mac OS-9 or IRIX break on standards-stretching CDs?
BTW, the names supplied as examples by Ron are 57 chars long, so even a
savage abbreviation like...
dictd-dictionaries-freedict-wel-eng-0.1.0-3mdk.noarch.rpm =>
dictd-freed-wel-eng-0.1.0-3mdk.noarch.rpm
...is not enough. IIRC, some of the Aurora components are like this as well,
but maybe Ron doesn't use (ie download and burn) Auroroa.
Cheers; Leon
