[syslinux] isolinux bug?

Izzy Blacklock izzyb at ecn.ab.ca
Tue Jul 9 23:02:38 PDT 2002

On Monday 08 July 2002 00:54, H. Peter Anvin wrote:
> Izzy Blacklock wrote:
> >>Mount your CD-ROM or ISO image using -o norock,nojoliet to see the
> >>filenames the way ISOLINUX sees them.
> >
> > Thanks.  I did not know about the mkisofs limits.  As it turns out, I was
> > using a -l in my mkisofs command line.  Should I still have had the
> > problem? My command line was as follows (except for the line breaks of
> > course):
> Please use the mount options I listed above to see what is problematic.
> 	-hpa

I haven't had a chance to try this yet, but I did take some time to read the 
man pages for mkisofs and found this:

------- 8< ----------------

-iso-level level
              Set the iso9660 conformance level. Valid numbers are 1..3.

              With level 1, files may only consist of one section and 
filenames are restricted to 8.3 characters.

              With level 2, files may only consist of one section.

              With level 3, no restrictions apply.

              With all iso9660 levels all filenames are restricted to upper 
case letters, numbers and the underscore  (_).  The
              maximum  filename  length  is restricted to 31 characters, the 
directory nesting level is restricted to 8 and the
              maximum path length is limited to 255 characters.


It looks like the dash isn't a valid character even when using the -l option.  
I'm guessing using -l causes the creation of a level 3 iso9660 filesystem.  

What would be involved in adding Rock Ridge support to isolinux?  These file 
naming restrictions are likely to cause a lot of problems for people.  At the 
very least, adding a note about the restrictions to your docs seems like a 
good idea!  It'd probably have saved me from making a fool of myself! :)

Thanks for your help and for creating such a wonderful product..  I'm happy to 
say I have a working linux boot CD now! :)


More information about the Syslinux mailing list