Re: [OE-core] [PATCH 0/5] wic: Add --rootfs option to --source param

2014-03-31 Thread João Henrique Freitas
Hi,

On Mon, Mar 31, 2014 at 11:39 AM, Tom Zanussi
wrote:

>
> But I think you could accomplish the same thing by just allowing the
> indirect string e.g. rootfs2 to resolve to either a full path, or as an
> image name, which would be treated as an instance of '-e image-name' for
> that partition.
>
> For example, we have the unmodified parttion in the .wks file as usual:
>
>   part /standby --source rootfs --rootfs-dir=rootfs2 --ondisk sda
> --fstype=ext3 --label secondary --align 1024
>
> Which could be resolved as either a full path to the rootfs dir:
>
>   wic create directdisk-multi-indirect-both --rootfs-dir
> rootfs2=/home/trz/yocto/master-cur/build/tmp/work/crownbay-poky-linux/core-image-minimal
>
> Or extracted from the '-e' ROOTFS_DIR output from the 'core-image-minimal'
> image:
>
>   wic create directdisk-multi-indirect-both --rootfs-dir
> rootfs2=core-image-minimal
>
> Does that make sense for this?
>
>

Yes. I think that is the point.


-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] wic: Add SD/MMC-Cards support

2014-03-19 Thread João Henrique Freitas
Hi Otavio


On Tue, Mar 18, 2014 at 1:35 PM, Otavio Salvador wrote:

> > I am not sure if is not necessary to fix others places. Until now it's
> the single point.
>
> I think this is a sub-optimal solution; we ought to add support for
> UUID as this is ensure to be stable across boot iterations;


You mean filesystem UUID or GUID ?

I think the root= kernel param accept a valid GUID
(/init/do_mounts.c) not fs UUID.

wic has some code to support gpt partitions. So GUID will be passed to
kernel root param (if the .wks was enable to it). I have never used but I
am going to try.

The patch fixes the mbr partitions (which is the default of wic).

Thanks.

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 0/5] wic: Add --rootfs option to --source param

2014-03-17 Thread João Henrique Freitas
Hi Otavio


> No, I don't. I think passing an image helps a lot.
>
>
Ok, I will work on it.

Thanks.

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 0/5] wic: Add --rootfs option to --source param

2014-03-17 Thread João Henrique Freitas
On Mon, Mar 17, 2014 at 11:53 AM, Otavio Salvador
wrote:

>
> So this allows you to include 'a directory' as source of a partition
> to be created, right?
>

Yes.


>
> If my understand is right, I like the feature. My only concern is
> people overusing it and adding contents which are not 'tracked' in the
> build system in a product release which seems attractive when we first
> think about it but cause some management, tracking and authenticity
> check problems in long term.
>
>
I don't know how to better address this from wic perspective. Usually
> we end doing multiple images as part of the build process for those
> special cases and I don't know how wic could be 'told' about those
> secondary rootfs existence.
>
>
I agree that this could be a problem. I will start to think a way to pass
--image param. Like this:

 part /standby --source rootfs --image=core-image-xpto \
 --ondisk sda --fstype=ext3 --label secondary --align 1024

So, wic could check it and add management, tracking, authenticity.

Do you have any suggestion?

Thanks.



> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
>



-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2 0/2] Add task to create kernel config fragments

2014-02-17 Thread João Henrique Freitas
Hi Otavio,


> I do like the patchset except that his cover letter seems outdate as
> the task now is diffconfig.


You are right.



> Maybe you could add another task too,
> which we use quite often in meta-fsl-arm, savedefconfig. This would
> easy people to generate strimmed versions for use.
>

Yes, after this patch is accepted, I will prepare the savedefconfig task
(cml1.bbclass).

Thanks.


> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
>



-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] unmaintained layers

2014-01-10 Thread João Henrique Freitas
Hi,

meta-erlang
>

maintained.

-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] boot-directdisk: add the support of vmdk

2013-12-12 Thread João Henrique Freitas
Hi,

Is ${IMAGE_FSTYPE} correct?

I can't find this variable.

Maybe IMAGE_FSTYPES ?

Thanks.


On Wed, Dec 4, 2013 at 4:50 AM, Zhu Yanjun  wrote:

> ---
>  meta/classes/boot-directdisk.bbclass |   24 +++-
>  1 file changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/meta/classes/boot-directdisk.bbclass
> b/meta/classes/boot-directdisk.bbclass
> index 5535728..b2bd210 100644
> --- a/meta/classes/boot-directdisk.bbclass
> +++ b/meta/classes/boot-directdisk.bbclass
> @@ -88,6 +88,15 @@ build_boot_dd() {
> grubefi_hddimg_populate $HDDDIR
> fi
>
> +   if [ ${IMAGE_FSTYPE} = "vmdk" ]; then
> +   if [ x${AUTO_SYSLINUXMENU} = x1 ] ; then
> +   install -m 0644
> ${STAGING_DIR}/${MACHINE}/usr/share/syslinux/vesamenu.c32
> ${HDDDIR}${SYSLINUXDIR}/vesamenu.c32
> +   if [ x${SYSLINUX_SPLASH} != x ] ; then
> +   install -m 0644 ${SYSLINUX_SPLASH}
> ${HDDDIR}${SYSLINUXDIR}/splash.lss
> +   fi
> +   fi
> +   fi
> +
> BLOCKS=`du -bks $HDDDIR | cut -f 1`
> BLOCKS=`expr $BLOCKS + ${BOOTDD_EXTRA_SPACE}`
>
> @@ -119,17 +128,22 @@ build_boot_dd() {
> parted $IMAGE mkpart primary fat16 0 ${END1}B
> parted $IMAGE unit B mkpart primary ext2 ${END2}B ${END3}B
> parted $IMAGE set 1 boot on
> -   parted $IMAGE print
> +
> +   if [ ${IMAGE_FSTYPE} != "vmdk" ]; then
> +   parted $IMAGE print
> +   fi
>
> awk "BEGIN { printf \"$(echo ${DISK_SIGNATURE} | fold -w 2 | tac |
> paste -sd '' | sed 's/\(..\)/\\x&/g')\" }" | \
> dd of=$IMAGE bs=1 seek=440 conv=notrunc
>
> OFFSET=`expr $END2 / 512`
> -   if [ "${PCBIOS}" = "1" ]; then
> -   dd if=${STAGING_DATADIR}/syslinux/mbr.bin of=$IMAGE
> conv=notrunc
> +   if [ ${IMAGE_FSTYPE} != "vmdk" ]; then
> +   if [ "${PCBIOS}" = "1" ]; then
> +   dd if=${STAGING_DATADIR}/syslinux/mbr.bin
> of=$IMAGE conv=notrunc
> +   fi
> +   dd if=$HDDIMG of=$IMAGE conv=notrunc seek=1 bs=512
> fi
> -   dd if=$HDDIMG of=$IMAGE conv=notrunc seek=1 bs=512
> -   dd if=${ROOTFS} of=$IMAGE conv=notrunc seek=$OFFSET bs=512
> +   dd if=${ROOTFS} of=$IMAGE conv=notrunc seek=$OFFSET bs=512
>
> cd ${DEPLOY_DIR_IMAGE}
> rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.hdddirect
> --
> 1.7.9.5
>
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2] boot-directdisk: Allow for EFI-only boot direct disk images

2013-09-13 Thread João Henrique Freitas
Hi,

No changes between v1 and v2. I just tried to fix the line length. Now I
understood my mistake.

I'm going to send a v3 with the right line length.

Thanks
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 0/6] Setup for VMDK to use Direct Disk

2012-03-27 Thread João Henrique Freitas
Hi,

I guess we can just put that in the docs for now. For future improvement
> though I wonder if we can trick the fetcher into just pulling across the
> current files into the rootfs. I'll put that on my todo list for later.
>


The following thread suggest a patch to fix it:

http://sourceforge.net/mailarchive/forum.php?thread_name=1307458172.10974.64.camel%40skunk&forum_name=genext2fs-devel

Thanks.

-- 
-------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core