Make backup pkg

Make backup pkg DEFAULT

Convert PS3 Game to PKG Files + Install

Many of my users are regularly requesting me for providing the complete process of how to make a pkg file. I am going to tell you the complete process of PS3 GAME_FOLDER covert to pkg files. This is the simple process so, please read the whole article. Once you learn, how to make a PKG file. Then you can easily make any PKG file in future. You can easily install your PKG file in your PS3 Phat, Slim and SuperSlim console up to CFW/OFW 4.81/4.82. But SuperSlim require PS3Xploit SuperSlim Jailbreak process. If you are a newbie and you don’t know about PS3 Super Slim Jailbreak. Then this article “How to Jailbreak PS3 SuperSlim OFW 4.82” will help you to Jailbreak your PS3 SuperSlim console. So, let’s get started

Imp. Note: All the games will not convert into PKG, maybe some games converted but not working on PS3

How to make PKG files

  • Download and extract PKG Maker Tools on your PC
  • After extract, you got 3 folders: CFW2OFW V11, PS3_Generate_LIC.DAT, and make-backup-pkg
  • Make sure your game folder has LIC.DAT Folder (Mandatory)
  • If your game folder has not the LIC folder then create it with the help of PS3_Generate LIC.DAT. (Open PS3_Generate_LIC.DAT and drag and drop your game folder to PS3_Generate_LIC)
  • Now open your GAME_FOLDER and copy PS3_GAME and paste it into the CFW2OFW V11 Folder
  • After that drag and drop PS3_GAME Folder on the CFW2OFW Helper
  • A process will start automatically; wait for the completion of the process and after that press any key to exit
  • Now a new GAME_FOLDER created. Inside it, you can see two folders BLUSxxxxx and NPUBxxxxx
  • Copy or Cut both folders and paste under the make backup pkg
  • Now run “do” exe, wait for the process completion
  • Once the process successfully is done, you got three pkg files (GAME, PATCH, LICENCE)
  • Copy or cut all 3 pkg files and paste into the PS3xploit-resigner-master folder
  • Now one by one drag and drop all three pkg files on the ps3xploit_rifgen_edatresign (After complete process you will get signed PKG files)
  • Keep the signed pkg files and delete previous all pkg files
  • Now copy or cut all 3 new signed pkg files and paste in your USB stick
  • Plug out USB stick from your PC and plug in your PS3 near to BD drive
  • On PS3 go to HAN Toolbox > HAN Enabler
  • Now go to the Package Manager > Install Package Files > Standard
  • Now install Game, Patch and License pkg files on by one
  • Your game is ready to play. Enjoy!

Some frequently asked question answers

Q1: Can I use my PS3 Phat, slim or Super Slim console?

A: Yes, you can easily use any PS3 console. In this process, there is no restriction of the PS3 console model.

Q2: Can I convert any ps3 game?

A: According to our experience up to 95% games will convert by this process. Only 5% games are not if you try to convert any game with this process and get a black screen it means you cant convert that game (it’s rare).

Q3: What is the console Firmware required to perform this process?

A: Make sure your console should be on 4.81/4.82 firmware, please update your console firmware if below then 4.81/4.82 otherwise your console may brick.

Q4: Di I need a jailbroken console to perform this process?

A: Yes, you need a jailbroken console. We already explained how to jailbreak PS3 console, further if you have PS3 super slim then please read our article how to jailbreak PS3 super slim console.

Convert PS3 Game to PKG files

Required files

  • PS3 PKG Maker Tools
  • PS3Xploit Resigner Master Tool “Resigner Tool”
  • PS3 Game (Copied Blu-Ray)
  • ACT DAT & IDPS (If you don’t know about ACT.DAT and IDPS. Then read How to install PS3 games on OFW 4.81/4.82)

Summary:- Finally, I hope that you easily got this article which is about how to convert the PS3 game to pkg. Further, if you have any query or need any help then you can ask me. I will get back to you as soon as possible. Please like and share my Facebook page and subscribe push notification. Also, bookmark this website for quick access in the future and get regular updates on game and software.

Sours: https://www.superpsx.com/convert-ps3-game-pkg-files-install/

CFW2OFW Compatibility List

TITLETITLE_IDWORKS via
INJECT / DTUWORKS via
HAN / HFWNotes ACE: Another Century's Episode R BLJS10081NoNoNot convertible

Ace Combat Assault Horizon

BLUS30613?YesWorks for HAN users. and Please test using the Inject/DTU Method BLES01392YesYesNone. BLJS10127??Untested

Adventure Time: Explore the Dungeon Because I Don't Know!

BLUS31214      ?            ?      Untested and update exists BLES01961NoYesafter passing the tutorial, the game freezes.

Afro Samurai

BLUS30264YesYesNone.

After Hours Athletes

BCES01335      ?      YesOnly Hustle Kings working, if you chose two others, game quit to PS3 main menu.

Agarest: Generations of War

BLES00594Yes?None.

Agarest: Generations of War 2 (Collector's Edition)

BLES01643Yes?None.

Agarest: Generations of War Zero

BLES01305Yes?None.

Air Conflicts: Pacific Carriers

BLUS31210NoNoNot convertible

Air Conflicts: Secret Wars

BLUS30850NoNoNot convertible

Air Conflicts: Vietnam

BLES01858NoNoNot convertibleBLJM61080NoNoNot convertible

Alice: Madness Returns

BLUS30607No      ?      Not convertible, PSN: NPUB30545 BLES01265No      ?      Not convertibleBLJM60359      ?            ?      Untested

Alien Colonial Marines

BLES01455Yes      ?      Black screen after intro. Doesn't work with BLUS version, game stops in the "installing necessary data" screen, tested with CFW2OFW, PS3 Game Convert 0.91 with HAN

Alien: Isolation

BLUS30832      ?            ?      Untested and update exists BLES01697NoYesPerfectly works with HAN. Inject dtu = Black screen after intro. [CFW2OFW Helper v8] [PS3GameConvert_V0.91] [Data Install] [SPRX]

Aliens Vs. Predator

BLUS30340YesYesconverted with CFW2OFW Helper v13, works with HAN/HEN. BLES00585YesYesconverted with CFW2OFW Helper v13, works with HAN/HEN. BLES00586      ?            ?      Untested and update exists

Alone In The Dark

BLUS30232YesYesNone. BLES00422      ?            ?      Untested and update exists BLAS50043YesYesNone.

Alpha Protocol

BLES00704NoNoNot convertible

Anarchy Reigns

BLES01232NoNoNone.

Angry Birds: Star Wars

BLUS31273YesYesThere is not update but exist INSDIR so converted with PS3GameConvert v0.91

Angry Birds: Trilogy

BLUS31054      ?            ?      Untested and update exists BLES01732YesYesNone.

AquaPazza: AquaPlus Dream Match

BLUS31321NoNoNot Convertible - PSN: NPUB-31336 BLJM60476      ?            ?      Untested; update exists - PSN: NPJB-00566

Ar Nosurge Ode To An Unborn Star

BLUS31478Yes?Works without patch.

Arcadia no Ikusahime

BLJS10224YesYesNone.

Arcana Heart 3 Love Max!!!!!
アルカナハート3 LOVE MAX!!!!!

BLUS31424      ?            ?      Untested and update exists BLJS10274Yes      ?      None.

Armored Core 4

BLUS30027NoNoNot convertible - No PSN release either
Note: No available patch/game updates but the eboot.bin from demos, NPUB90008 or NPEB90009 might help. BCAS20005NoNoNot convertibleBLES00039NoNoNot convertibleBLJM60062NoNoNot convertible

Armored Core For Answer

BLUS30187NoNoNot convertible Game has one patch but doesn't contain EBOOT.BIN.
UPDATE: Tested with BLJM60066 EBOOT and multiple variations of file structures.
Note: No available patch/game updates but the eboot.bin from demos, NPHB00033 or NPJB90067 might help. BLJM60066      ?            ?      Untested and update exists

Armored Core 5

BLUS30516      ?      Nofreezes after tutorial when loading screen for next mission BLES01440Yes      ?      None. BLAS50448YesYesNone.

Armored Core Verdict Day

BLUS31194      ?            ?      Untested and update exists BLES01898Yes      ?      None.

Army of Two

BLUS30057      ?            ?      Untested and update exists BLES00168NoNoConverted with CFW2OFW Helper v13 and PS3GameConvert v0.91, the game stucks at profile creation screen. (works perfectly converted on ISO)

Army of Two: The 40th Day

BLUS30408YesYesPlease Check the Backup with Ps3 Iso Rebuilder and the IRD File... Working Fine with HAN ... For HAN, use PS3GameConvert_v0.91. BLES00659      ?      Yesconverted with PS3GameConvert v0.91, no issues.

Army of Two: The Devil's Cartel

BLUS31069      ?            ?      Untested and update exists BLES01763Exclusive MethodYesInstall game data before DTU Creates "/game/BLES01767/" directory.

For HAN, use PS3GameConvert_v0.91.

BLES01767      ?            ?      Untested and update exists

Arslan: The Warriors of Legend
Arslan Senki X Musou

BLJM61308Yes?None.

Assassin's Creed

NPUB30588      ?      YesNone. BLUS30089      ?      NoInstalls, however boots back to XMB after start. Used CFW2OFW Helper v13. PS3GameConvert v0.91 breaks PS3, requiring to reboot. BLES00158      ?            ?      Untested and update exists BLKS20049      ?            ?      Untested and update exists

Assassin's Creed II

BLUS30364YesNoCFW2OFW: Installs, but boots back to XMB after start. PS3GameConvert: Installs, starts the game, but says that it has error with the disc. BLES00669      ?      NoInstalls, however boots back to XMB after start. Tested with CFW2OFW Helper v13 and PS3GameConvert v0.91. BLKS20167      ?            ?      Untested and update exists

Assassin's Creed II: Game of the Year Edition

BLES00899NoNoNot convertible

Assassin's Creed III

BLUS30991YesYesA folder called ASSASSIN_ISO with a dummy file (try: delete_me.txt) must be created inside the USRDIR folder. BLES01667YesYesA folder called ASSASSIN_ISO with a dummy file (try: delete_me.txt) must be created inside the USRDIR folder. BLES01668YesYesA folder called ASSASSIN_ISO with a dummy file (try: delete_me.txt) must be created inside the USRDIR folder.
(BLES01668 is Special Edition) BLES01669      ?            ?      Untested and update exists BLJM60516      ?      YesUse ps3gameconvert 0.91

Assassin's Creed IV Black Flag

BLUS31193YesYesFor HAN: Create a folder named ASSASSIN_ISO inside USRDIR folder. PKG makers may skip the ASSASSIN_ISO folder and not include it in the PKG since it's empty, to avoid this, make a dummy file inside it (in my case I named it delete_me.txt) BLES01882YesYesA folder called ASSASSIN_ISO must be created inside the USRDIR folder.

For HAN: Create a folder named ASSASSIN_ISO inside USRDIR folder. PKG makers may skip the ASSASSIN_ISO folder and not include it in the PKG since it's empty, to avoid this, make a dummy file inside it (in my case I named it delete_me.txt)

BLES01883      ?            ?      Untested and update exists BLES01884      ?            ?      Untested and update exists BLJM61056      ?      YesUse ps3gameconvert 0.91

Assassin's Creed Brotherhood

BLES00910YesYesNone. atualize por que da tela preta no HEN se não atualiza. BLUS30537YesYesCreate an ASSASSIN_ISO folder inside /PS3_GAME/USRDIR, add an empty text file and convert with PS3GameConvert_v0.91.

Assassin's Creed Revelations

BLES01467YesYesCreate an ASSASSIN_ISO folder inside PS3_GAME / USRDIR, add an empty notepad and convert with PS3GameConvert_v0.91. BLUS30905      ?      YesCreate an empty text file (Delete.me) on ASSASSIN_ISO folder inside PS3_GAME/USRDIR, convert with PS3GameConvert_v0.91.

Assassin's Creed Rogue

BLUS31465YesYesUse ps3gameconvert 0.91 BLES02061YesYesCreate an ASSASSIN_ISO folder inside PS3_GAME / USRDIR, add an empty notepad and convert with PS3GameConvert_v0.91 BLES02062      ?            ?      Untested and update exists

Asura's Wrath

BLUS30721YesYesNone.

Atelier Ayesha The Alchemist of Dusk

BLJM60486YesYesUse ps3gameconvert 0.91. If Title ID is BLUS31152, edit PARAM.SFO and change Title ID into BLJM60486 or BLAS50502 BLAS50502YesYesUse ps3gameconvert 0.91.

Atelier Escha & LogyAlchemist of Dusk Sky

BLJM61050YesYesUse ps3gameconvert 0.91 If Title ID is BLES01992, edit PARAM.SFO and change Title ID into BLJM61050.

Atelier Shallie Alchemists of the Dusk Sea
Shallie no Atelier: Tasogare no Umi no Renkinjutsushi

BLUS31525??Untested BLES02143Exclusive Method?Install game data before DTUBLJM61192YesYesUse ps3gameconvert 0.91 BLAS50771YesYesUse ps3gameconvert 0.91

Attack on Titan
A.O.T. Wings of Freedom
Shingeki no Kyojin

BLJM61326YesYesNone.
Sours: https://www.psdevwiki.com/ps3/CFW2OFW_Compatibility_List
  1. Lightweight decor fabric
  2. Ogdensburg fire dept
  3. Freemasonry masonic holy bible
  4. Samsung s plus
  5. Full circle yoga

How to Convert PS3 Game Folder into pkg file. Yes, friends, many of my subscribers are asking me about this process. SO, on their request, I am going to share with you the complete and fully working process for you. This is a very simple process you need to follow the steps carefully. Once you have done this process successfully then you can convert any PS3 Game_Folder into pkg file. After convert, you can use this file into your PS3 FAT, Slim, or Superslim console and play your favorite game.

Make sure your PS3 console should be jailbroken and have firmware 4.81 or 4.82. Below then this may brick your console. Besides that, if you don’t know how to jailbreak a PS3 Superslim, then click on the hyperlink. So, let’s start with the Convert PS3 Game Folder into the pkg file.

Some requirements for this process
  • PS3 PKG Maker Tools
  • PS3Xploit Resigner Master Tool “Resigner Tool”
  • PS3 Game (Copied Blu-Ray)
  • ACT DAT & IDPs file

Note: All games may not convert into pkg, other than this some converted but not play on your PS3 console, show you the black screen

How to Convert PS3 Game Folder into the pkg file
  1. Download and extract PKG Maker Tools on your PC
  2. After extract, you got 3 folders: CFW2OFW V11, PS3_Generate_LIC.DAT, and make-backup-pkg
  3. The game folder should have LIC.DAT Folder
  4. If your game folder has not the LIC folder then create it with the help of PS3_Generate LIC.DAT. (Open PS3_Generate_LIC.DAT and drag and drop your game folder to PS3_Generate_LIC)
  5. Now open your GAME_FOLDER and copy PS3_GAME and paste it into the CFW2OFW V11 Folder
  6. After that drag and drop PS3_GAME Folder on the CFW2OFW Helper
  7. A process will start automatically; wait for the completion of the process and after that press any key to exit
  8. Now a new GAME_FOLDER created. Inside it, you can see two folders BLUSxxxxx and NPUBxxxxx
  9. Copy or Cut both folders and paste under the make backup pkg
  10. Now run “do” exe, wait for the process completion
  11. Once the process successfully is done, you got three pkg files (GAME, PATCH, LICENCE)
  12. Copy or cut all 3 pkg files and paste into the PS3xploit-resigner-master folder
  13. Now one by one drag and drop all three pkg files on the ps3xploit_rifgen_edatresign (After the complete process you will get signed PKG files)
  14. Keep the signed pkg files and delete previous all pkg files
  15. Now copy or cut all 3 new signed pkg files and paste in your USB stick
  16. Plug out USB stick from your PC and plug in your PS3 near to BD drive
  17. On PS3 go to HAN Toolbox > HAN Enabler
  18. Now go to the Package Manager > Install Package Files > Standard
  19. Now install Game, Patch and License pkg files on by one
  20. Your game is ready to play. Enjoy!
Some general question answers about Convert PS3 Game Folder into the pkg file

Q1: Can I use my PS3 Phat(FAT), slim or Super Slim console?

A: Yes, you can easily use any PS3 console for this process; there is no restriction of the PS3 console make and model.

Q2: Can I convert any PS3 game?

A: Yes you can convert any PS3 game into pkg with this process. May some games not work and show you the black screen.

Q3: What is the console firmware required to perform this process?

A: Make sure your console should be on 4.81/4.82 firmware, please update your console firmware if below then 4.81/4.82 otherwise your console may brick.

Q4: Do I need a jailbroken console to perform this process?

A: Yes, for doing this process you need a jailbroken console. I already explained how to jailbreak the PS3 console in my previous article. Besides that, if you have PS3 super slim then please read my article on how to jailbreak PS3 super slim console.

Summary:- Finally, I hope that you easily understand this article How to convert PS3 Game Folder into a pkg file. Further, if you have any queries then write to me. I will revert back to you as soon as possible with the best possible solution. Please like and share my Facebook page and subscribe to push notification. Also, bookmark my website for quick access in the future and stay connected with me.

Like this:

LikeLoading...

Sours: https://www.pspcx.com/convert-ps3-game-folder-to-pkg-file/
How To Convert PS3 CFW Backup To PKG OFW For PS3 Super Slim / Slim PS3Xploit Tool

pkg

- Image Packaging System retrieval client

Synopsis

/usr/bin/pkg [] command [] []/usr/bin/pkg refresh [--full] [ ...]/usr/bin/pkg install [-nvq] [-g ...] [--accept] [--licenses] [--no-be-activate] [--no-index] [--no-refresh] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] [--reject ...] .../usr/bin/pkg uninstall [-nvq] [--no-be-activate] [--no-index] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] .../usr/bin/pkg update [-fnvq] [-g ...] [--accept] [--licenses] [--no-be-activate] [--no-index] [--no-refresh] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] [--reject ...] [ ...]/usr/bin/pkg list [-Hafnsuv] [-g ...] [--no-refresh] [ ...]/usr/bin/pkg info [-lr] [-g ...] [--license] [ ...]/usr/bin/pkg contents [-Hmr] [-a = ...] [-g ...] [-o ...] [-s ] [-t ...] [ ...]/usr/bin/pkg search [-HIaflpr] [-o ...] [-s ] /usr/bin/pkg verify [-Hqv] [ ...]/usr/bin/pkg fix [--accept] [--licenses] [ ...]/usr/bin/pkg revert [-nv] [--no-be-activate] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] (--tagged ... | ...)/usr/bin/pkg mediator [-aH] [-F ] [ ...]usr/bin/pkg set-mediator [-nv] [-I ] [-V ] [--no-be-activate] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] .../usr/bin/pkg unset-mediator [-nvIV] [--no-be-activate] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] .../usr/bin/pkg variant [-H] [variant. ...]/usr/bin/pkg change-variant [-nvq] [-g ...] [--accept] [--licenses] [--no-be-activate] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] = .../usr/bin/pkg facet [-H] [ ...]/usr/bin/pkg change-facet [-nvq] [-g ...] [--accept] [--licenses] [--no-be-activate] [--no-backup-be | --require-backup-be] [--backup-be-name ] [--deny-new-be | --require-new-be] [--be-name ] =[True|False|None] .../usr/bin/pkg avoid [ ...]/usr/bin/pkg unavoid [ ...]/usr/bin/pkg freeze [-n] [-c ] [] .../usr/bin/pkg unfreeze [-n] [] .../usr/bin/pkg property [-H] [ ...]/usr/bin/pkg set-property /usr/bin/pkg add-property-value /usr/bin/pkg remove-property-value /usr/bin/pkg unset-property .../usr/bin/pkg publisher [-HPn] [ ...]/usr/bin/pkg set-publisher [-Ped] [-k ] [-c ] [-g | --add-origin ...] [-G | --remove-origin ...] [-m | --add-mirror ...] [-M | --remove-mirror ...] [--enable] [--disable] [--no-refresh] [--reset-uuid] [--non-sticky] [--sticky] [--search-after ] [--search-before ] [--search-first] [--approve-ca-cert ] [--revoke-ca-cert ] [--unset-ca-cert ] [--set-property =] [--add-property-value =] [--remove-property-value =] [--unset-property ] /usr/bin/pkg set-publisher -p [-Ped] [-k ] [-c ] [--non-sticky] [--sticky] [--search-after ] [--search-before ] [--search-first] [--approve-ca-cert ] [--revoke-ca-cert ] [--unset-ca-cert ] [--set-property =] [--add-property-value =] [--remove-property-value =] [--unset-property ] []/usr/bin/pkg unset-publisher .../usr/bin/pkg history [-Hl] [-t [ | -],...] [-o ,...] [-n ]/usr/bin/pkg purge-history/usr/bin/pkg rebuild-index/usr/bin/pkg update-format/usr/bin/pkg version/usr/bin/pkg help/usr/bin/pkg image-create [-FPUfz] [--force] [--full | --partial | --user] [--zone] [-k ] [-c ] [--no-refresh] [--variant = ...] [-g | --origin ...] [-m | --mirror ...] [=] [--facet =(True|False) ...] [(-p | --publisher) [=]]

Description

is the retrieval client for the Image Packaging System. With a valid configuration, can be invoked to create locations for packages to be installed, called images, and install packages into those images. Packages are published by publishers, who can make their packages available at one or more repositories, or in package archives. retrieves packages from a publisher's repository or package archives and installs the packages into an image.

A publisher name identifies a person, group of persons, or an organization as the source of one or more packages. To avoid publisher name collisions and help identify the publisher, a best practice is to use a domain name that represents the entity publishing the packages as a publisher name.

A repository is a location where clients can publish and retrieve package content (files contained within the package such as programs and documents) and metadata (information about the package such as its name and description). As an example, a publisher named might have their repository located at the URI .

can also uninstall packages, refresh publisher metadata (such as the list of available packages), validate package installation in an image, and query the image for various tokens. These queries can also be made of (5) repositories.

Images can be of three types: full images, capable of providing a complete system; partial images, which are linked to a full image (parent image), but do not provide a complete system on their own; and user images.

Options

The following options are supported:

Operate on the image rooted at . If no directory was specified or determined based on environment, the default is /. See the “Environment Variables” section for more information.

or

Display a usage message.

Sub-commands

The following subcommands are supported:

Updates the client's list of available packages and publisher metadata for each publisher specified. If no publishers are specified, the operation is performed for all publishers.

With , force a full retrieval of all publisher metadata, instead of attempting an incremental update, and request that any proxies used during the operation ignore cached data. This option exists for troubleshooting purposes and should not be used on a regular basis.

Installs and updates packages to the newest version that match allowed by the packages installed in the image. To explicitly request the latest version of a package, use for the version portion of . For example, specify .

Some configuration files might be renamed or replaced during the installation process. For more information on how the package system determines which files to preserve, and how they are preserved during package operations, see “File Actions” in the (5) man page.

If a package is on the avoid list, installing it removes it from that list.

With , temporarily add the specified package repository or archive to the list of sources in the image from which to retrieve package data. If packages from the specified sources are also available from configured publishers in the image, the client will retrieve content for those packages from the specified sources only. When deciding which version of a package to use, publishers configured in the image, but not found in the given sources take precedence. After install or update, any packages provided by publishers not found in the image are added to the image configuration without an origin. This option can be specified multiple times.

With , perform a trial run of the operation with no package changes made.

With , hide progress messages during the requested operation.

With , issue verbose progress messages during the requested operation, and display detailed planning information (such as changing facets, mediators, and variants). This option can be specified multiple times to increase the amount of planning information displayed.

With , you indicate that you agree to and accept the terms of the licenses of the packages that are updated or installed. If you do not provide this option, and any package licenses require acceptance, the installation operation fails.

With , display all of the licenses for the packages that are installed or updated as part of this operation.

With , do not create a backup boot environment.

With , if a boot environment is created, do not set it as the active BE on the next boot. See (1M) for more information.

With , do not update the search indexes after the operation has completed successfully.

With , do not attempt to contact the repositories for the image's publishers to retrieve the newest list of available packages and other metadata.

With , name the created backup boot environment using the given argument. Use of implies . See also (1M).

With , rename the newly created boot environment to be the argument given. Use of implies . See also (1M).

With , always create a backup boot environment if a new boot environment will not be created. Without this option, a backup boot environment is created based on image policy. See in “Image Properties” below for an explanation of when backup boot environments are created automatically.

With , always create a new boot environment. Without this option, a boot environment is created based on image policy. See in “Image Properties” below for an explanation of when boot environments are created automatically. This option cannot be combined with .

With , do not create a new boot environment. This operation is not performed if a new boot environment is required.

With , prevent packages with names matching the given pattern from being installed. If matching packages are already installed, they are removed as part of this operation. Rejected packages that are the target of group dependencies are placed on the avoid list.

Removes installed packages that match .

If a package is the subject of a group dependency, uninstalling it places it on the avoid list. See the subcommand below.

For all other options, refer to the command above for usage and their effects.

With no arguments, or if asterisk (*) is one of the patterns provided, update all installed packages in the current image to the newest version allowed by the constraints imposed on the system by installed packages and publisher configuration. To explicitly request the latest version of a package, use for the version portion of . For example, specify .

If is provided, replaces packages that are installed, and that match , with the newest version allowed by the patterns and the constraints imposed on the system by installed packages and publisher configuration. Versions older or newer than what is already installed can be specified to perform in-place downgrades or upgrades of specific packages. Updating specific packages across package rename or obsolete boundaries is not supported.

Any preserved configuration files that are part of packages to be downgraded by and that have been changed since the original version was installed are renamed using the extension . For more information about how the package system determines which files to preserve, and how these files are preserved during package upgrades, see “File Actions” in the (5) man page.

With the option, do not execute the client up-to-date check when updating all installed packages.

For all other options, refer to the command above for usage and their effects.

Without arguments, display a list of packages in the current image, including information such as version and installed state. With arguments, display information for the specified packages. By default, package variants for a different architecture or zone type are excluded. The usual output is in three columns:

NAME (PUBLISHER) VERSION IFO system/core-os 0.5.11-0.169 i-- x11/wm/fvwm (fvwm.org) 2.6.1-3 i--

The first column contains the name of the package. If the publisher from which the package is installed (or available, if not installed) is not the first in the publisher search order, then the publisher name is listed in parentheses after the package name. The second column contains the release and branch versions of the package. See the (5) man page for information about release and branch versions and about variants.

The last column contains a set of flags that show the status of the package:

  • An in the column shows that the package is installed.

  • An in the column shows that the package is frozen.

  • An in the column shows that the package is obsolete. An in the column shows that the package has been renamed (a form of obsoletion).

With , omit the headers from the listing.

With , list installed packages and the newest version of packages that are available for installation. Packages are considered to be available for installation if they are allowed by the installed incorporations and by the image's variants. If one or more patterns are specified, then the newest version matching the specified pattern and allowed by any installed incorporations and the image's variants is listed. Without , list only installed packages.

With and , list all versions of all packages for all variants regardless of incorporation constraints or installed state. To explicitly list the latest version of a package when using these options, use for the version portion of . For example, specify .

With , use the specified package repository or archive as the source of package data for the operation. This option can be specified multiple times. Use of implies if is not specified.

With , display the newest versions of all known packages, regardless of installed state.

With , display a one-line short-form giving the package name and summary. This option can be used with , , or .

With , list only packages with newer versions available. This option cannot be used with .

With , show full package FMRIs, including publisher and complete version, all in the first column (the VERSION column disappears). This option can be used with , , or .

With , do not attempt to contact the repositories for the image's publishers to retrieve the newest list of available packages.

Display information about packages in a human-readable form. Multiple FMRI patterns can be specified. With no patterns, display information on all installed packages in the image.

With , use the specified package repository or archive as the source of package data for the operation. This option can be specified multiple times. Use of implies .

With , only display information for installed packages. This is the default.

With , match packages based on the newest available versions, retrieving information for packages not currently installed (if necessary) from the repositories of the image's configured publishers. At least one package must be specified when using this option. Without , only installed packages are displayed by default.

With , display the license texts for the packages. This option can be combined with or .

Display the contents (action attributes) of packages. With no options or operands, display the value of the attribute for actions installed in the current image, sorted alphabetically by attribute value. For information about actions and their attributes, see “Actions” in the (5) man page. See also the list of pseudo attribute names below.

With , limit the output to those actions that have an attribute named in the option argument with a value that matches the (glob) pattern in the option argument (following the attribute name with an equals sign). If multiple options are given, then actions matching any of them are displayed.

With , display information for packages that could be installed in this image from the specified package repository or archive. Packages that could be installed include packages that are currently installed and other packages that satisfy criteria for installation in this image, such as variant and facet restrictions. This option can be specified multiple times. Use of implies .

With , display all attributes of all actions in the specified packages, including actions that could not be installed in this image.

With , display the listed attributes, sorted according to the values of the first attribute listed. The option can be specified multiple times, or multiple attributes can be specified as the argument to one option by separating the attribute names with commas. Only actions that have the requested attributes are displayed.

With , display information for the newest available versions of packages that could be installed in this image from the repositories of the publishers configured in this image. Packages that could be installed include packages that are currently installed and other packages that satisfy criteria for installation in this image, such as variant and facet restrictions. At least one package must be specified when using this option.

With , sort actions by the specified action attribute. If not provided, the default is to sort by path or by the first attribute specified by the option. The option can be specified multiple times.

With , only list actions of the type specified. Multiple types can be specified in a comma-separated list. This option can be specified multiple times.

With , omit the headers from the listing.

With , display information only for those named packages.

Several special pseudo attribute names are available for convenience:

The value of the action's hash, if the action carries a payload.

The value of the action's key attribute. For example, for a action, the key attribute is the path to the file. Some actions do not have a key attribute.

The name of the action. For example, for a file action, this is .

All attributes of matching actions.

The full FMRI of the package containing the action, such as .

The name of the package containing the action, such as .

The publisher of the package containing the action, such as .

The short form FMRI of the package containing the action, such as

The and subcommands are related: Both query the system for the contents of packages. The subcommand displays actions in one or more installed or installable packages, filtering the output based on the specified options. The subcommand approaches the query from the other direction, displaying the names of all packages that contain a user-supplied token.

Each subcommand is capable of formulating some queries of which the other is capable. Care should be taken in choosing the subcommand, as a given query can be more naturally formulated in one than in the other.

Search for matches to the , and display the results. Which tokens are indexed are action-dependent, but can include content hashes and path names. For information about actions and their attributes, see “Actions” in the (5) man page. See also the list of pseudo attribute names in above and in below.

By default, queries are interpreted as a series of terms to be matched exactly. The and characters can be used as (3C)-style wildcards, allowing more flexible query matches.

With , omit the headers.

With , use a case-sensitive search.

By default, and with , perform the search and display information about the matching actions.

By default, prunes results from packages older than the currently installed version and from package versions excluded by current incorporations. Use to show all results, regardless of package version.

With , search the image's installed packages.

With , the columns of the results can be controlled. The option can be specified multiple times, or multiple attributes can be specified as the argument to one option by separating the attribute names with commas. In addition to the pseudo attributes outlined above, the following attributes are defined for search results:

Corresponds to the string that matched the search query.

Corresponds to the attribute that contained the string that matched the search query.

With , display packages that have some actions that match each query term. Using this option is equivalent to putting angle brackets () around each term in the query. See below for more description of the operator.

By default, and with , search the repositories corresponding to the image's publishers.

With , search the (5) repository located at the given URI. This can be specified multiple times. Package archives are not supported.

Both and (or ) can be specified together, in which case both local and remote searches are performed.

In addition to simple token matching and wildcard search, a more complicated query language is supported. Phrases can be searched for by using single or double quotation marks ( or ). Be sure to take your shell into account so that actually sees the or .

Boolean search using AND and OR is supported. Field, or structured, queries are supported. The syntax for these is . Missing fields are implicitly wildcarded. A search for matches all action types in all packages with a key of and that match the token . Explicit wildcards are supported in the and fields. The and must match exactly.

To convert actions to the packages that contain those actions, use . With the option, searching for results in information about the actions matching , while searching for results in a list of packages containing actions that matched .

Validate the installation of packages in the current image. If current signature policy for related publishers is not , the signatures of each package are validated based on policy. See in “Image Properties” below for an explanation of how signature policies are applied.

With , omit the headers from the verification output.

With , print nothing, but return failure if there are any fatal errors.

With , include informational messages regarding packages.

Fix any errors reported by . Verification of installed package content is based on a custom content analysis that might return different results than those of other programs.

With , you indicate that you agree to and accept the terms of the licenses of the packages that are updated or installed. If you do not provide this option, and any package licenses require acceptance, the operation fails.

With , display all of the licenses for the packages to be installed or updated as part of this operation.

Revert files to their as-delivered condition. Either all files tagged with a particular value, or individual files can be reverted. File ownership and protections are also restored.


Caution

Caution - Reverting some editable files to their default values can make the system unbootable, or cause other malfunctions.


For all other options, refer to the command above for usage and their effects.

Display the current selected version and/or implementation of all mediators, or with arguments, only the mediators specified.

With , list the mediations that can be set for currently installed packages.

With , specify an alternative output format. Currently, only (Tab Separated Values) is valid.

With , omit the headers from the listing.

Set the version and/or implementation for the specified mediators in the current image.

With , set the implementation of the mediated interface to use. By default, if no version is specified, all implementation versions are allowed. To specify an implementation with no version, append an at sign (@).

With , set the version of the mediated interface to use.

If the specified mediator version and/or implementation is not currently available, any links using the specified mediators are removed.

For all other options, refer to the command above for their usage and effects.

Revert the version and/or implementation of the specified mediators to the system default.

With , revert only the implementation of the mediated interface.

With , revert only the version of the mediated interface.

For all other options, refer to the command above for their usage and effects.

Without arguments, display the current values of all variants set in this image. With arguments, display the value of each specified set in this image.

With , omit the headers from the listing.

See “Facets and Variants” in the (5) man page for more information about variants.

Change the values of the specified variants set in the current image.

For option usage and effects, refer to the command above.

Changing the value of a variant can cause package content to be removed, updated, or installed. Changing a variant value can also cause entire packages to be installed, updated, or removed to satisfy the new image configuration. See “Facets and Variants” in the (5) man page for more information about variants.

Without arguments, display the current values of all facets that have been explicitly set in this image by using the command. With arguments, display the value of each specified set in this image.

With , omit the headers from the listing.

See “Facets and Variants” in the (5) man page for more information about facets.

Change the values of the specified facets set in the current image.

Facets can be set to or . Setting a facet to applies the default value of to that facet; thus, any actions subject to the facet will be installed. See “Actions” in the (5) man page for information about actions..

For option usage and effects, refer to the command above.

Changing the value of a facet can cause package content to be removed, updated, or installed. Changing a facet value can also cause entire packages to be installed, updated, or removed to satisfy the new image configuration. See “Facets and Variants” in the (5) man page for more information about facets.

Avoids the specified packages if they are the target of a group dependency by placing the package names that currently match the specified patterns on the avoid list. Only packages that are not currently installed can be avoided. If a package is currently the target of a group dependency, uninstalling the package places it on the avoid list.

Without any arguments, display each avoided package along with any packages that have a group dependency on that package.

Packages that are on the avoid list are installed if needed to satisfy a required dependency. If that dependency is removed, the package is uninstalled.

Remove the specified packages from the avoid list. Packages on the avoid list that match an installed package's group dependency cannot be removed using this subcommand. To remove a package from the avoid list that matches a group dependency, install the package.

Without any arguments, display the list of avoided packages.

Freeze the specified packages to the versions specified. If no version is given, the package must be installed and is frozen at that installed version. When a package that is frozen is installed or updated, it must end up at a version that matches the version at which it was frozen. For example, if a package was frozen at 1.2, then it could be updated to 1.2.1, 1.2.9, 1.2.0.0.1, and so on. That package could not end up at 1.3, or 1.1. A publisher presented in the is used to find matching packages. However, publisher information is not recorded as part of the freeze. A package is frozen with respect to its version only, not its publisher. Freezing a package that is already frozen replaces the freeze version with the newly specified version.

If no packages are provided, information about currently frozen packages is displayed: package names, versions, when the package was frozen, and any associated reasons.

Freezing a package does not prevent removal of the package. No warning is displayed if the package is removed.

With , record the with the packages that are frozen. The reason is shown if a freeze prevents an installation or update from succeeding.

With , perform a trial run of the operation, displaying the list of packages that would be frozen without freezing any packages.

Remove the constraints that freezing imposes from the specified packages. Any versions provided are ignored.

With , perform a trial run of the unfreeze, displaying the list of packages that would be unfrozen without unfreezing any packages.

Display image property information. With no argument, display the names and values for all image properties. If a specific list of property names is requested, display the names and values for those properties. See “Image Properties” below for descriptions of image properties.

With , omit the headers from the listing.

Update an existing image property or add a new image property.

Add a value to an existing image property or add a new image property.

Remove a value from an existing image property.

Remove an existing image property or properties.

Display publisher information. With no arguments, display the list of all publishers, their origin URIs, and mirrors in order of search preference. If specific publishers are requested, display detailed configuration for those publishers.

With , omit the headers from the listing.

With , display only the first publisher in the publisher search order.

With , display only enabled publishers.

Update an existing publisher or add a package publisher. If no options affecting search order are specified, new publishers are appended to the search order and are thus searched last.

With or , set the specified publisher first in the search order. When installing new packages, this publisher is searched first. Updates to already installed packages come from the same publisher that originally provided the package as long as that publisher remains sticky. When or is used with , only added publishers are placed first in search order.

With , specify that higher ranked publishers than this one can provide updates to packages originally installed from this publisher.

With , specify that updates to packages that were installed from this publisher must also come from this publisher. This is the default behavior.

With , alter the publisher search order so that the publisher being modified is searched before the specified publisher. When used with , only applies to added publishers.

With , alter the publisher search order so that the publisher being modified is searched after the specified publisher. When used with , only applies to added publishers.

With , add the given certificate as a CA certificate that is trusted. The hashes of the PEM representation of the user-approved CA certificates are listed in the detailed output of the command.

With , treat the certificate with the given hash of its PEM representation as revoked. The hashes of the user-revoked CA certificates are listed in the detailed output of the command.

With , remove the certificate with the given hash from the list of approved certificates and the list of revoked certificates.

With , update an existing publisher property or add a new publisher property.

With , add a value to an existing publisher property or add a new publisher property.

With , remove a value from an existing publisher property.

With , remove an existing publisher property.

With and , specify client SSL certificate and key respectively.

With (), add the specified URI or path as an origin for the given publisher. This should be the location of a package repository or archive.

With (), remove the URI or path from the list of origins for the given publisher. The special value can be used to remove all origins.

With , do not attempt to contact the repositories for the image's publishers to retrieve the newest list of available packages and other metadata.

With , choose a new unique identifier that identifies this image to its publisher.

With (), add the URI as a mirror for the given publisher.

With (), remove the URI from the list of mirrors for the given publisher. The special value can be used to remove all mirrors.

With , retrieve publisher configuration information from the specified repository URI. If a publisher is specified, then only the matching publisher is added or updated. If no publisher is specified, all publishers are added or updated as appropriate. This option cannot be combined with the , , , , , , , , , , , or options.

With (), enable the publisher. With (), disable the publisher. A disabled publisher is not used when populating the package list or in certain package operations (install, uninstall, and update). However, the properties for a disabled publisher can still be set and viewed. If only one publisher exists, it cannot be disabled.

With , retrieve publisher configuration information from the specified repository URI. If a publisher is specified, then only the matching publisher is added or updated. If no publisher is specified, all publishers are added or updated as appropriate. See above for descriptions of other options that can be used with the option. The option cannot be combined with the , , , , , , , , , , , or options.

Remove the configuration associated with the given publisher or publishers.

Display the command history of the applicable image.

With , omit the headers from the listing.

With , display log records for a comma-separated list of timestamps, formatted with (see (3C)). To specify a range of times, use a hyphen (-) between a start and finish timestamp. The keyword can be used as an alias for the current time. If the timestamps specified contain duplicate timestamps or overlapping date ranges, only a single instance of each duplicate history event is printed.

With , display log records in long format, which, in addition to the standard format, includes the outcome of the command, the time the command completed, the version and name of the client used, the name of the user who performed the operation, and any errors that were encountered while executing the command.

With , display only the specified number of most recent entries.

With , display output using the specified comma-separated list of column names. Valid column names are:

The name of the boot environment this operation was started on.

The of the boot environment this operation was started on.

The name of the client.

The version of the client.

The command line used for this operation.

The time that this operation finished.

The user id that started this operation.

The new boot environment created by this operation.

The of the new boot environment created by this operation.

The name of the operation.

A summary of the outcome of this operation.

Additional information on the outcome of this operation.

The snapshot taken during this operation. This is only recorded if the snapshot was not automatically removed after successful operation completion.

The time that this operation started.

The total time taken to perform this operation. For operations that take less than one second, 0:00:00 is shown.

The username that started this operation.

If the or columns are specified, they must be the last item in the list, in order to preserve output field separation. These two columns cannot be shown in the same command.

An asterisk (*) is shown after the values for or if the boot environment is no longer present on the system.

The values for and are obtained by looking up the current boot environment name, using the or fields. If a boot environment was subsequently renamed, and later deleted, the values displayed for and are the values recorded at the time of the operation.

Deletes all existing history information.

Rebuilds the index used by . This is a recovery operation not intended for general use.

Updates the format of the image to the current version. Once this operation has completed, the image can no longer be used with older versions of the (5) system.

Display a unique string identifying the version of (1). This string is not guaranteed to be comparable in any fashion between versions.

At the location given by , create an image suitable for package operations. The default image type is user, as given by the () option. The image type can be set to a full image ( or ) or to a partial image ( or ) linked to the full image enclosing the given path. Additional origins can be specified using or . Additional mirrors can be specified using or .

A package repository URI must be provided using the or option. If a publisher name is also provided, then only that publisher is added when the image is created. If a publisher name is not provided, then all publishers known by the specified repository are added to the image. An attempt to retrieve the catalog associated with this publisher is made following the initial creation operations.

For publishers using client SSL authentication, a client key and client certificate can be registered via the and options. This key and certificate are used for all publishers added during image creation.

If the image is to be run within non-global zone context, then the () option can be used to set an appropriate variant.

With (), force the creation of an image over an existing image. This option should be used with care.

With , do not attempt to contact the repositories for the image's publishers to retrieve the newest list of available packages and other metadata.

With , set the specified variant to the indicated value. See “Facets and Variants” in the (5) man page for more information about variants.

With , set the specified facet to the indicated value. See “Facets and Variants” in the (5) man page for more information about facets.

With , set the specified image property to the indicated value. See “Image Properties” below for descriptions of image properties.

Image Properties

The following properties define characteristics of the image. These properties store information about the purpose, content, and behavior of the image. To view the current values of these properties in the image, use the command. To modify the values of these properties, use the and commands.

(string) Specify when a boot environment is created during packaging operations. The following values are allowed:

Apply the default BE creation policy, .

Requires a reboot for all package operations by performing them in a new BE set as active on the next boot. A backup BE is not created unless explicitly requested.

This policy is the safest, but is more strict than most sites need since no packages can be added without a reboot.

For package operations that require a reboot, a new BE is created and set as active on the next boot. If packages are modified or content that could affect the kernel is installed and the operation affects the live BE, a backup BE is created but not set as active. A backup BE can also be explicitly requested.

This policy is potentially risky only if newly installed software causes system instability, which is possible but relatively rare.

For package operations that require a reboot, a new BE is created and set as active on the next boot. A backup BE is not created unless explicitly requested.

This policy carries the greatest risk since if a packaging change to the live BE makes further changes impossible, there might be no recent BE to which one can fallback.

(string) A path name that points to a directory where CA certificates are kept for SSL operations. The format of this directory is specific to the underlying SSL implementation. To use an alternate location for trusted CA certificates, change this value to point to a different directory. See the portions of (3openssl) for requirements for the CA directory.

Default value:

(boolean) If this is set to , the package client attempts to contact any CRL distribution points in the certificates used for signature verification to determine whether the certificate has been revoked since being issued.

Default value:

(boolean) If this is set to , the package client removes the files in its content-cache when install or update operations complete. For update operations, the content is removed only from the source BE. When a packaging operation next occurs in the destination BE, the package client flushes its content cache if this option has not been changed.

This property can be used to keep the content-cache small on systems with limited disk space. This property can cause operations to take longer to complete.

Default value:

(boolean) This property tells the client to discover link-local content mirrors using mDNS and DNS-SD. If this property is set to , the client attempts to download package content from mirrors it dynamically discovers. To run a mirror that advertises its content via mDNS, see (1M).

Default value:

(boolean) Send the image's Universally Unique Identifier (UUID) when performing network operations. Although users can disable this option, some network repositories might refuse to talk to clients that do not supply a UUID.

Default value:

(string) Determine what checks will be performed on manifests when installing, updating, modifying, or verifying packages in the image. The final policy applied to a package depends on the combination of image policy and publisher policy. The combination will be at least as strict as the stricter of the two policies taken individually. By default, the package client does not check whether certificates have been revoked. To enable those checks, which might require the client to contact external web sites, set the image property to . The following values are allowed:

Ignore signatures for all manifests.

Verify that all manifests with signatures are validly signed, but do not require all installed packages to be signed. This is the default value.

Require that all newly installed packages have at least one valid signature. The and commands also warn if an installed package does not have a valid signature.

Follow the same requirements as but also require that the strings listed in the property appear as a common name of the certificates used to verify the chains of trust of the signatures.

(list of strings) A list of names that must be seen as common names of certificates while validating the signatures of a package.

(string) The path name of the directory that contains the trust anchors for the image. This path is relative to the image. The default value is .

(boolean) This property indicates whether the image should use the system repository as a source for image and publisher configuration and as a proxy for communicating with the publishers provided. The default value is . See (1M) for information about system repositories.

Publisher Properties

The following properties define signature policy for a particular publisher. The image properties of the same name define signature policy for the image. To view the current values of these properties for a particular publisher, use the command. To modify the values of these publisher signature policy properties, use the and options of the command.

(string) This property functions identically to the image property of the same name except that it only applies to packages from the particular publisher.

(list of strings) This property functions identically to the image property of the same name except that it only applies to packages from the particular publisher.

Examples

Example 1 Create an Image With Publisher Configured

Create a new, full image, with publisher , stored at .

$ pkg image-create -F -p example.com=http://pkg.example.com:10000 \/aux0/example_root

Example 2 Create an Image, Specifying Additional Origins and Mirror

Create a new, full image, with publisher , that also has an additional mirror, two additional origins, and is stored at .

$ pkg image-create -F -p example.com=http://pkg.example.com:10000 \-g http://alternate1.example.com:10000/ \-g http://alternate2.example.com:10000/ \-m http://mirror.example.com:10000/ \/aux0/example_root

Example 3 Create an Image With No Publisher Configured

Create a new, full image with no publishers configured at .

$ pkg image-create -F /aux0/example_root

Example 4 Install a Package

Install the latest version of the package in the current image.

$ pkg install application/widget

Example 5 List Specified Contents of a Package

List the contents of the package. Display the action name, the mode of the file (if defined), the size (if defined), the path, and the target (if a link). Limit the action to types , , , and , since specifying the attribute, which is available for all actions, displays a line for all actions, which is not desired here.

$ pkg contents -t dir,file,link,hardlink \-o action.name,mode,pkg.size,path,target system/file-system/zfs ACTION.NAME MODE PKG.SIZE PATH TARGET dir 0755 etc dir 0755 etc/fs dir 0755 etc/fs/zfs link etc/fs/zfs/mount ../../../usr/sbin/zfs link etc/fs/zfs/umount ../../../usr/sbin/zfs dir 0755 etc/zfs dir 0755 kernel dir 0755 kernel/drv dir 0755 kernel/drv/amd64 file 0755 1706744 kernel/drv/amd64/zfs file 0644 980 kernel/drv/zfs.conf dir 0755 kernel/fs dir 0755 kernel/fs/amd64 hardlink kernel/fs/amd64/zfs ../../../kernel/drv/amd64/zfs ...

Example 6 List Specified Contents of Two Packages

List the contents of and , limiting the display to just the package name and path attributes of actions whose attribute ends in or .

$ pkg contents -o pkg.name,path -a path=\*.desktop \-a path=\*.png web/browser/firefox mail/thunderbird PKG.NAME PATH web/browser/firefox usr/share/applications/firefox.desktop mail/thunderbird usr/share/applications/thunderbird.desktop web/browser/firefox usr/share/pixmaps/firefox-icon.png mail/thunderbird usr/share/pixmaps/thunderbird-icon.png ...

Example 7 Search for a Package

Search the package database for the token .

$ pkg search bge INDEX ACTION VALUE PACKAGE driver_name driver bge pkg:/driver/network/[email protected] basename file kernel/drv/sparcv9/bge pkg:/driver/network/[email protected] basename file kernel/drv/amd64/bge pkg:/driver/network/[email protected] pkg.fmri set solaris/driver/network/bge pkg:/driver/network/[email protected]

The token is in the package both as the basename for the file action representing and as a driver name.

Example 8 Search for Packages that Depend on the Specified Package

Search for installed packages that depend on .

$ pkg search -l 'depend::package/pkg' INDEX ACTION VALUE PACKAGE incorporate depend package/[email protected] pkg:/consolidation/ips/[email protected] require depend package/[email protected] pkg:/system/[email protected] require depend package/[email protected] pkg:/package/pkg/[email protected]

Example 9 Search for Dependencies

Search for all dependencies in installed packages.

$ pkg search -l 'depend:incorporate:' INDEX ACTION VALUE PACKAGE incorporate depend pkg:/[email protected],5.11-0.133 pkg:/consolidation/osnet/[email protected] incorporate depend pkg:/[email protected],5.11-0.133 pkg:/consolidation/osnet/[email protected] ...

Example 10 Add a Publisher

Add a new publisher , with a repository located at .

$ pkg set-publisher -g http://www.example.com/repo example.com

Example 11 Add a Publisher With Key and Certificate

Add a new publisher , with a secure repository located at , and a key and certificate stored in the directory .

$ pkg set-publisher -k /root/creds/example.key \-c /root/creds/example.cert -g https://secure.example.com/repo \example.com

Example 12 Add and Automatically Configure a Publisher

Add a new publisher with a repository located at using automatic configuration.

$ pkg set-publisher -p /export/repo

Example 13 Add and Manually Configure a Publisher

Add a new publisher with a repository located at using manual configuration.

$ pkg set-publisher -g /export/repo example.com

Example 14 Verify All Signed Packages

Configure an image to verify all signed packages.

$ pkg set-property signature-policy verify

Example 15 Require All Packages To Be Signed

Configure an image to require all packages to be signed, and require the string to be seen as a common name for one of the certificates in the chain of trust.

$ pkg set-property signature-policy require-names example.com

Example 16 Require All Packages From a Specified Publisher To Be Signed

Configure an image so that all packages installed from publisher must be signed.

$ pkg set-publisher --set-property signature-policy=require-signatures \example.com

Example 17 Require a Specified String in the Chain of Trust

Add the string to the image's list of common names that must be seen in a signature's chain of trust to be considered valid.

$ pkg add-property-value signature-require-names foo

Example 18 Remove a String From the Chain of Trust for a Specified Publisher

Remove the string from the list of common names that must be seen to validate a signature for the publisher .

$ pkg set-publisher --remove-property-value signature-require-names=foo \example.com

Example 19 Add a Trusted CA Certificate

Add the certificate stored in as a trusted CA certificate for the publisher .

$ pkg set-publisher --approve-ca-cert /tmp/example_file.pem \example.com

Example 20 Revoke a Certificate

Revoke the certificate with the hash for publisher , preventing the certificate from validating any signatures for packages from .

$ pkg set-publisher --revoke-ca-cert a12345 example.com

Example 21 Forget About a Certificate

Make forget that the certificate was ever added or revoked by the user.

$ pkg set-publisher --unset-ca-cert a12345 example.com

Example 22 Downgrade a Package

Downgrade the installed package to an older version.

$ pkg update [email protected]

Example 23 Switch Conflicting Package Installation

In the case of two conflicting packages, change which package is installed. Suppose package A depends on either package B or package C, and B and C are mutually exclusive. If A and B are installed, use the following command to switch to using C instead of B without uninstalling A:

$ pkg install --reject B C

Example 24 List Packages in a Package Archive

List all versions of all packages in a package archive.

$ pkg list -f -g /my/archive.p5p

Example 25 List Packages in a Package Repository

List all versions of all packages in a repository.

$ pkg list -f -g http://example.com:10000

Example 26 Display Information About a Package in a Package Archive

Display the package information for the latest version of a package in a package archive. The package might or might not be currently installed.

$ pkg info -g /my/archive.p5p pkg_name

Example 27 Display Contents of a Package in a Package Archive

Display the contents of a package in a package archive. The package is not currently installed.

$ pkg contents -g /my/archive.p5p pkg_name

Example 28 Remove All Publisher Origins and Mirrors

Remove all of the origins and mirrors for a publisher and add a new origin.

$ pkg set-publisher -G '*' -M '*' -g http://example.com:10000 \example.com

Environment Variables

The directory containing the image to use for package operations. Ignored if is specified.

Seconds to wait trying to connect during transport operations (for each attempt) before the client aborts the operation. A value of 0 means wait indefinitely.

Default value: 60

Seconds below the limit (1024 bytes/sec) during transport operations before the client aborts the operation. A value of 0 means do not abort the operation.

Default value: 30

Maximum number of transient transport errors before the client aborts the operation. A value of 0 means do not abort the operation.

Default value: 4

Maximum number of HTTP or HTTPS redirects allowed during transport operations before a connection is aborted. A value of 0 means do not abort the operation.

Default value: 5

Maximum number of transport attempts per host before the client aborts the operation. A value of 0 means do not abort the operation.

Default value: 4

,

HTTP or HTTPS proxy server.

Exit Status

The following exit values are returned:

Command succeeded.

An error occurred.

Invalid command line options were specified.

Multiple operations were requested, but only some of them succeeded.

No changes were made - nothing to do.

The requested operation cannot be performed on a live image.

The requested operation cannot be completed because the licenses for the packages being installed or updated have not been accepted.

The image is currently in use by another process and cannot be modified.

An unanticipated exception occurred.

Files

A (5) image can be located arbitrarily within a larger file system. In the following file descriptions, the token is used to distinguish relative paths. For a typical system installation, is equivalent to

Metadata directory for a full or partial image.

Metadata directory for a user image.

Within a particular image's metadata, certain files and directories can contain information useful during repair and recovery. The token refers to the top-level directory containing the metadata. is typically one of the two paths given above.

Location of conflicting directories and files moved during a package operation. Location of unpackaged contents of a removed directory.

Contains a directory for each publisher. Each directory stores publisher-specific metadata.

Other paths within the directory hierarchy are private and are subject to change.

Attributes

See (5) for descriptions of the following attributes:

Availability

Interface Stability

Uncommitted

See Also

(1), (1m), (3C), (5), (1M)

PreviousNext
Sours: https://docs.oracle.com/cd/E23824_01/html/E21796/pkg-1.html

Backup pkg make

Convert PS3 Folder Games to PKG

When we talk about PS3 games. There are lots of choices such as action, battle royal, scary, shooter games, etc. But when we talk about PS3 Game installation. We must understand the formats of the game. Sony only releases two types of formats, One is disk format which we call PS3 Folder game and another one is PKG which we download directly from PSN store. Here you’ll learn how to convert PS3 folder Games to PKG.

PS3 CFW installer users easily just copy and paste PS3 folder games and enjoy with the help of MultiMan. PS3 HAN installer users are only able to install PKG. It doesn’t mean that you are HAN installer user so that you can’t install PS3 folder games. Easily you can. You just need to read & understand this article carefully. As usual, I always mentioned it. You need a jailbroken console. If you don’t have a jailbroken console. Read PS3Xplot v3.0.1 PS3 Super Slim Jailbreak 4.84. Now let’s get started.

Requirements:-

  • A Laptop or Desktop
  • A USB or External Hard Drive
  • Jailbroken Console

How to Convert PS3 Folder Games to PKG

  1. Extract Require file anywhere on your computer into one folder.
  2. Copy your PS3_GAME folder and paste it on CFWOFW Converter V11 folder.
  3. Drag and drop your PS3_GAME folder on CFW2OFW Helper.
  4. Go to (Game Name) Folder and copy both result folders.
  5. Paste result folders on PKG Maker Folder.
  6. Run Do exe
  7. Copy Result (Game, Patch, Licence) File
  8. Paste result files on PS3 Resigner Master
  9. One by one sign all PKG by dragging and drop on the resigner master exe.

Require Files

Note: Before the start PS3 folder Games to PKG converting process. Make sure your game has Licence Folder and files. If you don’t have, use PS3 Licence Generator to generate your Game license folder & file.

FAQs:-

Q1:- My PS3 keeps exiting the game by itself and Returning to XMB?

A1: There can be two reasons. First, Make sure your converted game has LICENCE game folder and file or not. If not use the PS3 Licence generator to generate the license. 2nd, There are lots of Resigner Master versions. Just try it with a different one and your problem will resolve.

Conclusions: I hope you got all the pieces of information about PS3 Folder game to PKG. Leave your feedback in the comment section or your issues. Follow me on YouTube and Facebook Page to stay connected with me.

Sours: https://www.smartgametech.com/convert-ps3-folder-games-pkg/
How To Split Large PKG Game Files For Your PS3 External HDD ( Very Easy 2020)

Is it funny. And I am also stunned now, how funny, however, then it was all very serious. And like that, a little bit, where I was a little jerking, where I shoved where, in which hole (and how not scary. It was to pick up some rubbish on the train ???), I got my first orgasm !!.

Similar news:

For several minutes the man enjoyed the sight of his mother. When the elderly woman pissed in pain, the master let go of her tongue, removed the hook with the load. Returning to his victim, the sadist ran his hand over the chest of the sobbing slave. From this touch.the old woman, for a moment, calmed down, but then, she uttered a heart-rending cry.



548 549 550 551 552