netnomad the md5 check is already in the latest RCs.
Updated version script and /etc/sysconfig/boot_path config sent to Jason for review, hopefully will be released for testing. Now allows user to specify how many dCore*.gz and *.md5.txt backups to keep, any more are auto-purged during the update process once the new version was successfully downloaded. Default is 3 backups, change as desired. Without the updated boot_path config file the download directory will not display and you'll get the error below. Note the output now also displays the MAXBACKUPS setting.
dCore*.gz download path from /etc/sysconfig/boot_path (MAXBACKUPS = 3):
Not specified, create /etc/sysconfig/boot_path entry, exiting..
Then either remove boot_path from /opt/.filetool.lst and reboot to get the new config file or just cut/paste from below and re-configure:
boot_path config:
# Specify download directory for version -c or version -r dCore updates. The full dCore boot
# pathway must be specified (contains the dCore-*.gz and vmlinuz-* files). The version command
# automatically backs up the old dCore-*.gz and *.md5.txt file before downloading the update.
# Specify the maximum number of backups to store below. Reboot to complete the update.
# If this file is modified, add an /opt/.filetool.lst entry to save changes:
# etc/sysconfig/boot_path
# NO SPACES, ONLY ONE ENTRY FOR EACH OPTION
# BOOTPATH ENTRY MUST START WITH A SLASH
# BOOTPATH ENTRY MUST CONTAIN /mnt/* IF DOWNLOAD DIRECTORY IS NOT MOUNTED AFTER BOOT
# Note dCore uses the symlink 'tcedir' to point to the /tce directory. The dCore installer by default
# uses /etc/sysconfig/tcedir/boot, on the actual system this may be something like /mnt/sdb4/tce/boot.
# Use BOOTPATH=/* to specify dCore boot path directory:
#BOOTPATH=/etc/sysconfig/tcedir/boot
#BOOTPATH=/mnt/sdb4/tce/boot
BOOTPATH=/etc/sysconfig/tcedir/boot
# USE MAXBACKUPS=* to specify number of backups to keep:
#MAXBACKUPS=3
MAXBACKUPS=3
Note RCs 2016.02.28.23.36 and older don't need this yet, updating to the next RC won't need it yet, updating after that will require the new boot_path config.
Sorry for the hassles, learning as i go, should have provided a better config file at the start, thanks.