2020-10-30 03:05 AM
Hello ST Teams!
Question, again!
I'd like to know if the image "st-image-core" or "st-image-weston" are compatible with the "read-only-rootfs" from yocto append? (thud or dunfell)
Well I've already tried on the st-image-core and bitbake compilation failed, saying something about user-fs.
Any hints would be welcome!
Have a nice confined day!
Solved! Go to Solution.
2020-11-16 08:08 AM
Well after some attempt, i've been able to get a read only rootfs using st-image-core ans SDK2.
I've found that if I modify local.conf by adding "read-only-rootfs" in EXTRA_IMAGE_FEATURES
it cannot bitbake , stating errors about vendorfs and ldconfig
But, if i made a copy of st-image-core.bb (and rename it) and put it in my own layer (/meta-something/images/my-custom-image.bb)
i add 'read-only-rootfs' in the "image-features-part"
It bitbakes ok, and i have a rootfs in readonly mode.
The final goal is to have an almost stateless device in order to have a robust embedded device.
Next step, dive into simlink and others things!
seeya!
links that helped, in french, sorry!
2020-11-05 07:29 AM
Hi @Eldam ,
I escalate your point to some expert.
In the meantime can you share exact error trace or even complete logs of the build ?
Thx
Olivier
2020-11-16 08:08 AM
Well after some attempt, i've been able to get a read only rootfs using st-image-core ans SDK2.
I've found that if I modify local.conf by adding "read-only-rootfs" in EXTRA_IMAGE_FEATURES
it cannot bitbake , stating errors about vendorfs and ldconfig
But, if i made a copy of st-image-core.bb (and rename it) and put it in my own layer (/meta-something/images/my-custom-image.bb)
i add 'read-only-rootfs' in the "image-features-part"
It bitbakes ok, and i have a rootfs in readonly mode.
The final goal is to have an almost stateless device in order to have a robust embedded device.
Next step, dive into simlink and others things!
seeya!
links that helped, in french, sorry!