Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] Enhance checkpoint/restart Kconfig options
Date: Thu, 4 Jun 2009 15:41:14 -0500	[thread overview]
Message-ID: <20090604204114.GA3513@us.ibm.com> (raw)
In-Reply-To: <20090604184504.F1BCB2F8@kernel>

Quoting Dave Hansen (dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> 
> I spent way too much time yesterday trying to figure out why
> my c/r tests weren't running.  It turned out that I didn't
> have any of the namespaces enabled, the sys_unshare() was
> failing, and the debugging didn't explain any of this.
> 
> So, to protect the world from repeating my mistakes, let's
> improve the Kconfig options a bit.
> 
> 1. Don't say "Enable" in the c/r menu, that's just silly
> 2. move the c/r menu next to the namespaces
> 3. make CHECKPOINT select all of the namespaces
> 4. put a Kconfig 'comment' in explaining how everything
>    got selected.
> 5. Put the namespaces in their own menu
> 
> Perhaps I should break this up a bit and we can push some
> of this to the beginning of the series.  Thoughts?

Yes the selects are needed imo.

-serge

      parent reply	other threads:[~2009-06-04 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090604184504.F1BCB2F8@kernel>
2009-06-04 20:01 ` [PATCH] Enhance checkpoint/restart Kconfig options Nathan Lynch
     [not found]   ` <m3iqjbix8u.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-04 20:17     ` Dave Hansen
2009-06-05  1:32       ` Oren Laadan
2009-06-05  4:25       ` Nathan Lynch
     [not found]         ` <m2zlcnfgst.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-05 19:01           ` Dave Hansen
2009-06-04 20:41 ` Serge E. Hallyn [this message]

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=20090604204114.GA3513@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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