generic-poky/meta/recipes-core/initrdscripts/files/init-boot.sh

#!/bin/sh

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

mkdir /proc
mkdir /sys
mount -t proc proc /proc
mount -t sysfs sysfs /sys

exec sh
initrdscripts: Add the simplest init script When booting from initramfs, one must provide a /init link. This one is the simplest one, just forking a shell, allowing for the smallest initramfs. 2008-11-05 12:50:06 +00:00			`#!/bin/sh`

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 <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-09-15 22:41:37 +00:00			`PATH=/sbin:/bin:/usr/sbin:/usr/bin`

initrdscripts: Add the simplest init script When booting from initramfs, one must provide a /init link. This one is the simplest one, just forking a shell, allowing for the smallest initramfs. 2008-11-05 12:50:06 +00:00			`mkdir /proc`
			`mkdir /sys`
			`mount -t proc proc /proc`
			`mount -t sysfs sysfs /sys`

			`exec sh`