On Sat, Apr 05, 2014 at 09:25:33PM +1100, Erik de Castro Lopo wrote: > Erik de Castro Lopo wrote: > > > Can anyone figure out from what we know so far if this is an schroot > > but or a systemd bug? > > > > If someone can give me a gentle nudge in the right direction I'm willing > > to invest some time on this because I really do need this bug fixed. > > Now I can't even re-produce this bug. > > I'm still using schroot 1.6.8-1 with systemd 204-8 but upgrading something > else (no clue what) seems to have fixed. > > I have schroot working properly again. I'm very happy. If no one else can > re-produce this then the bug should be closed.
There's definitely a bug here, in fact two bugs: - systemd shouldn't be breaking things by altering defaults that have worked for over a decade, thereby breaking every user of mount --bind. This is utterly wrong. mount --bind is in widespread use and, like it or not, there are thousands of programs and scripts that, unwittingly or not, depend upon the existing kernel default. - schroot should be able to cope with the default being changed; there's a patch to do this; it just needs updating to work on non-Linux systems and I'll apply it. The bits of the existing patch just need wrapping in "if(Linux)" conditionals. I'll fix this in schroot of course, as I have for many minor portability issues over the years. I do have some rather bad things to say about systemd's attitudes here, but I'll refrain from it here. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
