From: ChenQi <Qi.Chen@windriver.com>
To: Jack Mitchell <ml@communistcode.co.uk>,
<openembedded-core@lists.openembedded.org>
Subject: Re: making /var/log persistent
Date: Wed, 12 Aug 2015 18:33:42 +0800 [thread overview]
Message-ID: <55CB2106.4070908@windriver.com> (raw)
In-Reply-To: <55CB2008.4020101@communistcode.co.uk>
On 08/12/2015 06:29 PM, Jack Mitchell wrote:
> I'm trying to make /var/log persistent and I'm having trouble. I've
> made a bbappend to base_files which contains:
>
> dirs755_append = " \
> /var/log \
> "
>
> volatiles = "tmp"
>
> Looking in the resulting image, /var/log is indeed now a directory and
> not a symlink to volatile storage, however when the image is flashed
> to target and booted it is reverted back to being a symlink; I assume
> by some init script?
>
> Can anyone shed any light on what more is required to get a persistent
> log directory.
>
> Cheers,
> Jack.
I sent out a series of patches regarding this area.
The patch title is "[OE-core] [PATCH 0/4] Support persistent /var/log".
Regards,
Chen Qi
prev parent reply other threads:[~2015-08-12 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:29 making /var/log persistent Jack Mitchell
2015-08-12 10:33 ` ChenQi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55CB2106.4070908@windriver.com \
--to=qi.chen@windriver.com \
--cc=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox