In Slitaz 4.0, there is a Syslinux module, md5sum.c32.
I customized the ISO and added files. Slitaz works correctly, so I have no problem with it.
But when I use md5sum.c32 in the customized ISO, it gives inconsistent results. I mean that even when the files tested are in fact correct, the result of md5sum.c32 states that some files are "not checked".
To replicate this problem in the original Slitaz 4.0 ISO, I boot it once, select to check media. When the check finishes I go back to the menu and select the same option (check media) again, without rebooting.
By repeating the checksum in the original Slitaz 4.0 again and again about 10 times (maybe more, I lost track), I finally see the same behavior as happened with the customized ISO. The checksum was OK the first 10 (or so) times (without rebooting), and then suddenly the result of md5sum.c32 changes and some files give a "not checked" result.
After that, If I reboot once and try the same procedure again (repeating check media several times without rebooting in between), then I see the same strange behavior: files that pass the first 10 (or so) times and then they return "not checked". Interestingly, the fail happens exactly at the same point in the checksum.
In Cook, there is a new "c32box.c32 md5sum" module that includes (or replaces) md5sum.c32. The new c32box.c32 behaves exactly the same as the older md5sum.c32.
The easiest way to replicate this problem is to customize the ISO with many more (say, 180) files than the original and to include the added files in the corresponding md5 check list file.
Moreover, after the last checksum run, the boot prompt won't let me do anything. At this point, trying to start the menu again fails, as trying to start any other kernel.
Please, Can someone else replicate this behavior?
Can this problem in "md5sum.c" be solved?