From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: UBIFS images
Date: Mon, 11 Jul 2011 16:07:23 +0100 [thread overview]
Message-ID: <1310396843.20015.965.camel@rex> (raw)
In-Reply-To: <4E1B0525.4030107@mlbassoc.com>
On Mon, 2011-07-11 at 08:13 -0600, Gary Thomas wrote:
> I'm trying to use UBIFS on my target and I found that the images
> are not quite right. The soft-link points to the wrong file.
>
> $ ls -l tmp/deploy/images/*ubi*
> -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.img
> lrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifs
>
> I've looked through meta/classes/image_types.bbclass but it's not
> clear to me [yet] where that soft-link gets built and why it gets
> it wrong.
>
> Any pointers?
image_types.bbclass:
ln -s ${IMAGE_NAME}.rootfs.${type} ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.${type}
The problem is that $type=ubifs but the extenstion the ubifs image
generates is ubifs.img:
IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}"
and we don't support generating image types where the image extension
and the type name differ...
I'd guess the quick fix is s/ubifs.img/ubifs/ in the above...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-11 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 14:13 UBIFS images Gary Thomas
2011-07-11 14:20 ` Gary Thomas
2011-07-11 15:07 ` Richard Purdie [this message]
2011-07-11 15:15 ` Gary Thomas
2011-07-11 16:15 ` Tom Rini
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=1310396843.20015.965.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@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.