On 01/07/2013 03:05 AM, Otavio Salvador wrote:
On Sun, Jan 6, 2013 at 7:44 AM, <qi.c...@windriver.com> wrote:
From: Chen Qi <qi.c...@windriver.com>
Support read-only rootfs by providing a specific conf file for volatile storage.
[YOCTO #3406]
Signed-off-by: Chen Qi <qi.c...@windriver.com>
I prefer this solution than the previous one however why you don't use
a sato-volatile-conf package to provide this?
Because the there exists a one-to-one (or almost one-to-one)
correspondence between the volatile conf file and the specific image.
If there is a 'sato-volatile-conf' package, then there should be a
'minimal-volatile-conf', and maybe a 'custom-volatile-conf' if users are
using a customized image.
So I think it's simpler to let the image recipe provide the conf file.
The only thing we have to do, when adding read-only rootfs support to
some image, is to add the conf file to SRC_URI and install it in
choose_volatile_conf.
Kind Regards,
Chen Qi
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
