BigAdmin System Administration Portal
XPerts

BigAdmin XPerts

XPert Transcript: Solaris 10 OS Installation
Sundar Yamunachari - Sun Microsystems, Inc.

XPerts Home
Last Updated June 2005
 
 
Page 2 (11-20 of 41 results) Pages:  Previous « | 1 - 2 - 3 - 4 | » Next
  1. After installing the Solaris 10 OS, how can I go back and install individual packages from the install media?
  2. When performing a jumpstart installation, how can I make it execute post-installation scripts?
  3. Does SUNWjass support the Solaris 10 OS?
  4. How can I disable services managed by SMF with a finish script?
  5. In setting up the sysidcfg for Solaris 10 OS hands-free jumpstart installation, how do I account for the question concerning using NFS version 4?
  6. You used to have to rebuild the kernel after changing some /etc/system parameters. Is this still true in the Solaris 10 OS, or are they dynamic?
  7. How many CDs do I need for configuring the JumpStart server?
  8. Can you give me some tips on how to activate/start Apache+Tomcat for the Solaris 10 OS on SPARC?
  9. What is the minimum or recommended Solaris Software group if I am planning to use the Solaris Zones feature for hosting J2EE applications and a database server?
  10. I want to upgrade from Solaris 9 to 10, but it's giving me errors, e.g. "uninstall live upgrade packages for solaris 10".

Q: After installing the Solaris 10 OS, how can I go back and install individual packages from the install media?

A: If you are installing from the DVD media, use the following steps:

  1. Insert the DVD media (SPARC or x86) depending on your system. The Solaris_10 SPARC DVD is mounted as /cdrom/sol_10_305_sparc, and the x86 DVD is mounted as /cdrom/sol_10_305_x86.

  2. Use pkgadd to install the required packages. For example, if you want to install SUNWusb and SUNWusbs, use the following command:
    # pkgadd -d /cdrom/sol_10_305_sparc/s0/Solaris_10/Product SUNWusb SUNWusbs
    

If you are using CD media, there are four CD-ROMs, and you need to identify where the packages you want to install are located.

  1. Insert the CD-ROM where the required packages are located. The Solaris 10 CD-ROMs are mounted as /cdrom/sol_10_305_<arch>_<cd_number> except for cdrom 1, which is mounted as /cdrom/sol_10_305_<arch>. For example, Solaris 10 SPARC cd1 is mounted as cdrom/sol_10_305_sparc, and Solaris 10 x86 cd 3 is mounted as /cdrom/sol_10_305_x86_3.

  2. Use pkgadd to install the required packages. To find out what packages are available in Solaris 10 SPARC cd 1, traverse to /cdrom/sol_10_305_sparc/Solaris_10/Product. If the required package(s) are there, you can use pkgadd to install the packages. For example, if you want to install SUNWusb and SUNWusbs, use the following command:
    # pkgadd -d /cdrom/sol_10_305_sparc/Solaris_10/Product SUNWusb SUNWusbs
    

Back to top


Q: When performing a jumpstart installation, how can I make it execute post-installation scripts? For example, how can I make it reboot after installation, run JASS, and reboot again?

A: The jumpstart installation method can be used to customize the Solaris 10 installation using begin and finish scripts.

The begin script runs before starting the jumpstart installation and can be used to back up some data or clean up the system.

The finish script can be used to customize the system after the installation is completed. For example the configuration file /etc/system can be modified to increase shared memory and semaphores to use Oracle.

The begin and finish scripts should be specified in the rules file, and the check script should be executed to create the rules.ok file. The following is an example rules file entry with begin and finish script.

hostname my-host my_begin.sh my_profile my_finish

where my_begin and my_finish are the begin and finish script for the installation to be used for the host my-host. my_profile is the jumpstart profile used for the installation. A few examples of finish scripts are available in the media under the Solaris_10/Misc/jumpstart_sample directory. For more information see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.

If you want to do multiple reboots using jumpstart installation, there is no direct method of doing it as a part of a finish script. But you can set up a Service Management Facility (SMF) service from the jumpstart finish script to enable JASS to be run after completing the Solaris installation and reboot.

Editor's note: The JumpStart Architecture and Security Scripts (JASS) toolkit is now known as the Solaris Security Toolkit.

Back to top


Q: Does SUNWjass support the Solaris 10 OS?

A: Currently the Solaris 10 OS does not support the JumpStart Architecture and Security Scripts (JASS) toolkit. (Note: This is now called the Solaris Security Toolkit.) Solaris 10 support is targeted for release 4.2 of the Toolkit. Check the Solaris Security Toolkit page to find out when release 4.2 will be available.

Back to top


Q: How can I disable services managed by SMF with a finish script?

A: During the time of the installation, the SMF repository on the system being installed is not completely populated. After installation during the first reboot, the system imports all the installed manifests that aren't already in the seed repository. So manipulating the repository (with enable/disable) is not recommended.

However, the finish script can replace the generic.xml file with a custom XML file with the required services turned on/off. See the /var/svc/profile/generic.xml file. The /var/svc/profile/generic.xml profile is delivered as a symbolic link to a default open or closed profile. You can just repoint the link at your custom profile using the finish script.

Back to top


Q: In setting up the sysidcfg for Solaris 10 OS hands-free jumpstart installation, how do I account for the question concerning using NFS version 4 where you either accept the default or enter the NIS domain name currently being used?

A: A sample script, set_nfs4_domain, is provided in the Solaris 10 distribution media and is located in the ${CDrom_mnt_pt}/Solaris_10/Misc/jumpstart_sample directory. A copy of this script should be modified to set the NFS4_DOMAIN variable to site-specific needs and be called from within JumpStart's finish script. The target system's NFSv4 domain is therefore preconfigured as part of the JumpStart finish phase, and thus suppresses any first boot prompts.

Follow these steps to perform unattended installations:

  1. Create a copy of the set_nfs4_domain script in the same directory as your JumpStart's finish.sh scripts.
  2. Edit the script and set the NFS4_DOMAIN variable to your specific needs.
  3. Edit your finish.sh script and append a call to set_nfs4_domain.
  4. Perform the JumpStart installations as usual.

Back to top


Q: I just installed the Solaris 10 OS on a new Sun Fire v240 server. Before I can install my database, I must modify/create some /etc/system parameters, such as:
set semsys:seminfo_semmap=64
set shmsys:shminfo_shmmin=100
(more like these)
I haven't done this in over 10 years. You used to have to rebuild the kernel after changing these types of parameters. Is this still true in the Solaris 10 OS, or are they dynamic?


A: The Solaris 10 OS limits like semaphores and shared memory can be changed by changing the value in /etc/system. You have to reboot the system to make the new limits effective. Only in SunOS 4.x, you need to rebuild; this is no longer needed for Solaris 2.x, which includes the Solaris 10 OS.

Back to top


Q: How many CDs do I need for configuring the JumpStart server? There are four installation CDs, but when I saw documentation on the web, it still says 1 of 2 and 2 of 2.

A: The Solaris 10 OS consists of 4 CD-ROMs, and they are named Solaris 10 Software 1 through Solaris 10 Software 4. In the Solaris 9 OS, the CD-ROMs are called 1 of 2 and 2 of 2.

Back to top


Q: I have just been installing the Solaris 10 OS on SPARC. It comes with preconfigured Apache+Tomcat. However, I cannot find any documentation about how it is configured and how I can activate/start Apache+Tomcat. Can you provide me a link or give me some tips?

A: The Apache software is installed in /usr/apache. The configuration files are under /etc/apache. The file README.solaris under /etc/apache will give you a head start. The main configuration file to be modified to run Apache is /etc/apache/httpd.conf. There is an example httpd.conf called httpd.conf-example provided under /etc/apache as a starting point. The configuration file tomcat.conf should be modified to use tomcat. The Apache documentation is under /usr/apache/htdocs/manual.

The Apache web server can be started by typing /usr/apache/bin/httpd or using the script /usr/apache/bin/apachectl. You can start or stop Apache web server using apachectl start and apachectl stop.

Back to top


Q: What is the minimum or recommended Solaris Software group if I am planning to use the Solaris Zones feature for hosting J2EE applications and a database server? Can I use software partitions created by Solaris Volume Manager for a non-global zone's file system?

A: The minimum software group required for Solaris Zones is End User Solaris Software Group (SUNWCuser). If you are planning to use database server and J2EE applications, it is better to use Entire Solaris Software Group (SUNWCall) or Entire Solaris Software Group Plus OEM Support (SUNWCXall).

Currently you cannot use Solaris Volume Manager meta devices for non-global Zones in the Solaris 10 OS.

Back to top


Q: I have installed the Solaris 9 OS and now want to upgrade it to Solaris 10 version. It's giving me the errors "Cannot upgrade to Solaris 10", "uninstall live upgrade packages for solaris 10". What am I missing here?

A: To use Live upgrade, you need to install the Solaris Live Upgrade packages on your current OS. The release of the Solaris Live Upgrade packages must match the release of the OS you are upgrading to. For example, if your current OS is the Solaris 8 release and you want to upgrade to the Solaris 10 release, you need to install the Solaris Live Upgrade packages from the Solaris 10 release.

Also, your system should have the patches to run Java 2 runtime environment to use Solaris 10 Live upgrade Installer.

For more information, please check the Solaris 10 documentation titled Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Back to top


BigAdmin