Renumber man pages for IPD4

Author: citrus-it

README.md

@@ -1,4 +1,4 @@
-This is the OmniOS child of pkg(5)
+This is the OmniOS child of pkg(7)
 
 Branches:
 

doc/actions.txt

@@ -1,6 +1,6 @@
 
 PSARC/2008/190
-pkg(5): image packaging system
+pkg(7): image packaging system
 
 SUPPORTED ACTIONS
 

doc/case-outline.txt

@@ -1,6 +1,6 @@
 
 PSARC/2008/190
-pkg(5): image packaging system
+pkg(7): image packaging system
 
 CASE OUTLINE
 

doc/catalog-v1.txt

@@ -1,16 +1,16 @@
-pkg(5): image packaging system
+pkg(7): image packaging system
 
 CATALOG FORMAT AND CACHING PROPOSAL
 
 1.  Overview
 
-    The pkg(5) server and client catalogs currently provides a summary
+    The pkg(7) server and client catalogs currently provides a summary
     view of the packages provided by a repository: the FMRIs of each
     package, the last time the set of available packages changed, and
     the total number of packages.  The server uses this information
     for publication checks, to fulfill client requests, for search
     indexing and analysis, and to enable browser-based access to the
-    repository via the BUI (Browser User Interface).  pkg(5) clients
+    repository via the BUI (Browser User Interface).  pkg(7) clients
     use this information to determine what packages are available, to
     validate user input, and to fulfill packaging operation requests.
 
@@ -73,7 +73,7 @@ CATALOG FORMAT AND CACHING PROPOSAL
 
     - the existing caching mechanisms do not provide the information
       needed to determine (ahead of time) what package manifests need
-      to be retrieved during packaging operations, which leaves pkg(5)
+      to be retrieved during packaging operations, which leaves pkg(7)
       clients unable to provide sufficient feedback to the user during
       plan creation such as number of bytes to be transferred, time
       estimates, etc.

doc/client_api_versions.txt

@@ -515,7 +515,7 @@ Version 53:
 Incompatible with clients using versions 0-52:
 
     General changes:
-        * Support for pkg(5) archives has been added; a file URI
+        * Support for pkg(7) archives has been added; a file URI
           containing the location of an archive can be used anywhere
           that a repository location is (except for search).
 
@@ -1148,7 +1148,7 @@ Changes:
                 history."""
 
         def parse_p5i(self, fileobj=None, location=None):
-                """Reads the pkg(5) publisher json formatted data at 'location'
+                """Reads the pkg(7) publisher json formatted data at 'location'
                 or from the provided file-like object 'fileobj' and returns a
                 list of tuples of the format (publisher object, pkg_names).
                 pkg_names is a list of strings representing package names or

doc/depot.rst

@@ -25,7 +25,7 @@ DEPOT
 
 1.  Summary
 
-    This document describes the architecture of a pkg(5) depot server as
+    This document describes the architecture of a pkg(7) depot server as
     implemented in pkg.depotd(1m).  This includes: an overview of the depot
     server's filesystem layout, operations provided by the depot server,
     the interfaces provided by the depot server, and a description of how

doc/depot.txt

@@ -3,7 +3,7 @@ DEPOT
 
 1.  Summary
 
-    This document describes the architecture of a pkg(5) depot server as
+    This document describes the architecture of a pkg(7) depot server as
     implemented in pkg.depotd(1m).  This includes: an overview of the depot
     server's filesystem layout, operations provided by the depot server,
     the interfaces provided by the depot server, and a description of how
@@ -17,8 +17,8 @@ DEPOT
 
 2.  Discussion
 
-    A pkg(5) depot server provides a way for clients to interact with package
-    content and metadata contained within a pkg(5) repository, and with the
+    A pkg(7) depot server provides a way for clients to interact with package
+    content and metadata contained within a pkg(7) repository, and with the
     depot server itself.  It accomplishes this by providing an HTTP-based
     interface suitable for usage by pkg(1) clients and web user agents.
 
@@ -140,7 +140,7 @@ DEPOT
 2.2.1.  Operation Types
 
     Each operation that the depot server provides is either designed to interact
-    with a pkg(5) repository, or with the depot server itself.  These operations
+    with a pkg(7) repository, or with the depot server itself.  These operations
     can be categorized as follows:
 
     - content
@@ -150,7 +150,7 @@ DEPOT
     - depot
         These operations are read-only, and permit retrieval of: the list of
         operations that the depot server currently provides (including protocol
-        version and pkg(5) software version), statistics information, and other
+        version and pkg(7) software version), statistics information, and other
         depot information.
 
     - metadata
@@ -217,7 +217,7 @@ DEPOT
                 Nothing
 
             Returns:
-                text/plain data containing the version of the pkg(5) software that
+                text/plain data containing the version of the pkg(7) software that
                 the depot is based upon, a list of the operations currently
                 supported, and the protocol version supported for each
                 operation.
@@ -252,7 +252,7 @@ DEPOT
                     If-Modified-Since: {ISO 8601 formatted date and time in UTC}
 
             Returns:
-                Either the contents of a pkg(5) catalog file, or the entries
+                Either the contents of a pkg(7) catalog file, or the entries
                 that were added since the specified date as they are found
                 in the catalog file, separated by newlines.
 
@@ -267,7 +267,7 @@ DEPOT
                 http://pkg.opensolaris.org/info/0/[email protected],5.11-0.101:20081119T235706Z
 
             Expects:
-                A URL-encoded pkg(5) FMRI, excluding the 'pkg:/' scheme prefix
+                A URL-encoded pkg(7) FMRI, excluding the 'pkg:/' scheme prefix
                 and publisher information, and including the full version
                 information.
 
@@ -298,7 +298,7 @@ DEPOT
                 http://pkg.opensolaris.org/manifest/0/[email protected],5.11-0.101:20081119T235706Z
 
             Expects:
-                A URL-encoded pkg(5) FMRI excluding the 'pkg:/' scheme prefix
+                A URL-encoded pkg(7) FMRI excluding the 'pkg:/' scheme prefix
                 and publisher information and including the full version
                 information.
 
@@ -318,7 +318,7 @@ DEPOT
                 http://pkg.opensolaris.org/release/p5i/0/SUNWcs
 
             Expects:
-                A full or partial URL-encoded pkg(5) FMRI, excluding the
+                A full or partial URL-encoded pkg(7) FMRI, excluding the
                 publisher prefix.  If the partial or full FMRI is valid, it will
                 be added to the datastream as is.  If it includes the wildcard
                 character '*', a search of the repository's catalog for matching
@@ -327,7 +327,7 @@ DEPOT
                 found, a 404 error will be raised.
 
             Returns:
-                Returns a pkg(5) information datastream based on the repository
+                Returns a pkg(7) information datastream based on the repository
                 configuration's publisher information and the provided full or
                 partial FMRI or matching entries.  The Content-Type of the
                 response is 'application/vnd.pkg5.info'.
@@ -347,7 +347,7 @@ DEPOT
                 Nothing
 
             Returns:
-                Returns a pkg(5) information datastream based on the repository
+                Returns a pkg(7) information datastream based on the repository
                 configuration's publisher information.  The Content-Type of the
                 response is 'application/vnd.pkg5.info'.
 
@@ -457,7 +457,7 @@ DEPOT
                 http://pkg.opensolaris.org/open/0/system%[email protected]
 
             Expects:
-                A URL-encoded pkg(5) FMRI (excluding timestamp).
+                A URL-encoded pkg(7) FMRI (excluding timestamp).
 
             Returns:
                 Response status of 200 on success and an identifier for the new

doc/dev-guide/chpt10.txt

@@ -274,7 +274,7 @@ mediated links are delivered:
           Specifies the implementation of the mediator for use in addition to
           or instead of the ``mediator-version``.  Implementation strings are
           not considered to be ordered.  A string is arbitrarily selected by
-          |pkg5| if not explicitly specified by a system administrator.
+          |pkg7| if not explicitly specified by a system administrator.
 
           The value can be a string of arbitrary length composed of
           alpha-numeric characters and spaces.  If the implementation itself can
@@ -291,7 +291,7 @@ mediated links are delivered:
           override applies, or if one of the links is version-mediated.
 
      mediator-priority
-          When resolving conflicts in mediated links, |pkg5| normally
+          When resolving conflicts in mediated links, |pkg7| normally
           chooses the link with the greatest value of ``mediator-version`` or
           based on ``mediator-implementation`` if that is not possible.  This
           attribute is used to specify an override for the normal conflict

doc/dev-guide/chpt11.txt

@@ -290,7 +290,7 @@ Example 6: Unknown Extension Value
 
     pkg install: The certificate whose subject is 
     /C=US/ST=California/L=Menlo Park/O=pkg5/CN=cs5_ch1_ta3/emailAddress=cs5_ch1_ta3
-    could not be verified because it has an extension with a value that pkg(5)
+    could not be verified because it has an extension with a value that pkg(7)
     does not understand.
     Extension name:keyUsage
     Extension value:Encipher Only

doc/dev-guide/chpt3.txt

@@ -232,7 +232,7 @@ Types of Actions
 
 There are currently twelve action types in IPS.  The following
 sections describe each action type, and the attributes that
-define these actions.  The action types are detailed in the |pkg5| man
+define these actions.  The action types are detailed in the |pkg7| man
 page, and are repeated here for reference.
 
 Each section contains an example action, as it would appear in a manifest
@@ -475,7 +475,7 @@ Set Actions
                            The name and version of the containing package.
 
      info.classification
-                           One or more tokens that a |pkg5| client can use
+                           One or more tokens that a |pkg7| client can use
                            to classify the package.  The value should have
                            a scheme (such as ``org.opensolaris.category.2008``
                            or ``org.acm.class.1998``) and the actual
@@ -543,7 +543,7 @@ Driver Actions
      The driver action represents a  device  driver.  The  driver
      action  does not reference a payload. The driver files themselves
      must be installed as ``file`` actions.  The  following
-     attributes are recognized (see ``add_drv(1M)`` for more information):
+     attributes are recognized (see ``add_drv(8)`` for more information):
 
      name
                     The name of the driver. This is usually,  but
@@ -586,7 +586,7 @@ Driver Actions
                     This specifies an entry in ``/etc/devlink.tab``.
                     The value is the exact line to go into the
                     file, with tabs denoted by ‘``\t``’. See
-                    ``devlinks(1M)`` for more information. A given
+                    ``devlinks(8)`` for more information. A given
                     driver can have more than one ``devlink``
                     attribute.
 
@@ -843,12 +843,12 @@ User Actions
 
      group-list
                     Secondary groups to which the  user  belongs.
-                    See ``group(4)``.
+                    See ``group(5)``.
 
      ftpuser
                     Can be set to ``true`` or ``false``.  The default
                     value of ``true`` indicates that the user is
-                    permitted to login via FTP. See ``ftpusers(4)``.
+                    permitted to login via FTP. See ``ftpusers(5)``.
 
      lastchg
                     The number of days between January  1,  1970,
@@ -863,7 +863,7 @@ User Actions
 
      max
                     The maximum number of days  the  password  is
-                    valid.  The default value is empty.  See ``shadow(4)``.
+                    valid.  The default value is empty.  See ``shadow(5)``.
 
      warn
                     The number of days  before  password  expires
@@ -887,18 +887,18 @@ User Actions
                     Set to empty.
 
      For more information on the values of these attributes, see
-     the ``shadow(4)`` man page.
+     the ``shadow(5)`` man page.
 
      A example of a user action is::
 
-        user gcos-field="pkg(5) server UID" group=pkg5srv uid=97 username=pkg5srv
+        user gcos-field="pkg(7) server UID" group=pkg5srv uid=97 username=pkg5srv
 
 
 Group Actions
 `````````````
 
      The  group  action  defines  a  UNIX  group  as  defined  in
-     ``group(4)``.  No support is present for group passwords. Groups
+     ``group(5)``.  No support is present for group passwords. Groups
      defined with this action initially have no user list.  Users
      can  be added with the user action. The following attributes
      are recognized:

doc/dev-guide/chpt5.txt

@@ -103,7 +103,7 @@ Run Basic Checks
 Run the Solver
 ``````````````
 
-   The solver forms the core of the computation engine used by |pkg5|
+   The solver forms the core of the computation engine used by |pkg7|
    to determine the packages that can be installed, updated or removed,
    given the constraints in the image and constraints introduced by any
    new packages for installation.

doc/dev-guide/macros.txt

@@ -6,9 +6,9 @@
 
 .. |packagemanager| replace:: ``packagemanager(1)``
 .. |pkg| replace:: ``pkg(1)``
-.. |pkg.depotd| replace:: ``pkg.depotd(1M)``
-.. |pkg.sysrepo| replace:: ``pkg.sysrepo(1M)``
-.. |pkg5| replace:: ``pkg(5)``
+.. |pkg.depotd| replace:: ``pkg.depotd(8)``
+.. |pkg.sysrepo| replace:: ``pkg.sysrepo(8)``
+.. |pkg7| replace:: ``pkg(7)``
 .. |pkgdepend| replace:: ``pkgdepend(1)``
 .. |pkgdiff| replace:: ``pkgdiff(1)``
 .. |pkgfmt| replace:: ``pkgfmt(1)``
@@ -25,7 +25,7 @@
 
 .. |svc.startd| replace:: ``svc.startd(1M)``
 .. |beadm| replace:: ``beadm(1M)``
-.. |zonecfg| replace:: ``zonecfg(1M)``
+.. |zonecfg| replace:: ``zonecfg(8)``
 
 .. Terminology - we want hyperlinks to the right places for these eventually
 ..  and only use these macros the first time we mention these.

doc/facets.txt

@@ -16,7 +16,7 @@ both sparc and x86, since the two architecture's files intersect or
 collide.  Other examples include debug vs non-debug binaries, and
 global vs nonglobal zones.
 
-In pkg(5), options that may be selected or not selected, such as various
+In pkg(7), options that may be selected or not selected, such as various
 locales, documentation, etc., are referred to as facets.  Options which
 are mutually exclusive are called variants.  Both variants and facets
 appear as tags on IPS actions, and result in the action being
@@ -100,7 +100,7 @@ of the change.
 
 Because of the need to select the appropriate variant types prior to
 installation or parsing manifests, only variant.debug.* variants can
-used with pkg(5) without making explicit changes to the source
+used with pkg(7) without making explicit changes to the source
 code. Developers are encourged to design their components not to
 intersect in the filesystem so that facets may be used rather than
 variants.

doc/guide-basic-ops.rst

@@ -22,7 +22,7 @@
 
 .. _Basic operations:
 
-|pkg5| basic operations
+|pkg7| basic operations
 =======================
 
 We provide a brief summary of the client operations and their invocation

doc/guide-implementation-depot.rst

@@ -26,7 +26,7 @@ presented via a URL-based mechanism that allows each to be versioned so
 that changes in protocol can be hidden from older clients as the
 interfaces to operations evolve.
 
-Operations made available by a |depotd1m| server can be accessed via
+Operations made available by a |depotd8| server can be accessed via
 GET or POST, as appropriate for each operation, via a URL such as the
 following:
 
@@ -61,7 +61,7 @@ Operation Types
 ---------------
 
 Each operation that the depot server provides is either designed to interact
-with a pkg(5) repository, or with the depot server itself.  These operations
+with a pkg(7) repository, or with the depot server itself.  These operations
 can be categorized as follows:
 
     - content
@@ -71,7 +71,7 @@ can be categorized as follows:
     - depot
         These operations are read-only, and permit retrieval of: the list of
         operations that the depot server currently provides (including protocol
-        version and pkg(5) software version), statistics information, and other
+        version and pkg(7) software version), statistics information, and other
         depot information.
 
     - metadata