svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
pkgtrans(1)
pkgtrans(1) User Commands pkgtrans(1)
NAME
pkgtrans - translate SVR4 package format
SYNOPSIS
pkgtrans [-inos] device1 device2
[pkginst]...
DESCRIPTION
The pkgtrans utility translates an installable SVR4 package from one
format to another. It translates:
o a file system format to a datastream
o a datastream to a file system format
o one file system format to another file system format
OPTIONS
The options and arguments for this command are:
-i Copies only the pkginfo(5) and pkgmap(5) files.
-n Creates a new instance of the package on the destination device
if any instance of this package already exists, up to the number
specified by the MAXINST variable in the pkginfo(5) file.
-o Overwrites the same instance on the destination device. Package
instance will be overwritten if it already exists.
-s Indicates that the package should be written to device2 as a
datastream rather than as a file system. The default behavior is
to write a file system format on devices that support both for‐
mats.
OPERANDS
device1 Indicates the source device. The package or packages on this
device will be translated and placed on device2. See DEVICE
SPECIFIERS, below.
device2 Indicates the destination device. Translated packages will
be placed on this device. See DEVICE SPECIFIERS, below.
pkginst Specifies which package instance or instances on device1
should be translated. The token all may be used to indicate
all packages. pkginst.* can be used to indicate all in‐
stances of a package. If no packages are defined, a prompt
shows all packages on the device and asks which to trans‐
late.
The asterisk character (*) is a special character to some
shells and may need to be escaped. In the C-Shell, the *
must be surrounded by single quotes (') or preceded by a
backslash (\).
DEVICE SPECIFIERS
Packaging tools, including pkgtrans, pkgadd(8), and pkgchk(8), have op‐
tions for specifying a package location by specifying the device on
which it resides. Listed below are the device types that a package can
be stored to and retrieved from. Note that source and destination de‐
vices cannot be the same.
device Packages can be stored to a character or block device by
specifying the device identifier as the device. A common
example of this device type is /dev/rmt/0 for a removable
magnetic tape. pkgtrans can also produce regular file sys‐
tem files in a stream format, which is suitable for stor‐
age on a character device, web server, or as input to
pkgadd(8).
directory Packages can be stored onto a directory by specifying an
absolute path to a file system directory. The package con‐
tents reside in a directory within the specified direc‐
tory. The package directory name must be identical to its
PKG specification in the pkginfo(5) file. An example de‐
vice specification of this type is /export/packages.
EXAMPLES
Example 1 Translating Packages on /tmp
The following example translates packages pkg1 and pkg2 on /tmp into a
datastream format:
example% pkgtrans -s /tmp /tmp/datastream.pkg pkg1 pkg2
Example 2 Translating a Package Datastream
The following example translates a package datastream into a file sys‐
tem format package:
example% pkgtrans /tmp/pkg1.pkg ~/tmp pkg1
ENVIRONMENT VARIABLES
The MAXINST variable is set in the pkginfo(5) file and declares the
maximum number of package instances.
EXIT STATUS
0 Successful completion.
>0 An error occurred.
USAGE
The pkgtrans command is used to transform legacy SVR4 packages as were
used for Solaris 10 and older releases. Packages for Solaris 11 and
later releases should use the IPS package system instead. See
pkgsend(1) and pkgrecv(1) for similar functionality in IPS.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitypackage/svr4 _ Interface StabilityCommitted
SEE ALSO
pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkginfo(5), pkgmap(5),
attributes(7), installf(8), pkgadd(8), pkgask(8), pkgrm(8), removef(8)
NOTES
By default, pkgtrans does not translate any instance of a package if
any instance of that package already exists on the destination device.
Using the -n option creates a new instance if an instance of this pack‐
age already exists. Using the -o option overwrites an instance of this
package if it already exists. Neither of these options are useful if
the destination device is a datastream.
In their current implementations, pkgadd(8), pkgtrans and other package
commands can process a datastream of up to 4 GB.
HISTORY
Support for package signatures, including the -a, -g, -k, and -P op‐
tions, was added in Solaris 9 12/03 (Update 5) and removed in Oracle
Solaris 11.4.60.
The pkgtrans utility, including support for the -i, -n, -o, and -s op‐
tions, was added to Solaris in Solaris 2.0.
Oracle Solaris 11.4 3 Jan 2025 pkgtrans(1)