make_chroot: move ending summary to cros_sdk
Pull the logging out and discard the nfs check.
BUG=b:191307774
TEST=`cros_sdk` still works
Change-Id: Ib31bc67e0e6330052ab6af4ab1af6ec2135faad4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/2971572
Reviewed-by: Alex Klein <saklein@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
diff --git a/sdk_lib/make_chroot.sh b/sdk_lib/make_chroot.sh
index 3663b09..38ccf05 100755
--- a/sdk_lib/make_chroot.sh
+++ b/sdk_lib/make_chroot.sh
@@ -566,29 +566,4 @@
# VM ourselves until that gets fixed upstream.
enter_chroot sudo eselect java-vm set system openjdk-bin-11
-CHROOT_EXAMPLE_OPT=""
-if [[ "$FLAGS_chroot" != "$DEFAULT_CHROOT_DIR" ]]; then
- CHROOT_EXAMPLE_OPT="--chroot=$FLAGS_chroot"
-fi
-
command_completed
-
-cat <<EOF
-
-${CROS_LOG_PREFIX:-cros_sdk}: All set up. To enter the chroot, run:
-$ cros_sdk --enter $CHROOT_EXAMPLE_OPT
-
-CAUTION: Do *NOT* rm -rf the chroot directory; if there are stale bind
-mounts you may end up deleting your source tree too. To unmount and
-delete the chroot cleanly, use:
-$ cros_sdk --delete $CHROOT_EXAMPLE_OPT
-
-EOF
-
-is_nfs() {
- [[ $(stat -f -L -c %T "$1") == "nfs" ]]
-}
-
-if is_nfs "${SUDO_HOME}"; then
- warn "${SUDO_HOME} is on NFS. This is untested. Send patches if it's broken."
-fi
