From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.chez-thomas.org (hermes.mlbassoc.com [64.234.241.98]) by mx1.pokylinux.org (Postfix) with ESMTP id 6A17E4C80095 for ; Mon, 11 Jul 2011 10:15:15 -0500 (CDT) Received: by mail.chez-thomas.org (Postfix, from userid 999) id DDFCB1660206; Mon, 11 Jul 2011 09:15:14 -0600 (MDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hermes.chez-thomas.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable version=3.3.2 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by mail.chez-thomas.org (Postfix) with ESMTP id 34CE21660204; Mon, 11 Jul 2011 09:15:14 -0600 (MDT) Message-ID: <4E1B1382.4070203@mlbassoc.com> Date: Mon, 11 Jul 2011 09:15:14 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Thunderbird/3.1.10 MIME-Version: 1.0 To: Richard Purdie References: <4E1B0525.4030107@mlbassoc.com> <1310396843.20015.965.camel@rex> In-Reply-To: <1310396843.20015.965.camel@rex> Cc: Poky Project Subject: Re: UBIFS images X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 15:15:15 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 07/11/2011 09:07 AM, Richard Purdie wrote: > 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... Thanks A bigger question is why is there an unused image command (IMAGE_CMD_ubi) which seems to do it right and also sets up a proper volume layout vs the current command (IMAGE_CMD_ubifs) which is incorrect? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------