There is no bug in mkisofs.
I beg to differ.
If the file names do not sort the way you like with the number of characters you allow mkisofs to use for ISO-9660 it is _your_ fault:
mkisofs makes choices in that case. It choses the order in which it makes the names unique. It choses to start with the last file on the command line giving it number 000. It then works it's way back to the first file on the command line. All I am reporting is that it makes more sense to me to start with the first file, and increase the 3 digit number until it reaches the last non-unique file on the command line.
If you are saying that mkisofs by design parses the files in reverse order when checking for ISO-9660 unique names, please explain why this is the logical thing to do.
Sincerely,
Richard van den Berg
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
