Customizing Automated Installations With Manifests and Profiles

How to Update a First-Boot Script or Service

If you change the script or the service manifest, use this procedure to install the update.

Before You Begin

Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Install Oracle Solaris.

1. Copy the updated files to your prototype directory.

   $ cp first-boot-script-svc-manifest.xml proto/lib/svc/manifest/site
   $ cp first-boot-script.sh proto/opt/site

2. Increment the package version.

   In the package manifest, change the value of the pkg.fmri attribute to the following, for example:

   first-boot-script@1.0,5.11-0.1

3. Publish the new version.

   Publish the new version of the package to the repository.

   $ pkgsend publish -d ./proto -s ./firstbootrepo first-boot-script.p5m
   pkg://firstboot/first-boot-script@1.0,5.11-0.1:2013123T231948Z 
   PUBLISHED

4. Update the package.

   Use the pkg list -af command to make sure you can access the new version. You might need to use the pkg refresh firstboot command to update the package list. Use the pkg update command to update the package.

5. Reboot the test system.
6. After booting, verify installed packages.

   Security best practices recommend that you run the following command to help ensure that packaged file system objects have not been changed insecurely. For more information, see Verifying Packages and Fixing Verification Errors in Updating Systems and Adding Software in Oracle Solaris 11.4.

   $ pkg verify -v