Hi So the boot-archvie and failsafe are different animals, the boot-archive is updated when binaries in the archive are changed.
The failsafe is never rebuilt, luupgrade script compresses it and then copies the compressed archive to the new boot env, it never rebuilds it though. errors from lu around failsafe typically involve errors compressing it ( or just running out of space copying it ) So in u8 there are two boot-archives one specifically for amd64, if your system is amd64 based it will copy in the amd archive as well. Enda Gary Mills wrote: >> <div id="jive-html-wrapper-div"> >> >> There is an entire chapter about using bootadm and >> rebuilding<br> >> the boot archives in the sys admin docs:<br> >> <br> >> <a class="moz-txt-link-freetext" >> href="http://docs.sun.com/app/docs/doc/817-1985/archiv >> e-123?a=view">http://docs.sun.com/app/docs/doc/817-198 >> 5/archive-123?a=view</a><br> > > And all it says about the failsafe archive is this: > > The failsafe boot archive is the second type of archive that is > created when you install the Solaris OS. > > A failsafe boot archive has the following benefits and characteristics: > > * Is self-sufficient > * Can boot on its own > * Is created by default during installation of the OS > * Requires no maintenance > > It still seems to me that `luupgrade' tried to rebuild it. > It certainly has shell functions to do that. -- Enda O'Connor x19781 Software Product Engineering Patch System Test : Ireland : x19781/353-1-8199718
