[systemd-devel] cdrom_id and 60-cdrom_id.rules behavior
rmilasan at suse.com
Thu Jan 15 02:42:39 PST 2015
On Thu, 15 Jan 2015 11:38:33 +0100
"Martin Pitt" <martin.pitt at ubuntu.com> wrote:
> Oliver Neukum [2015-01-15 11:31 +0100]:
> > No, the events are generated. And it is processed.
> > There is just no unmounting.
> That sounds like a bug/missing feature in cdrom_id --eject-media then.
> You could try and replace it with /usr/bin/eject, which does the
> unmounting of all partitions first, fail on busy, and does the eject
> at last?
> > But what is the motivation of in effect disabling door locking?
> We don't -- we specifically leave it locked so that we get the "eject
> button pressed" events. (See my other response for some details).
We could add the unmount functionality also to cdrom_id if we are on
L3 Support Engineer
SUSE Linux (http://www.suse.com)
email: rmilasan at suse.com
GPG fingerprint: B6FE F4A8 0FA3 3040 3402 6FE7 2F64 167C 1909 6D1A
More information about the systemd-devel