Scott Rotondo writes: > 1. If the boot archive and the filesystem ever disagree, the boot > archive is wrong. The right (unconditional) action is to rebuild the > boot archive and boot again. This can only fail if the filesystem > contents themselves are incorrect. [1] > > Does everyone agree with the paragraph above, or are there additional > complications?
I do. It's unclear whether _everyone_ does. > Perhaps this idea has been considered before and rejected, but I don't > know why. Can anyone enlighten me? The periodic rebuild was considered during the original newboot case, and rejected because it was too hackish -- we should know when things change and rebuild only when necessary. > [2] We'd probably want to allow for settling time (e.g. make sure at > least a minute has passed since the last file was updated) to avoid > rebuilding in the middle of a patch/package install. It might not be feasible in general to avoid smacking into an update of some sort, but the idea of making sure that the newest changed file is not newer than some benchmark time is an interesting one ... more so if we didn't set the last modification time during unpacking. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
