Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Mukesh G <mukgbv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Obtaining the latest kernel to test out the latest on the containers
Date: Tue, 24 Jun 2008 17:26:18 -0500	[thread overview]
Message-ID: <20080624222618.GA16783@us.ibm.com> (raw)
In-Reply-To: <c7704c490806241353s53493204g5db4ad45e77d238c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Mukesh G (mukgbv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> Hi,
> 
>     Where do I get the latest kernel sources to test out the latest on the
> containers?

Hi,

generally go to lxc.sf.net and click on 'Patches'.  Currently the latest
patchset is at:

	http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc5-mm3-lxc1/

Download the patch or the broken-out patchset, and apply on top of
2.6.26-rc5-mm3.  And please let us know how it goes!

thanks,
-serge

  parent reply	other threads:[~2008-06-24 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 20:53 Obtaining the latest kernel to test out the latest on the containers Mukesh G
     [not found] ` <c7704c490806241353s53493204g5db4ad45e77d238c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-24 22:26   ` Serge E. Hallyn [this message]
     [not found]     ` <20080624222618.GA16783-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-06-24 23:52       ` Mukesh G
     [not found]         ` <c7704c490806241652wb8862b2k9643fd902f4b9505-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-24 23:54           ` Mukesh G
     [not found]             ` <c7704c490806241654t56ccfe74k5711dfd81779ae1f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-30 23:09               ` Mukesh G
     [not found]                 ` <c7704c490806301609n3437aa7dlbd191200ce4205ec-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-30 23:44                   ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080624222618.GA16783@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=mukgbv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox