Ar Maw, 2006-06-20 am 11:05 +0200, ysgrifennodd Andreas Mohr: > But how would HAL safely determine whether a (IDE/USB) drive is busy? > As my test app demonstrates (without HAL running), the *very first* open() > happening during an ongoing burning operation will kill it instantly, in the > USB case. > Are there any options left for HAL at all? Still seems to strongly point > towards a kernel issue so far.
In the IDE space O_EXCL has the needed semantics. At least it does on Fedora and I don't think thats a Fedora patch, not sure if this is the case for the USB side of things. > One (rather less desireable) way I can make up might be to have HAL > keep the device open permanently and do an ioctl query on whether it's "busy" > and then quickly close the device again before the newly started > burning process gets disrupted (if this even properly works at all). O_EXCL used by cdrecord is probably the right thing _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
