* Jakub Moc wrote [14.06.12 02:49]:
I tried to reproduce the problem but unfortunately I couldn't setup a
correct virtualized environment but i still have some comments to your
changes.
> --- /usr/share/initramfs-tools/scripts/local-top/dmraid 2010-12-20
> 22:10:10.000000000 +0100
> +++ /usr/share/initramfs-tools/scripts/local-top/dmraid 2012-06-14
> 03:47:15.171595455 +0200
> @@ -2,7 +2,7 @@
>
> # local-top script for dmraid.
>
> -PREREQS=""
> +PREREQS="udev"
> prereqs()
> {
> echo $PREREQS
The udev script should already been run as it is in init-top which is
executed before local-top. So this change is IMO unnecessary.
> @@ -17,7 +17,7 @@
> esac
>
> # Activate any dmraid arrays that were not identified by udev and vol_id.
> -
> +/sbin/udevadm settle --timeout=30
> if devices=$(dmraid -r -c); then
> for dev in $devices; do
> dmraid-activate $dev
I think instead of just calling udevadm we should check if the
executable is available, e.g:
,----
| if [ -x /sbin/udevadm ]; then
| /sbin/udevadm settle --timeout=30
| elif [ -x /sbin/udevsettle ]; then
| /sbin/udevsettle --timeout=30
| fi
`----
If you can test your script without the PREREQS change i would be happy
to integrate these changes into dmraid.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
