Forcing an eject on a user is unsafe. 1453916160/1461780480 (99.5%) @2.5x, remaining 0:02 1457225728/1461780480 (99.7%) @0.7x, remaining 0:01 builtin_dd: 713760*2KB out /dev/hdd: flushing cache /dev/hdd: stopping de-icing /dev/hdd: writing lead-out /dev/hdd: reloading tray Please pause before reloading tray and give them a message telling them you are about to eject it so the user has a chance to prepare for it. I have an Antec SOHO tower and therefore my computer has a door covering the drives. These forced ejects make my heart pound, and eventually either the drive is going to break, or the door from all these forced ejects. The door won't stay open, either, so I can't really help it :-)
Could you please report this upstream to: http://fy.chalmers.se/~appro/linux/DVD+RW/ ?? Thx!
I think he's overwhelmed with mail or something because I sent an email to him a while ago about something else, and never got a reply. Therefore, I don't know if he got the email about that, and I'll send him an email, but would like this open until I get a response. If I don't, maybe someone else can try. The word redhat.com in an email addy might catch his eye and he might read it sooner. Nowadays, you never know if spam filters didn't accidentally catch my email. OTOH, couldn't the kernel have some parameter to put some kind of message on the screen with a blue screen or something to warn the user of an eject like: A program (PID: xxxx name: xxxx) is requesting to eject a removable media, please open the front door on your computer case and then press any key.
hmm, ok... I'll ask the kernel guys what to do...
He said the kernel patch should fix the need for an automatic reload. I've come to think that this should be handled at the kernel level. I'm moving it to kernel, because I think that we should have a way to make it so that the user has a chance to prepare the system for an eject. By kernel option, when a program wants to eject removable media without the user initiating the eject (i.e. if the user didn't use the eject command directly -- if this can be known), then a blue screen will come up giving the user a chance to prepare the computer for the removable media to be ejected, and press ESC to cancel the eject. The issue is that there are so many programs that do this without thinking. It could damage sensitive drives on some computers with front doors, etc.
the kernel defaults to never ejecting. Ever. Any other ejecting is initiated or enabled by userspace applications....
... and you have to be root to do so basically even!... (or at least have raw device access which is basically equivalent to root)
I will not fix this, cause it would affect to many existing burning tools, like k3b, which rely on dvd+rw to behave exactly like it does. Please convince the author.