[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwS0=yb1Nwq=ph6-B5XRY-r7h+EjXq9EDDH7oj8UObrQw@mail.gmail.com>
Date: Tue, 22 Nov 2011 08:44:21 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Pavel Emelyanov <xemul@...allels.com>
Cc: Tejun Heo <tj@...nel.org>, Oleg Nesterov <oleg@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Alan Cox <alan@...ux.intel.com>,
Roland McGrath <roland@...k.frob.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
James Bottomley <jbottomley@...allels.com>
Subject: Re: [RFC][PATCH 0/3] fork: Add the ability to create tasks with given pids
On Tue, Nov 22, 2011 at 8:30 AM, Pavel Emelyanov <xemul@...allels.com> wrote:
>>>
>>> I think that systemd guys can play with it. E.g. respawning daemons with predefined
>>> pids sounds like an interesting thing to play with.
>>
>> But wouldn't CAP_CHECKPOINT be enough for systemd?
>
> It would, but what's the point in granting to a systemd (which can be a container's
> init by the way) the ability to use the _whole_ checkpoint/restore engine?
Christ, stop making it sound like we would *want* systemd to do even
more odd things.
Quite frankly, any feature that is sold with ".. and systemd can use
this fox Xyz", is a *misfeature* in my opinion. Core infrastructure
like systemd should use a *minimal* interface, not some random
extended features.
I'm starting to really dislike this whole feature discussion.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists