From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Fixes for read-only-rootfs
Date: Wed, 10 Apr 2013 16:42:24 +0100 [thread overview]
Message-ID: <cover.1365608262.git.paul.eggleton@linux.intel.com> (raw)
There were a number of things breaking read-only-rootfs support; this
patchset fixes the most serious issues.
The following changes since commit f9d88a559dd2479893d7570676d42955ee3b8845:
tinylogin: Fix mix of tabs and spaces for SRC_URI indentation (2013-04-10 13:15:14 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/read-only-rootfs-fixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/read-only-rootfs-fixes
Paul Eggleton (4):
rpm-postinsts: don't create broken postinst script
rpm-postinsts: avoid errors during boot with read-only-rootfs enabled
initscripts: fix read-only-rootfs-hook.sh to avoid using unionfs
initscripts: fix read-only-rootfs-hook.sh to start earlier
.../initscripts-1.0/read-only-rootfs-hook.sh | 16 +++++-----------
meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
meta/recipes-devtools/rpm/rpm-postinsts.bb | 12 ++++++------
3 files changed, 12 insertions(+), 18 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-04-10 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 15:42 Paul Eggleton [this message]
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
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=cover.1365608262.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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