Replies: 1 comment 1 reply
-
There are some threads linked from #636 about this. Mender includes a |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
This is a follow up question to this question Readonly RootFS with an OverlayFS but a slightly different topic therefore i opening up a new question. Btw, thank you everyone for the help there!
So during the above mentioned question, i learned how to modify the partition layout, and how to tell meta-tegra (or the yocto enviroment) to use my custom partition layout and to create an *.img file ( .e.g overlay.img).
Now my follow up question is the following: How to add a new partition , however in contrast to the overlay partition this one should not start empty. That means i have recipes where i want to install to the specific partition / specific image.
Previously i created the overlay.img with this code :
However from my understanding that creates just an empty image, which this time is not very useful.
In other words what i wish i know:
In my head it goes something like this:
install -d ${D}/new_partition
Does this make sense? Any hints, tips or just links that points me in the right directions will be appreciated. There should be at least one example already in the meta-tegra layer is assume, e.g /boot ? But i could not find it.
Beta Was this translation helpful? Give feedback.
All reactions