diff options
| author | Darren Hart <dvhart@linux.intel.com> | 2011-09-15 15:41:37 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-09-16 13:29:35 +0100 |
| commit | 4617ae0f433876037c2c9a0dfdb5e373e7a5c77b (patch) | |
| tree | 1c6c4a4240e648f8bedc0fc0420da922c0ed3db1 /meta/recipes-core/images/core-image-minimal-initramfs.bb | |
| parent | 97249b6d12e9a87bac97a48ad35434084bbe70e3 (diff) | |
| download | openembedded-core-4617ae0f433876037c2c9a0dfdb5e373e7a5c77b.tar.gz openembedded-core-4617ae0f433876037c2c9a0dfdb5e373e7a5c77b.tar.bz2 openembedded-core-4617ae0f433876037c2c9a0dfdb5e373e7a5c77b.zip | |
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>
Diffstat (limited to 'meta/recipes-core/images/core-image-minimal-initramfs.bb')
0 files changed, 0 insertions, 0 deletions