From: Kamil I. <ac...@wp...> - 2014-01-01 22:19:23
|
On 27.12.2013 02:39, Roger wrote: > For the past few months, I've experimented with UDF writing and tend to prefer > UDF when compared to ISO image format. > > I'm really trying to read the CDW code, but not getting really far due to the > massive amount of require source code reading. :-/ > > (I got about as far as looking at the menus, and realizing the 'Create ISO > menu' would need to be heavily modified to allow or hook-in another image > writing type.) > > Anyways, for historical reasons and those scanning the web for UDF writing > instructions, here's what I do withing Bash command line with relatively good > success. (Atypically as always, write first to read-write media before doing a > final write to write once media.) > > [...] Well, looks... complicated :) If memory serves me well, I was able to create an ISO image file with just one (or maybe two) command executed with exec(), and here we have a series of commands to be executed in sequence. One of them also depends on user being able to successfully run commands with sudo without the need to provide user password. It surely could be done, and in first implementation I could just somehow* capture return value from a command to only get its success/failure status, to know whether I can execute the next command in sequence. Maybe later on I could also capture some error messages printed to stdout/stderr to learn why a command has failed. Complicated, but probably doable :) *) maybe I could get this value through environment variable described in man exec(3), or maybe I should execute these commands with system(). Learning how to get value returned by executed commands should be the first thing to do when implementing the procedure you described. Best regards, Kamil |