Le 28/04/2015 01:11, Michael Biebl a écrit :
Am 27.04.2015 um 21:56 schrieb Michael Biebl:
Ok, I can confirm that adding such a bind mount to /tmp activates
tmp.mount, even if tmp.mount has been disabled. Retitling the bug report
accordingly.
I can also confirm, that this is a regression from -12 to -13 by
installing those two versions from snapshot.d.o.
I did a test build with
debian/patches/PrivateTmp-shouldn-t-require-tmpfs.patch reverted, and
that seems indeed to fix this particular issue.
Interesting side-effect.
Didier, any idea?
It's a weird side-effect indeed. The patch only downgrades the
relationship with this mount, which already exists in systemd mem. I
have no immediate idea what's happening there and a quick look at the
code this morning didn't help either.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
