[CRIU] [PATCH 0/2] crit core-dump feature, v2

[Ruslan Kuprieiev]

I can't agree that we should move core-dump outside as it is a logical 
part of CRiu Image Tool -- it
transforms CRIU images into another form of saving state - core dump.  
I'm also afraid that making
core-dump feature standalone will make it harder for users to get it. If 
it will be a part of crit -- users
will get everything in one package. It is also quite handy to have all 
criu-images-related stuff under one
command - crit.

P.haul analogy doesn't work here, as p.haul is a completely separate 
project with a complex logic inside
and can't be united with anything in the main criu repo. Core-dump, in 
it's turn, is a far less complex
and is a part of CRIT, which we ship along with criu, so I see no reason 
why we should keep core-dump
outside criu repo and outside CRIT.


On 30.04.15 10:48, Cyrill Gorcunov wrote:
> On Thu, Apr 30, 2015 at 10:40:11AM +0300, Ruslan Kuprieiev wrote:
>> Do you mean make whole crit to be a standalone project?
>> Or just a core-dump part?
> core-dump only. We really gonna drop off our in-criu image viewer
> but use crit instead.