lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 0d9cf29 08/18: Clarify documentation


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 0d9cf29 08/18: Clarify documentation
Date: Thu, 21 May 2020 19:43:11 -0400 (EDT)

branch: master
commit 0d9cf29c23f1cfcf97a4494e290df2501dddee7c
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>

    Clarify documentation
    
    The host's /var presumably always exists (gobolinux and nixos
    notwithstanding). But a debian chroot's /var presumably does not exist
    until debootstrap has been run (at present, the centos and redhat
    scripts create the chroot's /var/cache/apt/archives/ before running
    debootstrap, but that seems uncultured).
---
 lmi_setup_11.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lmi_setup_11.sh b/lmi_setup_11.sh
index bd1ca9c..3c23e73 100755
--- a/lmi_setup_11.sh
+++ b/lmi_setup_11.sh
@@ -65,7 +65,7 @@ type=plain
 EOF
 
 # Bind-mount apt archives for the chroot's debian release. Do this:
-#   - after invoking 'debootstrap', so that /var exists; and
+#   - after invoking 'debootstrap', so the chroot's /var exists; and
 #   - before invoking 'apt-get' in the chroot, to save bandwidth; and
 #   - while not chrooted, so that the host filesystem is accessible.
 mount --bind "${CACHEDIR}" /srv/chroot/"${CHRTNAME}"/var/cache/apt/archives



reply via email to

[Prev in Thread] Current Thread [Next in Thread]