Use PERSISTENCE_PATH with a trailing "/".

When using PERSISTENCE_PATH we should prepend and append a pathname
separator as this is done with other user provided paths as well, e.g.
LIVE_MEDIA_PATH.
Move check for block device to mount_persistence_media().

We should only check for the persistence media path being a block device
where it is really required which is the case in mount_persistence_media().
Remount writable when moving the mountpoint of the persistence device.

If the persistence device has been mounted before, e.g. for mounting the
rootfs image file, then we should try to remount it writable. This way the
result for both cases, 1. was and 2. was not mounted before, are identical.
Blacklist devices used for /live/rootfs/* insted of /live/medium.

The path /live/medium is used for probing different devices when searching
for the live rootfs. There is no reason why that device should be banned
from being used for persistence storage. Instead the devices that are
actually used as the backing storage for the live rootfs should be banned.
Add support for persistence-storage type "directory".

This adds support for mounting a plain writable directory as the
persistence storage layer. The $PERSISTENCE_PATH and the persistence-label
are taken into account when searching for the persistence.conf file.
Updating debhelper install file to include additional scripts in new location.
Releasing debian version 4.0~a14-1.
Install components into /lib/live/boot folder.
Releasing debian version 4.0~a15-1.
Updating package descriptions.
Applying patch from Michael Prokop <mika@grml.org> to update udev usage in is_nice_device() for newer udev versions.
Releasing debian version 4.0~alpha16-1.
Rewrapping control file.
Properly boot from mdadm via findiso boot option.

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.

See http://bts.grml.org/grml/issue1270
Updating to standards version 3.9.5.
Correcting spelling typo in overlay component breaking booting from uncompressed filesystems, thanks to John Bazik <jsb@cs.brown.edu> (Closes: #728250).
Releasing debian version 4.0~alpha17-1.
Adding initial Japanese live-boot manpage translation from victory <victory.deb@gmail.com>.
Applying patch revising grammar and spelling in live-boot.7 manpage, thanks to victory <victory.deb@gmail.com>.
Updating live-boot translation files from the original English text.