![]() ![]() : and mind you, 99.9% of all usb sticks report to have removable media even when they don't. Of course we're always out of date (since there are tens of thousands of devices) so it turns out this isn't really working well. This white-list has included a ton of iPod and related devices. if we should send a eject command when the last volume is unmounted. Historically in GNOME we have used a white-list to determine which devices are "ejectable" e.g. ![]() iPod/Kindle/others will stop serving data and the "Device is not safe Basically, in order to use the device again, you will have to replug itĢ. There are two interesting side effects hereġ. the host can no longer address the device. OTOH, if the device reports having removable media then what happens when sending the eject command to the target is that it will appear as the media is removed. If the device reports having removable media (attr 'removable' in sysfs is 0) then, AFAICT from the specs, nothing happens. the command varies depending on the command set used to speak to the device. ![]() In a nutshell it involves sending a special command to the device. The eject command itself is describe in the man page for eject(1). Only when all volumes are unmounted, we then send the eject command to the device via DeviceKit-disks via eject(1). If one of the mounts are busy the operation fails with G_IO_ERROR_BUSY. > What does eject do on non-ejectable volumes? Can we know if it will do anythingįirst, in GVfs g_eject() ensures that all mounts of the drive is unmounted then the eject command is sent to the device. Comment 3 David Zeuthen (not reading bugmail) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |