AppsAudit update check

[bmarkus]

Please add version check for TCB to AppsAudit, indicate availability of new TC version.

[roberts]

Core boot files' location is not readily available. There is no single consistent file with such purpose as is for tce (.tce_dir). Instead such location is in the boot loader. As we don't enforce any particular boot loader, it would mean trying to scan and parse a myriad of boot loaders, and then possibly, even likely, find several candidates. Even if a scan of the entire drives is attempted the boot files are not required to be at root-level as is tce and where scanning is an available option. Various boot loaders allow boot files to be placed nearly anywhere so therefore a total scan could be very time consuming with still a possibilty of find multiples or could possible be on a removable device that is not even available to attempt mounting. Is such effort worth it when typically a base upgrade is copying over one file?

[roberts]

On the other hand if an informational only display that the running version is not current is desired then that is possible.

[bmarkus]

On the other hand if an informational only display that the running version is not current is desired then that is possible.

Yes, it is the idea. I was supprised reading previous answer. Just a single information that new version is available or up to date. No update, no download. It's a small thing but makes user happy.

[robc]

Core boot files' location is not readily available. There is no single consistent file with such purpose as is for tce (.tce_dir). Instead such location is in the boot loader. As we don't enforce any particular boot loader, it would mean trying to scan and parse a myriad of boot loaders, and then possibly, even likely, find several candidates. Even if a scan of the entire drives is attempted the boot files are not required to be at root-level as is tce and where scanning is an available option. Various boot loaders allow boot files to be placed nearly anywhere so therefore a total scan could be very time consuming with still a possibilty of find multiples or could possible be on a removable device that is not even available to attempt mounting. Is such effort worth it when typically a base upgrade is copying over one file?

I don't think you need to go as far as replacing the system image for an update.  Just downloading the new image to the tce/ directory and having the user move it to their boot directory would be good.  Perhaps even renaming an existing image in the tce/ to tinycore-old.gz or tinycore-ver#.gz. 

Though, if the image is kept in a standard place (ie tce/) then the users can setup (or the install script can) their bootloaders to boot from an image in the tce/ dir.

Perhaps this can be looked at for tc 4.x as a new feature.

[jur]

Core boot files' location is not readily available. There is no single consistent file with such purpose as is for tce (.tce_dir). Instead such location is in the boot loader. As we don't enforce any particular boot loader, it would mean trying to scan and parse a myriad of boot loaders, and then possibly, even likely, find several candidates. Even if a scan of the entire drives is attempted the boot files are not required to be at root-level as is tce and where scanning is an available option. Various boot loaders allow boot files to be placed nearly anywhere so therefore a total scan could be very time consuming with still a possibilty of find multiples or could possible be on a removable device that is not even available to attempt mounting. Is such effort worth it when typically a base upgrade is copying over one file?

I don't think you need to go as far as replacing the system image for an update.  Just downloading the new image to the tce/ directory and having the user move it to their boot directory would be good.  Perhaps even renaming an existing image in the tce/ to tinycore-old.gz or tinycore-ver#.gz. 

Though, if the image is kept in a standard place (ie tce/) then the users can setup (or the install script can) their bootloaders to boot from an image in the tce/ dir.

Perhaps this can be looked at for tc 4.x as a new feature.

+1