Gregory Haynes f2a893b74c Actually set a sane PATH for inside chroot ... In I084aff7e449f5de811a6169ec90e352ada7da439 we attemped to address a bug for systems which dont have a path that works well for inside a chroot. Turns out there were multiple issues: * The PATH we were setting was after we attempted to call sh. * PATH was being set in a sibling process to the command being run. * PATH was not being exported so it was not effecting child processes. Using env to set a sane path before we attempt to run our commands addresses these issues. Change-Id: I4285f8048465ee5c2490116447d32033007bd185		2015-04-28 00:02:15 +00:00
..
common-defaults	Make sure sbin paths are in $PATH	2013-12-16 14:42:59 -05:00
common-functions	Dont try to unmount if were not using tmpfs	2015-03-24 18:30:55 +00:00
die	Fix copyrights for HP work.	2012-11-15 16:20:32 +13:00
img-defaults	Export image properties	2015-04-01 20:33:17 +00:00
img-functions	Actually set a sane PATH for inside chroot	2015-04-28 00:02:15 +00:00
ramdisk-defaults	Enable dracut deploy ramdisks	2014-10-17 21:44:09 -05:00
ramdisk-functions	Fix dhclient in Fedora ramdisks	2015-03-31 12:27:40 +01:00