Patch -- Solaris

                                                                

                                                           PATCH

Well, what does it mean?

What is the First image clicked in mind when we heard the word “patch”

• A puncture in bike and a small patch is applied on that area & done.
• A cut in hand and a Band-Aid is applied on that area & done …
• A damp on wall and a small patch of coating is applied on that area & done…

Well … there are several examples … now let’s explain these

So… what these examples are trying to say??

There was some problem with something and we applied something to correct that problem…Right??

Well… the same is applied in case of programs … How??

Today it is very simple to understand… almost everybody has smartphone and several apps installed in it… but u might noticed that on every here & there they are updating themselves… why so ?

To rectify some bugs or some issues faced by users…

Well… it means that the

“Patch is fixing the program by updating some or all of their codes “

OR

“Patch is a fix to a reported software program”

 We can deal with Patches by CMD as well as GUI

GUI            

#smc &       

then go to – this computer – patches – action

Command Line

#patchadd

#patchrm

Patch    =     110453-01

            Base code-Rev. no.

  

root@sol-test-2:>/# patchadd  <patch> [simply install the patch]

root@sol-test-2:>/# patchadd –d < patch >

root@sol-test-2:>/# patchadd –u <patch>

root@sol-test-2:>/# patchadd –p   [installed patch list details]

Ok... Now what is this

-u

-d

-u      this is security breach, means it installs unconditionally.         File validation is turned off. It will install, if the               contents of patch are even modified.

-d      it thinks that you had already tested the patch and don’t      want to be backed up

Let’s understand this –d in detail…

root@sol-test-1:>/hgfs/vM_SHARE/x86# patchadd -d 119060-62

Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Done!

Checking patches that you specified for installation.

Done!

Approved patches will be installed in this order:

119060-62

Executing prePatch script...

Checking installed patches...

Executing prepatch script...

Installing patch packages...

Patch 119060-62 has been successfully installed.

See /var/sadm/patch/119060-62/log for details

Executing postpatch script...

Patch packages installed:

  SUNWxorg-client-docs

  SUNWxwacx

  SUNWxwfnt

  SUNWxwfs

  SUNWxwice

  SUNWxwinc

  SUNWxwman

  SUNWxwopt

  SUNWxwplr

  SUNWxwplt

  SUNWxwpmn

  SUNWxwrtl

  SUNWxwsrv

  SUNWxwxst

root@sol-test-1:>/hgfs/vM_SHARE/x86# patchrm 119060-62

Validating patches...

Loading patches installed on the system...

Done!

Checking patches that you specified for removal.

Done!

The following patches cannot be removed since they were installed without creating their backout data.

119060-62

No patches to remove.

It means that when we do patchadd without –d it will create a backup of that old patch and when we remove the new installed patch the old (backed up) one will replace it.

If we use –d then the system will understand that we know what we are doing and we don’t not require the old patch to be backed up by the system…

Ok…

Now what the patchadd will do after installing patch

·         It moves the old or outdated patch (create backup of old) directory to the

/var/sadm/pkg/<pkg Name>/save    directory

·         It logs the patch installation to the /var/sadm/patch/<patch id Dir.>

·         It updates the /var/sadm/pkg/<pkg-name>/pkginfo file  

Means when the patch is installed , old files that are replaced are backed up in to /var/sadm/pkg/<pkg Name>/save    directory… these files are used when we want to go back to previous patch

#patchrm <patch name>              [to remove patch]

-f       is used when need to forceful removal, without considering     about dependency

MONITORING

root@sol-test-2:>/# showrev -p

root@sol-test-2:>/# patchadd –p

both ends in same result, only difference is showrev -p can be used by any user whereas patchadd –p can be run only by root

There are 3 Fields in the o/p of

showrev –p

Requires :            It is telling about dependencies, means these                  following patches Must be installed before                      this one

Obsoletes :           Overridden by new version / revision

Incompatibles :       Patches that are Incompatible with this patch,                  that’s why this Patch cannot be installed

PATCH MANAGEMENT:

PROACTIVE                There is a problem and fix is released, but                          my system is running very normal, must                              think twice before applying, b’coz                                  currently there is no issue with system and                          might several occur after patch

REACTIVE                 The system is suffering and fix is released

SECURITY                 Security patch mgmt.requires to be pro and

                         Reactive mgmt.

PROACTIVE WHILE FRESH INSTALLATION     

                         Probably this is the best patch mgmt. that                          we install All latest patch or cluster just                          after OS installation.