On Mon, May 13, 2002 at 10:36:01PM +0200, Joerg Schilling wrote:
> >From [EMAIL PROTECTED] Mon May 13 22:18:40 2002
> 
> >On Mon, May 13, 2002 at 01:13:58PM -0700, Dan Hollis wrote:
> >> On Mon, 13 May 2002, Joerg Schilling wrote:
> >> > It prints: "File %s is too large - ignoring\n"
> >> > It is not possible to put files > 2 GB into a ISO-9660 fs.
> >> 
> >> What about UDF?
> 
> >Just curring symptoms. If UDF than NO ISO at all. But mkisofs can't
> >switch of ISO. So i don't use UDF.
> 
> All UDF media should include ISO-9660. mkisofs is correct.

You should make mkisofs more correct. It should refuse to make
incompatible disc by default. Currently it says nothing when filenames
aren't compatible and/or filenames are to long. (Or "-r" and/or "-J"
switches that behaviour off. That are the only options i use)

I grep for the "print" myself and put the "exit 1" behind it myself. But
i would prefer to not do that with every release in the future. I'm OK
with a commandline-option i can put into my image-creation script. (And
i think my other would prefer such on option, or mkisofs to die when i
skips files. I think most people didn't notice that behaviour because
not so many use DVD-R currently. Like the "You have 10 seconds left" in
cdrecord that did "exit 0" in the past, when you pressed "Control-C".
Nobody noticed that, but my script just wippes the image when cdrecord
does an "exit 0", so i lost an image (I had the luck that "Midnight
Commander" could restore that file. But that took 24 hours) Same with my
image-creation script. It BELIEVES mkisofs. When mkisofs says
"everything OK", then everything is OK and the source-files can be
wipped. This behaviour destroys that "trust" situation.)






Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to