On Mon, 19 Mar 2007, Matthew Garrett wrote: > > But you still have to deal with mounted filesystems, no matter if it a > > cardbus or a cdrom. Wouldn't we need something like 'save removal' > > triggered from userspace like you maybe know from 'the other' operating > > system? > > Yes, there's a need for a mechanism to deal with all of this safely, but > the same is true of any storage device that can be hotplugged (USB, > firewire, anything in a hotplug bay...)
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. IMO should do as PCMCIA and hotplug PCI does, and do that in kernel space. The time window where one can ask the user something or notify it is not a good idea to eject is between (1) and (2). If the eject command is issued, delete devices (includes sync, of course) and eject. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
