From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 5/6] scripts: Add helper scripts to mount/umount chroot directory.
Date: Thu, 14 Jun 2018 11:28:45 +0200 [thread overview]
Message-ID: <20180614112845.13d7e15d@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180613135829.3151-6-mosipov@ilbers.de>
Am Wed, 13 Jun 2018 15:58:28 +0200
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Mount/umount the required directories in chroot by passing path to
> rootfs directory as an argument.
>
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> scripts/mount_chroot.sh | 7 +++++++
> scripts/umount_chroot.sh | 7 +++++++
> 2 files changed, 14 insertions(+)
> create mode 100755 scripts/mount_chroot.sh
> create mode 100755 scripts/umount_chroot.sh
>
> diff --git a/scripts/mount_chroot.sh b/scripts/mount_chroot.sh
> new file mode 100755
> index 0000000..8390edb
> --- /dev/null
> +++ b/scripts/mount_chroot.sh
> @@ -0,0 +1,7 @@
> +#!/bin/bash
> +sudo mount /tmp $1/tmp -o bind
> +sudo mount proc $1/proc -t proc -o nosuid,noexec,nodev
> +sudo mount sysfs $1/sys -t sysfs -o nosuid,noexec,nodev
> +sudo mount devtmpfs $1/dev -t devtmpfs -o mode=0755,nosuid
> +sudo mount devpts $1/dev/pts -t devpts -o gid=5,mode=620
> +sudo mount tmpfs $1/dev/shm -t tmpfs -o
> rw,seclabel,nosuid,nodev diff --git a/scripts/umount_chroot.sh
> b/scripts/umount_chroot.sh new file mode 100755
> index 0000000..a4abde0
> --- /dev/null
> +++ b/scripts/umount_chroot.sh
> @@ -0,0 +1,7 @@
> +#!/bin/bash
> +sudo umount $1/tmp
> +sudo umount $1/proc
> +sudo umount $1/sys
> +sudo umount $1/dev
> +sudo umount $1/dev/pts
> +sudo umount $1/dev/shm
I already mentioned those "sudos" should go, from both scripts. It
might be a good idea to invent something like an fstab that both
scripts access, and "set -e". For umount you could also check whether
"--recursive" can be used, that way you would not have to mention all
directories twice and the fstab idea would not be needed.
Henning
next prev parent reply other threads:[~2018-06-14 9:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:58 [RFC PATCH 0/6] ISAR SDK root filesystem Maxim Yu. Osipov
2018-06-13 13:58 ` [RFC PATCH 1/6] isar-bootstrap-helper: Add option --copyrepo to setup_root_file_system() Maxim Yu. Osipov
2018-06-14 8:51 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 2/6] isar-debootstrap: split into host and target recipes Maxim Yu. Osipov
2018-06-14 8:59 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 3/6] sdkchroot: Added recipe-devel to create SDK root filesystem Maxim Yu. Osipov
2018-06-14 9:19 ` Henning Schild
2018-06-14 10:46 ` Maxim Yu. Osipov
2018-06-14 11:07 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 4/6] meta/class/image: Add do_isar task to trigger SDK rootfs creation Maxim Yu. Osipov
2018-06-14 9:23 ` Henning Schild
2018-06-14 11:49 ` Maxim Yu. Osipov
2018-06-18 9:56 ` Baurzhan Ismagulov
2018-06-13 13:58 ` [RFC PATCH 5/6] scripts: Add helper scripts to mount/umount chroot directory Maxim Yu. Osipov
2018-06-14 9:28 ` Henning Schild [this message]
2018-06-13 13:58 ` [RFC PATCH 6/6] doc: Add description of ISAR SDK root filesystem creation Maxim Yu. Osipov
2018-06-14 8:48 ` [RFC PATCH 0/6] ISAR SDK root filesystem Henning Schild
2018-06-14 8:51 ` Jan Kiszka
2018-06-14 9:34 ` Henning Schild
2018-06-14 9:46 ` Maxim Yu. Osipov
2018-06-18 7:08 ` Henning Schild
2018-06-19 7:33 ` 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=20180614112845.13d7e15d@md1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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