Tian He wrote: > Say I run "pkg install [email protected],5.11-0.127:20091111T131831Z" to update > to build 127. Here are several questions: > > 1. Will this command only update packages that has already been > installed, or will it install all packages listed in the manifest?
"entire" is an incorporation, which merely constrains the versions of installed packages -- it does not pull packages onto the system itself. > 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. Why do you want to update using this mechanism? Because you want to update to something other than the latest build? Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
