From cc5ecb4e9cb29c45369cc07014c15202f4a5fd78 Mon Sep 17 00:00:00 2001 From: Lucas Alvares Gomes Date: Wed, 19 Jun 2013 17:00:10 +0100 Subject: [PATCH] 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 --- elements/base/dib-first-boot | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/elements/base/dib-first-boot b/elements/base/dib-first-boot index 48a5bab9..67dbed56 100755 --- a/elements/base/dib-first-boot +++ b/elements/base/dib-first-boot @@ -5,7 +5,7 @@ set -o xtrace touch /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 # delete itself rm $0