Le jeudi 19 décembre 2013 à 12:35 -0800, Steve Langasek a écrit :
> The reasons for not upgrading to the current version of logind aren't to do
> with any fragility of the existing glue code (the systemd-shim package), but
> because logind 205 has a new dependency on systemd as cgroup manager, whic
On Thu, Dec 19, 2013 at 09:53:01AM -0800, Russ Allbery wrote:
> Adrian Bunk writes:
> > Ubuntu is also using udev and logind without using systemd, so they are
> > and will continue to be available stand-alone.
> Ubuntu is maintaining a variety of moderately fragile glue in order to
> make this
Could someone (Steve, most likely) provide a bit of background for how
upstart upstream maintenance works and relates to its packaging?
This question is prompted by a few different things, set off by looking at
the SELinux support since this is something I expect to start looking at
for my day job
On Thu, Dec 19, 2013 at 09:57:48AM -0800, Russ Allbery wrote:
> Ian Jackson writes:
> > Russ Allbery writes:
> >> * Lots of really interesting defense-in-depth security features. I
> >> particularly liked ReadWriteDirectories, ReadOnlyDirectories,
> >> InaccessibleDirectories, PrivateNetwork,
On Thu, Dec 19, 2013 at 09:57:48AM -0800, Russ Allbery wrote:
> Ian Jackson writes:
> > Russ Allbery writes:
> >> * Lots of really interesting defense-in-depth security features. I
> >> particularly liked ReadWriteDirectories, ReadOnlyDirectories,
> >> InaccessibleDirectories, PrivateNetwork
Ian Jackson writes:
> Russ Allbery writes:
>> * Lots of really interesting defense-in-depth security features. I
>> particularly liked ReadWriteDirectories, ReadOnlyDirectories,
>> InaccessibleDirectories, PrivateNetwork, and NoNewPrivileges, which
>> provide a sort of lightweight process
Adrian Bunk writes:
> Ubuntu is also using udev and logind without using systemd, so they are
> and will continue to be available stand-alone.
Ubuntu is maintaining a variety of moderately fragile glue in order to
make this happen and currently can't upgrade to the current version of
logind. Th
On Thu, Dec 19, 2013 at 09:43:05AM +0200, Adrian Bunk wrote:
> On Wed, Dec 18, 2013 at 02:53:39PM -0800, Russ Allbery wrote:
> > Adrian Bunk writes:
> > > [1] Personally, I am sceptical whether it is a good idea to switch to a
> > > different init system for jessie. But I am not on a desperat
Ian Jackson writes:
> Russ Allbery writes ("Bug#727708: Quick upstart and systemd feature
> comparison"):
>> * Lots of really interesting defense-in-depth security features. I
>> particularly liked ReadWriteDirectories, ReadOnlyDirectories,
>> InaccessibleDirectories, PrivateNetwork, and NoN
On Thu, Dec 19, 2013 at 11:15:24AM +, Ian Jackson wrote:
> Steve Langasek writes ("Bug#727708: upstart proposed policy in Debian"):
> > It's also been suggested that instead of requiring modification of the init
> > scripts at all, this logic should be provided by the upstart package in a
> > /
Russ Allbery writes ("Bug#727708: Quick upstart and systemd feature
comparison"):
> * StandardError=syslog. This would be *so nice* for *so many things*.
> Particularly for running Java applications, which are very bad about not
> sending everything to syslog even when one tries to write them
Steve Langasek writes ("Bug#727708: upstart proposed policy in Debian"):
> It's also been suggested that instead of requiring modification of the init
> scripts at all, this logic should be provided by the upstart package in a
> /lib/lsb/init-functions.d/ fragment that automatically DTRT.
If I wan
12 matches
Mail list logo
