<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>splitting the root file filesystem into different partitions is a common task and supported from every operating system during install and should be also supported from yocto’s build system<o:p></o:p></p><p class=MsoNormal>based on the current available documentation it seems impossible to accomplish this task, the only available result is one full blown image containing the root partition<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>currently the only idea i had is to run bitbake which will generate the root image containing everything<o:p></o:p></p><p class=MsoNormal>create afterwards my own images with the desired size (also a new root image because in this case IMAGE_ROOTFS_SIZE does not reflect the ending image size)<o:p></o:p></p><p class=MsoNormal>mount every image and move the directories from the bitbake produced image into this new images<o:p></o:p></p><p class=MsoNormal>and finally flash that images to my devices<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>what do you mean?<o:p></o:p></p><p class=MsoNormal>should this basic core functionality part of yocto’s build process without an overhead for everyone to create isolated solutions?<o:p></o:p></p><p class=MsoNormal>do you see a better workaround as to create new images and movements after the build process?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>thank you in advance<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>br<o:p></o:p></p><p class=MsoNormal>Andre<o:p></o:p></p></div></body></html>