Hi
You are "strict" or you are not strict. If you are not strict that it is pointless to talk about being strict. Someone else would say that Joerg is just "inconsequent". "Silently" IGNORING a file can't be the behaviour of a program that is used in an automatic process. (And placing checks before or after image-creation can't be the job of my script. "mkisofs" is specialized in doing the job, so it should do it correct or die with an error(level)) On Mon, May 13, 2002 at 03:00:27PM -0700, Seth Kurtzberg wrote: > If you make mkisofs completely "correct", it becomes rather useless. > > The default behavior of mkisofs happens to also be the default behavior of > tar; that is, tar continues merrily on its way after an error (at least GNU > tar does). > > There are good reasons to allow a process that takes a long time to complete, > such as mkisofs, to continue after an error is encountered rather than just > quit. > > A command line argument to say "quit on error" would be fine, but my vote is > to keep the default behavior the way it is. > > On Monday 13 May 2002 02:24 pm, Matthias Schniedermeyer wrote: > > 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 > > -- > Seth Kurtzberg > MIS Corp. > Office: (480) 661-1849 > Fax: (480) 614-8909 > email: [EMAIL PROTECTED] > pager: 888-605-9296 or email [EMAIL PROTECTED] -- 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]
