From 462afb6bf4b12814e77ebd618a03200cb77eb95f Mon Sep 17 00:00:00 2001 From: Michael Prokop Date: Thu, 27 Mar 2014 09:33:52 +0100 Subject: [PATCH] Make sure to not leak any mdadm configurations from the build system 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 --- etc/grml/fai/config/scripts/GRMLBASE/98-clean-chroot | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/etc/grml/fai/config/scripts/GRMLBASE/98-clean-chroot b/etc/grml/fai/config/scripts/GRMLBASE/98-clean-chroot index b7f93e0..1d18dd3 100755 --- a/etc/grml/fai/config/scripts/GRMLBASE/98-clean-chroot +++ b/etc/grml/fai/config/scripts/GRMLBASE/98-clean-chroot @@ -205,6 +205,13 @@ EOF $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 -- 2.1.4