Pages

Friday, May 27, 2011

CollabNet Subversion - svn


Subversion

CollabNet Subversion is an enterprise-ready distribution of Subversion that includes certified binaries and platform-specific installers.
CollabNet Subversion downloads are available for:
These binaries are certified by CollabNet.
Other Subversion downloads are also available for:
These downloads are hosted by CollabNet, but not certified by CollabNet. They are created and maintained by the openCollabNet community.

Thanks to : http://www.open.collab.net/downloads/subversion.html

Suggestions are always welcome...! Without signing also you can send your comments.

Cannot start Microsoft Office Outlook. Cannot Open the Outlook Window

When you click on the icon to start Outlook, the window shows up briefly and then disappears, popping up the message:  Cannot Start Microsoft Office Outlook.  Cannot Open the Outlook Window .




simply run:  outlook.exe /resetnavpane


Suggestions are always welcome...! Without signing also you can send your comments.



How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system?

Windows XP

If you have Windows XP, there are two methods to determine whether you are running a 32-bit or a 64-bit version. If one does not work, try the other.
  1. Click Start, and then click Run.
  2. Type winmsd.exe, and then click OK.
  3. When System Summary is selected in the navigation pane, locate Processor under Item in the details pane. Note the value.
    • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of Windows.
    • If the value that corresponds to Processor starts with ia64 or AMD64, the computer is running a 64-bit version of Windows.

Windows Server 2003

If you have Windows Server 2003, there are two methods to determine whether you are running a 32-bit or a 64-bit version. If one does not work, try the other.
View System Information window

  1. Click Start, and then click Run
  2. Type winmsd.exe, and then click OK.
  3. When System Summary is selected in the navigation pane, locate Processor under Item in the details pane. Note the value.
    • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of Windows.
    • If the value that corresponds to Processor starts with EM64T or ia64, the computer is running a 64-bit version of Windows.
  4. Windows Vista or Windows 7

    If you have Windows Vista or Windows 7, there are two methods to determine whether you are running a 32-bit or a 64-bit version. If one does not work, try the other.
    Method 1: View System window in Control Panel
    1. Click Start
      Collapse this imageExpand this image
       Start button
      , type system in the Start Search box, and then click system in the Programs list.
    2. The operating system is displayed as follows:
      • For a 64-bit version operating system: 64-bit Operating System appears for the System type under System.
      • For a 32-bit version operating system: 32-bit Operating System appears for the System type under System.
    Method 2: View System Information window
    1. Click Start
      Collapse this imageExpand this image
       Start button
      , type system in the Start Search box, and then click System Information in the Programs list.
    2. When System Summary is selected in the navigation pane, the operating system is displayed as follows:
      • For a 64-bit version operating system: x64-based PC appears for the System type under Item.
      • For a 32-bit version operating system: x86-based PC appears for the System type under Item.
Thanks to :http://support.microsoft.com/kb/827218

Suggestions are always welcome...! Without signing also you can send your comments.

Installing Solaris 10 on a Sun Blade 150


Installing Sun Solaris 10





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 my 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. I provided a step-by-step document on how to download and install the latest Sun Solaris 10 Patch Cluster: Patching Sun Solaris 10
Thanks to : Jeff Hunter, Sr. Database Administrator url : http://www.idevelopment.info/data/Unix/Solaris/SOLARIS_Installing_Solaris_10.shtml#Using Serial Console Connection

Suggestions are always welcome...! Without signing also you can send your comments.

DB2 Installation steps

4. Prerequisites

Prerequisites are the hardware and software elements needed on your system before you can install and use DB2 Express-C 9. This section covers:

  • Hardware requirements:
    • Supported processors
    • Disk space requirements
    • Memory requirements
  • Software requirements:
    • Linux distributions
    • Kernel levels and libraries requirements
    • Additional software requirements


4.1. Hardware requirements

4.1.1. Supported processor architectures


  • x86 (32-bit processor)
  • x86–64 (64-bit processor)
  • POWER™ (any iSeries™ or pSeries® that supports Linux)

4.1.2. Disk space requirements

Take into account the disk space requirements before you install and configure DB2 on your distribution:
Table 1. Disk space requirements
Install type Description Required disk space
Typical DB2 is installed with most features and functionality, including graphical tools such as the Control Center. 460 to 560 MB
Compact DB2 is installed with basic features and functionality, but without the graphical tools. 380 to 460 MB
Custom This option allows you to select the features and functionality that you want to install. 320 to 820 MB

It's important to allocate enough disk space for the software, along with the product documentation (if desired) and the databases you create.
In DB2 9, product documentation is accessed through the DB2 Information Center, either via the web, or as a local system installation. To install this locally requires at least 100 MB when installing the core English language files. Additional space is required for other additional languages. If disk space is an issue, you can configure DB2 to access the Information Center from the Web. More detail about this is provided in Installing the DB2 Information Center.

4.1.3. Memory requirements

We recommend that you should allocate a minimum of 512 MB of RAM for DB2 Express-C 9, and additional memory should be allocated for other software and communication processes. When determining memory requirements, consider the following points:

  • Your SWAP space should be at least twice as much as your RAM.
  • Additional memory should be allocated for any non-DB2 software that may be running on your system.
  • Additional memory is necessary to support database clients and database activity.
  • These memory requirements will be affected by the size and complexity of your database system, as well as specific performance requirements.
  • The maximum RAM allowed for a DB2 Express-C installation is 4 GB.

4.2. Software requirements

4.2.1. Distribution levels that are supported by DB2 Express-C 9

For a list of all the distributions that are officially supported, as well as the latest information about kernels, libraries, integrated cluster environments, and papers, visit the DB2 for Linux validation web site listed in Resources.

4.2.2. Additional software requirements

Depending on your DB2 requirements, you may be required to install additional software packages for DB2 to function properly. Make sure that these software packages are installed prior to using DB2.

  • X Window System software, capable of rendering a graphical window manager (KDE, Gnome, etc.). You will need this if you want to use the DB2 graphical installer, or any of the DB2 graphical tools.
  • A web browser, to view topics in the DB2 Information Center.
  • If you are using NIS or NIS+ for security authentication on your system, you must create DB2 user accounts before installing DB2.
  • Additional packages, as outlined in the following table:
    Table 2. Package requirements
    Package name RPM name Description
    compat-libstdc++ compat-libstdc++ Required by 64-bit architectures only. Required for backwards compatibility with standard C++ libraries used by DB2.
    nfs-utils nfs-utils (version 1.0 or later) Network File System support package. It allows access for local files to remote machines. Required for systems utilizing NFS mounted drives.
    To check whether you have these packages installed, use the rpm -q commands:

    rpm -qa compat-libstdc++*

    To install these packages on Red Hat Linux, use the Red Hat Linux installation CDs and the rpm command, or the up2date utility. For example, to install the compat-libstdc++ package from the Red Hat Linux CD, mount the Red Hat Linux CD #4, and enter this command as root:

    rpm -ivh /mnt/cdrom/RedHat/RPMS/compat-libstdc++-296-2.96-132.7.2.i386.rpm
    To install using the up2date package, run this command as root:

    up2date compat-libstdc++

    To install these packages on SUSE Linux, you can also use rpm or use the handy YaST (Yet another Setup Tool) utility. For example, to install nfs-utils on SLES 9 using YaST:

    1. Log on as root
    2. From the YaST Control Center, select Software -> Software Management, then use the search "nfs-utils" to find the appropriate packages.

      5. Installation considerations and planning

      After verifying that your system meets the basic requirements, you should plan your installation by considering installation methods and the creation of users and groups:

      • Installation choices:
        • db2setupinstallation
        • db2_installinstallation
        • DB2 response file installation
      • User and group setup:
        • User and group requirements
        • Creating users

      5.1. Installation methods

      After downloading and extracting the tar.gz file, the file tree looks like this:

      exp/ -|
          disk1/ -|
            db2_install    (* command line installation script *)
            db2setup       (* GUI installation launcher *)
            installFixPack (* not applicable for Express-C *)
            db2/ -|        (* installation and licensing files *)
            doc/ -|        (* install instructions and release notes *)

      You can use three methods to install DB2:

      • db2setup utility
      • db2_install utility
      • a DB2 response file
      Each method has its own advantages and disadvantages. The choice of method depends on your level of expertise and type of environment, but in general, if a graphical interface is available, using db2setup is recommended for ease of installation.

      5.1.1. db2setup installation

      The db2setup command starts the DB2 Launchpad, a graphical tool that configures and organizes the DB2 installation. It lays down the DB2 filesets, creates and configures DB2 instances, users and groups, communications, the administration database used by the DB2 Tools, and sets up notification processes. The DB2 Launchpad also allows you to create a response file for replicating a particular setup to other systems.
      Using db2setup is the best method for less experienced users, because most of the configuration is automatically performed during the installation. As mentioned previously, you require an X Window System capable of rendering a graphical user interface to use db2setup successfully.

      5.1.2. db2_install installation

      The db2_install command script installs all DB2 packages on your Linux system. This method is reliable and commonly used by expert users for installing DB2 on larger, more complex systems. However, tasks such as setting up users and groups, creating instances, tools catalog database creation, and notification setup need to be performed manually after the installation is completed.
      One limitation to db2_install is that it only installs user assistance (like help, messages, and tool interfaces) in English, whereas db2setup supports the installation of additional languages. Also, a db2_install installation can take longer (because of the higher number of manual configuration tasks); it requires a higher level of knowledge and skill, and it cannot be used to create response files.

      5.1.3. Response file installation

      A response file can be created using the DB2 Setup Wizard or by editing an existing DB2 response (.rsp) file. It allows you to install DB2 across multiple machines with consistent installation and configuration settings. A response file installation is fast, because it bypasses the graphical wizard configuration. Another advantage of using a response file instead of the db2_install command is that it creates a Database Administration Server (DAS) on each machine, while with db2_install the DAS must be created manually after installation.
      There is a sample response file (db2exp.rsp) included on the installation image that can be modified and used to install DB2, configure users, create instances, set up notification, create the tools catalog, and configure a large number of database management parameters. This is the quickest installation method if you already have all the information you need. Unlike db2setup, the response file installation is not interactive, and it takes longer to prepare the response file initially.

      5.2. User and group setup

      DB2 requires user IDs and groups for database authentication. This section discusses these IDs and groups and how to create them.

      5.2.1. User and group requirements

      DB2 requires a minimum of three users and groups: an instance owner, a fenced user, and the Database Administration Server (DAS) user. You may use the default names provided by the setup utilities, or specify your own user and group names. For example, consider the following default user IDs and group names produced by the DB2 Setup Launchpad:
      Table 3. Default user IDs and group names
      Required user User name Group name Description
      Instance owner db2inst1 db2grp1 Administers a DB2 instance
      Fenced user db2fenc1 db2fgrp1 Responsible for executing "fenced" user defined functions, such as JDFs and stored procedures.
      DAS user dasusr1 dasadm1 Administers the DB2 Administration Server

      5.2.2. Creating users

      You must have root authority to create users and groups. There are three ways to create a DB2 user ID:

      • DB2 Launchpad: the DB2 Launchpad installation creates all of the required users and groups for you during installation. The default users and groups that get created are displayed in the table above. This method also gives you the option to specify your own user and group names.
      • Response file: Users can also be created during a response file installation if you specify user and group information in the response file. For example, consider the following entries in a response file that create the three required users and groups for DB2:

        * DAS user
        DAS_USERNAME = dasusr1
        DAS_GROUP_NAME = dasadm1
        DAS_HOME_DIRECTORY = /home/dasusr1
        DAS_PASSWORD = ******
        * Instance-owning user
        inst1.NAME = db2inst1
        inst1.GROUP_NAME = db2grp1
        inst1.HOME_DIRECTORY = /db2home/db2inst1
        inst1.PASSWORD = ******
        inst1.AUTOSTART = YES
        inst1.AUTHENTICATION = SERVER
        inst1.SVCENAME = db2c_db2inst1
        inst1.PORT_NUMBER = 50001
        inst1.FCM_PORT_NUMBER = 60000
        inst1.MAX_LOGICAL_NODES = 4
        * Fenced user
        nst1.FENCED_USERNAME = db2fenc1
        inst1.FENCED_GROUP_NAME = db2fgrp1
        inst1.FENCED_HOME_DIRECTORY = /db2home/db2fenc1
        inst1.FENCED_PASSWORD = ******

      • Manually using command line. To use this method, follow these steps:

        1. Log on to your machine as root.
        2. Create groups for the instance owner, the fenced user and the DAS user by using these commands:

          groupadd db2grp1
          groupadd db2fgrp1
          groupadd dasadm1
          Linux will create the groups using the first available group ID (GID) numbers available. You can specify GID numbers if you prefer.
        3. Create a user that belongs to each group and specify the home directory. For example, you can choose to place all home directories in /db2home by entering these commands:

          useradd -g db2grp1  -m -d /db2home/db2inst1 db2inst1 -p password1
          useradd -g db2fgrp1 -m -d /db2home/db2fenc1 db2fenc1 -p password2
          useradd -g dasadm1  -m -d /db2home/dasusr1 dasusr1 -p password3
                              

      5.2.3. Adding existing users as DB2 users

      To enable existing system users to act as DB2 instance administrators, you must make a few modifications to the existing user accounts:

      • Add your user to the db2grp1 group. The SYSADM_GROUP database manager configuration parameter controls who has that level of access for all databases in that instance. You can determine what group is set as the SYSADM group by entering:

        db2 get dbm cfg | grep SYSADM_GROUP

        By default, DB2 sets this as the db2grp1 group. To add the user to the SYSADM group, modify the /etc/groups file (as root), adding the user account ID to the line for the DB2 system admin group. For example:

        db2grp1:x:102:jackc,ellenp,frankj

      • Update the user's profile by adding the following lines to the .bashrc file in the home directory

        # The following three lines have been added by the DB2 SYSADM.
        if [ -f /home/frankj/sqllib/db2profile ]; then
            . /home/frankj/sqllib/db2profile
        fi

      • After installation, if you wish to grant or revoke access to databases (or other objects), use the "User and Groups" section of the Control Center or the GRANT and REVOKE SQL statements. If you want to see an example, by default the SAMPLE database grants a number of privileges to "PUBLIC".

      . Installing DB2 Express-C

      This chapter covers a typical setup scenario for installing DB2 Express-C on a 32-bit Linux system, using the db2setup installation method.

      6.1. db2setup installation

      6.1.1. Prerequisites



      • Ensure that your system meets the software, memory, and disk requirements outlined in Section 5.
      • You require root authority to perform the installation.
      • The DB2 Setup Launchpad is a graphical installer. You must have X Window System software capable of rendering a graphical user interface for the DB2 Setup Launchpad to run on your machine.

      6.1.2. Procedure

      To install DB2 Express-C 9:

      1. Log on to the system as a user with root authority.
      2. If you are installing from a CD or DVD, enter the command to mount the DB2 installation media. For example,

        mount /media/cdrom
        If you are using a downloaded tar.gz file, extract the contents of this archive to a location on your harddrive. For example, presuming the tar.gz file was downloaded to the /tmp directory:

        cd /tmp
        tar zxf db2exc_912_LNX_x86.tar.gz

      3. Change to the install directory. For the CD/DVD install:

        cd /media/cdrom/exp/disk1
        For the downloaded and extracted tar.gz file:

        cd /tmp/exp/disk1

      4. Run the db2setup command.

        ./db2setup

      5. When the IBM DB2 Setup Launchpad opens, select "Install a Product".
      6. Select the "Install New" button in the main window.
      7. When the Welcome to the DB2 Setup wizard window appears, click "Next".
      8. Read the license agreement and select the "Accept" button if you accept the terms (the "Decline" button is selected by default). Click "Next".
      9. On the Select the installation typewindow, select the type of installation you want to perform. You have three installation options:
        • Typical: 460–560 MB. This option installs and configures most of the DB2 components, using a typical configuration with default values. This option includes all of the core features, along with ODBC support, and commonly used tools such as the Control Center. You can select the "View Features" button to see what components get installed with this option.
        • Compact: 380–460 MB. This option installs and configures only the basic DB2 components, with minimal configuration performed on your computer. With this option you get the base server and client support, along with Java and SQL procedure support. Again, you can click the "View Features" button for more information.
        • Custom: 320–820 MB. This option allows you to install only those components that you select; and to create and customize a basic DB2 instance.
        Make your choice and click "Next". (The remainder of these instructions are based on the Custom installation option).
      10. On the Select the installation action window, choose the "Install DB2 Express on this computer" radio button. You can also choose to save your installations settings in a response file by selecting "Save your settings in a response file". You should choose this option if you plan to install DB2, with these same settings, on other computers in your environment.
      11. Choose the DB2 elements you want on the Select the features to install window. You can preview each component by selecting it and reading the corresponding description in the Description section.
        You can also choose where to install the DB2 program files. By default for a first time installation, this location is /opt/ibm/db2/V9.1/ Once you have decided what features you want to install and the destination, click "Next".
      12. Select what languages you want installed for the messages and user interface on your computer in the Languages window. English is always installed, regardless of other language choices. Click "Next".
      13. In the Specify the location of the DB2 Information Center window, select how you want to access the DB2 Information Center. The DB2 Information Center contains documentation for DB2 and other related DB2 products. The "On the IBM Web site" button is selected by default. By choosing this option, DB2 is configured to access documentation on the Web using your browser. If you have a copy of the DB2 Information Center installed elsewhere on an intranet server, you can choose the "On the following intranet server" button. Specify the values in the Host name and Port number text fields (the default value for the port number is 51000). Click the "Help" button for more information, otherwise click "Next".
      14. Fill out the information for the user that will administer the DB2 Administration Server in the Set user information for the DB2 Administration Server window. Select either the "New user" button, or the "Existing user" button. The Password and Confirm password text boxes are outlined in red indicating required fields that must be filled in for the installation to continue. If you choose to create a new user, a user account will be created (including a home directory) on your Linux system. Click "Next".
      15. If you want to create a new basic DB2 instance to store your database, then select the "Create a DB2 instance" button on the Set up a DB2 instance window. Otherwise, select the "Defer this task until after installation is complete" button. If you select this second option, you will need to create a new instance after the installation by using the db2icrt command. Click "Help" for more information, otherwise click "Next".
      16. If you create a new instance, fill out the information for the DB2 instance owner on the Set user information for the DB2 instance owner window. Select either the "New user" button, or the "Existing user" button. The Password and Confirm password text boxes are outlined in red indicating required fields that must be filled in for the installation to continue. Again, if you choose to create a new user, a user account will be created (including a home directory) on your Linux system. Click "Next".
      17. Fill out the information for the DB2 fenced user on the Set user information for the fenced user window. Select either the "New user" button, or the "Existing user" button. The Password and Confirm password text boxes are outlined in red indicating required fields that must be filled in for the installation to continue. For more information on fenced users, and how fenced users relate to fenced and non-fenced user-defined functions (UDFs) and stored procedures, click "Help". Otherwise, click "Next" to continue.
      18. Configure the DB2 instance for TCP/IP communications on the Configure instance IP communication and startup window. You may either accept the default values found in the Service name and Port number fields, or select your own. If you want to configure the instance properties at a later time, select the "Do not configure at this time" button. This service name and port are added to the services file for the system, typically found in /etc/services.
        You can also choose whether to start up this instance at system startup. This is recommended if you are planning on running your system as a DB2 server. Click "Next".
      19. On the Prepare the DB2 tools catalog window, select the "Prepare the DB2 tools catalog" button if you want to use the Task Center or Task Scheduler. This option creates a local database that stores task metadata. If you do not have this task repository, the scheduler will not function. If you want to create a DB2 tools catalog after you finish the installation, select the "Do not prepare the DB2 tools catalog" button. You can create the DB2 tools catalog later manually by using the CREATE TOOLS CATALOG command. Click "Next".
        If you decide to create a DB2 tools catalog, you can specify which instance, database, and schema in which to store the DB2 tools catalog. The DB2 tools catalog will be placed in the home directory of the instance owner. Click "Next".
      20. Specify a notification mail server and contact list on the Set up notifications window. This allows DB2 to notify administrators if a database requires attention. Either create a new contact list that is stored locally, or use an existing global contact list that resides on a remote DB2 server. Use an available SMTP server that will accept an unauthenticated SMTP message for e-mail notifications. You may also choose to skip this step; DB2 will still record all administration notifications in the log files. Click "Next".
      21. If you specified a new local list for contacts in the previous step, then in the Specify a contact for health monitor notification, you can add a name and email address where DB2 Health Center messages will be sent for any health alerts from DB2 databases.
      22. On the Start copying files window, review the installation settings, and then click "Finish" to complete the installation. The Current settings panel provides a summary of your installation and configuration settings.
      While the files are being copied to your computer, you will see two status bars on the Installing DB2 Express window, one indicating the progress of each individual installation task, and one for the overall installation progress. When the installation is finished, the Setup Complete window indicates what, if any, post-installation steps need to be taken, along with a tab (labelled "Log File") that shows the log file report for the installation. Click "Finish" to close this window and the Setup Launchpad.

      7. Installing DB2 Express-C on Red Hat Enterprise Linux (RHEL) 4

      Before proceeding, please ensure that you have read Section 5 and Section 6.
      These installation notes are based on a single-partition installation using the 2.6.9-55.0.2 EL kernel.

      7.1. Installation notes

      The installation on Red Hat Enterprise Linux 4 completed successfully, with no problems getting the GUI installer working, and no errors during the install. This smooth installation isn't surprising, given that RHEL 4 is an officially supported platform for DB2.

      7.2. Post-installation notes

      Basic test results (see Section 21 for more details) were successful.
      However, I found that after a reboot, the DB2 instance was not being restarted automatically, so clients could not connect to the database. To correct this problem, execute this command as the instance owner:

      db2set DB2AUTOSTART=YES
      This will ensure that the DB2 instance is initialized and ready to receive incoming connections after a reboot (intentional or otherwise).
      Also, to allow DB2 access through the iptables-based firewall (which is enabled by default), it was necessary to modify the iptables firewall ruleset, which is kept in the /etc/sysconfig/iptables file. If you have enabled your firewall (using the iptables service), and you want to enable external connectivity to your DB2 server, you must open up TCP and UDP access to ports 523 and TCP access to any DB2 service ports. To make this work, add these rules to the iptablesfile (anywhere amongst the -j ACCEPT rules):

      -A RH-Firewall-1-INPUT -p udp -m udp --dport 523 -j ACCEPT
      -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 523 -j ACCEPT
      -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 50000 -j ACCEPT
      These rules were added directly to the iptables file to ensure that they persist in case of a system reboot. Note that you will need to add another new TCP rule to allow firewall access if you create any additional instances later.
      You can use db2 get dbm cfg | grep SVCENAME to retrieve the service names and then check the /etc/services for the equivalent port values to open on your firewall.
      ----------------------------------------------------------------------------------------------

      Removing DB2 Express-C

      Uninstalling DB2 Express-C is a bit more detailed than the installation process. Unfortunately, at this time, there is no GUI-based uninstaller utility like there is for installation. Follow the steps below to completely remove the DB2 Express-C software from your system. Since the database files are kept in the home directory of the instance user, you can keep the database files by skipping the removal of the instance owner (the last step).

      1. Remove the Database Administration Server. Switch to the DAS owner (dasusr1 by default), either through the su - dasusr1 command or by logging in to the system directly as the DAS user, and issue the command db2admin stop. Then switch to the root user, and issue the /opt/ibm/db2/V9.1/instance/dasdrop command.
      2. Remove the DB2 instance(s). Switch to the instance owner (db2inst1 by default), either through the su - db2inst1 command or by logging in to the system directly as the instance user, and issue the command db2stop. Then, as root, remove the instance by issuing the /opt/ibm/db2/V9.1/instance/db2idrop db2_instance command, where db2_instance refers to the actual instance name you want to drop (for example, /opt/ibm/db2/V9.1/instance/db2idrop db2inst1). If you want to verify which instances are present on your system, run the /opt/ibm/db2/V9.1/instance/db2ilist command.
      3. Remove the software installation. As root, run the /opt/ibm/db2/V9.1/install/db2_deinstall -a command. This will remove the installation of DB2 from your system.
      4. If no longer need the DB2 database files (which are kept in the home directory of the instance owner), you can remove the users that were created during the installation of DB2 Express-C by entering these commands as root:

        userdel -r db2inst1
        userdel -r dasusr1
        userdel -r db2fenc1
        (If you created different user names during installation, substitute as necessary.)

        Thanks to : http://tldp.org/HOWTO/DB2-HOWTO/prerequisites.html
      Suggestions are always welcome...! Without signing also you can send your comments.

In Solaris, How to Setup DNS Client configuration / name server ?


DNS Client Setup:
First Create the file called /etc/resolv.conf - which includes the primary and secondary DNS server IP address for Solaris system, it can be your own DNS server or your ISPs DNS server:
# touch /etc/resolv.conf
Open /etc/resolv.conf using vi text editor:
# vi /etc/resolv.conf
Add the following lines to it:
search nixcraft.in
nameserver 202.54.1.30
nameserver 202.54.1.18
Where,
  • nameserver IP : It is IP of first DNS server
  • search nixcraft.in : Default domain name to search. For example, if you type command nslookup www, it will search it as www.nixcraft.in
2) Enable the name resolving using DNS as follows:
# cp /etc/nsswitch.dns /etc/nsswitch.conf
3) Test new name server by running the nslookup command as follows:
# nslookup nixcraft.in
OR
# /usr/sfw/sbin/nslookup nixcraft.in
Output:
Server:  gwbsd2vsnl.nixcraft.in
Address:  192.168.1.202

Non-authoritative answer:
Name:    nixcraft.in
Address:  202.71.128.225
Thanks to : Nixcraft : http://www.cyberciti.biz/tips/solaris-dns-client-configuration.html

Suggestions are always welcome...! Without signing also you can send your comments.

General Unix Information

General Unix Information

There are numerous flavours of Unix; AIX (IBM), Solaris (SUN), Xenix, Linux etc. all of which conform to the Posix standard. Unix often comes with a number of command shells, e.g. Bourne Shell ($ prompt) or C shell (% prompt with enhancements on the Bourne Shell) or Korn shell ($ prompt) which have slightly differing command syntax, although principally they are the same. The shell interprets the commands that you type. The 'Tea Sea Shell' (tcsh) is often used in the Linux environment and contains useful attributes such as 'up-arrow' and 'down-arrow' recall of previous command entries, and the use of the TAB key to complete commands (much like the Cisco IOS!). The shell interprets commands with the operating system kernel. The beauty of Unix is that hundreds of people can access one box at once and each one can run a number of programs, a separate shell opens for each log on that occurs, and each user can have a completely different 'environment' setup, different colours, priviledges, file and directory access and different shell.

Unix file names can be up to 14 characters long and include the _ and the . characters.

Every Unix command or filename is case sensitive, unlike DOS, this is the most common error to be aware of. Commands leave 'notes' for programs (such as printing) that are 'buried' in the Unix system. This is so that one user does not hog one program, many people can access it. Such a program is called a 'daemon'.

Below is a diagram illustrating a typical Unix file system structure on a box:


unix file system

An Absolute Pathname starts from the root directory e.g. /user/bin. The Relative pathname points to a file or directory that is relative to the position that you are in within the directory tree and this does not start with a /.

Information about users is kept in the passwd file which sits in the /etc directory along with the other configuration files. For each user there are seven fields separated by colons:
  • User name (first part of e-mail address).
  • Encrypted password.
  • UID (Users ID) needed by the Unix system. User names can change without changing user permissions.
  • GID (Group ID). A user may be a member of several groups each having different permissions.
  • Comment containing more detail on the user if desired.
  • User's home directory.
  • The shell to be used by the particular user.
Nowadays, when you are confronted with a Unix box you will come across an X-windows interface. To get to a command line interface, grab the three button mouse click the right button and select programs clicking on it with the left mouse button. In the list of programs that appear select either shell or command to open a command line window (much like a DOS box in Microsoft Windows). You normally need to click on the title bar or border before you can type in the window, sometimes the X-window interface has been set up such that the mouse moving over the window is enough to highlight the box. Any number of these command line windows can be opened. Resizing them is achieved by selecting the bottom right hand corner with the left mouse button (a circle appears) and dragging the window edges to the required size. Minimising a window is achieved by 'left-clicking' on the top left corner of the menu bar and selecting close. Selecting quit closes the window.

Keystrokes


Ctrl-c


Stops a command or program that is currently being executed.

Ctrl-d


Removes you from the current environment, this will log you out of the system if you are at a shell prompt.

Ctrl-h, Del


Deletes the last character typed and moves back one space. Unlike DOS, the backspace key does not work!

Ctrl-q


Resumes the command that was halted by Ctrl-s.

Ctrl-s


Temporarily halts the current command being executed, e.g. scrolling of text on the screen.

Ctrl-u, Ctrl-x, @


Cancels what you have just typed, so that you can start again.

Ctrl-x


Deletes the current line of text being entered.

Directory Commands


cd


Stands for change directory, e.g.
cd /user/dave
takes you to dave's personal directory. The first / refers to root. Root is the equivalent of / in DOS. Typing cd without a path takes you back to your home directory, i.e. where you arrive when you first log on. Typing cd.. takes you up one directory, whereas typing cd ../user/dave, takes you up one directory and then right down to the '/user/dave' directory.

df -k


Stands for disk free, gives you the amount of space available on the disk that you are currently on.

mkdir


Means 'make directory', e.g.
mkdir user
creates a directory called user in the directory you are in when you issue the command.

pwd


Stands for print working directory and prints the directory that you are in to the screen.

rmdir


Means remove directory e.g.
rmdir user
removes the directory user provided that it is empty!

System Commands


-&


Using this switch after a command causes it to operate in the background, allowing you to continue using the same command line window without having to open another one.

*


This wildcard character matches any number of characters and is useful in searches, e.g.
g*
matches all files beginning with 'g'.

?


This wildcard character matches any single character, e.g.
g??
matches all three character files beginning with 'g'.

>


Redirect output from a program to a file, e.g.
ls -l > listing
redirects the listing of ls -l into a file called 'listing'.

<


Redirect output from a file into a program, e.g.
mail john < hello
redirects the greeting letter called 'hello' to John, rather than you having to type it.

|


Pipe output from one program to another, e.g.
who | wc -l
gives a count of the users on the system.

>>


This append adds the input to an existing file without overwriting the original, e.g.
postcript >> letter
adds the contents of 'postscript' to an existing file called 'letter'.

chsh


Means change shell and changes the shell that the user is using. The user will be prompted for a password since the 'passwd' file is being changed, then the user will need to type the path to the shell e.g. /bin/bash.

echo


This 'echoes' arguments to the screen, e.g.
echo $SHELL
displays the value of the environment variable SHELL. This could return /bin/tcsh (Linux often uses this shell) or /bin/bash. echo $PATH displays the current path.

env


The environment gives you the variables set up for the particular user that issues the command.

exit, Ctrl-d


Logs you out.

jobs


This lists the jobs running under the current shell in 'job ID' order. You can type bg %jobid to put a particular job running in the background. Ctrl Z also suspends a job. Typing fg %jobid brings the job back to the foreground.

kill


This kills a process e.g.
kill 5173
kill the process which has been given the temporary number 5173. This process number is found by using the ps command. Do not use kill 1 as this kills the system scheduler! If a process refuses to die you can type kill -KILL [PID] to stop a process immediately without any tidying up on exitting. Finally, kill -HUP [PID] tells the process that an event has occurred, or a configuration file change has occurred and needs to br reread.

man


The manual command is very useful for finding out comprehensive information on an individual command e.g.
man cd
gives all the information on the command cd. Typing man -k mail lists the Unix commands that relate to the word mail.

passwd


Allows you or the administrator to change passwords.

printenv


The 'prints the environment' variables to the screen.

ps


The process status command shows the programs currently running. ps -a shows all the processes being run by all users. An example is the following:
ps -ef | grep erpcd
where '-ef' gets the process number and pipes it to grep which filters on the following word, in this case for the program 'erpcd'.

The following information is shown:
  • PID Process ID.
  • TTY Each shell opened has a 'character special' called a 'tty' (held in '/dev').
  • STAT State, either 'S', sleeping, or 'R', running.
  • TIME CPU time that the process is taking up.
  • COMMAND The command running.
Typing ps x shows all the processes relating to X windows, whereas ps ax shows all the processes being run by everybody. Typing ps ux gives even more information such as the user.

setenv


The command set environment variable, sets aside a small amount of memory to hold paths etc. e.g.
setenv GUI /usr/utility/gui_r4
sets a variable 'GUI' with the path that follows to the actual program. This program can now be run by typing 'GUI'.
setenv DISPLAY :0.0
sets an X window session locally.
These settings are commonly setup permanently in the user's .profile (located in the '/etc' directory). This can be edited with any text editor.

The following are common environment variables:
  • SHELL The current shell.
  • HOME The current user's home directory.
  • HOSTNAME The name of the computer.
  • DISPLAY The X display that the applications are to use.
  • LD_LIBRARY_PATH The search path for libraries.
  • PATH The search path for applications.
If you wish to append directories to the path then type setenv PATH ${PATH} : /search/here. In order to use it then you need to cache the new path by typing rehash.

The DISPLAY variable is made up of three parts 'hostname : displaynumber : screennumber'. The hostname is the computer, whilst the other variables are '0' unless several machines are connected. X windows looks to this variable to find out where to send the X Windows traffic.

set path


Sets a path where regularly used programs or data are found e.g.
set path=($path /usr/utility/gui_r4/bin)
sets the path '/usr/utility/gui_r4/bin'.

Some commands used to set the environment come from the C shell. In order to check which shell you are running type echo $SHELL, if this does not return '/sbin/csh' then you type /bin/csh.

su


The command switch user switches the login user to another user, e.g.
su root
switches to the 'root' login.

top


Gives a constantly updating view of the top 20 processes (a real time version of 'ps'), i.e. those that are using the CPU the most.

who


This displays the users currently logged on the system.

whoami


Displays who you are currently logged on as. (e.g. 'root', a user etc.)

xhost +


Opens an X window for a program to run in. After issuing this you would then run the program (e.g. Netscape).

File Commands


.


The dot is not a command as such. If a file is spelled with a dot at the beginning, Unix treats it as a hidden file. Configuration files are often preceded with a dot.

cat


The concatenate command displays a file, e.g.
cat bankletter
displays the contents of 'bankletter' on the screen.
cat > newletter
takes whatever you type and redirects it into the file 'newletter', Ctrl-d gets you out of it.
cat >> existing
takes whatever you type and appends it to an existing file called 'existing' funnily enough.

chmod


The command change mode changes the mode or permissions, of a file or a directory. When you do an ls -l you will see in the first column, a line of 10 characters looking something like 'drwx-w-rw-'. The 'd' means 'directory' (you could have '-' for file, 'l' for link to a file, 'b' for a 'block special', 'c' for a 'character special', 'p' for a 'named pipe', or 's' for 'socket'). The next three characters refer to the permissions of the login user, in this case the user has read, write and execute access to the directory. The next three characters refer to the permissions of the group and the final three characters refer to the permissions of all users. The chmod command can be used in various ways as shown by the following examples:
  • chmod go-rwx newletter removes read, write and execute permissions for users in the group (g), and all other users, for the file 'newletter'. Using a '+' instead of '-' adds the permissions. You can also use 'o' for others, or 'u' for user.
  • chmod 766 newletter causes the file 'newletter' to have read, write and execute permissions for the user, read and write permissions for the group members and read and write permissions for all other users. Why? Well, the 7 represents 111(binary) and 6 represents 110(binary) for each set of three 'rwx's. 'r' being set is given binary 1, 'x' being not set is given binary 0. Read permission is '4', write permission is '2', execute permission is '1' and no permissions is given with '0'.
  • chmod 700 dirname results in drwx------ for the directory which restricts access to everyone bar the owner.
  • chmod 664 filename gives -rw-rw-r-- that allows you and your group to read and edit the file but all others can only read the file.
  • chmod 600 filename gives -rwx------ creates a private file that only you can see and edit.
You can change permissions for groups of files with one command by using wildcards such as *.

chown


Use this to change ownership of a file e.g.
chown dave myfile
changes the ownership of the file 'myfile' to dave. This can only be carried out by the owner of the original file. A way around this is for the recipient to copy the file, then the copied file becomes their own.

chgrp


Use this to change group ownership of a file.

compress


This compresses a file e.g.
compress myfile
results in a file called 'myfile.Z'. The command uncompress can be used to uncompress the file.

cp


The copy command copies files from one directory to another, or to the same directory with a different name, e.g.
cp bankletter /user/dave/bankletter1
copies the file 'bankletter' from the directory that you are currently in, to the '/user/dave' directory with a new name 'bankletter1'.

file


This returns information on the content of a file, e.g.
file myletter
might return 'ASCII' to say that Unix guesses that 'myletter' contains ASCII.

find


This finds a file or directory, e.g.
find / -name na -print &
this finds a file with name 'na' starting the search from the 'root' and printing the result to the shell window, whilst still allowing you to carry on using it.

grep


This stands for global regular expression and print and is a search utility, e.g.
grep "325 Victory"
searches the current directory for files containing the text '325 Victory'.

gzip


GNU zip compresses files to create a '**.gz' file.

head


This command followed by a filename, displays the first ten lines of that file.

less


This is a way of displaying a file, it will give a percentage of file so far displayed at the bottom of the screen, and you can progress through reading the file by pressing the space bar.

ln


The command link, links files and directories, e.g.
ln -s/export/home/fred usr/fred
creates a copy of 'fred' in the '/export/home/' directory in the 'usr/fred' directory. A 'hard link' is like a Windows 'shortcut', there can be a number of them, with different names and they take up little space. A 'soft link' is identified with the '-s' switch and creates a copy of the file elsewhere.

lp (for System V) or lpr (for BSD)


The command line printer, prints a file, e.g.
lp newletter
prints 'newletter'.

lpstat -a all


The line printer stats command checks the printer queue in System V Unix.

ls


This lists the contents of the current directory, e.g.
ls /etc
lists the files and sub-directories of the current directory.
  • ls -l gives a long list of directories including file sizes, permissions, type etc. Using the -a switch causes 'all' files to be listed including those hidden files starting with ..
  • ls -c lists files by creation time.
  • ls -p marks directories with a slash at the end of the name.
  • ls -x displays the list in rows across the screen.
  • Using ls | more is useful for large directories as it stops the screen scrolling, you press the 'Return' key to advance one line at a time, or press the space bar to advance one page at a time.
You can type 'ls' and then define one or more directories for it to list.

more


This is another way of displaying a file, it will give a percentage of file so far displayed at the bottom of the screen, and you can progress through reading the file by pressing the space bar. Whilst in more, if you type v you will be taken straight to the vi editor.

mv


This moves a file from one directory to another or renames it in the same directory, e.g.
mv bankletter bankletter1
renames 'bankletter' to 'bankletter1'.

pg filename


Displays the content of the file one page at a time. You advance pages by pressing 'Return'. Option -l displays one more line, option n moves you to the page number specified by n and options +n and -n moves you forward or backward the number of pages specified by n.

rm


'remove' a file, e.g.
rm oldletter
removes the file 'oldletter'. Using rm -rf recursively removes all files and directories below the one that you are in. Using rm -i gives you the option of cancelling or confirming the command.

sort


Sorts the contents of a file, e.g.:
sort -o outfile infile

The contents of 'infile' are sorted in alphabetical order and fed into a new file called 'outfile', as defined by the switch '-o'.

tail


This means the tail end, this dynamically displays the file that is being written to in real time, e.g.
tail -f logfile
shows the file 'logfile' which is being written to.

tar


The command tape archive is an file archiving command. It creates a single uncompressed archive file from several, ideal for sending data over networks. Often files are archived, and then compressed using 'gzip'. E.g.
tar -tvf tarfile
displays the contents of a tarfile.
tar -xvf tarfile
extracts the contents of a tarfile. 'x' is extract, 'v' means 'verbose' and 'f' means the file.
tar -xvf tarfile target
extracts the file target from the tarfile.

touch


This just creates an empty file for appending to later on e.g.
touch log
creates an empty file called 'log' that needs to be available for another program to write to it perhaps.

uncompress


This command uncompresses a 'gzip' file, e.g.
uncompress myfile.gz
uncompresses the file 'myfile.gz'.

wc


The command word count counts the words in a particular file, e.g.
wc letter
counts the number of words in the file 'letter'

Simple Scripting


A Unix script is the equivalent of the DOS batch file. Using vi, the following could be typed into a file called 'new_script':
echo These users are on the system
who
echo Here is a detailed listing of the directory you are in
ls -al
The command chmod u+x new_script makes the script file executable by the logged in user.

Networking Commands


arp


Displays the 'Address Resolution Protocol' table e.g.
arp -a
displays all arp entries for all connected devices.
arp -d <ip address>
deletes the arp entry for that particular IP address.

ftp


The command file transfer protocol attaches you to another IP device e.g.
ftp 141.205.15.154
attaches you to the device with address 141.205.15.154. You are normally presented with a login and password screen.

Commands that are used in FTP are:
  • dir - directory listing.
  • quit - quit from ftp.
  • cd - change directory.
  • get or mget - get a file (or multiple files).
  • put or mput - put a file (or multiple files).
  • bin - sets up your system to receive binary files.
  • hash - displays hashes whilst files are being transferred.
  • lcd - local change directory changes the directory on your local machine to which you are sending and receiving files. This is useful as it saves you having to quit ftp to carry out the directory change.
The Hosts file can be found in the directory '/etc'.

netstat


This stands for network statistics, e.g.
netstat -r
displays the routing table of the Unix box.
netstat -a
displays alll network information.

Unix uses routed to listen to RIP in order to discover the Default Gateway.

ping


Ping an IP device e.g.
ping 141.205.51.26

rlogin


This works like telnet, e.g.
rlogin 141.205.52.16
takes you to another Unix machine only. To quit you press 'return', '~', .' and 'return' again.

telnet


Ctrl-6 and then Ctrl-] gets you to the telnet> prompt where typing close gets you out of telnet.

vstat


This displays CPU utilisation and gives a list of processes and their share of CPU utilisation, e.g.
vstat 10
displays the CPU utilisation every 10 seconds.

ifconfig


This displays the IP configuration of the box, e.g.
ifconfig -a
displays all IP configuration.

If you want to look at the routing process you can type:
ps -ef type grep routed
to send the 'routed' information to a file.

snoop


This command captures the network packets in a readable format, e.g.
snoop -p 23
captures all IP traffic using port 23 (Telnet). use Ctrl-C to stop the snoop.

Useful vi commands


Each command needs to be preceded by pressing the escape key!

i insert mode.
<esc> leave insert mode and go into command mode.
a append characters to the end of the line.
o open a line below your cursor.
O open a line above.
<shift>g go to the bottom of the file.
r replace the letter that you are on with the one you type next.
x erase the character that you are on.
dd delete the line that you are on. A number before dd deletes that number of lines.
yy copy the line you are on. A number before yy copies that number of lines.
p paste the line you are on below you.
P paste the line you are on above you.
:wq write and quit the file that you are editing.
:wq! write and quit the file that you are editing, even if it is designated as read only!
:w! write to a read only file.
:q quit.
:q! discard any editing and quit.
/ this takes you to the bottom of the window where you can type a string and return to perform a search in the file.

(The character ! is often referred to as pling)

You can use vedit which is vi with more user friendly additions and also ed, or emacs.

Thanks to : http://www.rhyshaden.com/unix.htm

Suggestions are always welcome...! Without signing also you can send your comments.