From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 1/1] meta/isar-bootstrap: deactivate daemon activation in chroot environment
Date: Tue, 5 Jun 2018 13:05:43 +0200 [thread overview]
Message-ID: <61268cf1-e32b-29d8-cb20-bbaddbd76aa7@siemens.com> (raw)
In-Reply-To: <20180604112159.18605-2-claudius.heine.ext@siemens.com>
On 2018-06-04 13:21, [ext] claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Daemons are started in postinst steps of debian packages. Those daemons
> should not be started within the chroot environment, since they will be
> left running.
>
> This commit disables the execution of daemons the same way upstream
> debian does it in debootstrap and debian-installer, by replacing deamon
> executing binaries with fake ones.
>
> This is then reversed in the image cleanup step.
>
> Signed-off-by: Claudius Heine <ch@denx.de>
> ---
> meta/classes/isar-bootstrap-helper.bbclass | 2 +
> .../isar-bootstrap/files/chroot-setup.sh | 133 ++++++++++++++++++
> .../isar-bootstrap/isar-bootstrap.bb | 11 +-
> 3 files changed, 144 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-core/isar-bootstrap/files/chroot-setup.sh
>
> diff --git a/meta/classes/isar-bootstrap-helper.bbclass b/meta/classes/isar-bootstrap-helper.bbclass
> index 4195a88..6101e9a 100644
> --- a/meta/classes/isar-bootstrap-helper.bbclass
> +++ b/meta/classes/isar-bootstrap-helper.bbclass
> @@ -74,5 +74,7 @@ setup_root_file_system() {
> /usr/bin/apt-get autoremove --purge --yes
> sudo -E chroot "$ROOTFSDIR" \
> /usr/bin/apt-get clean
> + sudo "$ROOTFSDIR/chroot-setup.sh" "cleanup" "$ROOTFSDIR"
> + sudo rm -f "$ROOTFSDIR/chroot-setup.sh"
> fi
> }
> diff --git a/meta/recipes-core/isar-bootstrap/files/chroot-setup.sh b/meta/recipes-core/isar-bootstrap/files/chroot-setup.sh
> new file mode 100644
> index 0000000..801e005
> --- /dev/null
> +++ b/meta/recipes-core/isar-bootstrap/files/chroot-setup.sh
> @@ -0,0 +1,133 @@
> +#!/bin/sh
> +# This file is based on:
> +# https://salsa.debian.org/installer-team/debian-installer-utils/blob/master/chroot-setup.sh
What's the license of this? I would assume - in the absence of any
specific statement - it's GPL. Then this should be documented here,
specifically as it deviates from the Isar default license.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-06-05 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 11:21 [PATCH 0/1] Disable daemon activation claudius.heine.ext
2018-06-04 11:21 ` [PATCH 1/1] meta/isar-bootstrap: deactivate daemon activation in chroot environment claudius.heine.ext
2018-06-05 11:05 ` Jan Kiszka [this message]
2018-06-04 17:36 ` [PATCH 0/1] Disable daemon activation Henning Schild
2018-06-04 17:48 ` Claudius Heine
2018-06-04 18:02 ` Henning Schild
2018-06-05 8:42 ` Maxim Yu. Osipov
2018-06-05 11:52 ` Claudius Heine
2018-06-05 12:38 ` Maxim Yu. Osipov
2018-06-05 12:45 ` Claudius Heine
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=61268cf1-e32b-29d8-cb20-bbaddbd76aa7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.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