Do not "exit" if boot option nonetworking is set but "return" instead

Nowadays we're running under one main script which sources all
the further scripts. If we 'exit' in a script then we'd just exit
the main init sequence, resulting in a kernel trace because the
real™ init hasn't been found/executed.

Thanks to Florian Ermisch <floh.edo@googlemail.com> for the initial bug report
Refresh debian/patches/
Release new version 4.0~a13-1+grml.2
Update 9990-misc-helpers.sh to support latest udev version [Closes: issue1278]

When booting the ISO in hard-disk mode udev's
'udevadm test-builtin' emits this error message:

| calling: test-builtin
| error reading /lib/udev/hwdb.bin: No such file or directory
| load module index
| unload module index

and fails to boot because using udevadm test-builtin in the
is_nice_device function no longer recognizes proper DEVICES.

Including the /lib/udev/hwdb.bin file in the initramfs doesn't
help either as udevadm test-builtin was a debug interface and
never supposed to be used public.

This patch addresses the issue by using udevadm info and checking
if the DEVTYPE of the device is 'disk'. This should work with the
majority of DEVICES.

Closes: https://github.com/grml/live-boot-grml/pull/3

Thanks: Ulrich Dangel <mru@spamt.net> for the initial patch
Thanks: Michael Biebl <biebl@debian.org> for helping in resolve this issue
Release new version 4.0~a13-1+grml.3
Add patch to properly boot from mdadm via findiso boot option [Closes: issue1270]

For example grml-rescueboot uses findiso for booting the ISO.
When booting from a software RAID using mdadm then
/scripts/local-top/mdadm being used inside
/scripts/boot/9990-misc-helpers.sh leaks its output to the
environment, causing invalid data used inside the
mount_images_in_directory function. Because the invalid data
results in a failing mount_images_in_directory execution we end
up with failed boot and error message:

  "No supported filesystem images found at ...."

So instead redirect output of /scripts/local-top/mdadm to
/boot.log. Also make sure to check for existence of
/conf/conf.d/md before accessing it (the file doesn't always
exist).

While at it also make sure the same logic is used for
/scripts/local-top/lvm2.

Thanks: thinkgear <thinkgear@thinkgear.net> for reporting and providing a test VM
Release new version 4.0~a13-1+grml.4
Add support for label "persistence" to forensic mode

Since Grml release 2013.02 the live-boot code uses the label
persistence as the default.
Release new version 4.0~a13-1+grml.5