From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] initrd contamination and explict PATH
Date: Thu, 15 Sep 2011 15:41:36 -0700 [thread overview]
Message-ID: <cover.1316126173.git.dvhart@linux.intel.com> (raw)
I ran into a bit of a nasty issue where EXTRA_IMAGE_FEATURES set in my
local.conf was causing core-image-initramfs to pull a bunch of files into
my initrd, including bash and a 100+MB vmlinux image. The 85M initrd caused
some strange initial boot behavior, and bash in the initrd caused our init
scripts to fail as bash has a different default PATH than busybox.
The following patches address these issues.
Live boot tested on 32 bit x86.
The following changes since commit bb4a5c44da23a1bb363f1f081cf1644fd7975957:
linux-yocto: remove emenlow from meta-yocto bbappend (2.6.37 version) (2011-09-15 11:27:22 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib dvhart/initrdscripts
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/initrdscripts
Darren Hart (2):
Set an explicit path for the initrd scripts
Prevent IMAGE_FEATURES from contaminating initrd
.../images/core-image-minimal-initramfs.bb | 3 +++
meta/recipes-core/initrdscripts/files/init-boot.sh | 2 ++
.../initrdscripts/files/init-install.sh | 2 ++
meta/recipes-core/initrdscripts/files/init-live.sh | 4 +++-
4 files changed, 10 insertions(+), 1 deletions(-)
--
1.7.6
next reply other threads:[~2011-09-15 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 22:41 Darren Hart [this message]
2011-09-15 22:41 ` [PATCH 1/2] Set an explicit path for the initrd scripts Darren Hart
2011-09-15 22:41 ` [PATCH 2/2] Prevent IMAGE_FEATURES from contaminating initrd Darren Hart
2011-09-16 12:32 ` [PATCH 0/2] initrd contamination and explict PATH Richard Purdie
2011-09-17 19:54 ` Darren Hart
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.1316126173.git.dvhart@linux.intel.com \
--to=dvhart@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 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.