We got two methods to do POST,you could choice the way you think it’s
easy to do.Of course
you must replace you CPU & DIMM from BAD Slot.

>1:Do the setting in OS ,then reset the system
>(*maybe you couldn’t run this command because you haven’t root’s permission *)
>a. #/usr/sbin/eeprom auto-boot=force
>b. #/usr/sbin/eeprom diag-switch?=true
>c. #/usr/sbin/eeprom diag-level=max
>d. #/usr/sbin/eeprom diag-device=disk
>e. #init 6
>
>
>2:Reboot the machine and do the setting
>
>power on the system, and enter “stop+A” to make functional system enter OK
>status,and do commands as follows.
>
>a. ok setenv diag-switch? true
>b. ok setenv diag-level max
>c. ok setenv diag-device disk
>d. ok reset-all
>
>
>
>
>**************
>
>After you do the POST and enter OS,pls do “#prtdiag”then take the message to us.
>If you cann’t run “prtdiag” pls do “#/usr/sbin/prtdiag”.
>If you still can’t run “#/usr/sbin/prtdiag”
>pls do “#find / -name prtdiag” to find where is the command of “prtdiag” in the SF 440.

pkg-get is a tool to automate download and installation of binary packages from archive sites that support it.
This tool simplifies fetching the latest version of a package from compatible sites to be as simple as

# pkg-get install gcc
This will automatically download the appropriate version for your architecture and OS revision (if available), and install the package. If you have an older version of the package already installed, using ‘upgrade’ instead of ‘install’ will replace the older version with a newer one, if available.

If the archive supports dependancies, pkg-get will also download any needed dependancies. For example

pkg-get install mod_php
should triger an automatic
pkg-get install apache
which in turn should automatically trigger
pkg-get install openssl

Downloading pkg-get

For the newer pkg-get version 2, that supports the latest features like a descriptions file, go to
blastwave.org’s pkg-get download page
The older version of pkg-get can be obtained by SHIFT-clicking on:

BOLTpget.pkg v1.9.9 (last update, Dec 6, 2002)

Occasionally, there have been problems downloading the .pkg file. If you cannot download the .pkg file, shift-click to download this UU-Encoded Version. run uudecode BOLTpget.pkg.uue, and you will then have the BOLTpget.pkg file
Once downloaded, install with

# pkgadd -d BOLTpget.pkg
and run ‘pkg-get -U’ to initialize the local catalog of available packages, after tweaking the url in pkg-get.conf Then you’re all set to go!

From : pkg-get

insert cd 1of 4 and go to /cdrom/cdrom0//Solaris_8/Product
The package might be any of the 4 CD’s, I’ve moved onto DVD’s, sorry.
Then:
# pkgadd -d . SUNWman
This should then add the package to your system.
Add the location to the your ~/.profile as MANPATH= ; export MANPATH
After that run:
# catman -w
This will build the man page catalogs so you can use the “-k” option to search the pages.
The catman command may take a few minutes to return.

Sometimes it’s useful to create a virtual network interface on your Solaris box, so that you can associate multiple IP addresses with the same host and not have to go through all the trouble of buying another NIC.

Here’s a quick HOWTO. Let’s assume our network card is eri0, and we want to create a virtual interface called eri0:1

Create the virtual interface:
# ifconfig eri0:1 plumb

Configure the virtual interface:
# ifconfig eri0:1 179.164.83.161 netmask 255.255.255.0 broadcast 179.164.83.255

Check to make sure it worked:

# ifconfig -a

lo0: flags=1000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843 mtu 1500 index 2
inet 179.164.83.160 netmask ffffff00 broadcast 179.164.83.255
ether 0:3:ba:9:63:9b
eri0:1: flags=1000842 mtu 1500 index 2
inet 179.164.83.161 netmask ffffff00 broadcast 179.164.83.255

Finally bring up your new virtual interface:
# ifconfig eri0:1 up

To make it come up on start:

create /etc/hostname.eri0:1 with hostname in it
make sure the hostname is in /etc/hosts

NOTE: The IP addresses in this story have been changed to protect the innocent.

–
Reference : http://cliff.blogs.plymouth.edu/

6.3.0.1 RC scripts
SunOS 4.1.X uses the RC scripts rc.boot, rc.ip, rc, rc.single, and rc.local, all in /etc. The major functions performed by these scripts are listed in the next table.

SunOS 5.X uses the RC scripts rcS, rc0, rc1, rc2, rc3, rc5, and rc6 in /sbin. These start or stop services defined in the scripts contained in the /etc/rc#.d directories. The S scripts are run during startup, lower through higher run-level. The K scripts are run during shutdown, higher through lower run-level. These RC scripts provide the functions listed in the next table.

30.2 SunOS 4.1.X and 5.X Administrative File Differences
The following table lists some of the important files that have been changed.

From : http://wks.uts.ohio-state.edu/sysadm_course/html/sysadm-115.html

http://wks.uts.ohio-state.edu/sysadm-course/html/sysadm-577.html