dracut/test/TEST-02-SYSTEMD/test-init.sh

#!/bin/sh
: > /dev/watchdog

. /lib/dracut-lib.sh

export PATH=/usr/sbin:/usr/bin:/sbin:/bin
command -v plymouth > /dev/null 2>&1 && plymouth --quit
exec > /dev/console 2>&1

echo "dracut-root-block-success" | dd oflag=direct,dsync of=/dev/disk/by-id/ata-disk_marker

export TERM=linux
export PS1='initramfs-test:\w\$ '
[ -f /etc/mtab ] || ln -sfn /proc/mounts /etc/mtab
[ -f /etc/fstab ] || ln -sfn /proc/mounts /etc/fstab
stty sane
echo "made it to the rootfs!"
if getargbool 0 rd.shell; then
    strstr "$(setsid --help)" "control" && CTTY="-c"
    setsid $CTTY sh -i
fi
echo "Powering down."
mount -n -o remount,ro /
poweroff -f
add systemd module 13 years ago			`#!/bin/sh`
ci: use /dev/disk/by-id Due to parallel probing of the linux kernel `/dev/sd` can't be used to reliably address a hard disk. This can be seen by the many spurious failures of the dracut CI, where `mdadm` failed with error 524 or tests failed due to the success marker message written to the wrong disk. don't rely on `/dev/sd` but use disk ids and `/dev/disk/by-id/ata-disk_<name>` specify the exact qemu machine architecture `-M q35` needed for the disk ids. A later patch will move this to `run-qemu`, when all tests are converted * due to `-M q35` the interface names have changed from `ens2` -> `enp0s1` and `ens3` -> `enp0s2` 4 years ago			`: > /dev/watchdog`

fix(TEST SYSTEMD): shellcheck 4 years ago			`. /lib/dracut-lib.sh`
cope with "rd.shell=0" in the testsuite If emergency and shutdown-emergency hooks are called, the systemd should poweroff the testsuite, therefore "rd.shell=0" is given on the test suite kernel command lines. "rd.shell=0" has to be parsed correctly by the test suite real root init also. 9 years ago
fix: make testsuite pass on OpenSuse and Arch This removes some hard assumptions about the file system layout. It also hardens the tests with network interface renaming rules and guards. 4 years ago			`export PATH=/usr/sbin:/usr/bin:/sbin:/bin`
fix(TEST SYSTEMD): shellcheck 4 years ago			`command -v plymouth > /dev/null 2>&1 && plymouth --quit`
			`exec > /dev/console 2>&1`
test: correct cmdline reading functions 9 years ago
ci: use /dev/disk/by-id Due to parallel probing of the linux kernel `/dev/sd` can't be used to reliably address a hard disk. This can be seen by the many spurious failures of the dracut CI, where `mdadm` failed with error 524 or tests failed due to the success marker message written to the wrong disk. don't rely on `/dev/sd` but use disk ids and `/dev/disk/by-id/ata-disk_<name>` specify the exact qemu machine architecture `-M q35` needed for the disk ids. A later patch will move this to `run-qemu`, when all tests are converted * due to `-M q35` the interface names have changed from `ens2` -> `enp0s1` and `ens3` -> `enp0s2` 4 years ago			`echo "dracut-root-block-success" \| dd oflag=direct,dsync of=/dev/disk/by-id/ata-disk_marker`

add systemd module 13 years ago			`export TERM=linux`
			`export PS1='initramfs-test:\w\$ '`
			`[ -f /etc/mtab ] \|\| ln -sfn /proc/mounts /etc/mtab`
			`[ -f /etc/fstab ] \|\| ln -sfn /proc/mounts /etc/fstab`
			`stty sane`
			`echo "made it to the rootfs!"`
cope with "rd.shell=0" in the testsuite If emergency and shutdown-emergency hooks are called, the systemd should poweroff the testsuite, therefore "rd.shell=0" is given on the test suite kernel command lines. "rd.shell=0" has to be parsed correctly by the test suite real root init also. 9 years ago			`if getargbool 0 rd.shell; then`
style: shfmt reformat reproducible with: ``` $ shfmt_version=3.0.1 $ wget "https://github.com/mvdan/sh/releases/download/v${shfmt_version}/shfmt_v${shfmt_version}_linux_amd64" -O shfmt $ chmod u+x shfmt $ ./shfmt -w . ``` 4 years ago			`strstr "$(setsid --help)" "control" && CTTY="-c"`
			`setsid $CTTY sh -i`
add systemd module 13 years ago			`fi`
			`echo "Powering down."`
			`mount -n -o remount,ro /`
			`poweroff -f`