8.Show the registered depots on the local system again: $ swlist
#Initializing...
#Target "my_system" has the following depot(s): /var/spool/sw
/my_depots/new_directory_depot
The newly created depot is listed.
9.Show the contents of the new depot:
$ swlist
#Initializing...
#Contacting target "my_system"...
#
#Target: my_system:/my_depots/new_directory_depot
PHCO_27780 1.0
Note that PHCO_27780 is present.
Advanced topic:
You can use the
Copying products with patch dependencies to depots
Add new or updated applications (including products with patch dependencies) to new or existing directory depots by using swcopy with the enforce_dependencies=false and autoselect_patches=false options. Using the default options could select extra patches from different patch bundles on
Registering and unregistering directory depots
You must register a directory depot if you want its contents to be available for remote access by
For example, you might be in the process of creating a directory depot to use for patch installation on production systems. Prior to completing testing on the depot, you do not want users to perform any installations from this depot; therefore, you need to restrict access to the depot. In this case, you simply unregister the depot to prevent remote access. You can also register or unregister tape depots, but you cannot use a registered tape depot as a software source for remote systems.
Registering and unregistering directory depots | 71 |