##################################################################################
# BB (neu) < BB (aktuell) : update unterbinden
# BB (neu) = BB (aktuell) && CC (neu) < CC (aktuell) : update unterbinden
##################################################################################
if [ "$middle_newFWver" -lt "$middle_currFWver" ] ; then
echo "error: Firmware downgrade not allowed"
echo "set INFO led to off (modul=7, state=1)"
echo 7,1>${LED_DEVICE}
exit $INSTALL_FIRMWARE_VERSION
else
echo "DEBUG: $middle_newFWver >= $middle_currFWver"
fi
if [ "$middle_newFWver" -eq "$middle_currFWver" ] ; then
if [ "$minor_newFWver" -lt "$minor_currFWver" ] ; then
echo "error: Firmware downgrade not allowed"
echo "set INFO led to off (modul=7, state=1)"
echo 7,1>${LED_DEVICE}
exit $INSTALL_FIRMWARE_VERSION
else
echo "DEBUG: $minor_newFWver >= $minor_currFWver"
fi
else
echo "DEBUG: $middle_newFWver > $middle_currFWver"
fi
echo "Accept Firmware Version: xx.${newFWver}"--mode=permissions
When adding files to an archive, tar will use permissions for the archive members, rather than the permissions from the files. The program chmod and this tar option share the same syntax for what permissions might be. See section `File permissions' in GNU file utilities. This reference also has useful information for those not being overly familiar with the Unix permission system.
Of course, permissions might be plainly specified as an octal number. However, by using generic symbolic modifications to mode bits, this allows more flexibility. For example, the value `a+rw' adds read and write permissions for everybody, while retaining executable bits on directories or on any other file already marked as executable.
