Re: burning changing files
dagurasu dagurasu <[email protected]>
| Newsgroups | gmane.comp.kde.k3b |
|---|---|
| Message-ID | <[email protected]> |
> > 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. _________________________________________________________________ Make every IM count. Download Windows Live Messenger and join the i’m Initiative now. It’s free. http://im.live.com/messenger/im/home/?source=TAGWL_June07 ------------------------------------------------------------------------- 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/