> Steven Sim wrote: > > Folks; > > > > Today Sun BIG ADMIN website posted an article by > Lynne Thompson entitled > > "What's New in Patching " > > > > See > http://www.sun.com/bigadmin/sundocs/articles/patch-wn. > jsp > > > > Could somebody here elaborate more on the following > statement.... > > > > ".........Now, deferred-activation patching uses > the loopback file > > system (lofs) to ensure the stability of the > running system. When a > > patch is applied to the running system, the lofs > preserves stability > > during the patching process. These large kernel > patches have always > > required a reboot, but now the required reboot > activates the changes > > made by the lofs.".. > > > > It's a bit confusing......especially the part about > "lofs preserves > > stability during the patching process".... > > > > Hopefully I can get one of those who actually did the > work to post a > blog entry about it. Anyway, the executables and > libraries which need > to remain stable during the entire duration of the > patching application > and would be affected by the patch operation are > copied into a temporary > location, lofs is used to mount them up into the > original location, and > then we can patch the originals without adversely > affecting the binaries > in use. You must reboot at the end of such a patch > application to get > the system back into a consistent state. > > Live Upgrade for patching is still recommended, since > it's at least as > safe and doesn't require quiescing the system to > apply such patches, but > this provides an alternative when that is not an > option. >
Is this the new patching scheme that is going to be open sourced for project Indiana? ---Bob This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
