On 3/19/07, Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> wrote: > True. The best available procedure to do this for ACPI bay/dock currently > is, AFAIK: > > 1. Send event when bay/dock "please release" button/lever is pressed. Do > *nothing* else. I know bay does this right, maybe dock doesn't. > > 2. Wait for something to echo 1 >eject or to call the appropriate routine > directly, or (if this exists) for an notification from firmware that the > user IS disconnecting the device for real. > > 3. delete the device. This means force-umount, force-close, etc. > > 4. Tell the hardware to eject. > > > Note that currently (2) and (3) are swapped, as (3) is being done by > userspace request, instead of by the kernel. This is something I *don't* > like. Userspace wants to (non-force-)-unmount by itself after (1), so it can stop the eject process if the filesystems cannot be cleanly unmounted. So the force-unmount at (3) ends up being a redundant safety measure at best. Shem ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
