Carl-Daniel Hailfinger wrote:
Check for a terminating LAR member which tells us that no further LAR member except the bootblock will be found after this member. The LAR member has a normal MAGIC, but all other parts of struct lar_header are 0xff. That way, adding a new member in place of the terminating member will not need an erase cycle.
I don't see a gain in this. Since we know the position and size of the lar archive anyways, we know nothing will come after the bootblock.
There should not be any headers that do not belong to real "files" in the lar, that would be breaking our model.