Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] initscripts: fix read-only-rootfs-hook.sh to start earlier
Date: Thu, 11 Apr 2013 10:23:10 +0100	[thread overview]
Message-ID: <4933851.zWqthAfPy0@helios> (raw)
In-Reply-To: <13df7c921cb.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com>

On Thursday 11 April 2013 08:29:49 Bernhard Reutner-Fischer wrote:
> On 10 April 2013 17:42:28 Paul Eggleton <paul.eggleton@linux.intel.com> 
wrote:
> > Mount /var/volatile ourselves so that we can set up the writable area
> > first. This fixes the urandom service not starting properly when
> > read-only-rootfs is enabled.
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > ---
> > 
> >  .../initscripts/initscripts-1.0/read-only-rootfs-hook.sh             |   
> >  1 + meta/recipes-core/initscripts/initscripts_1.0.bb                    
> >  |    2 +- 2 files changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git
> > a/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
> > b/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
> > index 4f3e0d9..9cf0921 100644
> > ---
> > a/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
> > +++
> > b/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
> > @@ -5,6 +5,7 @@
> > 
> >  [ "$ROOTFS_READ_ONLY" = "no" ] && exit 0
> >  
> >  if [ "$1" = "start" ] ; then
> > 
> > +	grep -q "tmpfs /var/volatile" /proc/mounts || mount /var/volatile
> 
> Or just use mountpoint(1)?

That would have been a better choice if I had known about it, yes. I'll send a 
patch to change it.

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2013-04-11  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 15:42 [PATCH 0/4] Fixes for read-only-rootfs Paul Eggleton
2013-04-10 15:42 ` [PATCH 1/4] rpm-postinsts: don't create broken postinst script Paul Eggleton
2013-04-10 15:42 ` [PATCH 2/4] rpm-postinsts: avoid errors during boot with read-only-rootfs enabled Paul Eggleton
2013-04-10 15:42 ` [PATCH 3/4] initscripts: fix read-only-rootfs-hook.sh to avoid using unionfs Paul Eggleton
2013-04-10 15:42 ` [PATCH 4/4] initscripts: fix read-only-rootfs-hook.sh to start earlier Paul Eggleton
2013-04-11  6:29   ` Bernhard Reutner-Fischer
2013-04-11  9:23     ` Paul Eggleton [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=4933851.zWqthAfPy0@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.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