Now there is a boot option "checkfs". It is not like the one that was before and was dropped, this one simply checks to see if the partition about to be mounted for /opt, /home, and/or TCE directory contains errors, nothing is done or fixed. If errors are found, it gives you an option to continue at your own risk or follow the recommended reboot and fix the errors with the "base" boot option and the e2fsck command. Works with the LABEL and UUID option of specifying devices. The results can be seen in the files /tmp/checkfs.*, such as /tmp/checkfs.sda2, /tmp/checkfs.sdb4, etc. Simply needed a check for a large number of mounts between fixes or an just an unclean unmount does not constitute file system errors. Only a true error will result in the "red flag" and an option to reboot.

On my A10 board I have had a few hard resets due to lockup, and ended up seeing the havoc that can be when a corrupted EXT file system was being used in a live session. This boot code can at least prevent using an unusable file system.

with the last cut i experienced the looping update-requests again.perhaps it has something to do that i use dcore with an usbstick?without permanent /home, /opt or /usr and so on?

i did an update this morning and after the reboot i checked the update-situation again and updatesce replied that there are no additional updates needed.then in the afternoon, after a further reboot, i checked with updatesce -c -a again and i guess that i got offered the same update-requests that were updated in the morning.i'm sure that no updates were downloaded during the merge-process.after the next reboot updatesce told me that no updates are available for the chosen sces.

Do you want to review the list of packages that have updates available?Enter y to view and q to exit reading the package list. (y/N): SCE: 000-base-jessieAvailable package updates: console-setup debian jessie main console-setup-freebsd debian jessie main console-setup-linux debian jessie main keyboard-configuration debian jessie main

after a successful update and a fresh reboot,updatesce wants to update exactly the same packages, although all requested updates are done.

I have just added a more reliable checking of startup script md5sums and also added checking of -data.tar.gz extra file updates. This way, anything at all updated with the package - Debian package, startup script, data.tar.gz files - will call for the package to be updated with a run of updatesce.

Hold off on testing the last cut and I will upload this sometime tomorrow.

Many changes and bugfixes to the updatesce routine. Now, if a package has a new or changed startup script it is listed as an available update. And if a new data.tar.gz file is added or the existing one is updated then the package is also listed to be updated. And if there is a new prebuilt or Debian dependency added to a package or the existing ones have been updated, then that package is also listed for update.

EDIT: I had updated alsa-utils.deb2sce and firefox-data.tar.gz for testing purposes, those should appear as updates for any SCEs containing them the first time you run updatesce.

This completes the updatesce concept, and now to find the bugs. The following dCore x86 ports have a new cut in release candidates.

Fixed a bug in the dependency routine that uses grep when dealing with the main DEBINX packages file. Awk has been and is still used for the extra repos as their packages files are small so they have been unaffected. The issue was the grep routine was pulling in all entries that were "this dep, or that dep, or that dep" where the awk routine just used the first one and ignored the rest, the first match is normally the smallest and most basic, which for our purpose is the desired behavior. Now grep pulls the needed info for the package at hand from the large DEBINX file, and awk works with the small snippet to correctly parse deps but with the same performance as before if GNU grep is being used.