public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "T. Schaffner" <tobias.schaffner@siemens.com>
To: <isar-users@googlegroups.com>
Cc: <quirin.gylstorff@siemens.com>, <henning.schild@siemens.com>,
	"Tobias Schaffner" <tobias.schaffner@siemens.com>
Subject: [PATCH v2] fix broken fsck type in initramfs-fsck-hook-ext4
Date: Mon, 9 Jan 2023 09:32:20 +0100	[thread overview]
Message-ID: <20230109083220.365058-1-tobias.schaffner@siemens.com> (raw)

From: Tobias Schaffner <tobias.schaffner@siemens.com>

The initramfs-fsck-hook-ext4 script did not copy the fsck binary as the
wrong type variable was used to identify the needed filesystem type.

Set the type to ext4 as the script is ext4 only anyways.

Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
---
 .../initramfs-fsck-hook/files/initramfs.fsck.ext4.hook      | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-support/initramfs-fsck-hook/files/initramfs.fsck.ext4.hook b/meta/recipes-support/initramfs-fsck-hook/files/initramfs.fsck.ext4.hook
index 23f7c28..1bccc81 100644
--- a/meta/recipes-support/initramfs-fsck-hook/files/initramfs.fsck.ext4.hook
+++ b/meta/recipes-support/initramfs-fsck-hook/files/initramfs.fsck.ext4.hook
@@ -26,13 +26,11 @@ if [ ! -x /sbin/fsck ]; then
 	exit 0
 fi
 
-fsck_types="ext4"
-
 copy_exec /sbin/fsck
 copy_exec /sbin/logsave
 
-if prog="$(command -v fsck.${type})"; then
+if prog="$(command -v fsck.ext4)"; then
   copy_exec "$prog"
 else
-  echo "Warning: /sbin/fsck.${type} doesn't exist, can't install to initramfs, ignoring."
+  echo "Warning: /sbin/fsck.ext4 doesn't exist, can't install to initramfs, ignoring."
 fi
-- 
2.34.1


             reply	other threads:[~2023-01-09  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  8:32 T. Schaffner [this message]
2023-01-24  7:35 ` Uladzimir Bely

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=20230109083220.365058-1-tobias.schaffner@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=quirin.gylstorff@siemens.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