All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Read-only rootfs, excluding /tmp and /var/logs
Date: Wed, 29 Oct 2014 13:01:37 +0800	[thread overview]
Message-ID: <545074B1.1000904@windriver.com> (raw)
In-Reply-To: <CANMvBxCyi6V2RzxyD=twcUMpCfFGLJcjThES+W2ihZYTbhtzTA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On 10/28/2014 09:47 PM, Andrew Wozniak wrote:
> Greetings,
>
> I'm fairly new to the Yocto environment but have worked with lower 
> level Linux build systems. To get started, my target needs to have a 
> read-only rootfs, while excluding specific directories like /tmp and 
> /var/logs...
>
> The Project Dev Manual 5.15 section mentions the configuration of a 
> read-only filesystem. I haven't tried this method yet and was 
> wondering if there are any options for custom exclusions other than 
> the /tmp and /var/run mentioned in the docs.
>
>

I think you are using a sysvinit based system, right?

With the current project, you can follow the two steps below o make 
things work:
1. Modify meta/recipes-core/initscripts/initscripts-1.0/volatiles file, 
remove the corresponding entries for /tmp and /var/log.
You can do this via a bbappend file in your own layer, or you could just 
modified the installed file (/etc/default/volatiles/00_core).

2. Edit your /etc/fstab, add corresponding entries.

I think this is an area we should do better in Yocto.

Best Regards,
Chen Qi


[-- Attachment #2: Type: text/html, Size: 1963 bytes --]

      parent reply	other threads:[~2014-10-29  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 13:47 Read-only rootfs, excluding /tmp and /var/logs Andrew Wozniak
2014-10-28 14:20 ` Anders Darander
2014-10-29  5:01 ` 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=545074B1.1000904@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.