From: Henning Schild <henning.schild@siemens.com>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 2/2] isar-image: refactor do_rootfs()
Date: Wed, 7 Nov 2018 19:45:31 +0100 [thread overview]
Message-ID: <20181107194531.17356c59@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20181101101302.8674-2-Cedric_Hombourger@mentor.com>
Am Thu, 1 Nov 2018 11:13:02 +0100
schrieb Cedric Hombourger <Cedric_Hombourger@mentor.com>:
> Split the do_rootfs() shell function into four (smaller) shell
> functions to generate the fstab file (isar_image_gen_fstab), populate
> the root file-system (isar_image_gen_rootfs), configure it
> (isar_image_conf_rootfs) and perform some house-keeping
> (isar_image_cleanup). do_rootfs is now a python function and
> sequentially calls the helper functions listed above.
>
> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> ---
> meta/classes/isar-image.bbclass | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/isar-image.bbclass
> b/meta/classes/isar-image.bbclass index ec2b9e3..e0508be 100644
> --- a/meta/classes/isar-image.bbclass
> +++ b/meta/classes/isar-image.bbclass
> @@ -21,7 +21,7 @@ ISAR_RELEASE_CMD ?= "${ISAR_RELEASE_CMD_DEFAULT}"
> do_rootfs[root_cleandirs] = "${IMAGE_ROOTFS} \
> ${IMAGE_ROOTFS}/isar-apt"
>
> -do_rootfs() {
> +isar_image_gen_fstab() {
> cat > ${WORKDIR}/fstab << EOF
> # Begin /etc/fstab
> /dev/root / auto
> defaults 0 0 @@ -33,11 +33,15 @@
> devtmpfs /dev devtmpfs
> mode=0755,nosuid 0 0 # End /etc/fstab
> EOF
> +}
>
> +isar_image_gen_rootfs() {
> setup_root_file_system --clean --keep-apt-cache \
> --fstab "${WORKDIR}/fstab" \
> "${IMAGE_ROOTFS}" ${IMAGE_PREINSTALL} ${IMAGE_INSTALL}
> +}
>
> +isar_image_conf_rootfs() {
> # Configure root filesystem
> if [ -n "${DISTRO_CONFIG_SCRIPT}" ]; then
> sudo install -m 755 "${WORKDIR}/${DISTRO_CONFIG_SCRIPT}"
> "${IMAGE_ROOTFS}" @@ -45,7 +49,9 @@ EOF
> "${BAUDRATE_TTY}"
> sudo rm "${IMAGE_ROOTFS}/${DISTRO_CONFIG_SCRIPT}"
> fi
> +}
>
> +isar_image_cleanup() {
> # Cleanup
> sudo rm "${IMAGE_ROOTFS}/etc/apt/sources.list.d/isar-apt.list"
> test ! -e "${IMAGE_ROOTFS}/usr/share/doc/qemu-user-static" && \
> @@ -57,3 +63,10 @@ EOF
> sudo umount -l ${IMAGE_ROOTFS}/proc
> sudo rm -f
> "${IMAGE_ROOTFS}/etc/apt/apt.conf.d/55isar-fallback.conf" }
> +
> +python do_rootfs() {
> + bb.build.exec_func("isar_image_gen_fstab", d)
> + bb.build.exec_func("isar_image_gen_rootfs", d)
> + bb.build.exec_func("isar_image_conf_rootfs", d)
> + bb.build.exec_func("isar_image_cleanup", d)
> +}
I am loosing my proxies somewhere in current next ... i suspect this
guy but did not confirm yet.
Henning
next prev parent reply other threads:[~2018-11-07 18:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:12 [PATCH 0/4] add support for OE's ROOTFS_*_COMMAND Cedric Hombourger
2018-10-29 16:13 ` [PATCH 1/4] isar-image-base: introduce and use isar-image class Cedric Hombourger
2018-11-09 13:42 ` Baurzhan Ismagulov
2018-10-29 16:13 ` [PATCH 2/4] isar-image: refactor do_rootfs() Cedric Hombourger
2018-11-29 15:06 ` Jan Kiszka
2018-10-29 16:13 ` [PATCH 3/4] base: add 'lib' folder of each layer to python's module search path Cedric Hombourger
2018-10-29 16:13 ` [PATCH 4/4] isar-image: add support for OE's ROOTFS_*_COMMAND Cedric Hombourger
2018-10-29 16:45 ` [PATCH 0/4] " Henning Schild
2018-10-29 16:55 ` Hombourger, Cedric
2018-10-30 9:25 ` Henning Schild
2018-10-30 11:02 ` Hombourger, Cedric
2018-10-30 12:41 ` Henning Schild
2018-10-30 12:45 ` Hombourger, Cedric
2018-10-31 6:10 ` [PATCH v2 0/2] introduce isar-image class Cedric Hombourger
2018-10-31 6:10 ` [PATCH v2 1/2] isar-image-base: introduce and use " Cedric Hombourger
2018-10-31 6:10 ` [PATCH v2 2/2] isar-image: refactor do_rootfs() Cedric Hombourger
2018-10-31 6:39 ` [PATCH v2 0/2] introduce isar-image class Jan Kiszka
2018-10-31 6:51 ` chombourger
2018-11-01 11:43 ` Maxim Yu. Osipov
2018-11-09 13:26 ` Baurzhan Ismagulov
2018-11-01 10:13 ` [PATCH v3 1/2] isar-image-base: introduce and use " Cedric Hombourger
2018-11-01 10:13 ` [PATCH v3 2/2] isar-image: refactor do_rootfs() Cedric Hombourger
2018-11-07 13:20 ` Jan Kiszka
2018-11-08 7:59 ` Hombourger, Cedric
2018-11-08 8:28 ` Jan Kiszka
2018-11-07 18:45 ` Henning Schild [this message]
2018-11-07 19:46 ` Cedric Hombourger
2018-11-07 20:16 ` Cedric Hombourger
2018-11-08 6:52 ` Jan Kiszka
2018-11-08 8:13 ` Henning Schild
2018-11-07 13:07 ` [PATCH v3 1/2] isar-image-base: introduce and use isar-image class 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=20181107194531.17356c59@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=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