Deinstallation of PMDF deletes only those files present in the distribution kit. In particular, deinstallation will not remove files such as the PMDF configuration file, /pmdf/table/pmdf.cnf, and other such site-generated files, and thus you will not need to reconfigure PMDF after deinstalling and reinstalling or upgrading.

1.6.1 Step-by-Step Deinstallation Instructions

1. Deinstallation should be done by root. If you are not already logged in as root, do so now.
2. Move to the root directory:

   # cd /

3. Check what PMDF packages you currently have installed; e.g.,

   # pkginfo | grep PMDF application PMDFbase PMDF Base Product application PMDFdoc PMDF Documentation application PMDFlan PMDF LAN Product

4. Use the pkgrm command to deinstall any PMDF packages, e.g.:

   # pkgrm PMDFlan PMDFdoc PMDFbase

   Note that multiple packages can be deinstalled at once by listing them separated by spaces on the pkgrm command line. You may use the -n switch if you do not want to be prompted regarding removal of each individual package, e.g.,

   # pkgrm -n PMDFlan PMDFdoc PMDFbase

   Note also that PMDFbase must be the last package deinstalled (if listing multiple packages on one line, list PMDFbase last) since the other packages depend upon it. Further, note also that such layered product packages as PMDFlan, PMDFsync, PMDFx400, PMDFxgs, and PMDFdoc cannot be used unless the PMDFbase package is installed.

5. If you are upgrading from PMDF V5.1-7 which had been previously installed in the directory literally named /pmdf, that is, if PMDF V5.1-7 had been installed in a /pmdf directory which was not a symbolic link to another directory, then you must perform a special step to properly deinstall PMDF before upgrading. This special step may also be necessary if you are upgrading from PMDF V5.1-4. (The normal deinstallation procedure is sufficient if upgrading from PMDF V5.1-9 or later. The normal deinstallation procedure is also sufficient if upgrading from PMDF V5.1-7 or PMDF V5.1-4 if PMDF had been installed in a different directory with a symbolic link to /pmdf.)
   After performing the normal pkgrm command to deinstall all PMDF packages, you must then issue another pkgrm command on the PMDFbase package to complete its deinstallation.
   For instance, a site that has the V5.1-7 PMDFbase, PMDFlan, and PMDFdoc packages installed would need to issue the commands:

   # pkgrm PMDFlan PMDFdoc PMDFbase # pkgrm PMDFbase

   The deinstallation dialogue for such a site would look something like:

   # pkgrm PMDFlan PMDFdoc PMDFbase The following package is currently installed: PMDFlan PMDF LAN Product V5.1-7 (sparc) 5.1-7 Do you want to remove this package? y ## Removing installed package instance <PMDFlan> ## Verifying package dependencies. ## Processing package information. ## Removing pathnames in class <none> ...lots of files... The following package is currently installed: PMDFdoc PMDF Documentation (sparc) 5.1-7 Do you want to remove this package? y ## Removing installed package instance <PMDFdoc> ## Verifying package dependencies. ## Processing package information. ## Removing pathnames in class <none> ...lots of files... The following package is currently installed: PMDFbase PMDF Base Product V5.1-7 (sparc) 5.1-7 Do you want to remove this package? y ## Removing installed package instance <PMDFbase> ## Verifying package dependencies. ## Processing package information. ## Removing pathnames in class <none> ...lots of files... pkgrm: ERROR: unable to remove directory </> ## Updating system information. Removal of <PMDFbase> partially failed. # pkgrm PMDFbase The following package is currently installed: PMDFbase PMDF Base Product V5.1-7 (sparc) 5.1-7 Do you want to remove this package? y ## Removing installed package instance <PMDFbase> (A previous attempt may have been unsuccessful.) ## Verifying package dependencies. ## Processing package information. ## Removing pathnames in class <none> ## Updating system information. Removal of <PMDFbase> was successful.

   
   The initial pkgrm command will not succeed in fully deinstalling PMDFbase. This is why the second command is required. (If PMDF is not fully deinstalled, then a subsequent attempt to install PMDF will not be complete; some new images will not be installed due to the presence of the old images.)