From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: paul.eggleton@intel.com
Subject: Re: [PATCH] self-hosted-image: Increase space for build and allow builder user sudo access
Date: Tue, 03 Apr 2012 17:54:13 -0700 [thread overview]
Message-ID: <4F7B9BB5.8060409@linux.intel.com> (raw)
In-Reply-To: <1333499919-11883-1-git-send-email-sgw@linux.intel.com>
On 04/03/2012 05:38 PM, Saul Wold wrote:
> We need to have about 40G to do a full sato build even with rm_work enabled
> Add sudo priveleges inorder to allow the builder user to setup the tap/tun
> devices needed by runqemu
>
> Signed-off-by: Saul Wold<sgw@linux.intel.com>
> ---
> meta/recipes-core/images/self-hosted-image.bb | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-core/images/self-hosted-image.bb b/meta/recipes-core/images/self-hosted-image.bb
> index 39f0fc4..46dcc5f 100644
> --- a/meta/recipes-core/images/self-hosted-image.bb
> +++ b/meta/recipes-core/images/self-hosted-image.bb
> @@ -12,11 +12,8 @@ CORE_IMAGE_EXTRA_INSTALL = "\
>
> IMAGE_FEATURES += "x11-mini package-management"
>
> -# Ensure there's enough space to do a core-image-minimal build, with rm_work enabled
> -IMAGE_ROOTFS_EXTRA_SPACE = "1048576"
> -#IMAGE_ROOTFS_EXTRA_SPACE = "2621440"
> -#IMAGE_ROOTFS_EXTRA_SPACE = "20971520"
> -#IMAGE_ROOTFS_EXTRA_SPACE = "5242880"
> +# Ensure there's enough space to do a core-image-sato build, with rm_work enabled
> +IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
>
> # Do a quiet boot with limited console messages
> APPEND += "quiet"
> @@ -54,6 +51,9 @@ fakeroot do_populate_poky_src () {
> chown builder.builder ${IMAGE_ROOTFS}/home/builder/pseudo
>
> chown -R builder.builder ${IMAGE_ROOTFS}/home/builder/poky
> +
> + # Allow builder to use sudo to setup tap/tun
> + echo "builder ALL=(ALL) NOPASSWD: ALL"> /etc/sudoers
> }
>
> IMAGE_PREPROCESS_COMMAND += "do_populate_poky_src; "
Yup, forgot the PR Bump! It been fixed in mut
Sau!
next prev parent reply other threads:[~2012-04-04 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 0:38 [PATCH] self-hosted-image: Increase space for build and allow builder user sudo access Saul Wold
2012-04-04 0:54 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 14:54 Saul Wold
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=4F7B9BB5.8060409@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.