<div dir="ltr"><div class="gmail_extra">Hi All,</div><div class="gmail_extra"><br></div><div class="gmail_extra">I've created a patch to fix this issue. </div><div class="gmail_extra">It can be enabled by setting SEPARATE_ROOTFS = "1" in local.conf. Rootfs.img is then put into a separate ext3 partition.</div><div class="gmail_extra"><br>In hope it will be useful.</div><div class="gmail_extra"><br></div><div class="gmail_extra">---<br></div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div>Petr<br></div></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 4, 2014 at 11:25 PM, Gary Robertson <span dir="ltr"><<a href="mailto:gary.robertson@linaro.org" target="_blank">gary.robertson@linaro.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>AFAIK, the reasons for using FAT are:<br>(1) it is the most universally accepted filesystem format for devices and OS environments,<br></div>(2) it is usable with almost all boot loaders produced anywhere by anyone, and<br></div>(3) it is the de facto standard format for flash-based devices of all types<br><br></div>Your solution of creating a small FAT partition for booting and ext3 for the root filesystem is probably<br></div>the cleanest way of implementing large filesystem images for a Linux environment.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Dec 4, 2014 at 2:10 PM, Petr Nechaev <span dir="ltr"><<a href="mailto:petr.nechaev@cogentembedded.com" target="_blank">petr.nechaev@cogentembedded.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div dir="ltr"><span><div style="font-size:13px">Hi All,</div><div style="font-size:13px"><br></div><div style="font-size:13px"> 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.</div><div style="font-size:13px"> The problem occurs in build_fat_img() function in bootimg.bbclass. <br></div><div style="font-size:13px"><br></div></span><div style="font-size:13px"> 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. </div><div style="font-size:13px"><br></div><div style="font-size:13px"> 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?</div><div style="font-size:13px"><br></div><div style="font-size:13px">---<br></div><div style="font-size:13px"><div dir="ltr">Petr</div></div></div></div>
</div>
<br></div></div><span class=""><font color="#888888">--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br></font></span></blockquote></div><br></div>
</blockquote></div></div></div>