initramfs-tools will use shellcheck on its own code and will probably
ship a shellcheck autopkgtest that checks its hooks and script
directory. That's how the shellcheck issues in systemd's initramfs-tools
scripts were found.
```
shellcheck -e SC1091 $(find debian/extra/initramfs-tools/ -type f)
```
This updates the initramfs-tools init-top udev script to trigger udevadm
actions with type specified. This mimicks the
systemd-udev-trigger.service. Without type specified only devices are
triggered, but triggering subsystems may also be required and should happen
before triggering the devices. This is the case for example on s390x with zdev
generated udev rules.
LP: #1713536
initramfs-tools is not actually using util-linux mount (yet), so making
mount -n --move the first alternative would trigger an error message if
users have built their initramfs without busybox support.
Due to recent changes in busybox and initramfs-tools the mount
utility is no longer the one from busybox but from util-linux.
The latter does not support mount -o move.
The former supports both -o move and --move, so use it instead to be
compatible with both.
See this discussion for more details:
https://bugs.debian.org/823856Closes: #844775
This Linux kernel module has been broken since 2.6.30 and as a result
was removed in 3.5. The Debian Jessie kernel no longer ships this
module.
Closes: #752775
This does not concern udev in particular, but is handled by initramfs-tools
itself (scripts/local). The intention of this parameter is not to statically
wait for the given time, but wait *up to* that time for the root device to
appear.
Thanks to Thomas Conté for pointing this out!
