We haven't run into this issue yet, though it was reported
on the debian-live mailing list:
https://lists.debian.org/debian-live/2014/03/msg00063.html
and we don't want to have anyone using grml-live run into it.
Thanks: Evgeni Golov for the pointer
Reviewed-by: Evgeni Golov
$ROOTCMD ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf
fi
$ROOTCMD ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf
fi
+# make sure we don't leak any mdadm configurations
+# that are present on the build system to the live system
+if [ -f "${target}/etc/mdadm/mdadm.conf" ] ; then
+ echo "Found /etc/mdadm/mdadm.conf, getting rid of any possible enabled ARRAY settings."
+ sed -i '/^ARRAY/d' "${target}/etc/mdadm/mdadm.conf"
+fi
+
if ! $ROOTCMD test -x /usr/bin/updatedb ; then
echo "Warning: updatedb not installed"
else
if ! $ROOTCMD test -x /usr/bin/updatedb ; then
echo "Warning: updatedb not installed"
else