On Mon, Jan 7, 2013 at 1:06 AM, ChenQi <qi.c...@windriver.com> wrote: > 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.
The problem of not using a package for it is regarding upgrades; it is not possible to upgrade the configuration file using the package manager. I know most systems using the read-only-fs will be small and do not use a package manager at all but some use cases will do (mine, in case). So I do believe we ought to have a one-to-one correspondence here. -- 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
