Archive for the ‘Linux OS’ Category

How To Connect to a Remote Server in Linux, Solairs, Ubuntu

August 19th, 2015, posted in Solaris
Share

What Is SSH ??


One essential tool to master as a system administrator is SSH.
SSH, or Secure Shell, is a protocol used to securely log onto remote systems. It is the most common way to access remote Linux and Unix-like servers, such as VPS instances.
In this guide, we will discuss how to use SSH to connect to a remote system.


Basic Syntax


The tool on Linux for connecting to a remote system using SSH is called, unsurprisingly, ssh.
The most basic form of the command is:

ssh remote_host

The remote_host in this example is the IP address or domain name that you are trying to connect to.
This command assumes that your username on the remote system is the same as your username on your local system.
If your username is different on the remote system, you can specify it by using this syntax:

ssh remote_username@remote_host

Once you have connected to the server, you will probably be asked to verify your identity by providing a password.
Later, we will cover how to generate keys to use instead of passwords.
To exit back into your local session, simply type:

exit
Share

CRON Troubleshooting Guide

July 15th, 2015, posted in Solaris
Share

Cron facility can be used to schedule regularly occurring commands or scripts. Users can submit cron jobs by adding an entry to their respective crontabs located in /var/spool/cron/crontabs directory and stored as their login name. Below are few of the troubleshooting tips and best practices which can be helpful in many cases.

 

Important cron files :

The important files related cron are :

/etc/cron.d/cron.allow
— File containing usernames that have permission to submit cronjobs
/etc/cron.d/cron.deny
— File containing usernames that don’t have permission to submit cronjobs
/var/cron/log
— Cron Log file
/var/spool/cron/crontabs
— Directory containing individual crontab files of all users.


How to edit a crontab :

The best way to edit a crontab is using the command crontab -e. Another way of doing it is :
1. su to the user whose cron you want to change
2. crontab -l > file [ copy the crontab to a file ].
3. vi file [ make changes to the file as per your need ]
4. crontab file [ this makes the “file” as new crontab ]
There is no need to restart the cron daemon after this.

Note : If by mistake you simple run only crontab command, don’t try to come out by typing CTRL+D as it will remove all the entries in the crontab file. Use CTRL+C to come out of the crontab command.
Check whether cron daemon is running
Check if the cron daemon is running in the system [prior to solaris 10] :

# ps -ef |grep cron
 To start or stop cron daemon use:
# /etc/init.d/cron [stop|start]
 In case of Solaris 10, check the for the cron service status :
# svcs -p svc:/system/cron
 To make sure cron jobs are running properly, add below entry in the crontab.
* * * * * date > /dev/console
 This will print the date every minute to the console. You can also use pts terminal you are working on, if you don’t have the access to console.

Controlling access to crontab :
– The file /etc/cron.d/cron.allow can be used to allow users to submit cron jobs.
– If the cron.allow file is not present cron checks /etc/cron.d/cron.deny file to see which users are not allowed to submit cron jobs.
– If a user is present in both the files, the cron daemon checks the cron.allow file first and ignores the cron.deny file.
– If both files are missing only root can run the jobs.

Check permission and path to the script :
Seems silly, but I have seen many people doing this mistake of not giving executable permissions to the script they want to run from cron.

# chmod u+x /path/to/script

Also make sure that the cron entry has absolute path to the script and also to the shell used by the script:

* 5 * * * /bin/bash /path/to/script.sh

Check the cron logs :
Many a time the cron log file /var/cron/log clearly points out the issue in the cronjob. Check for the period in which the scripts should have run in the cron log. this would most probably point out the error in the cronjob.

Be careful when emptying a crontab :
If you delete all the cron jobs using crontab -e, the command crontab -l will still show all the cron jobs. this is because crontab -e does not know what to do with an empty crontab file. So it does not update any changes. The proper way to delete all the jobs from the crontab is :
# crontab -r

Check cron permissions
Sometimes you must have encountered an error “error in message queue open”. One of the reasons of this is a wrong permission to cron and crontab. The proper permissions of cron and crontab are :

# ls -l /usr/sbin/cron
-r-xr-xr-x 1 root sys 57420 Jan 22 2005 /usr/sbin/cron
 # ls -l /usr/bin/crontab
 -r-sr-xr-x 1 root bin 20336 Jan 22 2005 /usr/bin/crontab
 Note the setuid permissions on crontab file.

‘crontab -e’ command returns a number and a ‘?’
Sometimes when you try to edit a crontab file using crontab -e command, it prints a number and a ‘?’. This is because by default the editor used by crontab -e command is the default solaris editor ‘ed’ and not vi editor. When ed starts up it prints the number of characters in the crontab file and does not have a prompt.

To avoid this, simple com out of the ed editor by typing q. Now set the EDITOR environmental variable to vi and run crontab -e again :

# EDITOR=vi
# export EDITOR
Password expired for a user :
Many a times cron jobs fail because the password has expired for the user owning the job. In that case you would see below error in the cron log file /var/cron/log :

Authentication token is no longer valid; new one required
CRON (oracle) ERROR: failed to open PAM security session: Success
CRON (oracle) ERROR: cannot set security context
The solution to this problem is to extend the password for the user :

# passwd -x 10 oracle
Redirection / special symbols and their meanings
It is good to know some of the redirection and special symbols being used when adding an entry to the crontab. Any mistake in using them may again lead to a cron job failure. An example of using these symbols in a cron job entry is :

0 5 * * * /bin/bash -l -c ‘export RAILS_ENV=my_env; cd /my_folder; ./script/script.rb 2>&1 > ./log/my_log.log’
Redirection file descriptors
There are 3 standard file descriptors :

1. stdin 0 – Standard input to the program.
2. stdout 1 – Standard output from the program.
3. stderr 2 – Standard error output from the program.
Normally stdin is from the keyboard and stdout and stderr goes to the terminal. But we can redirect it to a file. One of the most commonly used (and confusing) redirection is “2>&1″. It means take the standard error output from the command and send it to the same place where standard output is going.

Other than the most redirection symbols, there are many other symbols used while entering a cron job entry in the crontab :

;
Used to separate two commands on one line
&
Run the command in the background
&&
Run the following command only if the previous command completes successfully, (i.e., grep string file && cat file)
||
“Run the following command only if the previous command did not complete successfully, (i.e., grep string file || echo “”String not found””)”
( )
The command within the parentheses is executed in a subshell

= single forward quote – Don’t assign any special meaning to any character within these quotations

Take the following character literally. Also used to “”escape”” a new-line character so that a user can continue a command on more than one line
” “
Allow variable and command substitution with these quotations
`command`
` = single back quote – Take the output of this command and substitute it as an argument on the command line
#
Everything following # until is a comment

Share

How to create and extract zip, tar, tar.gz and tar.bz2 files in Linux

May 12th, 2015, posted in Solaris
Share

Data compression has been extremely useful to us over the years. Whether its a zip file containing images to be sent in a mail How to create and extract zip tar tar.gz and tar.bz2 files in Linux, Linux,How to create and extract zip,How to create and extract tar,How to create and extract ,create and extract zip,linux,solaris 10,solaris,or a compressed data backup stored on a server, we use data compression to save valuable hard drive space or to make the downloading of files easier. There are compression formats out there which allow us to sometimes compress our data by 60% or more. I’ll run you through using some of these formats to compress and decompress files and directories on a Linux machine. We’ll cover the basic usage of zip, tar, tar.gz and the tar.bz2 formats. These are some of the most popular formats for compression used on Linux machines.

Before we delve into the usage of the formats I’d like to share some of my experience using the various formats of archiving. I’m talking about only a few data compression formats here, and there are many more out there. I’ve realized that I need two or three formats of compression that I’m comfortable using, and stick to them. The zip format is definitely one of them. This is because zip has become the de-facto standard choice for data compression, and it works on Windows as well. I use the zip format for files that I might need to share with Windows users. I like to use the tar.gz format for files that I would only use on my Mac and Linux machines.

 

ZIP

Zip is probably the most commonly used archiving format out there today. Its biggest advantage is the fact that it is available on all operating system platforms such as Linux, Windows, and Mac OS, and generally supported out of the box. The downside of the zip format is that it does not offer the best level of compression. Tar.gz and tar.bz2 are far superior in that respect. Let’s move on to usage now.
To compress a directory with zip do the following:

# zip -r archive_name.zip directory_to_compress

Here’s how you extract a zip archive:

# unzip archive_name.zip

 

TAR

Tar is a very commonly used archiving format on Linux systems. The advantage with tar is that it consumes very little time and CPU to compress files, but the compression isn’t very much either. Tar is probably the Linux/UNIX version of zip – quick and dirty. Here’s how you compress a directory:

# tar -cvf archive_name.tar directory_to_compress

And to extract the archive:

# tar -xvf archive_name.tar.gz

This will extract the files in the archive_name.tar archive in the current directory. Like with the tar format you can optionally extract the files to a different directory:

# tar -xvf archive_name.tar -C /tmp/extract_here/

 

TAR.GZ

This format is my weapon of choice for most compression. It gives very good compression while not utilizing too much of the CPU while it is compressing the data. To compress a directory use the following syntax:

# tar -zcvf archive_name.tar.gz directory_to_compress

To decompress an archive use the following syntax:

# tar -zxvf archive_name.tar.gz

This will extract the files in the archive_name.tar.gz archive in the current directory. Like with the tar format you can optionally extract the files to a different directory:

# tar -zxvf archive_name.tar.gz -C /tmp/extract_here/

 

TAR.BZ2

This format has the best level of compression among all of the formats I’ve mentioned here. But this comes at a cost – in time and in CPU. Here’s how you compress a directory using tar.bz2:

# tar -jcvf archive_name.tar.bz2 directory_to_compress

This will extract the files in the archive_name.tar.bz2 archive in the current directory. To extract the files to a different directory use:

# tar -jxvf archive_name.tar.bz2 -C /tmp/extract_here/

Data compression is very handy particularly for backups. So if you have a shell script that takes a backup of your files on a regular basis you should think about using one of the compression formats you learned about here to shrink your backup size.

Over time you will realize that there is a trade-off between the level of compression and the the time and CPU taken to compress. You will learn to judge where you need a quick but less effective compression, and when you need the compression to be of a high level and you can afford to wait a little while longer.

Share

Changing Root’s Password

May 3rd, 2015, posted in Solaris
Share

When changing root’s password, you must always run chkey -p immediately after changing the password with the passwd command. Failure to run chkey -p after changing root’s password will result in root being unable to properly log in.

To change a root password, follow these steps:

  1. Log in as root.
  2. Change root’s password using passwd.Do not use nispasswd.
  3. Run chkey -p.You must use the -p option.
Share

Installing Sun Solaris 10

March 2nd, 2015, posted in Solaris
Share

Installing Sun Solaris 10 by Jeff Hunter Sr. Database Administrator,Installing Sun Solaris 10,Jeff Hunter Sr. Database Administrator,Jeff Hunter,Sr. Database Administrator,Database Administrator,SunSolaris,SunSolaris 10

Installing Sun Solaris 10

by Jeff Hunter, Sr. Database Administrator


Contents

 

 

 

 



Overview

This article documents installing the 6/06 (June 2006) release of Solaris 10
from CD-ROM. For the purpose of this example, I will be installing Solaris 10
on a Sun Blade 150 with the following configuration:

  • Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard, OpenBoot 4.6
  • 1,792 MB RAM Memory
  • Two – 40 GB IDE Western Digital Hard Drives – (/dev/dsk/c0t0d0 and /dev/dsk/c0t2d0)
  • Built-in Ethernet – (eri0)
  • CDROM – (/dev/dsk/c0t1d0)

Installing Solaris 10 will require 5 CDs found in the
Solaris media kit labeled “Solaris 10 Software
or downloaded from
http://www.sun.com/software/solaris/ – (Solaris 10 6/06).
Before starting the
installation process, ensure that you have noted the following items:

  • Determine the host name of the system you are installing
  • Determine the language and locales you intend to use on the system
  • If you intend to include the system in a network, gather the following information:
    • Host IP address
    • Subnet mask
    • Type of name service (DNS, NIS, or NIS+, for example)
    • Domain name
    • Host name of server
    • Host IP address of the name server


Using Serial / Console Connection

For a complete discussion of connecting to a Sun
serial console from Linux, see article
Using Serial Consoles – (Sun Sparcs)“.

For this particular installation, I will NOT be using a VGA monitor connected to the
built-in frame-buffer (video card). The installation will be done using the serial
port of the Sun Blade as a console. A serial cable (null modem) will be connected from
the serial port of a Linux machine to the serial port of the Sun Blade. Keep in mind
that you will not be able to make use of the serial console of the Sun Blade if it
was booted with the keyboard/mouse plugged in. In order to make use of the serial console,
you will need to disconnect the keyboard/mouse and reboot the Sun server. On the Sun Blade
100/150, if the keyboard/mouse are plugged in during the boot phase, all console output will
be redirected to the VGA console.

From the Linux machine, you can use a program called minicom. Start it up with the command
minicom“. Press “Ctrl-A Z” to get to the main menu.
Press “o” to configure minicom. Go to “Serial port setup” and make
sure that you are set to the correct “Serial Device” and that the speed on line
E matches the speed of the serial console you are connecting to. (In most
cases with Sun, this is 9600.) Here are the settings I made when using
Serial A / COM1 port on the Linux machine:

+-----------------------------------------------------------------------+
| A -    Serial Device      : /dev/ttyS0                                |
| B - Lockfile Location     : /var/lock                                 |
| C -   Callin Program      :                                           |
| D -  Callout Program      :                                           |
| E -    Bps/Par/Bits       : 9600 8N1                                  |
| F - Hardware Flow Control : Yes                                       |
| G - Software Flow Control : No                                        |
|                                                                       |
|    Change which setting?                                              |
+-----------------------------------------------------------------------+

After making all necessary changes, hit the ESC key to go back to
the “configurations” menu. Now go to “Modem and dialing“.
Change the “Init string” to “~^M~“. Save the settings
(as dflt), and then restart Minicom. You should now see a console login prompt.

[root@bertha1 root]# minicom

Welcome to minicom 2.00.0

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 17 2004, 04:52:10.

Press CTRL-A Z for help on special keys

alex console login: root
Password:
Last login: Tue Nov  4 18:55:41 on console
Nov  7 12:17:24 alex login: ROOT LOGIN /dev/console
Sun Microsystems Inc.   SunOS 5.8       Generic Patch   October 2001
#
# init 0
INIT: New run level: 0
The system is coming down.  Please wait.
System services are now being stopped.
Print services stopped.
Nov  7 12:17:38 alex syslogd: going down on signal 15
The system is down.
syncing file systems... done
Program terminated
ok


Starting the Installation

The installation process starts at the ok prompt. The previous
section of this document provides the steps required to not only gain
access to the console port of the Sun SPARC server, but also how to get the
server to an ok prompt. If when logging on, the machine is already
booted into the O/S, (you have a console login like the following: “alex console login:“),
you will need to bring the machine to its EEPROM (ok prompt) by initiating
init 0 like in the
Using Serial / Console Connection
section above.

The first step in installing Solaris 10 is to boot the machine from
Disk 1 of the Solaris 10 Software CDs. You will need to
get the machine to the ok prompt. You can do this by shutting the system
down using init 0. Once at the ok prompt,
type in boot cdrom. (Or in some cases, you can use
reboot cdrom). From here, the installation program prompts
you for system configuration information that is needed to complete
the installation.

If you were performing a
network installation, you would type:
ok boot net

In almost all cases, you will be installing the Solaris 10 software
on a new system where it will not be necessary to preserve any data
already on the hard drive. Using this assumption, I will
partition the first single 40 GB IDE hard drive (/dev/dsk/c0t0d0)
as the system disk.


Answering the Screen Prompts

Let’s start the installation process! Put the Solaris 10 Software
(Disk 1 of 5) in the CDROM tray and boot to it:

Solaris Installation Boot Screen
ok boot cdrom
Resetting ...


Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.6, 1792 MB memory installed, Serial #52928138.
Ethernet address 0:3:ba:27:9e:8a, Host ID: 83279e8a.


Rebooting with command: boot cdrom
Boot device: /pci@1f,0/ide@d/cdrom@1,0:f  File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface eri0...
SUNW,eri0 : 100 Mbps full duplex link up
Configured interface eri0
Beginning system identification...
Searching for configuration file(s)...
Search complete.
Discovering additional network configuration...

The boot process may take several minutes to complete, but once done,
you will start answering a series of prompts.

The following section will walk you through many of the screen prompts
from the installation.

The first two prompts are from the command line interface (CLI) and
are used to specify the language and terminal. Use English for the Language.
As for a terminal setting, I commonly telnet to a Linux server
(that is connected from the serial port of the Linux server to the serial
port of the Sun machine). From the Linux server, I use “minicom” to
connect from the Linux server to the Sun server. The best terminal
for this type of installation is “DEC VT100“:

  Language                             : English
  What type of terminal are you using? : 3) DEC VT100
You should be able to use a terminal type of “DEC VT100”
or “X Terminal Emulator (xterms)”.
Depending on the terminal being used for installation
while using the command line interface, it may be required
to precede any of the function key responses
(i.e. F2_Continue) with the ESC key (i.e. ESC – F2_Continue).
For the purpose of this installation, I am using minicom 2.0
and configured the installation to use a DEC VT100 terminal.
Given this configuration I did not have to precede any
of the function key responses with the ESC key.

Many of the screens to follow will ask you about networking information.
When asked if the system will be connected to a network, answer Yes.

Many of the screens should be easy to complete except for the
Names Services” section. In almost all cases, you will want to use
DNS naming services, but if your machine is not currently configured within DNS,
this section will fail and no information entered about Names Services will be stored
and configured.

If this is the case, you will need to select None under the Names Services
section. The network configuration will then need to be completed after the installation process
by updating certain network files on the local hard drive.
This will be documented in the “Post Installation Procedures” of this document.


Screen 1 : The Solaris Installation Program

This is the Solaris Installation Welcome screen.

Hit F2 to continue

Screen 2 : Identify This System

This screen informs you about how you will need to identify the computer as it applies to network connectivity.

Hit F2 to continue

Screen 3 : Network Connectivity

Networked
---------
[X] Yes
[ ] No

Hit F2 to continue

Screen 4 : DHCP

Use DHCP
--------
[ ] Yes
[X] No

Hit F2 to continue

Screen 5 : Host Name for eri0

Enter the host name which will identify this system on the network.
For the purpose of this example, I will use the host name “alex“.

Host name for eri0: alex

Hit F2 to continue

Screen 6 : IP Address for eri0

Enter the Internet Protocol (IP) address for this network interface.

IP address for eri0: 192.168.1.102

Hit F2 to continue

Screen 7 : Subnet for eri0

On this screen you must specify whether this system is part of a
subnet. For the purpose of this example, this interface will be
part of a subnet.

System part of a subnet
-----------------------
[X] Yes
[ ] No

Hit F2 to continue

Screen 8 : Netmask for eri0

Netmask for eri0: 255.255.255.0

Hit F2 to continue

Screen 9 : IPv6 for eri0

In this example, I will not be enabling IPv6.

Enable IPv6 for eri0
--------------------
[ ] Yes
[X] No

Hit F2 to continue

Screen 10 : Set the Default Route for eri0

I will manually specify the IP address of my router.

Default Route for eri0
----------------------
[ ] Detect one upon reboot
[X] Specify one
[ ] None

Hit F2 to continue

Screen 11 : Default Route IP Address for eri0

Router IP Address for eri0: 192.168.1.1

Hit F2 to continue

Screen 12 : Confirm Information for eri0

This is a confirmation screen. Verify all data is correct.

              Host name: alex
             IP address: 192.168.1.102
System part of a subnet: Yes
                Netmask: 255.255.255.0
            Enable IPv6: No
          Default Route: Specify one
      Router IP Address: 192.168.1.1

Hit F2 to continue

Screen 13 : Configure Security Policy

Configure Kerberos Security
---------------------------
[ ] Yes
[X] No

Hit F2 to continue

Screen 14 : Confirm Information

This is a confirmation screen. Verify all data is correct.

Configure Kerberos Security: No

Hit F2 to continue

Screen 15 : Name Service

Name service
------------
[ ] NIS+
[ ] NIS
[X] DNS
[ ] LDAP
[ ] None

Hit F2 to continue

Screen 16 : Domain Name

Host name: idevelopment.info

Hit F2 to continue

Screen 17 : DNS Server Addresses

Server's IP address: 63.67.120.23
Server's IP address: 63.67.120.14
Server's IP address:

Hit F2 to continue

Screen 18 : DNS Search List

Search domain:
Search domain:
Search domain: 
Search domain:
Search domain:
Search domain:

Hit F2 to continue

Screen 19 : Confirm Information

This is a confirmation screen. Verify all data is correct.

      Name service: DNS
       Domain name: idevelopment.info
Server address(es): 63.67.120.23
                    63.67.120.14

Hit F2 to continue

Screen 20 : Time Zone

Continents and Oceans
---------------------
[ ] Africa
[X] Americas
[ ] Antarctica
[ ] Arctic Ocean
[ ] Asia
[ ] Atlantic Ocean
[ ] Australia
[ ] Europe
[ ] Indian Ocean
[ ] Pacific Ocean
[ ] other - offset from GMT
[ ] other - specify time zone file

Hit F2 to continue

Screen 21 : Country or Region

Countries and Regions
---------------------
[X] United States
[ ] Anguilla
[ ] Antigua & Barbuda
[ ] Argentina
[ ] Aruba
[ ] Bahamas
[ ] Barbados
[ ] Belize
[ ] Bolivia
[ ] Brazil
[ ] Canada
[ ] Cayman Islands
[ ] Chile
[ ] Colombia
[ ] Costa Rica
[ ] Cuba
[ ] Dominica
[ ] Dominican Republic
[ ] Ecuador
[ ] El Salvador
[ ] French Guiana
[ ] Greenland
[ ] Grenada
[ ] Guadeloupe
[ ] Guatemala
[ ] Guyana
[ ] Haiti
[ ] Honduras
[ ] Jamaica
[ ] Martinique
[ ] Mexico
[ ] Montserrat
[ ] Netherlands Antilles
[ ] Nicaragua
[ ] Panama
[ ] Paraguay
[ ] Peru
[ ] Puerto Rico
[ ] St Kitts & Nevis
[ ] St Lucia
[ ] St Pierre & Miquelon
[ ] St Vincent
[ ] Suriname
[ ] Trinidad & Tobago
[ ] Turks & Caicos Is
[ ] Uruguay
[ ] Venezuela
[ ] Virgin Islands (UK)
[ ] Virgin Islands (US)

Hit F2 to continue

Screen 22 : Time Zone

Time zones
----------
[X] Eastern Time
[ ] Eastern Time - Michigan - most locations
[ ] Eastern Time - Kentucky - Louisville area
[ ] Eastern Time - Kentucky - Wayne County
[ ] Eastern Standard Time - Indiana - most locations
[ ] Eastern Standard Time - Indiana - Crawford County
[ ] Eastern Standard Time - Indiana - Starke County
[ ] Eastern Standard Time - Indiana - Switzerland County
[ ] Central Time
[ ] Central Time - Michigan - Wisconsin border
[ ] Central Time - North Dakota - Oliver County
[ ] Mountain Time
[ ] Mountain Time - south Idaho & east Oregon
[ ] Mountain Time - Navajo
[ ] Mountain Standard Time - Arizona
[ ] Pacific Time
[ ] Alaska Time
[ ] Alaska Time - Alaska panhandle
[ ] Alaska Time - Alaska panhandle neck
[ ] Alaska Time - west Alaska
[ ] Aleutian Islands
[ ] Hawaii

Hit F2 to continue

Screen 23 : Date and Time

Date and time: YYYY-MM-DD HH:MM

  Year   (4 digits) : <enter year>
  Month  (1-12)     : <enter month>
  Day    (1-31)     : <enter day>
  Hour   (0-23)     : <enter hour>
  Minute (0-59)     : <enter minute>

Hit F2 to continue

Screen 24 : Confirm Information

This is a confirmation screen. Verify all data is correct.

    Time zone: Eastern Time
               (US/Eastern)
Date and time: 2006-11-26 15:11:00

Hit F2 to continue

Screen 25 : Solaris Interactive Installation

There are two ways to install your Solaris software: “Standard” or “Flash“.
Choose the “Standard” method (F2_Standard).

Hit F2 to continue

Screen 26 : Eject a CD/DVD Automatically?

During the installation of Solaris software, you may be using one or more
CDs/DVDs. You can choose to have the system eject each CD/DVD automatically
after it is installed or you can choose to manually eject each CD/DVD.

[X] Automatically eject CD/DVD
[ ] Manually eject CD/DVD

Hit F2 to continue

Screen 27 : Reboot After Installation?

After Solaris software is installed, the system must be rebooted. You can
choose to have the system automatically reboot, or you can choose to
manually reboot the system if you want to run scripts or do other
customizations before the reboot. You can manually reboot a system by using
the reboot(1M) command.

[X] Auto Reboot
[ ] Manual Reboot

Hit F2 to continue

Screen 28 : Solaris Interactive Installation

This screen recognizes if a previous version of Solaris is installed and whether you would
like to upgrade or not. Always select the install option (F4_Initial).

Hit F4 to continue

Screen 29 : Initializing

The system is being initialized.

Loading install media, please wait…

Screen 30 : License

Read through the software license agreement.

Hit F2 to accept the license and continue

Screen 31 : Select Geographic Regions

Select the geographic regions for which support should be installed.
--------------------------------------------------------------------
> [ ] Australasia
> [ ] Asia
> [ ] Eastern Europe
> [ ] Northern Europe
> [ ] Northern Africa
> [ ] Middle East
> [ ] Southern Europe
> [ ] South America
> [ ] Central America
> [ ] Central Europe
V [/] North America
    [ ]     Canada-English (ISO8859-1)
    [ ]     Canada-French (ISO8859-1)
    [ ]     French
    [ ]     Mexico (ISO8859-1)
    [ ]     Spanish
    [X]     U.S.A. (UTF-8)
    [X]     U.S.A. (en_US.ISO8859-1)
> [ ] Western Europe

Hit F2 to continue

Screen 32 : Select System Locale

Select the initial locale to be used after the system has been installed.
-------------------------------------------------------------------------
[X]     POSIX C ( C )
    North America
[ ]     U.S.A. (UTF-8) ( en_US.UTF-8 )
[ ]     U.S.A. (en_US.ISO8859-1) ( en_US.ISO8859-1 )
[ ]     U.S.A. (en_US.ISO8859-15) ( en_US.ISO8859-15 )

Hit F2 to continue

Screen 33 : Select Products

Select the products you would like to install.
----------------------------------------------
V [X] Solaris 10 Extra Value Software.................   87.26 MB
  [X]     Sun Validation Test Suite 6.2...................   69.92 MB
  [X]     Sun Install Check 2.0.2.........................   17.34 MB
> [ ] Java Enterprise System..........................    0.00 MB

Hit F2 to continue

Screen 34 : Additional Products

To scan for additional products, select the location you wish to scan.

Web Start Ready product scan location:
--------------------------------------
[X]  None
[ ]  CD/DVD
[ ]  Network File System

Hit F2 to continue

Screen 35 : Select Software

Select the Solaris software to install on the system.
-----------------------------------------------------
[ ]  Entire Distribution plus OEM support ....... 5641.00 MB
[X]  Entire Distribution ........................ 5593.00 MB
[ ]  Developer System Support ................... 5468.00 MB
[ ]  End User System Support .................... 4452.00 MB
[ ]  Core System Support ........................  958.00 MB
[ ]  Reduced Networking Core System Support .....  916.00 MB

Hit F2 to continue

Screen 36 : Select Disks

You must select the disks for installing Solaris software. If there
are several disks available, I always install the Solaris software
on the boot disk c0t0d0. NOTE: ** denotes current boot disk

----------------------------------------------------------

Disk Device                     Available Space
===============================================
[X] ** c0t0d0             38162 MB  (F4 to edit)
[ ]    c0t2d0             38162 MB

      Total Selected:  38162 MB
   Suggested Minimum:   4319 MB

 


I generally select F4 to edit the c0t0d0 disk to ensure that the
root directory is going to be located on this disk.

----------------------------------------------------------
On this screen you can select the disk for installing the 
root (/) file system of the Solaris software.

Original Boot Device : c0t0d0

          Disk
      ==============================
      [X] c0t0d0    (F4 to select boot device)

 


On this screen, I typically select F4 to select boot device
to ensure the root file system will be located on slice zero, c0t0d0s0.

----------------------------------------------------------
On this screen you can select the specific slice for the root (/) file
system. If you choose Any of the Above, the Solaris installation program
will choose a slice for you.

Original Boot Device : c0t0d0s0

          [X]  c0t0d0s0
          [ ]  c0t0d0s1
          [ ]  c0t0d0s2
          [ ]  c0t0d0s3
          [ ]  c0t0d0s4
          [ ]  c0t0d0s5
          [ ]  c0t0d0s6
          [ ]  c0t0d0s7
          [ ]  Any of the Above

Hit F2 to after selecting Disk Slice


Hit F2 to continue with your Boot Disk selection


Screen 37 : Reconfigure EEPROM?

Do you want to update the system’s hardware (EEPROM) to always boot from c0t0d0?

Hit F2 to Reconfigure EEPROM and Continue

Screen 38 : Preserve Data?

Do you want to preserve existing data? At least one of the disks you’ve selected for
installing Solaris software has file systems or unnamed slices that you may want to save.

Hit F2 to continue

Screen 39 : Automatically Layout File Systems?

Do you want to use auto-layout to automatically layout file systems?
Manually laying out file systems requires advanced system administration
skills.

I typically perform an “Auto” File System Layout (F2_Auto Layout).

Hit F2 to Perform Auto Layout.

Screen 40 : Automatically Layout File Systems

On this screen you must select all the file systems you want auto-layout to
create, or accept the default file systems shown.

File Systems for Auto-layout
========================================
[X]  /
[ ]  /opt
[ ]  /usr
[ ]  /usr/openwin
[ ]  /var
[X]  swap

Hit F2 to continue

Screen 41 : File System and Disk Layout

The summary below is your current file system and disk layout, based on the
information you’ve supplied.

NOTE: If you choose to customize, you should understand file systems, their
intended purpose on the disk, and how changing them may affect the operation
of the system.

File sys/Mnt point Disk/Slice                            Size
=============================================================
/                  c0t0d0s0                        5267    MB
swap               c0t0d0s1                        513     MB
overlap            c0t0d0s2                        38162   MB
/export/home       c0t0d0s7                        32381   MB

 


I generally select F4 (F4_Customize) to
edit the partitions for disk c0t0d0. If this is a workstation,
I make only three partitions:

  • / : I often get the sizes for the individual filesystems
    (/usr, /opt, and /var) incorrect.
    This is one reason I typically create only one partition as /
    that will be used for the entire system (minus swap space). In most
    cases, I will be installing additional disks for large applications
    like the Oracle RDBMS, Oracle Application Server, or other J2EE application
    servers.

 

  • overlap : The overlap partition represents entire disk and is slice s2 of the disk.
  • swap : The swap partition size depends on the size of RAM in the system.
    If you are not sure of its size, make it double the amount of RAM in your system.
    I typically like to make swap 2GB.

 

-------------------------------------------------
Boot Device: c0t0d0s0

=================================================
  Slice  Mount Point                 Size (MB)
     0   /                               36112
     1   swap                             2049
     2   overlap                         38162
     3                                       0
     4                                       0
     5                                       0
     6                                       0
     7                                       0
=================================================
                         Capacity:       38162 MB
                        Allocated:       38161 MB
                   Rounding Error:           1 MB
                             Free:           0 MB

Hit F2 to continue


This is what the File System and Disk Layout screen looks like now.

File sys/Mnt point Disk/Slice                            Size
=============================================================
/                  c0t0d0s0                        36112   MB
swap               c0t0d0s1                        2049    MB
overlap            c0t0d0s2                        38162   MB

Hit F2 to continue

Screen 42 : Mount Remote File Systems?

Do you want to mount software from a remote file server? This may be
necessary if you had to remove software because of disk space problems.

Hit F2 to continue

Screen 43 : Profile

This is a confirmation screen. Verify all data is correct.

        Installation Option: Initial
                Boot Device: c0t0d0
            Client Services: None

                    Locales: U.S.A. (UTF-8)
                             U.S.A. (en_US.ISO8859-1)
              System Locale: C ( C )

                   Software: Solaris 10, Entire Distribution

File System and Disk Layout: /                   c0t0d0s0 36112 MB
                             swap                c0t0d0s1 2049 MB

                   Products: Solaris 10 Extra Value Sof ...>   87.26 MB
                                Sun Validation Test Suite 6    69.92 MB
                                Sun Install Check 2.0.2        17.34 MB

Hit F2 to Begin the Installation

Screen 44 : Initial Installation Progress

Afterwards it starts configuring disks, making partitions, and installing software indicating the progress.

Preparing system for Solaris install

Configuring disk (c0t0d0)
        - Creating Solaris disk label (VTOC)

Creating and checking UFS file systems
        - Creating / (c0t0d0s0)

==================================================================
Solaris Initial Install

    MBytes Installed:  422.08
    MBytes Remaining: 3648.09

          Installing: JavaVM run time environment

  *****
  |    |     |     |     |     |  

  0   20    40    60    80    100 

==================================================================

Solaris 10 software installation succeeded

Customizing system files
        - Mount points table (/etc/vfstab)
        - Unselected disk mount points (/var/sadm/system/data/vfstab.unselected)
        - Network host addresses (/etc/hosts)
        - Network host addresses (/etc/hosts)
        - Environment variables (/etc/default/init)

Cleaning devices

Customizing system devices
        - Physical devices (/devices)
        - Logical devices (/dev)

Installing boot information
        - Installing boot blocks (c0t0d0s0)

Installation log location
        - /a/var/sadm/system/logs/install_log (before reboot)
        - /var/sadm/system/logs/install_log (after reboot)

Install of CD 1 complete.
Executing SolStart postinstall phase...
Executing finish script "patch_finish"...


Finish script patch_finish execution completed.
Executing JumpStart postinstall phase...

The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.

The finish script log 'finish.log'
is located in /var/sadm/system/logs after reboot.


   Pausing for 90 seconds at the "Reboot" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]
syncing file systems... done
rebooting...
Resetting ...




Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.6, 1792 MB memory installed, Serial #52928138.
Ethernet address 0:3:ba:27:9e:8a, Host ID: 83279e8a.



Rebooting with command: boot
Boot device: /pci@1f,0/ide@d/disk@0,0:a  File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: alex
Configuring devices.
SUNW,eri0 : 100 Mbps full duplex link up
Loading smf(5) service descriptions: 91/91
Creating new rsa public/private host key pair
Creating new dsa public/private host key pair


        This system is configured with NFS version 4, which uses a domain
        name that is automatically derived from the system's name services.
        The derived domain name is sufficient for most configurations. In a
        few cases, mounts that cross different domains might cause files to
        be owned by "nobody" due to the lack of a common domain name.

        Do you need to override the system's default NFS version 4 domain
        name (yes/no) ? [no] : no

        For more information about how the NFS version 4 default domain
        name is derived and its impact, refer to the man pages for nfs(4)
        and nfsmapid(1m), and the System Administration Guide: Network
        Services.



Starting Solaris Install Launcher in Command Line Mode.

Screen 45 : Continue Installation (Part 2)

After the system reboots, the installer will start the Solaris Install
Launcher in command line mode. You will then be asked for disk 2 of 5.

==================================================================
Please specify the media from which you will install Solaris 10 Software 2 for
SPARC Platforms.

Alternatively, choose the selection for "Skip" to skip this disc and go on to
the next one.

Media:

1. CD/DVD
2. Network File System
3. Skip

   Media [1]: 1

Please insert the CD/DVD for Solaris 10 Software 2 for SPARC Platforms.

After you insert the disc, please press Enter.

Enter S to skip this disc and go on to the next one.
To select a different media, enter B to go Back.

<Replace disk 1 with disk 2 and hit ENTER to continue>

Reading Solaris 10 Software 2 for SPARC Platforms.... /



Launching installer for Solaris 10 Software 2 for SPARC Platforms. Please
Wait...


The following items will be installed:

Product: Solaris 10 packages (part 2)
Location: /
Size: 887.16 MB
-------------------------------------
     Solaris 10 packages (part 2)    887.16 MB



Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

   What would you like to do [1]? 1

Solaris 10 packages (part 2)
|-1%--------------25%-----------------50%-----------------75%--------------100%|

   Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

Screen 46 : Continue Installation (Part 3)

You will then be asked for disk 3 of 5.

Please specify the media from which you will install Solaris 10 Software 3 for
SPARC Platforms.

Alternatively, choose the selection for "Skip" to skip this disc and go on to
the next one.

Media:

1. CD/DVD
2. Network File System
3. Skip

   Media [1]: 1

Please insert the CD/DVD for Solaris 10 Software 3 for SPARC Platforms.

After you insert the disc, please press Enter.

Enter S to skip this disc and go on to the next one.
To select a different media, enter B to go Back.
    []

<Replace disk 2 with disk 3 and hit ENTER to continue>

Reading Solaris 10 Software 3 for SPARC Platforms.... /



Launching installer for Solaris 10 Software 3 for SPARC Platforms. Please
Wait...

The following items will be installed:

Product: Solaris 10 packages (part 3)
Location: /
Size: 726.4 MB
-------------------------------------
     Solaris 10 packages (part 3)    726.4 MB



Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

   What would you like to do [1]? 1

Solaris 10 packages (part 3)
|-1%--------------25%-----------------50%-----------------75%--------------100%|

   Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

Screen 47 : Continue Installation (Part 4)

You will then be asked for disk 4 of 5.

Please specify the media from which you will install Solaris 10 Software 4 for
SPARC Platforms.

Alternatively, choose the selection for "Skip" to skip this disc and go on to
the next one.

Media:

1. CD/DVD
2. Network File System
3. Skip

   Media [1]: 1

Please insert the CD/DVD for Solaris 10 Software 4 for SPARC Platforms.

After you insert the disc, please press Enter.

Enter S to skip this disc and go on to the next one.
To select a different media, enter B to go Back.
    []

<Replace disk 3 with disk 4 and hit ENTER to continue>

Reading Solaris 10 Software 4 for SPARC Platforms.... /



Launching installer for Solaris 10 Software 4 for SPARC Platforms. Please
Wait...


Java Accessibility Bridge for GNOME loaded.


The following items will be installed:

Product: Solaris 10 packages (part 4)
Location: /
Size: 557.77 MB
-------------------------------------
     Solaris 10 packages (part 4)    557.77 MB



Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

   What would you like to do [1]? 1

Solaris 10 packages (part 4)
|-1%--------------25%-----------------50%-----------------75%--------------100%|

   Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

Screen 48 : Continue Installation (Part 5)

You will then be asked for disk 5 of 5.

Please specify the media from which you will install Solaris 10 Software 5 for
SPARC Platforms.

Alternatively, choose the selection for "Skip" to skip this disc and go on to
the next one.

Media:

1. CD/DVD
2. Network File System
3. Skip

   Media [1]: 1

Please insert the CD/DVD for Solaris 10 Software 5 for SPARC Platforms.

After you insert the disc, please press Enter.

Enter S to skip this disc and go on to the next one.
To select a different media, enter B to go Back.
    []

<Replace disk 4 with disk 5 and hit ENTER to continue>

Reading Solaris 10 Software 5 for SPARC Platforms.... /



Launching installer for Solaris 10 Software 5 for SPARC Platforms. Please
Wait...


Java Accessibility Bridge for GNOME loaded.

The following items will be installed:

Product: Solaris 10 packages (part 5)
Location: /
Size: 733.65 MB
-------------------------------------
     Solaris 10 packages (part 5)    733.65 MB

Product: Sun Validation Test Suite 6.2
Location: /opt
Size: 58.84 MB
--------------------------------------
     Test binaries    44.77 MB
Man Pages and Documentation    8.69 MB
Core Framework    5.39 MB

Product: Sun Install Check 2.0.2
Location: /opt
Size: 17.06 MB
--------------------------------
     SUNWinck - Sun Install Check    256.6 KB
SUNWeke - Embedded Knowledge Engine    4.29 MB
SUNWicisr - Sun Install Check Input Source (Root)    9.76 MB
SUNWicis - Sun Install Check Input Source    2.78 MB
SUNWinckr - Sun Install Check (Root)    785 bytes



Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

   What would you like to do [1]? 1

Solaris 10 packages (part 5)
|-1%--------------25%-----------------50%-----------------75%--------------100%|

Installing Sun Validation Test Suite 6.2
|-1%--------------25%-----------------50%-----------------75%--------------100%|

Installing Sun Install Check 2.0.2
|-1%--------------25%-----------------50%-----------------75%--------------100%|

   Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

Launching installer. Please Wait...


Java Accessibility Bridge for GNOME loaded.


Installing Additional Software
|-1%--------------25%-----------------50%-----------------75%--------------100%|

   Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

   Pausing for 90 seconds at the "Reboot" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

Nov 26 17:43:40 alex reboot: rebooted by root
Nov 26 17:43:41 alex syslogd: going down on signal 15
syncing file systems... done
rebooting...
Resetting ...


Post-Installation Tasks

After successfully installing the Solaris operating platform
software, there may be several tasks that need to be performed
depending on your configuration.

  • Networking: If you will be using networking database files
    for your TCP/IP networking configuration, several files
    will need to be manually created and/or modified.
    I provided a step-by-step document on how to manually
    configure TCP/IP networking files to manually enable
    TCP/IP networking using files:Configuring TCP/IP on Solaris – TCP/IP Configuration Files – (Quick Config Guide)
  • Solaris 10 Patch Cluster: It is advisable to install the latest Sun Solaris Patch Cluster
    to ensure a stable operating environment.

 


<!– Created by: Jeff Hunter
–>
Last modified on: Tuesday, 13-May-2014 02:30:16 EDT


Page Count: 136029

 

 

Share