On 01/02/2014 10:30 AM, Ian Jackson wrote:
> Nikolaus Rath writes ("Re: Bug#727708: loose ends for init system decision"):
>> For example, a hypothetical future program to interactively adjust
>> program cgroups cannot be sysvinit compatible in any meaningful sense,
>> because it does not need to be supervised, started, or stopped. However,
>> this program would depend on the cgroups API offered by systemd. So this
>> program would not be allowed in Debian, unless its maintainer adds
>> support for whatever cgroups managed we would eventually use with upstart?
>
> I would hope that we can standardise on a single API to the system's
> single cgroup writer.
I certainly hope so too, but I think the question of how such a
situation would be handled needs to be answered. Even if we end up with
a standardized cgroup API, it may show up in a different disguise.
Best,
Nikolaus
--
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
»Time flies like an arrow, fruit flies like a Banana.«
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
