Fixed a few more minor nitpicks:

build/install-chroot.sh

 #!/bin/bash -e
 
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This script installs Debian-derived distributions in a chroot environment.
 # It can for example be used to have an accurate 32bit build and test
 # environment when otherwise working on a 64bit machine.
 # N. B. it is unlikely that this script will ever work on anything other than a
@@ skipping 202 matching lines @@
       echo "executing \"${target%bit} -c\"."
       exit 1
     fi
     echo "I can abort installation, I can overwrite the existing chroot,"
     echo "or I can delete the old one and then exit. What would you like to"
     printf "do (a/o/d)? "
     read choice
     case "${choice}" in
       a|A) exit 1;;
       o|O) sudo rm -rf "/var/lib/chroot/${target}"; break;;
-      d|D) sudo rm -rf "/var/lib/chroot/${target}"; exit 0;;
+      d|D) sudo rm -rf "/var/lib/chroot/${target}"      \
+                       "/usr/local/bin/${target%bit}"   \
+                       "/etc/schroot/mount-${target}"   \
+                       "/etc/schroot/script-${target}"
+           sudo sed -ni '/^[[]'"${target%bit}"']$/,${
+                         :1;n;/^[[]/b2;b1;:2;p;n;b2};p' \
+                       "/etc/schroot/schroot.conf"
+           trap '' INT TERM QUIT HUP
+           trap '' EXIT
+           echo "Deleted!"
+           exit 0;;
     esac
   done
   echo
 }
 sudo mkdir -p /var/lib/chroot/"${target}"
 
 # Offer to include additional standard repositories for Ubuntu-based chroots.
 alt_repos=
 grep -qs ubuntu.com /usr/share/debootstrap/scripts/"${distname}" && {
   while :; do
@@ skipping 210 matching lines @@
     if [ -n "$1" ]; then
       t="${s#session:}"
       [ "${t#${chroot}-}" == "${t}" ] && continue
     fi
     if ls -l /proc/*/{cwd,fd} 2>/dev/null |
        fgrep -qs "/var/lib/schroot/mount/${t}"; then
       echo "Session \"${t}\" still has active users, not cleaning up" | wrap
       rc=1
       continue
     fi
-    schroot -c "${s}" -e || rc=1
+    sudo schroot -c "${s}" -e || rc=1
   done
   exit ${rc}
 }
 
 list() {
   for e in $(schroot -l); do
     e="${e#chroot:}"
     [ -x "/usr/local/bin/${e}" ] || continue
     if schroot -l --all-sessions 2>/dev/null |
        sed 's/^session://' |
@@ skipping 173 matching lines @@
         echo
         # We prefer running the script in-place, but this might not be
         # possible, if it lives on a network filesystem that denies
         # access to root.
         tmp_script=
         if ! sudo "${target%bit}" sh -c "[ -x '${script}' ]" >&/dev/null; then
           tmp_script="/tmp/${script##*/}"
           cp "${script}" "${tmp_script}"
         fi
         # Some distributions automatically start an instance of the system-
-        # wide dbus daemon, when installing the Chrome build depencies. This
-        # prevents the chroot session from being closed. So, we always try
-        # to shut down any running instance of dbus.
+        # wide dbus daemon or of the logging daemon, when installing the Chrome
+        # build depencies. This prevents the chroot session from being closed.
+        # So, we always try to shut down any running instance of dbus and
+        # rsyslog.
         sudo "${target%bit}" sh -c "${script} --no-lib32;
               rc=$?;
+              /etc/init.d/rsyslog stop >/dev/null 2>&1 || :;
               /etc/init.d/dbus stop >/dev/null 2>&1 || :;
               exit $rc"
         rc=$?
         [ -n "${tmp_script}" ] && rm -f "${tmp_script}"
         [ $rc -ne 0 ] && exit $rc
         break
       ;;
       n|N)
         break
       ;;
@@ skipping 115 matching lines @@
 
 For Chrome, this probably means you want to make your "out" directory a
 symbolic link that points somewhere inside of "${HOME}/chroot".
 
 You still need to run "gclient runhooks" whenever you switch from building
 outside of the chroot to inside of the chroot. But you will find that you
 don't have to repeatedly erase and then completely rebuild all your object
 and binary files.
 
 EOF