> > > 2. When I ran "pkg image-update", after rebooting into the new BE, if > I > > run "uname -a", it will show that the build is updated. But it seems > that > > "pkg install entire..." doesn't do that (I did it without creating a > new BE > > manually, and I didn't reboot) > > The output of "uname -a" comes from the kernel, which needs to be restarted > (i.e., the machine needs to be rebooted) in order to be using the new > kernel bits. > > Note that "pkg install ent...@..." on the live BE shouldn't work. There > should be safeguards in place that prevent you from upgrading your system > on the existing root dataset -- it should error out and tell you that you > need to do it in an alternate BE. This is because it's extremely unsafe. > You are right, it actually showed the error. I wonder how the system knows whether the current BE is a clone or original...
> > Why do you want to update using this mechanism? Because you want to update > to something other than the latest build? > Yes. image-update gives the latest build while we want to control the versions of all machines. > > Danek > -- One way leads to another _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
