[OE-core] [oe-core] Rootfs over 4GB

[Gary Robertson]

AFAIK, the reasons for using FAT are:
(1) it is the most universally accepted filesystem format for devices and
OS environments,
(2) it is usable with almost all boot loaders produced anywhere by anyone,
and
(3) it is the de facto standard format for flash-based devices of all types

Your solution of creating a small FAT partition for booting and ext3 for
the root filesystem is probably
the cleanest way of implementing large filesystem images for a Linux
environment.


On Thu, Dec 4, 2014 at 2:10 PM, Petr Nechaev <
petr.nechaev at cogentembedded.com> wrote:

> Hi All,
>
>  I'm using oe-core for building images and have a problem. Rootfs.img is
> over 5GB and cannot be copied to FAT32 partition because of file size
> limit. This happens during do_bootimg task for core-image-sato-sdk. No
> warning is given by bitbake.
>  The problem occurs in build_fat_img() function in bootimg.bbclass.
>
>  I have temporarily fixed the problem in my build by extending
> bootimg.bbclass. I added new function which first splits *.hddimg into two
> partitions: FAT + ext3 and then puts rootfs.img to ext3 partition.
>
>  But, what is the right way of building core-image-sato-sdk with large
> rootfs? And what is the technical reason behind putting rootfs.img into a
> FAT partition?
>
> ---
> Petr
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20141204/cf252df8/attachment-0002.html>