By removing the need for an Internet connection for packaging operations, a Solaris 11 Local Image Packing Systems (IPS) Repository offers two major advantages: speed. 개요. 솔라리스 11의 설치에 대해 다룬다. 기존 버전과는 달리, 솔라리스 11부터 설치 미디어에는 설치에 필요한 최소한의.
Solaris 1. 1 - Image Packaging Systems. What is Image the Packaging System? The Image Packaging System (IPS) is a new network- centric software packaging and delivery system in Oracle Solaris 1. IPS allows efficient, observable, and controllable transitions between known configurations of software content providing administrators with safe system upgrade environments and better control over planned system downtime schedules. The ZFS file system is integral to IPS, providing administrators the ability to perform updates on a file system clones on live production systems. NOTE: While many IPS commands that query the system (list, info, contents, search, history) can be performed by any user, commands that make changes to the system image must be performed by adopting an appropriate administrative role. Understanding the Package FMRIEach software package is uniquely described by an FMRI (Fault Managed Resource Indicator), for example: pkg: //solaris/diagnostic/wireshark@1. T0. 63. 5ZFMRI Segment : Description solaris : Publisher diagnostic/wireshark : Package name 1.
Component : version 5. Build : version 0. Branch : version 2. T0. 63. 5Z : Package time stamp.
How to Update Your Local System From a Support Repository Update (SRU) ISO Image The procedure is documented in the README file that comes with the SRU ISO image. Oracle Solaris 11 is the enterprise OS build for the most challenging enterprise and cloud applications.
You could always create an x86 Solaris 10 system in VirtualBox, and create a flar archive from that. And since most people wont be running Solaris 10 zones on Solaris. Installation from CD/DVD or USB. Prior to installing, check the System Requirements and the Release Notes. The document First Steps with Oracle Solaris 11 Article. Recently I had a DBA at an IOUG event complain that they were unable to install from the Solaris 11.2 ISO. They had seen me demo Openstack a few weeks ago, and wanted. Solaris 11 hints Since Solaris 11 is now Officially released, I have started tinkering with it. This will be a container for my notes on it. Sections that grow too.
Installing Packages and Updating a System. Installing new packages on your system does not require a new boot environment (BE) to be created. However, creating a ZFS snapshot and clone initially consumes no additional space and is an instantaneous operation.
So it should be considered as an administrative best practice. Install a package called diagnostic/wireshark: # pkg install diagnostic/wireshark. Uninstall a package called diagnostic/wireshark using a short form of the package name: # pkg uninstall wireshark. Update all possible packages to the newest version, including all Oracle Solaris zones: # pkg update. Do a dry run of an update of all possible packages to the newest version: # pkg update - nv. Update all system packages to the newest version and require a new BE: # pkg update –be- name fix- nfs- issue. Getting Information or Searching for Packages.
List packages currently installed on a system: # pkg list. Show information about an installed package called wireshark: # pkg info wireshark. Show information about an uninstalled package called xchat: # pkg info - r xchat. Show the contents of an installed package called wireshark: # pkg contents wireshark. Show all PNG files of an installed package called wireshark: # pkg contents - o path - a path=*. Search all locally installed packages for the match gcc: # pkg search - l gcc.
Search all packages in the configured repositories that contain dev headergcrypt- module. Search for all packages in the configured repositories that have the classification Web Services/Application and Web Servers: # pkg search - o pkg. Application and Web Servers’Search for all packages installed locally that have a dependency on library/libxml. Managing Repositories and Publishers. List currently associated publishers: # pkg publisher. Add a publisher at a specified repository URI: # pkg set- publisher - p http: //www.
Add a publisher: # pkg set- publisher - g http: //www. Remove a publisher: # pkg unset- publisher siteapps. Query a repository URI for publisher names and package counts: # pkgrepo - s http: //pkg.
Change to the Oracle Solaris support repository with pre- downloaded certificatesand keys from the Oracle Solaris release repository: # pkg set- publisher - G http: //pkg. Miscellaneous Commands. Browse package command history (includes graphical Package Manager client): # pkg history. Purge package command history: # pkg purge- history. Verify the integrity of the current system image: # pkg verify.
Verify the integrity of installed package called wireshark: # pkg verify wireshark. Fix any errors reported by pkg verify on an installed package called wireshark: # pkg fix wireshark. Freeze a package called wireshark to prevent any accidental future updates: # pkg freeze wireshar. This post helps to get some quick answers about following questions.
How do I update my system to a specific Support Repository Update (SRU)? How to prevent pkg(1) from keeping a large download cache in /var/pkg/download? How to change the current publisher? How to remove a publisher via the CLI? How can I check which Support Repository Update (SRU) I have currently installed? How do I install pkgs into an alternate root?
How do I configure proxy access to pkg. How do I check if a bug is fixed on Solaris 1. How do I list all the available package groups? How do I list the contents of a package group? How do I determine which group is installed on my system? How do I update a local repository with only the changes from a remote repository?
How do I list the changes that would apply to my local repository during an update without actually updating my local repository? How do I locate the pkg that delivers a particular file? How do I list pkg dependencies?
How to Update Your Local System From a Support Repository Update (SRU) ISO Image How to Update an Oracle Solaris 1. Package Repository How do I set the default version of pkgs that allow multiple versions to be installed, like Java? How do I list all setuid and setgid programs? How do I update my system to a specific Support Repository Update (SRU)? First, get a list of all the available versions of the “entire” pkg (formatting modified slightly for this document): $ pkg search entire.
INDEX ACTION VALUE PACKAGEpkg. Support Repository Update(Oracle Solaris 1. SRU 0. 1). For more information see Document 1.
Support Repository Update(Oracle Solaris 1. SRU 0. 2). For more information see Document 1. Support Repository Update(Oracle Solaris 1. SRU 0. 3). For more information see Document 1. Support Repository Update(Oracle Solaris 1.
SRU 0. 4). For more information see Document 1. Support Repository Update(Oracle Solaris 1.
SRU 0. 4a). For more information see Document 1. By default this will return a list of available SRUs equal to or newer than the current system as pkg(1) by default prunes results which are older. You can display all available SRUs by appending the - f flag. Take note of the “pkg: /entire@” field and the numbers after the @. This is the value you will be using to upgrade (< SRU_version> below). You can now upgrade to that specific version using one of two methods: The long method – this method is good if you like to specify a nice name for for your boot environment in the grub menu using the - d option: # beadm create - d “BE Description” < New_BE> # beadm mount < new- be> /mnt# pkg - R /mnt install entire@< SRU_version> # bootadm update- archive - R /mnt# beadm unmount < New_BE> # beadm activate < New_BE> The short single command method: # pkg update –be- name < New_BE> entire@< SRU_version> The –be- name argument is an optional argument.
How to prevent pkg(1) from keeping a large download cache in /var/pkg/download? You can prevent pkg(1) from keeping a cache of successfully installed pkgs as by telling it to flush the content cache on success. First check what the current property is: # pkg property. PROPERTY VALUEbe- policy defaultca- path /etc/openssl/certscheck- certificate- revocation Falsedisplay- copyrights Trueflush- content- cache- on- success False < —– HEREmirror- discovery Falsepreferred- authority solarispublisher- search- order [‘solaris’]pursue- latest Truerequire- optional Falsesend- uuid Truesignature- policy verifysignature- required- names trust- anchor- directory etc/certs/CAuse- system- repo False#Change this property to true: # pkg set- property flush- content- cache- on- success true. The download cache will only be cleared the next time you install a pkg or perform an update. You can manually empty this directory in the mean time. How to change the current publisher? You can use the GUI (easy and intuitive) or the CLI: # pkg set- publisher - G http: //< old_publisher> / - g http: //< new_publisher> / solaris.
How to remove a publisher via the CLI?# pkg unset- publisher < publisher_name> —How can I check which Support Repository Update (SRU) I have currently installed? You can use “pkg info entire” to get a clear and concise description of the SRU you currently have installed: $ pkg info entire Name: entire Summary: entire incorporation including Support Repository Update (Oracle Solaris 1. SRU 0. 4a). For more information see Document 1. Description: This package constrains system package versions to the same build. WARNING: Proper system update and correct package selection depend on the presence of this incorporation. Removing this package will result in an unsupported system. Category: Meta Packages/Incorporations State: Installed Publisher: solaris Version: 0. Build Release: 5. Branch: 0. 1. 75.
Packaging Date: March 2, 2. PM Size: 5. B FMRI: pkg: //solaris/entire@0. T1. 60. 10. 6Z$Or you can use “pkg list entire” for a short output that doesn’t explicitly state the SRU, where $ pkg list entire. NAME (PUBLISHER) VERSION IFOentire 0.
How do I install pkgs into an alternate root?# pkg - R /path/to/alt/root install < pkg> But do NOT do this with zones. It may work, but it is better to do install the pkg from within the zone itself: # zlogin < zone> pkg install < pkg> How do I configure proxy access to pkg.