Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] sysvinit: modify bootlog location
Date: Tue, 14 May 2013 11:25:55 +0800	[thread overview]
Message-ID: <5191AEC3.2050503@windriver.com> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF8436FC4D2B@ALA-MBA.corp.ad.wrs.com>

On 05/14/2013 06:36 AM, Slater, Joseph wrote:
>
>> -----Original Message-----
>> From: Saul Wold [mailto:sgw@linux.intel.com]
>> Sent: Friday, May 10, 2013 3:00 PM
>> To: Burton, Ross; Slater, Joseph
>> Cc: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 1/1] sysvinit: modify bootlog location
>>
>> On 05/10/2013 02:42 AM, Burton, Ross wrote:
>>> On 9 May 2013 00:03, Joe Slater <jslater@windriver.com> wrote:
>>>> The default location for bootlog is volatile,
>>>> so we change it to something that is not.
>>> If this is a problem, why not make /var/log not volatile?  I never
>>> understood why the log directory was volatile to be honest.
>>>
>> How would we handle the Read-Only FS situation?
> Maybe we could change around the creation of bootlogd.log such that,
> if /var/local were not writeable, we'd stick it in /var/log.
>
> Joe
>
Hi all,

I once wanted to make /var/log not volatile, but then I realised that 
not preserving logs between reboots doesn't seem to bother any user, so 
I dropped the patches and marked the bug NOTABUG.
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=3397)

So the key problem here is, are we going to preserve logs between reboots?

If so, we can make /var/log not volatile, in the same way Laurentiu did 
with /var/cache, and add the following lines to the 
read-only-rootfs-hook.sh script to make things work in case of a 
read-only filesystem.

mkdir -p /var/volatile/log
mount --bind /var/volatile/log /var/log

Best Regards,
Chen Qi


>> Sau!
>>
>>> Ross
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>




      reply	other threads:[~2013-05-14  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 23:03 [PATCH 1/1] sysvinit: modify bootlog location Joe Slater
2013-05-10  9:42 ` Burton, Ross
2013-05-10 22:00   ` Saul Wold
2013-05-13 22:36     ` Slater, Joseph
2013-05-14  3:25       ` 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=5191AEC3.2050503@windriver.com \
    --to=qi.chen@windriver.com \
    --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