Use dib-run-parts on dib-first-boot.

At least on RedHat the run-parts command is very precarious and doesn't
even check for the return code of the scripts it runs causing the
dib-first-boot to delete itself even when something went wrong with the
configuration of the first boot of the image. Using the dib-run-parts
instead will make the whole first boot routine to be more robust and
less platform dependent.

Change-Id: I0073fd52fc1fc8848ca9277a84603124215cdb6e
This commit is contained in:
Lucas Alvares Gomes 2013-06-19 17:00:10 +01:00
parent 207aeced03
commit cc5ecb4e9c

View File

@ -5,7 +5,7 @@ set -o xtrace
touch /var/log/first-boot.d.log touch /var/log/first-boot.d.log
chmod 0600 /var/log/first-boot.d.log chmod 0600 /var/log/first-boot.d.log
run-parts /etc/first-boot.d >> /var/log/first-boot.d.log 2>&1 dib-run-parts /etc/first-boot.d >> /var/log/first-boot.d.log 2>&1
rm -fr /etc/first-boot.d rm -fr /etc/first-boot.d
# delete itself # delete itself
rm $0 rm $0