From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][master][PATCH] busybox_vmsep.inc: busybox changes for runx support
Date: Sat, 2 May 2020 11:10:04 -0400 [thread overview]
Message-ID: <20200502151003.GD9724@gmail.com> (raw)
In-Reply-To: <1588393237-11939-1-git-send-email-chandana.kalluri@xilinx.com>
merged.
Bruce
In message: [meta-virtualization][master][PATCH] busybox_vmsep.inc: busybox changes for runx support
on 01/05/2020 Sai Hari Chandana Kalluri wrote:
> Runx needs busybox static binary that contains symlinks to mount. However, in
> zeus, busybox by default uses BUSYBOX_SPLIT_SUID = 1. With the variable set,
> busybox binary gets split into two busybox.suid and busybox.nosuid busybox.suid
> contains links to mount while runx recipes pulls in busybox.nosuid.
>
> When vmsep is enabled, set BUSYBOX_SPLIT_SUID = 0 so that an unstripped busybox
> binary is generated which contains all the required links including mount.
>
> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
> ---
> recipes-core/busybox/busybox_vmsep.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/recipes-core/busybox/busybox_vmsep.inc b/recipes-core/busybox/busybox_vmsep.inc
> index b70a065..d4b1e6c 100644
> --- a/recipes-core/busybox/busybox_vmsep.inc
> +++ b/recipes-core/busybox/busybox_vmsep.inc
> @@ -6,3 +6,4 @@ SRC_URI += " \
> # we do this to get the target binary available to recipes that
> # depend on busybox
> SYSROOT_DIRS += "/bin"
> +BUSYBOX_SPLIT_SUID = "0"
> --
> 2.7.4
>
prev parent reply other threads:[~2020-05-02 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 4:20 [meta-virtualization][master][PATCH] busybox_vmsep.inc: busybox changes for runx support Chandana kalluri
2020-05-02 15:10 ` Bruce Ashfield [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=20200502151003.GD9724@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=chandana.kalluri@xilinx.com \
--cc=meta-virtualization@lists.yoctoproject.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 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.