What does "origin" in the TYPE column say about the package repository?

Consider the following:
root@scolll-server:~# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online https://pkg.oracle.com/solaris/support/
What does “origin” in the TYPE column say about the package repository?

Consider the following:
root@scolll-server:~# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online https://pkg.oracle.com/solaris/support/
What does “origin” in the TYPE column say about the package repository?

A.
It originates from oracle.com.

B.
It contains all of the package metadata.

C.
It supports packages for a single publisher.

D.
It has been configured as the default publisher.

E.
It contains only package content.

Explanation:
Use the pkg publisher command to check the origin of your publisher.
Example:
he following commands show adding an origin to the solaris publisher. If multiple origins are
configured for a given publisher in an image, the IPS client attempts to choose the best origin from
which to retrieve package data.
$ pkg publisher
PUBLISHER TYPE STATUS P LOCATION

solaris origin online F file:///export/repoSolaris11/
$ pfexec pkg set-publisher -g http://pkg.oracle.com/solaris/release/ solaris
$ pkg publisher
PUBLISHER TYPE STATUS P LOCATION
solaris origin online F file:///export/repoSolaris11/
solaris origin online F http://pkg.oracle.com/solaris/release/



Leave a Reply 5

Your email address will not be published. Required fields are marked *


Prossy

Prossy

I agree its B

Abourabba

Abourabba

type could be origin or mirror … so probably a is correct

bigsur

bigsur

origin = packages + package metadata
mirror = packages only
definitevly B