From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH v3 1/2] buildchroot+bootstrap: use rbinds for /dev and /proc
Date: Fri, 16 Nov 2018 08:31:35 -0800 [thread overview]
Message-ID: <1542385896-879-2-git-send-email-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <1542385896-879-1-git-send-email-Cedric_Hombourger@mentor.com>
Bind mount the entire hierarchy for /dev and /proc as recommended in Gentoo's
chroot setup guide.
Suggested-by: Henning Schild <henning.schild@siemens.com>
Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
---
meta/classes/buildchroot.bbclass | 6 ++++--
meta/classes/isar-bootstrap-helper.bbclass | 6 ++++--
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 6 ++++--
3 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/meta/classes/buildchroot.bbclass b/meta/classes/buildchroot.bbclass
index 870d27c..26d5e80 100644
--- a/meta/classes/buildchroot.bbclass
+++ b/meta/classes/buildchroot.bbclass
@@ -27,7 +27,9 @@ buildchroot_do_mounts() {
if ! grep -q ${BUILDCHROOT_DIR}/isar-apt /proc/mounts; then
mount --bind ${REPO_ISAR_DIR}/${DISTRO} ${BUILDCHROOT_DIR}/isar-apt
mount --bind ${DL_DIR} ${BUILDCHROOT_DIR}/downloads
- mount -t devtmpfs -o mode=0755,nosuid devtmpfs ${BUILDCHROOT_DIR}/dev
- mount -t proc none ${BUILDCHROOT_DIR}/proc
+ mount --rbind /dev ${BUILDCHROOT_DIR}/dev
+ mount --make-rslave ${BUILDCHROOT_DIR}/dev
+ mount --rbind /proc ${BUILDCHROOT_DIR}/proc
+ mount --make-rslave ${BUILDCHROOT_DIR}/proc
fi'
}
diff --git a/meta/classes/isar-bootstrap-helper.bbclass b/meta/classes/isar-bootstrap-helper.bbclass
index 1ac39db..62c0839 100644
--- a/meta/classes/isar-bootstrap-helper.bbclass
+++ b/meta/classes/isar-bootstrap-helper.bbclass
@@ -103,8 +103,10 @@ setup_root_file_system() {
sudo mount --bind ${REPO_BASE_DIR} ${ROOTFSDIR}/base-apt
fi
- sudo mount -t devtmpfs -o mode=0755,nosuid devtmpfs $ROOTFSDIR/dev
- sudo mount -t proc none $ROOTFSDIR/proc
+ sudo mount --rbind /dev ${ROOTFSDIR}/dev
+ sudo mount --make-rslave ${ROOTFSDIR}/dev
+ sudo mount --rbind /proc ${ROOTFSDIR}/proc
+ sudo mount --make-rslave ${ROOTFSDIR}/proc
# Install packages:
E="${@ bb.utils.export_proxies(d)}"
diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
index 592d042..cd93f6c 100644
--- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
+++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
@@ -241,8 +241,10 @@ isar_bootstrap() {
"${ROOTFSDIR}/chroot-setup.sh" "setup" "${ROOTFSDIR}"
# update APT
- mount -t devtmpfs -o mode=0755,nosuid devtmpfs ${ROOTFSDIR}/dev
- mount -t proc none ${ROOTFSDIR}/proc
+ mount --rbind /dev ${BUILDCHROOT_DIR}/dev
+ mount --make-rslave ${BUILDCHROOT_DIR}/dev
+ mount --rbind /proc ${BUILDCHROOT_DIR}/proc
+ mount --make-rslave ${BUILDCHROOT_DIR}/proc
export DEBIAN_FRONTEND=noninteractive
chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y
--
2.11.0
next prev parent reply other threads:[~2018-11-16 16:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 20:11 [PATCH] buildchroot: add sysfs mount since expected by some packages Cedric Hombourger
2018-11-10 7:15 ` [PATCH v2] " Cedric Hombourger
2018-11-12 9:31 ` Henning Schild
2018-11-13 4:59 ` [PATCH v3 1/2] buildchroot+bootstrap: use rbinds for /dev and /proc Cedric Hombourger
2018-11-13 4:59 ` [PATCH v3 2/2] buildchroot: add sysfs mount since expected by some packages Cedric Hombourger
2018-11-13 10:43 ` chombourger
2018-11-13 10:59 ` Jan Kiszka
2018-11-13 12:07 ` Henning Schild
2018-11-13 12:37 ` Hombourger, Cedric
2018-11-13 12:59 ` Jan Kiszka
2018-11-14 7:44 ` Henning Schild
2018-11-16 16:29 ` chombourger
2018-11-16 16:31 ` [PATCH v4 1/2] buildchroot+bootstrap: rbind mount for /dev Cedric Hombourger
2018-11-16 16:31 ` Cedric Hombourger [this message]
2018-11-16 16:31 ` [PATCH v4 2/2] buildchroot: add sysfs mount since expected by some packages Cedric Hombourger
2018-11-17 14:56 ` [PATCH v5 0/2] rbind mounts for /dev and /sys Cedric Hombourger
2018-11-17 14:56 ` [PATCH v5 1/2] buildchroot+bootstrap: rbind mount for /dev Cedric Hombourger
2018-11-19 9:25 ` Henning Schild
2018-11-20 12:36 ` chombourger
2018-11-17 14:56 ` [PATCH v5 2/2] buildchroot: add sysfs mount since expected by some packages Cedric Hombourger
2018-11-19 9:24 ` Henning Schild
2018-11-20 12:40 ` [PATCH v6 0/2] rbind mounts for /dev and /sys Cedric Hombourger
2018-11-20 12:40 ` [PATCH v6 1/2] buildchroot+bootstrap: rbind mount for /dev Cedric Hombourger
2018-11-20 12:40 ` [PATCH v6 2/2] buildchroot: add sysfs mount since expected by some packages Cedric Hombourger
2018-11-22 16:08 ` chombourger
2018-11-23 14:13 ` [PATCH v6 0/2] rbind mounts for /dev and /sys Maxim Yu. Osipov
2018-11-27 14:45 ` Maxim Yu. Osipov
2018-11-27 14:48 ` Hombourger, Cedric
2018-11-29 8:22 ` Maxim Yu. Osipov
2018-11-29 8:28 ` Hombourger, Cedric
2018-11-29 8:48 ` Maxim Yu. Osipov
2018-11-29 10:00 ` Baurzhan Ismagulov
2018-11-29 9:54 ` Henning Schild
2018-11-19 9:27 ` [PATCH v5 " Henning Schild
2018-11-19 9:30 ` Hombourger, Cedric
2018-11-13 12:06 ` [PATCH v3 1/2] buildchroot+bootstrap: use rbinds for /dev and /proc Henning Schild
2018-11-12 9:46 ` [PATCH v2] buildchroot: add sysfs mount since expected by some packages Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1542385896-879-2-git-send-email-Cedric_Hombourger@mentor.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox