Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Sep 2003 06:28:13 -0300
From:      Augusto Jun Devegili <freebsd@devegili.org>
To:        Dragoncrest <dragoncrest@voyager.net>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Questions about mkisofs
Message-ID:  <1064827693.694.8.camel@gandalf.middle.earth>
In-Reply-To: <5.2.0.9.2.20030928201854.022a7ec0@pop.voyager.net>
References:  <5.2.0.9.2.20030928201854.022a7ec0@pop.voyager.net>

next in thread | previous in thread | raw e-mail | index | archive | help
IIRC, Windows doesn't recognize Rock Ridge extensions. Try

mkisofs -R -J -V "My long volume" -o mycd.iso /path.to....

so that Joliet information is also recorded in the CD; Windows will
recognize it.

Regards,

Augusto

On Sun, 2003-09-28 at 21:30, Dragoncrest wrote:
>          Hi all.  Just curious of something.  I'm probably doing something 
> wrong and totally not paying attention, but for some reason when I run 
> mkisofs, all my files get truncated at 12 charecters and some weird 001 is 
> appended to the rest of the name.  I use the following command when 
> building an iso file for burning:  mkisofs -R -U -o mycd.iso 
> /path.to.files/to.be.burned/
> 
>          I'm obviously missing something because I've gotten files with 
> names up to 128 charecters long to be included in an iso when burning them 
> in windows, but not in freebsd using mkisofs.  I've also been able to make 
> the disk name 16 charecters long in windows but only 12 with mkisofs.  Can 
> someone tell me what I'm doing wrong with the options on mkisofs and help 
> me fix it?  Like I said, I've read the man file and I thought I had it all 
> correct, but apparently that's not true.  Much apreciated on the help.  Thanks.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1064827693.694.8.camel>