growisofs and long filenames

[Lennart Sorensen]

On Mon, Apr 11, 2005 at 07:26:25PM -0400, William O'Higgins wrote:
> I'm running an up-to-date Debian testing system, with a DVD burner that
> I bought for $60 (!) at Canada Computers last week.  Your basic +/- dual
> layer jobie.
> 
> My test disc copied oddly - my directory of MP3 files - all the files
> are there, and they all play, but the M3U tags have, in some cases
> (about half) gone wonky (or just gone) and the filenames are truncated.
> I wanted to try again, so I ran this:
> 
> growisofs -dry-run -Z /dev/dvd -R -J /home/media/
> 
> And the output is this:
> 
> Executing 'mkisofs -R -J /home/media/ | builtin_dd of=/dev/dvd obs=32k
> seek=0
> 
> And then a couple of pages of this:
> 
> Using DIGGI000.MP3;1 for
> /home/media/folk/digging_a_hole_to_china__ian_north.mp3
> 
> Which is, as I understand it, not supposed to happen.  Any suggestions?

That is very much _supposed_ to happen.  It has to generate an 8.3 name
for each file so that they can be stored on the CD for all systems to
read.  Those that support Joliet extensions will read the long names
through that, and those that support Rock Ridge extensions will convert
the names to long filenames through that.  If a system doesn't support
either extension system, it gets the generated short names.

If you plopped it in some mp3 playing device (like a dvd player or
something) which doesn't support either of the filename extensions, then
you will get 8.3 names.  If it has limits on the mp3 id tags, then it
will truncate those too.  What does it say if you mount the cd on linux?
does it have long filenames?  Does an mp3 tag reader show the tags as
you expect?  If so, then (as is most likely) the target device is at
fault and you did everything right.

Lennart Sorensen
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml