linux/poky.git/meta/recipes-core/initrdscripts, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

initramfs-framework: drop redundant /var/lock directory creation

2025-10-27T11:37:43+00:00

base-files already provides /var/lock as a symbolic link to /run/lock, and since /run is created and mounted as tmpfs during init, there is no need to explicitly create /var/lock within initramfs. This avoids the following spurious error during boot: mkdir: can't create directory '/var/lock': No such file or directory (From OE-Core rev: 24629a0e81291900edf0967bb218ba51dfa90ce9) Signed-off-by: Ricardo Salveti Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

initramfs-framework: mount /run and move to rootfs before switch_root

2025-08-21T09:29:56+00:00

Mount /run as tmpfs during early init and include it in the set of mounts moved to $ROOTFS_DIR prior to exec switch_root. Having /run available early lets initramfs modules stamp state that can later influence systemd service jobs, since systemd will reuse the mount point instead of creating a new one during boot. This is particularly useful with ostree, as it uses /run/ostree-booted as way to describe that the rootfs comes from an ostree deployment. (From OE-Core rev: 3a4bd7ddefbf5b412a2b4031d491f5a50f1908cd) Signed-off-by: Ricardo Salveti Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

nfsrootfs: disable warning message if bootargs root parameter have not been defined

2025-06-26T10:02:34+00:00

we have case that don't define root in bootargs, if [ ${bootparam_root} != "/dev/nfs" ] will output warning "/init.d/85-nfsrootfs: line 4: [: !=: unary operator expected" let variable expension result become string to solve this problem (From OE-Core rev: d50e12e5ae6a72535cacd0f767b1be1f89278f79) Signed-off-by: Jimmy Ho Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: set S from UNPACKDIR in recipes that use only local files

2025-06-20T11:07:26+00:00

There is no need to have two assignments; also setting S from UNPACKDIR (and not vice versa) is more logical as unpack task comes first, and tasks that come after unpack use S to access unpack results. Also adjust reference test data in selftest/recipeutils to reflect changes in test recipes. (From OE-Core rev: f64b7e5fb3181734c8dde87b27e872a026261a74) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

initramfs-framework: remove hard dependency with busybox

2025-04-11T10:49:59+00:00

In 'finish'script the Switch_root command with option -c is busybox specific. When package-core-base-utils is selected the boot is breaking with message "Switch_root: invalid option — ‘c’.It was reproduced using qemu. Remove -c option to make it compatible with both providers. It is tested using qemu with busybox and package-core-base-utils. In both cases qemu boots successfully and filesystem is accessible. Fixes [YOCTO #15716] CC: Yoann Congal CC: Randy MacLeod CC: jbk CC: Raj Khem CC: Adrian Freihofer (From OE-Core rev: 0f745024fd40518f98390008b4f613d5641df416) Signed-off-by: Christos Gavros Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

initrdscripts: add UBI support

2025-01-08T12:37:20+00:00

Mounting the rootfs failed when it was on UBI. This patch allows the rootfs to live on UBI. (From OE-Core rev: 197867f854cc19493b28fcd2300179cfc407e0a6) Signed-off-by: Walter Schweizer Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

initramfs-module-install: remove loongarch64 from COMPATIBLE_HOST

2025-01-03T11:05:03+00:00

Due to initramfs-module-install runtime depend on grub, and grub did not support loongarch64, remove loongarch64 from COMPATIBLE_HOST $ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf $ bitbake world |ERROR: Nothing RPROVIDES 'grub' (but oe-core/meta/recipes-core/initrdscripts/ initramfs-module-install_1.0.bb RDEPENDS on or otherwise requires it) |grub was skipped: incompatible with host loongarch64-wrs-linux (not in COMPATIBLE_HOST) |NOTE: Runtime target 'grub' is unbuildable, removing... |Missing or unbuildable dependency chain was: ['grub'] |ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. |Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'initramfs-module-install', 'grub'] (From OE-Core rev: 6440e1010ade2b4207879a2e8cd288bcd714a445) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

initramfs-framework: init: fix typo

2024-09-30T16:00:51+00:00

Amend a small typing error. (From OE-Core rev: c4ca9161d9de1a522a34c9088dedf6c346afbbed) Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Purdie