public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
	isar-users@googlegroups.com
Cc: claudius.heine.ext@siemens.com
Subject: Re: [PATCH] meta-isar/example-raw: Remove /etc/resolv.conf in postinst
Date: Tue, 17 Apr 2018 15:03:28 +0200	[thread overview]
Message-ID: <9f1829c8-331e-031c-8c03-37cc5b76c44a@siemens.com> (raw)
In-Reply-To: <20180417124618.30964-1-henning.schild@siemens.com>

On 2018-04-17 14:46, [ext] Henning Schild wrote:
> Issue: debootstrap copies /etc/resolv.conf from the host into the
> rootfs, and we need it there to use apt-get. But we do not always want
> it there after we are done installing
> 
> Fix: remove the leaked file in our image customization package, to reach
> a defined state. That happens to be the state we had with multistrap.
> 
> Impact: images will not contain a resolv.conf anymore, just like in the
> multistrap days. If you want one do not install example-raw and
> customize in your own hook
> 
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
>  meta-isar/recipes-app/example-raw/files/postinst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/meta-isar/recipes-app/example-raw/files/postinst b/meta-isar/recipes-app/example-raw/files/postinst
> index f60be8c..385473e 100644
> --- a/meta-isar/recipes-app/example-raw/files/postinst
> +++ b/meta-isar/recipes-app/example-raw/files/postinst
> @@ -19,4 +19,8 @@ chown -R isar:isar /var/lib/isar
>  # but we take the same password for this example
>  echo "root:root" | chpasswd
>  
> +# debootstrap will leak these two files from the build host, get them
> +# into a defined state
> +# every image will have to handle these two somehow
>  echo "isar" > /etc/hostname
> +rm -f /etc/resolv.conf

That cleaning should go into the generic images. It's not a customization.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-04-17 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 12:46 Henning Schild
2018-04-17 13:03 ` Jan Kiszka [this message]
2018-04-17 13:20   ` Henning Schild
2018-04-17 13:23     ` Jan Kiszka
2018-04-17 15:09       ` Henning Schild
2018-04-17 15:37 ` [PATCH] isar-bootstrap: Remove leaked hostname and resolv.conf from images Henning Schild
2018-04-19 15:35   ` Claudius Heine
2018-04-20 12:05     ` Henning Schild
2018-04-25 11:21   ` Jan Kiszka
2018-04-25 11:52     ` Alexander Smirnov
2018-04-25 13:33       ` Alexander Smirnov

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=9f1829c8-331e-031c-8c03-37cc5b76c44a@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=claudius.heine.ext@siemens.com \
    --cc=henning.schild@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