Wilkinson, Alex writes: > 0n Wed, Dec 12, 2007 at 11:07:01AM -0500, James Carlson wrote: > > >Of course, one way to get there would be to make sure that the boot > >archive is kept in sync all the time by eliminating the original files > >and storing them only in the archive. Another would be to make sure > >it resyncs on boot when needed. Still another would be to get rid of > >the archive and go back to the old ways. I suppose there are other > >options. The project team chose to keep it in sync by checking and > >rebuilding the archive on reboot/shutdown. > > What is meant by "the boot archive" ?
See bootadm(1M) and grub(5). It's part of GRUB, the x86 booting system. Basically, it's a file with an ISO file system image containing the system kernel and a few key related files. During boot, a portion of the kernel is loaded into memory by GRUB, along with the "boot archive." The kernel finds the boot archive and reads from it until it can get to the point where the real root (out on disk) can be mounted. When key files change (such as /etc/system and the contents of /kernel), the boot archive has to be rebuilt. That's what bootadm does, and that's invoked automatically during reboot(1M) and shutdown(1M). -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> 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 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
