From: ChenQi <Qi.Chen@windriver.com>
To: Khem Raj <raj.khem@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Randy Witt <randy.e.witt@intel.com>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Support persistent /var/log
Date: Thu, 28 May 2015 14:05:06 +0800 [thread overview]
Message-ID: <5566B012.1040006@windriver.com> (raw)
In-Reply-To: <CAMKF1soUQf-mTLfAMDDDh=_vMDss6qu5UVF9QUK=BDOSod7jKQ@mail.gmail.com>
On 05/28/2015 12:55 PM, Khem Raj wrote:
> On Tue, May 26, 2015 at 2:15 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> Randy, Khem, Otavio - this area was the subject of a discussion involving you
>> around the 1.8 release, if you could review this set and comment that would be
>> great.
>
> Looked at it but it didnt sound like it considered read only rootfs case at all.
read-only rootfs and persistent /var/log are all custom configurations.
If a user wants a read-only rootfs but a persistent /var/log, he'll need
to do more custom configurations like putting /var/ on a seperate
partition or something else.
The purpose of this patch is to provide an easy way to user to keep
their logs between reboots.
//Chen Qi
>> Thanks,
>> Paul
>>
>> On Tuesday 26 May 2015 13:43:58 ChenQi wrote:
>>> ping ....
>>>
>>> *ANY* comment would be welcome, really ...
>>>
>>> Thanks,
>>> Chen Qi
>>>
>>> On 03/24/2015 04:42 PM, Chen Qi wrote:
>>>> The following changes since commit
>> d3fcfe346b3472170641d9194243c4bbe06b8585:
>>>> systemd: fix firmware path to match linux-firmware (2015-03-23 11:27:13
>>>> +0000)>
>>>> are available in the git repository at:
>>>> git://git.openembedded.org/openembedded-core-contrib
>>>> ChenQi/persistent-var-log
>>>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h
>>>> =ChenQi/persistent-var-log>
>>>> Chen Qi (4):
>>>> bitbake.conf: add VOLATILE_LOG_DIR variable
>>>> base-files: respect VOLATILE_LOG_DIR
>>>> initscripts: support persistent /var/log
>>>> package.bbclass: support persistent /var/log
>>>>
>>>> meta/classes/package.bbclass | 2 +-
>>>> meta/conf/bitbake.conf | 4 ++
>>>> meta/files/fs-perms-persistent-log.txt | 66
>>>> ++++++++++++++++++++++
>>>> meta/recipes-core/base-files/base-files_3.0.14.bb | 4 +-
>>>> .../initscripts/initscripts-1.0/volatiles | 1 -
>>>> meta/recipes-core/initscripts/initscripts_1.0.bb | 3 +
>>>> 6 files changed, 76 insertions(+), 4 deletions(-)
>>>> create mode 100644 meta/files/fs-perms-persistent-log.txt
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>
prev parent reply other threads:[~2015-05-28 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 8:42 [PATCH 0/4] Support persistent /var/log Chen Qi
2015-03-24 8:42 ` [PATCH 1/4] bitbake.conf: add VOLATILE_LOG_DIR variable Chen Qi
2015-03-24 8:42 ` [PATCH 2/4] base-files: respect VOLATILE_LOG_DIR Chen Qi
2015-03-24 8:42 ` [PATCH 3/4] initscripts: support persistent /var/log Chen Qi
2015-03-24 8:42 ` [PATCH 4/4] package.bbclass: " Chen Qi
2015-04-07 3:10 ` [PATCH 0/4] Support " ChenQi
2015-05-26 5:43 ` ChenQi
2015-05-26 9:15 ` Paul Eggleton
2015-05-28 4:55 ` Khem Raj
2015-05-28 6:05 ` 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=5566B012.1040006@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--cc=raj.khem@gmail.com \
--cc=randy.e.witt@intel.com \
/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