[Libburn] Re: Cancelling an ongoing burn. Is this dangerous ?
manmower at signalmarketing.com
Thu Feb 9 07:22:16 PST 2006
On Thu, 9 Feb 2006, scdbackup at gmx.net wrote:
> For that i would need the prototype of the new burn_source
> constructor, which takes an fd and a size, like
> struct burn_source *burn_fd_source_new(int fd, off_t size);
> This would be implemented by adapting my patch from december.
> The patch seems straightforward to me. It is well tested
> meanwhile. About 300 CDs burned by using stdin as track source.
Please do this, I'll merge it fast.
> My current list of CVS things to test is:
> - read-only drives
> - padding
> - cancel
> What i believe is not repaired yet:
> - eject
> - the need to initialize-shutdown-initialize library and drive
> in order to get correct maximum speed of the inserted media
> - catch 22 with abort during burn_drive_grab() where the drive
> is not grabbed enough to be released and not released enough
> to be left behind.
I'll give the rest of your email a better look after work tonight.
Dana makes a good point.
More information about the libburn