On 03/26/10 04:12 PM, Will Fiveash wrote: > On Fri, Mar 26, 2010 at 03:55:03PM -0500, Shawn Walker wrote: >> On 03/26/10 03:51 PM, Will Fiveash wrote: >>> On Fri, Mar 26, 2010 at 01:42:55PM -0600, Mark J. Nelson wrote: >>>> >>>> You should use image-update, and it will create a new boot environment >>>> that will have the full contents of: >>>> >>>> A. All of the latest versions of non-osnet consolidations from your >>>> opensolaris.org publisher >>>> B. The baseline version of osnet packages from your workspace >>>> C. The specific updated packages from your most recent incremental >>>> build in usr/src/pkg (as you described in step 2 above) >>>> >>>> Now your base system has a stable boot environment, plus a test boot >>>> environment, and you can reboot from one into the other and back. >>> >>> And if I just want to update binaries in the current BE I can use >>> pkg install<some package name(s)> instead of pkg image-update, yes? >> >> Unless those packages have actions that have been tagged with >> reboot-needed, yes. >> >> If they're tagged with reboot-needed, then for now, you'll have to >> strip the reboot-needed bits off the actions in the manifest for the >> package. > > To this point, what will pkg install do if I've recompiled > libcryptoutil.so for debugging which is part of system-library.mf which > also contains: > > file path=lib/libc.so.1 reboot-needed=true > > which I have not recompiled (note libcryptoutil is not tagged > reboot-needed)? Is "pkg install system-library" smart enough to know to > know that a reboot isn't needed?
If the action for that file hasn't changed at all (when compared to the same action in the previous version of the package), then it won't be part of the operation plan, and so a reboot or use of a separate image shouldn't be required to my knowledge. -Shawn
