On Tue, 2006-02-14 at 20:34, Jan Setje-Eilers wrote: > The basic issue seems to be that the archive wasn't synced on that > node. This sync normally happens automatically during any sort of > orderly shutdown or reboot.
so, this aspect of the newboot design has always troubled me. seems that, in production, many systems will be installed and configured and will then stay up without reboot until something goes bump, either with power or hardware; on reboot they'll fail to come back automatically; as nothing except a clean shutdown updates the boot archive, in a intentional-reboots-are-rare environment (which we otherwise engineer for!) chances are that the on-disk boot archive will be wrong and approximately every failure-triggered reboot will notice a boot archive mismatch..
