Brian Harring f264b82dd2 Force our umount w/in the chroot. ... Do this via ensuring that any common.sh invoker of raw umount (say a root script) sees our umount path. Additionally, inject into default profiles our override, and via an upgrade scriptlet. This is round two; originally appeared as CL:32088, was reverted due to: https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos%20sdk/builds/2314/steps/BuildBoard/logs/stdio The fix however is just adding a single sudo mkdir. :/ BUG=chromium-os:23443 TEST=cros_sdk --replace --bootstrap TEST=cros_sdk --replace Change-Id: I0dc7522a9c623f40081d4f138cea0c2c45171fea Reviewed-on: https://gerrit.chromium.org/gerrit/32365 Commit-Ready: Brian Harring <ferringb@chromium.org> Tested-by: Brian Harring <ferringb@chromium.org> Reviewed-by: Chris Sosa <sosa@chromium.org>		2012-09-06 10:34:33 -07:00
..
enter_chroot.sh	Force our umount w/in the chroot.	2012-09-06 10:34:33 -07:00
make_chroot.sh	Force our umount w/in the chroot.	2012-09-06 10:34:33 -07:00
make_conf_util.sh	Don't look in chroot-based paths outside the chroot, even in jest.	2012-06-07 12:07:41 -07:00