It might be handy for the user to specify a different kernel config file
to check, perhaps the one of a kernel he's about to build. To allow that
we only set the CONFIG variable if it's not present in the environment
before. Also, if CONFIG is not found and we resort to a different file,
we say it explicitely, to avoid typos on the user's part resulting in
silently checking a different config than the one the user wanted.
Signed-off-by: Guido Trotter <ultrotter@quaqua.net>
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
#!/bin/bash
-CONFIG=/proc/config.gz
-GREP=zgrep
+
+# Allow environment variables to override grep and config
+: ${CONFIG:=/proc/config.gz}
+: ${GREP:=zgrep}
SETCOLOR_SUCCESS="echo -en \\033[1;32m"
SETCOLOR_FAILURE="echo -en \\033[1;31m"
}
if [ ! -f $CONFIG ]; then
+ echo "Kernel config $CONFIG not found, looking in other places..."
KVER="`uname -r`"
HEADERS_CONFIG="/lib/modules/$KVER/build/.config"
BOOT_CONFIG="/boot/config-$KVER"
echo "Please recompile with IKCONFIG_PROC or install the kernel headers"
echo
exit 1
+ else
+ echo "Found kernel config file $CONFIG"
fi
fi