Uwe Dippel writes: > If you look at the various posts of mine in here, I asked at different times > on essentially the same topic: What constitutes a Boot Environment; in the > meaning of 'how complete is it',
It's complete except for the bootstrap program, which is located in fixed sectors on the disk (outside of any file system). See installgrub(1M). > can it be transferred?'. No. For one reason why, see /etc/path_to_inst. The root file system for a given system contains critical information about the hardware on which the system is running. If you transfer that to a different machine, then all bets are off. It might possibly work if all of the stars are aligned. It probably won't work. As other posters have pointed out, FLASH archives are the mechanism designed to do what you're asking. It allows a preconfigured snapshot of a system to be installed on other systems. > Also, with respect to liveupgrade, I do understand lucreate, as to write the > current '/' to another slice. But I am told, you can't simply boot that. My > question: why would that be? Generally, you can boot it, as long as it's been activated at least once in the past. The 'luactivate' program modifies parts of the root file system to make it possible to boot. The 'init 6' step (for what it's worth) causes '/etc/init.d/lu stop' to run, which synchronizes the environments before switching and then updates the GRUB entries so that the right thing happens. > /dev/dsk/c1d0s4 15G 8.5G 6.1G 59% / > /dev/dsk/c1d0s7 42G 36G 5.5G 87% /export/home > I have two slices that I use. Why would those not be straightforward > mountable (like from grub menu?). They are. > If I lucreate /dev/dsk/c1d0s5, why not that one? That'll be yet another UFS file system containing a copy of the root. It may not necessarily be bootable. > I could understand if it was done on purpose, to avoid illegal cloning. It has nothing to do with that. As far as I know, Sun's never done that to Solaris, even before OpenSolaris. :-/ > I am asking also on the grounds, that to my understanding, a fully > self-contained BE after lucreate or luupgrade would very much increase the > attractiveness of OpenSolaris. It would simplify testing of an upgrade, just > as deployment (at least on a bunch of identical hardware, like in a students' > lab). No, please, don't tell me 'flash archive is much better'. That may be > the case, but as of now, we have procedures in place to dump/restore full > partitions and slices, and I am still curious why a Solaris slice doesn't > seem to like the handling as a slice as a fully self-contained (boot-)entity. Sadly, even though the Live Upgrade technology is mostly implemented as scripts (that you can go ahead and read if you want), it has a proprietary non-Sun origin. We don't have the rights to it. We can't give away the source code for it, or the design information, or really very much about it. Besides the man pages (which describe what you can do with it), I think the _best_ forum for discussing this sort of thing would be in the Indiana project team. They're removing *ALL* of the old LU stuff, and would likely be happy to discuss the new installer and boot environment manager, and how it works. -- 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-discuss mailing list [email protected]
