I looked at the populate-volatile.sh, and this seemed to almost do the job,
if I solve the problem using symlinks.
What it needs is a copy file function.
As a temporary solution, I created a derivative: populate-settings.sh
which will check /etc/default/settings in the same way populate-volatile.s
On Wed, Jun 13, 2018 at 9:28 AM, Ulf Samuelsson wrote:
> Thanks, is it more efficient than symlinking?
Efficient in what way?
Have you looked at the volatile-binds recipe in oe-core? Its job is to
setup enough bind mounts to enable systemd to run from a readonly
rootfs. Although it's currently s
Thanks, is it more efficient than symlinking?
Best Regards,
Ulf Samuelsson
> 13 juni 2018 kl. 15:20 skrev Anders Darander :
>
> * Ulf Samuelsson [180612 22:01]:
>
>> We want most of /etc to be read-only for security reasons,
>> and the overlayfs will make the whole of /etc writeable.
>
>> I t
* Ulf Samuelsson [180612 22:01]:
> We want most of /etc to be read-only for security reasons,
> and the overlayfs will make the whole of /etc writeable.
> I tried mount —bind /etc/timezone /persistent/etc/timezone, and it
> complained that they were not directories. Bind mounting /etc again
> wi
essage-
>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>> boun...@yoctoproject.org] On Behalf Of Ulf Samuelsson
>> Sent: den 9 juni 2018 11:51
>> To: yocto@yoctoproject.org
>> Subject: [yocto] How handle files needing updates in read-only
>> filesystem
>>
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Ulf Samuelsson
> Sent: den 9 juni 2018 11:51
> To: yocto@yoctoproject.org
> Subject: [yocto] How handle files needing updates in read-only
> filesystem
We have a rootfs which is read-only.
For files that needs to be updated, like "/etc/localtime"
we will create a symbolic link to a partition (/persistent) which
is retained between rootfs image updates.
/etc/localtime -> /persistent/etc/localtime
The original recipe will generate the real /etc
