|
Archived Sun SysAdmin Articles
|
18 May 2012
|
Updating Your Oracle Solaris 11 System from the Oracle Support Repository [26320]
Some Tips for the Process with a Focus on the Image Packaging System
The post "Tips for Updating Your Oracle Solaris 11 System from the Oracle Support Repository" by Peter Dennis explores Support Repository Updates (SRUs) and how best to maintain systems with the latest updates or a selected set of updates from Oracle. Dennis examines some of the more advanced uses of the Image Packaging System (IPS) and assumes a basic knowledge of the update process using the pkg(1) command-line utility.
(Get More Information . .)
|
|
30 Apr 2012
|
Creating and Configuring Virtual Ports Controlled by a Virtual Machine [26085]
A Feature of Oracle Solaris 11
Alexandre Chartre explains how to configure a SAN environment (such as zoning, LUN masking or QoS) using virtual (NPIV) instead of physical ports. This provides flexibility as you can then easily transfer a configuration from one physical HBA to another by just configuring a new HBA with the appropriate N_Port ID. In a virtual environment, it can be convenient to associate a virtual port with a virtual machine, and to have all LUNs visible through this virtual port assigned to the virtual machine. You can then manage the association of LUNs and virtual machines through the configuration of your SAN.
(Get More Information . .)
|
|
09 Apr 2012
|
Finding Your Way Around Among the IPS Package Groups [25950]
Details on Installing and Creating DIY Group Packages
A post on the Insights from Release Engineering explains the four current IPS system groups in the xml manifest files and used for different types of installations by various Solaris installers. These include the following:
- Oracle Solaris Desktop
- Oracle Solaris Large Server
- Oracle Solaris Small Server
- Oracle Solaris Automated Installer Client
The post adds that there are also several "feature" groups such as AMP and GNU Developer Tools that are not used directly by any installers. The post also provides details on retrieving group package information, installing a group, and creating a group of one's own.
(Get More Information . .)
|
|
04 Apr 2012
|
Configuring an NTP Client in Solaris 11 [25867]
Moellenkamp's How-to Shows How Easily It's Done
Joerg Moellenkamp shows how to configure an NTP client on a plain standard Solaris 11 in a recent blog post. His method includes a certain redundancy as he uses four time servers, thereby ensuring that at least one will be operational at all times. He also uses ntpdate to force a time synchronization rather than the ntp daemon, which does not provide a time synch. At the outset Moellenkamp characterizes the procedure as a simple one: The brevity and relatively uncomplicated nature of his procedure suggest that he is correct.
(Get More Information . .)
|
|
26 Mar 2012
|
How to Set up a Local Solaris 11 Auto Install Server [25754]
Downloading an OS Image is Step Number One
Stefan Hinker posts about setting up a local Solaris 11 Automated Installer, as does Unixman elsewhere in this issue. Hinker's post begins with downloading an OS image from the Oracle Solaris 11 page, a step that has a number of uses other than the installation of Automated Installer. Hinker suggests making a snapshot of the image and adding it as a file-based publisher and activating the repository service. Next, Hinker illustrates the use of the Support Repository Updates Index. The groundwork done, he then proceeds to installing Automated Install itself. Hinker's blog intersperses long stretches of code with explanatory comments.
(Get More Information . .)
|
|
12 Mar 2012
|
Solaris Fingerprint Database Returns to Solaris [25625]
Image Packaging System Improvements Deliver Added Benefits
Users who lamented the demise of the Solaris Fingerprint Database along with sunsolve can now be encouraged by the inclusion of an improved version in Solaris 11, Stefan Hinker posts. There are now both automatic and manual means in the IPS for verifying the integrity of installed software. Hinker outlines the procedure for using the command "pkg verify", which enables users to employ the IPS to verify each and every installed package against the repository it was installed from. The capability of the IPS to fix individual packages is one of the most important improvements that Hinker identifies.
(Get More Information . .)
|
|
