On Mon, 26.01.15 15:44, Michael Biebl (mbi...@gmail.com) wrote: > 2015-01-26 14:59 GMT+01:00 Dave Reisner <dreis...@archlinux.org>: > > This reverts part of c2c13f2df42e0, which introduced this with no > > explanation as to *why*. Enslaving the mount namespace breaks default > > behavior included in rules/60-cdrom_id.rules. Specifically, filesystems > > on optical media will not be properly unmounted when the physical eject > > button is used in the absence of a helper tool like udisks2. > > > > This was discussed here: > > > > http://lists.freedesktop.org/archives/systemd-devel/2015-January/026948.html > > > > And has been reported to several bug trackers: > > > > https://bugs.archlinux.org/task/42071 > > http://bugzilla.opensuse.org/show_bug.cgi?id=909418 > > https://bugs.freedesktop.org/bugzilla/show_bug.cgi?id=72206 > > We had to drop this from the Debian package as well: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762018
This appears to be bug in laptop-mode-utils, not in udev. I think it would be a good idea to fix bugs where they are, instead of taping over them in other packages. Also, I the bug report is pretty incomplete, it does not explain in any way why disabled mount propagation should result in a read-only root? This is all fishy. Please try to figure out what *really* is going on before fixing things at the wrong places. Thanks, Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel