From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why is /var/log symlinked to a tmpfs?
Date: Sun, 14 May 2017 15:56:14 +0200 [thread overview]
Message-ID: <20170514155614.50032272@free-electrons.com> (raw)
In-Reply-To: <1494763200132-164905.post@n4.nabble.com>
Hello,
On Sun, 14 May 2017 05:00:00 -0700 (PDT), PTaylor.us wrote:
> First, I must say that buildroot is a great tool. Thank you.
>
> I am using buildroot branch 2016.11.x.
>
> Why is /var/log a symlink to /tmp (which is mounted with a tmpfs). My
> understanding is that */var/log should be persistent across reboots*. I'm
> very curious why the default skeleton was setup like this. It is causing
> problems, for one, with journald where the "fix" I've seen suggested on this
> mailing list is to set the logging to "volatile".
The reason why /var/log is a symlink to a tmpfs is because we want to
support the root filesystem to be mounted read only.
We know the current skeleton has some issues with journald (see
https://bugs.busybox.net/show_bug.cgi?id=7892), and Yann E. Morin is
working on a patch series to address this, see:
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/systemd-skeleton
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/systemd-skeleton-2
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-14 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 12:00 [Buildroot] Why is /var/log symlinked to a tmpfs? PTaylor.us
2017-05-14 13:56 ` Thomas Petazzoni [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=20170514155614.50032272@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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