fix text
Teach the console update by url about the default auto update url.
Fix NanoBSD update detection for console update by URL
Ticket #428. Remove double included include.
Include config.inc and functions.inc
Decouple filter.inc from functions.inc. There is no need to process filter functions most of the time. Include filter.inc where it is needed
Correct out of place {
Fix option #2 in firmware upgrade (console) for NanoBSD, bdiff.
Remove newline
Add newline before DANGER
Add digital secutiry signature check to console upgrades.
Use tgz
Rename nanobsd firmware .bz2
Fix nanobsd update detection
Send log file to /conf/
Unbreak
Alert when we detect a nanobsd image.
Only unlink file if it exists.
Add support for the NanoBSD platform
Set firmware lock bit when doing the upgrade
Exit after firmware update
Add . for every second firmware update is running
Make $g a global
Sleep for 10 before checking to see if firmware.lock exists
Correct ordering, use a lock file. Launch upgrade in bg and look for lock file to guess if upgrade is in progress
Use product_name
Do not assume that we ship uniprocessor kernel on LiveCD any longer.
When bdiff is detected in the filename, invoke the binary updateroutines.
Make sure $d_fwupenabled_path is defined since it is initially definedin guiconfig.inc. At some point in the future these variables shouldbe moved to globals.inc.
Automatically assume the embedded platform on update if the platformis set to embedded or wrap. We do not include any kernels outsideof embedded anyways for this paticular platform.
Remove any previous MD5 sums after upgrade.
Exit immediately after firmware update operation completes.
Add carriage return
Make $fp global
Do not close STDIN until script is done processing.
Prompt for kernel type if it is not defined.
Ticket #1435
Close STDIN ($fp) handle before returning back to shell. Major doh's.
Mount image read write before upgrading.
Mount read/write before fetching url.
Use unlink_if_exists()
Unlink upgrade file on upgrade.
Use /root/ as temporary storage.
Fetch the filesize initially and compare it. In addition we compare MD5 to be absolutely sure.
Exit if URL or PATH is blank.
Add md5 support if the site is storing the value.
Add firmware update menu option which can fetch a URL from the internet or use a already fetched file from the file system.