On Fri, 01 Feb 2013 16:59:19 -0500 Colin Walters wrote: > > Yes, that's a way to programmatically do it on an as-needed basis, > > which is great, thanks. But what I was looking for was a way to > > tell systemd to change the default back to private at boot time as > > Lennart suggested in the commit. > > That has global system ramifications.
Sure. Of course, the original change to shared did too :) > It's somewhat unfortunate that > systemd overrides the kernel, but going forward programs can (at the > moment) assume under systemd that it's shared, and make things private > as necessary. If there were a configuration toggle, programs would > have to cope with both cases. Though maybe realistically they > already have to if Upstart doesn't do the same thing. It seems a little unfortunate that programs have to "know" what init system they are running under. Even if Upstart does change the kernel default (I have no idea one way or the other), sysvinit or some other init probably doesn't. Any program that wants to work correctly "everywhere" needs to set the expected behavior, I guess, even those that are currently expecting to find shared mounts. And that probably was true with or without the change Lennart made ... jake -- Jake Edge - LWN - j...@lwn.net - http://lwn.net _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
