>I created a CD image with mkisofs last night. It worked great under Linux
>when I mounted it as a loop back device so I burn it.
>
>The CD works fine in Linux but under Windows all the file names have been
>munged to 8.3. The command that I used was
>
>mkisofs -o image.iso -v -R /directory
>
>Should I use the -l option to allow full 31 character names? The man page
>says to use it with caution. Or should I just add -J and make it
>Joliet. Can you have both Rockwell and Joliet?
Not Rockwell, Rock Ridge. Yes.
>Basically I just want to create a directory tree that reserves the case
>the lenght of filename for all OS's. For all the extra bits such as
>permission, sym links etc I will go with whatever will work on Linux.
Here's a script I used to burn a StarOffice 5.2 CD.
#!/bin/sh
date=`date -u +'%Y-%m-%d %H:%M UTC'`
cd /u2/data
mkisofs -a \
-A "StarOffice 5.2 CD created on $date" \
-J -L -o /u2/data/so52.iso \
-P "Sun Microsystems (www.sun.com)" -p "Ken Yap" \
-r -T -V "SO52" -v so52
The options worth noting are -a to include all files, -J for Joliet dir info in
addition to RR, -L to allow filenames to begin with a period (or you lose some
Unix files), -r to set ids and permissions to sensible values, -T to generate
TRANS.TBL entries for non-RR systems. The other options are just icing. As you
can see, -l is not needed.
-J is probably the option you're wanting.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
