On Thu, 13 Dec 2007, James Carlson wrote: > 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 [ ... ]
It's pretty much analogue to what Linux calls "initrd". A filesystem image being loaded into RAM by the bootloader, to be used by the kernel before the real storage-based root fs becomes available. Implementation details, such as the name of said vehicle, differ. Concept identical. FrankH. _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
