Re: burning changing files

On Thursday 21 June 2007 00:04:20 dagurasu dagurasu wrote:
> > >  Does growisofs have this issue as well? Obviously if I'm working with
> >
> > growisofs simply calls mkisofs to create the image, so yes. :)
>
> Thanks...   So k3b uses growisofs (in certain cases) which uses mkisofs,
> which may have mention of this limitation in it's docs or at least in some
> discussion board, so technically it's covered.  Realistically though, this
> seems like a pretty big hazard and I'm surprised there's not a warning
> somewhere when you hit burn that says "Please make sure that no processes
> are accessing the data to be burned" or something clever to that effect.  
> This is a user type gui utility, users will use it to write their user
> files... which some process is likely to be changing.. (possibly even k3b
> itself if it happens to update a log file or something),  and there is
> really nothing obvious to tell them that they shouldn't do that.  I
> wouldn't be surprised if this accounts for a lot of the "bad media" people
> think they have.
>
> Maybe this is the wrong place to make this point though... not sure.

not at all. You are right. The question is: what is the best way to solve this 
issue in the GUI?
One possibility would be to monitor all files of the open projects and warn 
the user if one file changes. This would certainly not cover the case where a 
file changes during the burning but since this problem mostly occurs with the 
home folder where files change constantly it is very likely that the warning 
will appear before the burning starts.
The easier way would of course be to simply warn about this if files from the 
home dir are added...
What do you think?

Cheers,
Sebastian

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/