On Thu, 15 Jan 2015 12:22:50 +0100 "Robert Milasan" <[email protected]> wrote:
> On Thu, 15 Jan 2015 12:00:15 +0100 > "Oliver Neukum" <[email protected]> wrote: > > > On Thu, 2015-01-15 at 11:38 +0100, Martin Pitt 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? > > > > That does work. > > > > > > 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). > > > > Well, yes, but why is policy that should be left to the GUI placed > > into udev? > > > > Regards > > Oliver > > > > > > What about this little bundle of joy, the patch I mean, of course. > Please check attachment :) > > Might need work, but the basic idea seems to work, at least in my > tests. > Forget about the patch. If we are using cdrom_id from the console, it actually works and unmounts the media, but not from within a udev rule. Need to see why and will get back. -- Robert Milasan L3 Support Engineer SUSE Linux (http://www.suse.com) email: [email protected] GPG fingerprint: B6FE F4A8 0FA3 3040 3402 6FE7 2F64 167C 1909 6D1A _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
