summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJeremy Katz <katzj@redhat.com>2009-07-30 10:16:40 -0400
committerJeremy Katz <katzj@redhat.com>2009-07-30 12:59:24 -0400
commita2b1892f170857cfa28db220c64f99b7449d95a1 (patch)
treeee3766af5382b641a4182bad8392cb69683bc171
parentade8105a8515afee24220fd0cc1199e30c1c3142 (diff)
downloadanaconda-a2b1892f170857cfa28db220c64f99b7449d95a1.tar.gz
anaconda-a2b1892f170857cfa28db220c64f99b7449d95a1.tar.xz
anaconda-a2b1892f170857cfa28db220c64f99b7449d95a1.zip
Let's not exit from buildinstall.functions, say, ever
Exiting from a function being called could leave things in a weird state. The exit makes sense for mkinitrd, maybe less so when building installer images
-rwxr-xr-xscripts/buildinstall.functions7
1 files changed, 2 insertions, 5 deletions
diff --git a/scripts/buildinstall.functions b/scripts/buildinstall.functions
index 3b10dffde..2afb65235 100755
--- a/scripts/buildinstall.functions
+++ b/scripts/buildinstall.functions
@@ -56,11 +56,8 @@ EOF
while [ $n -lt ${#FILES[*]} ]; do
FILE="${FILES[$n]}"
if [ "$FILE" == "not found" ]; then
- cat 1>&2 <<EOF
-There are missing files on your system. The dynamic object $bin
-requires ${NAMES[$n]} n order to properly function. mkinitrd cannot continue.
-EOF
- exit 1
+ echo "WARNING: The dynamic object $bin requires ${NAMES[$n]} n order to properly function."
+ continue
fi
case "$FILE" in
/lib*)