]> code.ossystems Code Review - openembedded-core.git/commit
Set an explicit path for the initrd scripts
authorDarren Hart <dvhart@linux.intel.com>
Thu, 15 Sep 2011 22:41:37 +0000 (15:41 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 16 Sep 2011 12:29:35 +0000 (13:29 +0100)
commit4617ae0f433876037c2c9a0dfdb5e373e7a5c77b
tree1c6c4a4240e648f8bedc0fc0420da922c0ed3db1
parent97249b6d12e9a87bac97a48ad35434084bbe70e3
Set an explicit path for the initrd scripts

If we don't set PATH, then the shell will specify one for us.
Busybox adds the sbin dirs, but bash does not. I hit an
issue where bash (among other things) ended up in my initrd
and the boot scripts failed due to a bad default PATH. While
that is a separate issue, we should not be at the mercy of the
shell's default PATH. Update the initrdscripts to all specify:

PATH=/sbin:/bin:/usr/sbin:/usr/bin

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-core/initrdscripts/files/init-boot.sh
meta/recipes-core/initrdscripts/files/init-install.sh
meta/recipes-core/initrdscripts/files/init-live.sh
meta/recipes-core/initrdscripts/initramfs-boot_1.0.bb
meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
meta/recipes-core/initrdscripts/initramfs-live-install_1.0.bb