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

toolchain-shar-extract/init-install-efi-testfs: Unify question spaces

2019-04-04T21:57:32+00:00

unify the spacing for questions in various places e.g. before the [Y/n] there should be a space, and before "?" there should be none. Unify the questions where the system expect an answer from the end user. (From OE-Core rev: 7a3f128b19e55b751e81bc676e5946544b0c8735) Signed-off-by: Gianfranco Costamagna Signed-off-by: Gianfranco Costamagna Signed-off-by: Richard Purdie

initramfs-framework: add lvm module

2019-03-25T23:13:48+00:00

lvm module will initial lvm volume to support boot from Logical Volume. (From OE-Core rev: 3a4213f014fc4aa5be05dfc0722d87e01e5ff10c) Signed-off-by: Liwei Song Signed-off-by: Richard Purdie

initramfs-framework: mount efivarfs to make Intel VROC work well

2019-03-25T23:13:48+00:00

efivafs contain some meta data about Intel VROC, which will be used by mdadm to create raid device. These are preparation work to support boot from Intel VROC RAID disk. (From OE-Core rev: b25869c76975bbcec8d2f22f680e58976ec4de5c) Signed-off-by: Liwei Song Signed-off-by: Richard Purdie

initramfs-boot: create /dev/console

2019-01-11T10:39:09+00:00

The Yocto kernel expects a proper /dev/console to exist before running init, otherwise booting will fail with the message: Kernel panic - not syncing: /dev/console is missing or not a character device! Please ensure your rootfs is properly configured Add similar fix as was done for initramfs-framework and initramfs-live-boot in commits 0352841cd92f6316bcac092e2fff9d28c352b36b 1b64664f0c388f41084f5db6e46e3e68c53fb6d9 (From OE-Core rev: 490d6fbd14805b6c72b525fbe8c9c6e08d796597) Signed-off-by: Jacob Kroon Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

init-install-efi.sh: improve info message

2018-10-12T15:57:21+00:00

Let users know that the installation was successful and that pressing Enter would lead to a reboot. (From OE-Core rev: a5993d9afab060d07213c14c0188422c9e258693) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

initramfs-framework/udev: call settle before kill

2018-09-20T12:41:31+00:00

When mount command is executed in rootfs module of initrd, eudev creates a loop0 device node, applies rules and adds a inotify watch to it. Right after this step, we execute finish which first tries to kill any running udevd daemon before doing a switch_root. In some cases, it is possible that switch_root is executed before inotify_add_watch was actually processed which would lead to errors like: | inotify_add_watch(6, /dev/loop0, 10) failed: No such file or directory Make sure that we process all the events in queue before actually trying to kill udevd to prevent this race. Fixes [YOCTO #12861] (From OE-Core rev: a85c34d263fcf1542bbedcaf1634302466bb20cf) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

initramfs-framework: Don't use 'tr'

2018-09-13T16:38:07+00:00

tr is available in busybox, but not in toybox. Just use sed instead. (From OE-Core rev: 518cca6711f737f44ff74a5ac1308de8c9b49e78) Signed-off-by: Andrew Bresticker Signed-off-by: Richard Purdie

busybox/packagegroups: Break out the busybox-syslog dependency

2018-09-10T11:13:07+00:00

The busybox-syslog rrecomends is proving tricky as it gets pulled in early and there are conflicts between its use of update-alternatives and busybox needing to provide those things. We already have recipes using BAD_RRECOMMENDS to remove this dependency, it probably makes sense to spell it out explicitly and allow it to be overridden more easily. This patch does this, dropping the now unneeded BAD_RRECOMMENDS. It preserves the dependency as a recommendation for now, further cleanup may allow simplication of that. This unbreaks certain build failures on the autobuilder, more as a workaround but is a change we probably want to make anyway. (From OE-Core rev: 544ade2d78f1375d9e93d6bf5842d857ddaf3530) Signed-off-by: Richard Purdie

initramfs-framework: add nfsrootfs module

2018-07-09T21:48:39+00:00

nfsrootfs module mounts rootfs via nfs parsing "nfsroot" and "ip" cmdline options. (From OE-Core rev: d1737f2dabac5e338061863c78a91b4c115365c7) Signed-off-by: Oleksii Konoplitskyi Signed-off-by: Richard Purdie

initrdscripts/init-live.sh: fix mounts w/ spaces fail to move to real rootfs

2018-06-29T10:07:45+00:00

When there are spaces in the mount points of devices e.g.: a partition mounted at "/run/media/My Root Partition-sda1", the initrd fails to move such mount points over to the corresponding directories at /media under the real root filesystem, and the mount points would appear at the same location as they were mounted on when detected by initrd, for example: here: "/run/media/My Root Partition-sda1" instead of here: "/media/My Root Partition-sda1" This causes issues such as: * The disks/partitions cannot be formated with any filesystem using e.g. mkfs.ext4 or mke2fs in general. When tried to do so by making sure the device is not mounted, it failed with errors such as: > /dev/sda1 is apparently in use by the system; will not make a filesystem here! > /dev/sda1: Device or resource busy while setting up superblock * The read/write operations become extremely slow. e.g. Under testing, it took approx. 2 hours just to copy 700 MB of data to the partition, and it took more than 40 minutes to delete that data from it. Same operations took under 5 minutes on a partition that had no spaces in its mount point (or that was successfully moved to real root by initrd and appeared under /media instead of /run/media). This commit fixes such issues by quoting the arguments of failing mount move commands and by parsing OCT or HEX encoded special characters such as spaces to ASCII charecters in the mount points as kernel populates the procfs like so. (From OE-Core rev: 6f8f984ba363f764e83290b972ec31a90aad1603) Signed-off-by: Arsalan H. Awan Signed-off-by: Richard Purdie