From e4fe5542a5242a62d7fc83bd24f65aeadb4d9390 Mon Sep 17 00:00:00 2001 From: Darren Hart Date: Thu, 15 Sep 2011 15:41:37 -0700 Subject: 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 (From OE-Core rev: 4617ae0f433876037c2c9a0dfdb5e373e7a5c77b) Signed-off-by: Darren Hart Signed-off-by: Richard Purdie --- meta/recipes-core/initrdscripts/files/init-boot.sh | 2 ++ 1 file changed, 2 insertions(+) (limited to 'meta/recipes-core/initrdscripts/files/init-boot.sh') diff --git a/meta/recipes-core/initrdscripts/files/init-boot.sh b/meta/recipes-core/initrdscripts/files/init-boot.sh index 9d804fc3a7..e82eba025d 100644 --- a/meta/recipes-core/initrdscripts/files/init-boot.sh +++ b/meta/recipes-core/initrdscripts/files/init-boot.sh @@ -1,5 +1,7 @@ #!/bin/sh +PATH=/sbin:/bin:/usr/sbin:/usr/bin + mkdir /proc mkdir /sys mount -t proc proc /proc -- cgit v1.2.3-54-g00ecf