[PATCH 0/6][v3][lxc] Link LXC with USERCR
orenl at cs.columbia.edu
Thu Apr 1 16:36:32 PDT 2010
Sukadev Bhattiprolu wrote:
> Cedric Le Goater [clg at fr.ibm.com] wrote:
>> Hello Suka,
>> On 04/01/2010 03:55 AM, Sukadev Bhattiprolu wrote:
>>> Resending patches after fixing whitespace damage and the typo in
>>> configure.ac. Add a section to patch-0 (below) to describe the
>>> kernel build (commit-id, config tokens etc).
>> we plan to mergepatch 2,3,4 in lxc mainline real soon, maybe not as such,
>> but they won't be in the way anymore. For the moment, please keep 1,5,6 but
>> make it one patch. no need to resend them in a scattered mode.
> Ok. Can you apply 1,5,6 to a separate branch, say usercr-v1, so its easier
> for others to pull ? When I have some major changes I can resend the patches
> merged up to latest LXC and maybe we can then have usercr-v2 and so on.
>>> 1. Build C/R-enabled Linux kernel
>>> $ cd /root
>>> $ git-clone git://www.linux-cr.org/pub/git/linux-cr.git linux-cr
>>> $ cd linux-cr
>>> $ git-checkout ckpt-v20-dev
>>> I tested with commit 3522c57a9ec6f08a129a78322318abcb4467db28
>>> as HEAD.
>> we need to work on a better delivery scheme. I don't think a commit id is not
>> the most efficient way to dialog when integrating components. We'd rather use
>> a tarball or a patch on an identified kernel.
> Hmm, I thought we could just make a branch on the commit-id and apply
> any additional patches there and build.
> I will base it on a closed-release next time like ckpt-v20-rc1 rather
> than an open one like ckpt-v20-dev.
The stable and -rc versions are tagged with cr-vXX[-rcY].
For example, current version is cr-v21-rc2 (both linux-cr and user-cr)
More information about the Containers