Hi, patch committed. Also added cdio-eject.c to the example directory. I noticed, that we have 2 eject commands now :)
> A fix for this I think would be to issue either and info or warning > message that the tray door is open. If folks have an opinion on which, > let me know. Also whether the return should be DRIVER_OP_SUCCESS or some > other value. (We could even add a new code for something like NO_OP, but > that mean breaking the ABI.) >From the applications point of view, it is not really an error. So I would return DRIVER_OP_SUCCESS and maybe a warning message. The standard linux eject command does nothing and exits with zero return code in this case. Burkhard _______________________________________________ Libcdio-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/libcdio-devel
