summaryrefslogtreecommitdiffstats
path: root/arch-chroot.in
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@ubuntu.com>2018-10-23 20:26:40 -0400
committerLibravatarUnit 193 <unit193@ubuntu.com>2018-10-23 20:26:40 -0400
commit827a047f6fe1a8eff30c6059c8822a4b65665aa9 (patch)
treea52dd6a9bf2a0f6276f5bc043a37d91ad885b792 /arch-chroot.in
parent781cf3aa0d3f9a93d84481833f5c83aa9ee68ac0 (diff)
New upstream version 20upstream/20
Diffstat (limited to 'arch-chroot.in')
-rw-r--r--arch-chroot.in11
1 files changed, 11 insertions, 0 deletions
diff --git a/arch-chroot.in b/arch-chroot.in
index bfb83a3..fd6140e 100644
--- a/arch-chroot.in
+++ b/arch-chroot.in
@@ -13,6 +13,13 @@ usage: ${0##*/} chroot-dir [command]
If 'command' is unspecified, ${0##*/} will launch /bin/bash.
+Note that when using arch-chroot, the target chroot directory *should* be a
+mountpoint. This ensures that tools such as pacman(8) or findmnt(8) have an
+accurate hierarchy of the mounted filesystems within the chroot.
+
+If your chroot target is not a mountpoint, you can bind mount the directory on
+itself to make it a mountpoint, i.e. 'mount --bind /your/chroot /your/chroot'.
+
EOF
}
@@ -70,6 +77,10 @@ shift
[[ -d $chrootdir ]] || die "Can't create chroot on non-directory %s" "$chrootdir"
+if ! mountpoint -q "$chrootdir"; then
+ warning "$chrootdir is not a mountpoint. This may have undesirable side effects."
+fi
+
chroot_setup "$chrootdir" || die "failed to setup chroot %s" "$chrootdir"
chroot_add_resolv_conf "$chrootdir" || die "failed to setup resolv.conf"