linux/poky.git/meta/recipes-core/initscripts, branch yocto-3.1.23

initscripts: run umountnfs as a KILL script

2022-08-22T13:29:49+00:00

`rc` runs all the KILL scripts in a runlevel before the START scripts. The umountnfs script is currently configured as a START script, and runs after the networking KILL script. During shutdown, this causes a ~3 minute timeout after networking is shutdown when the system tries to connect to and unmount any mounted network shares. Fix this by changing the script configuration to "stop" so that it can run before networking is stopped and unmount any network shares safely. (From OE-Core rev: e59c72d570102d72786e44c8ace69fd4d0e8e5ef) Signed-off-by: Shruthi Ravichandran Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit c419bd4537756e9f6c2fe6da3a9b798526e27eca) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

initscripts: use quotes for shell variable comparision

2021-01-09T09:17:16+00:00

Helps to execute it with busybox shell (From OE-Core rev: 4e7338614f9c02a0a846645a51a78ddb69253f60) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie (cherry picked from commit 45ba0ca0352bca46f974d28781ac935d8e9ec3ea) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

initscripts: Fix populate-volatile.sh bug when file/dir exists

2020-08-07T20:20:21+00:00

The blocks which test for entry exitence (file or directory) use a `A && B || C` syntax. This form is not behaving as a if-then-else block even the code logic assumes that. C may run when A is true which breaks the case where VERBOSE is 'no' but the file/directory exists. Along with fixing these specific issues, this patch fixes the other instances where blocks of form `A && B || C` are used as if-then-else. (From OE-Core rev: 471094f8afa57548e9ff3fd7a99306f58b87d478) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie (cherry picked from commit 1b9ea22acb66554925720e04cf24100664234574) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

initscripts: Fix various shellcheck warnings in populate-volatile.sh

2020-08-07T20:20:21+00:00

(From OE-Core rev: 2c44581c3be7f1330f32870f9a9721a53a49f62b) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie (cherry picked from commit 0a128a238f63d52aa82f8c63ee2f84ab528b3346) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

initscripts: update postinst

2020-07-07T22:15:10+00:00

in container image, it don't have init system, install package initscripts will report error: systemctl: command not found fix by use same way as systemd.bbclass to decide if systemctl mask will run (From OE-Core rev: 6622515c1fa7025543aea37c4b37831577485811) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie (cherry picked from commit 790276bde066ecc9876120c3097dcd57a9936f00) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

initscripts/sysfs.sh: Mount /sys/firmware/efi/efivars when possible

2019-11-10T14:06:10+00:00

Without this change, efibootmgr is unable to recover BootOrder if lost during a previous write operation, e.g. exceeded storage capacity. This is problematic using EFI to manage boot flow from Linux (E.g. via RAUC). https://www.kernel.org/doc/Documentation/filesystems/efivarfs.txt (From OE-Core rev: 0fb92b500b7d6b84368ca3a85e675400c6473987) Signed-off-by: Haris Okanovic Signed-off-by: Richard Purdie

initscripts: enable alignment.sh init script for big endian ARM

2019-09-18T11:09:02+00:00

(From OE-Core rev: 2e00755bf231f1de5ab96ee5de0859cb0930d544) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

initscripts: remove warnings on read-only-rootfs (again)

2019-08-28T10:31:21+00:00

When the populate-volatile.sh initscript tests if a configured symlink is already in place, it uses readlink with the '-f' (follow) option: > [ "$(readlink -f $source)" = "$dest" ] If the test fails, it proceeds to delete the exisiting folder/file, and create the configured symlink. However, the '-f' option to readlink makes it follow symlinks pointing at symlinks. If the $dest argument is a symlink, the above test fails, and warnings are printed due to changing a read-only rootfs. This is the case for /tmp, and /etc/resolv.conf: > /tmp -> /var/tmp -> /var/volatile/tmp > /etc/resolv.conf -> /var/run/resolv.conf -> /run/resolv.conf Fix the warnings by removing the '-f' option, so that the test matches the configuration. [ YOCTO #10814 ] (From OE-Core rev: fb028a0a25c02ab56ad262afd8e6e9495a44673d) Signed-off-by: Martin Hundebøll Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie

initscripts: Add support for /etc/default/timestamp

2019-03-04T22:57:05+00:00

Source /etc/default/timestamp if present. This allows the rootfs to be read-only / store the file in a persistant location if the whole rootfs is updated. (From OE-Core rev: b4de37b7176630d9585b12c50d537cd561c7aeb9) Signed-off-by: Jeroen Hofstee Signed-off-by: Richard Purdie

initscripts: Update volatiles documentation to include binds

2019-02-19T16:14:57+00:00

Volatiles processing now handles bind mounts, so update the comment in the core file to indicate this. (From OE-Core rev: 520e8f5721aab90815186533038c2f9f834546d5) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie