From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image.bbclass: ensure makedevs does return true
Date: Tue, 1 Oct 2013 10:52:59 -0500 [thread overview]
Message-ID: <524AEFDB.4010804@windriver.com> (raw)
In-Reply-To: <1380642011-14346-1-git-send-email-sgw@linux.intel.com>
On 10/1/13 10:40 AM, Saul Wold wrote:
> When doing an incremental image generation, ensure that makedevs returns true when it encounters
> a node that already exists, otherwise image generation will fail.
>
> [YOCTO #5288]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/classes/image.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 7650594..463fa71 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -337,7 +337,7 @@ fakeroot do_rootfs () {
> for devtable in ${@get_devtable_list(d)}; do
> # Always return ture since there maybe already one when use the
> # incremental image generation
> - makedevs -r ${IMAGE_ROOTFS} -D $devtable
> + makedevs -r ${IMAGE_ROOTFS} -D $devtable || true
I'm a little worried about this patch. There is a known case where makedevs
will fail with a message indicating it can't do the name -> uid/gid
translations. In this case it just stops, and the nodes are never generated.
The underlying cause is that the passwd/group files never got installed onto the
target. Adding a specific check for this might be a good idea, but doing the ||
true will cause errors like that to be masked.
Perhaps finding a way to patch makedevs to no error when a node already exists?
--Mark
> done
> fi
>
>
prev parent reply other threads:[~2013-10-01 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 15:40 [PATCH] image.bbclass: ensure makedevs does return true Saul Wold
2013-10-01 15:52 ` Mark Hatle [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=524AEFDB.4010804@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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