public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] move expand-on-first-boot to /usr/lib
Date: Mon, 28 Oct 2024 10:53:02 +0300	[thread overview]
Message-ID: <186720fe12f4e02f2d61e58bd24a5a52d67f9832.camel@ilbers.de> (raw)
In-Reply-To: <20241021085802.234809-1-felix.moessbauer@siemens.com>

On Mon, 2024-10-21 at 10:58 +0200, 'Felix Moessbauer' via isar-users
wrote:
> All non-example, non user / admin executables belong to
> /usr/lib/<package>.
> Hence, move the expand-on-first-boot script there as well. This
> solves an
> issue in hardened systems where /usr/share is marked non-executable.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  .../expand-on-first-boot/expand-on-first-boot_1.5.bb          | 4
> ++--
>  .../expand-on-first-boot/files/expand-on-first-boot.service   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-support/expand-on-first-boot/expand-on-
> first-boot_1.5.bb b/meta/recipes-support/expand-on-first-boot/expand-
> on-first-boot_1.5.bb
> index ebb22c84..2596706d 100644
> --- a/meta/recipes-support/expand-on-first-boot/expand-on-first-
> boot_1.5.bb
> +++ b/meta/recipes-support/expand-on-first-boot/expand-on-first-
> boot_1.5.bb
> @@ -29,6 +29,6 @@ SRC_URI = " \
>      file://expand-last-partition.sh"
>  
>  do_install() {
> -    install -d -m 755 ${D}/usr/share/expand-on-first-boot
> -    install -m 755 ${WORKDIR}/expand-last-partition.sh
> ${D}/usr/share/expand-on-first-boot/
> +    install -d -m 755 ${D}/usr/lib/expand-on-first-boot
> +    install -m 755 ${WORKDIR}/expand-last-partition.sh
> ${D}/usr/lib/expand-on-first-boot/
>  }
> diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-
> on-first-boot.service b/meta/recipes-support/expand-on-first-
> boot/files/expand-on-first-boot.service
> index 58f4b55b..6f1799b9 100644
> --- a/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-
> first-boot.service
> @@ -14,7 +14,7 @@ ConditionPathIsReadWrite=/tmp
>  
>  [Service]
>  Type=oneshot
> -ExecStart=/usr/share/expand-on-first-boot/expand-last-partition.sh
> +ExecStart=/usr/lib/expand-on-first-boot/expand-last-partition.sh
>  ExecStartPost=-/bin/systemctl disable expand-on-first-boot.service
>  ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
>  
> -- 
> 2.39.5
> 

Applied to next, thanks.

-- 
Best regards,
Uladzimir.



-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/186720fe12f4e02f2d61e58bd24a5a52d67f9832.camel%40ilbers.de.

      reply	other threads:[~2024-10-28  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  8:58 'Felix Moessbauer' via isar-users
2024-10-28  7:53 ` Uladzimir Bely [this message]

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=186720fe12f4e02f2d61e58bd24a5a52d67f9832.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=felix.moessbauer@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