Some time every week , when I turn off my AMD64 SNV workstation for the night , a spontaneous " bootadm update-archive " is run. Even though I have not installed new software and have not fiddled with disks a.s.o.
I have customers running solaris 10 1/06 for X86 that are experiencing that servers cant reboot after a power outage because the bootadm archive is not "current" These experiences seems to render the Boot-Archive more of a problem than an asset. If the system marks the boot-archive invalid without notifying the administrator and the system later has a power outage it seems too me that some procedures around the boot-archive is not well thought out. My feeling is that the system should, on its own initiative, immediately regenerate the boot-archive if some event makes it nessesary to do so. To postpone the boot-archive regeneration until the shutdown sequence is clearly not a strategy that fullfills the goal of the boot-archive . At least I assume that the goal is to make the boot process more secure. and less prone to failure. As it is now the validity of the boot-archive after a power-outage is questionable . regards Lars Tunkrans This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
