SUN/Solaris Tools & Scripts

This is a small and simple guide to creating SUN/Solaris software packages and it has been developed through two years. In this how-to you will be guided through all the necessary information you need to build SUN/Solaris packages. An example by packaging a small and simple software is also provided.
The guide is not finished yet. You can download it in one zipZ File here.

analyze_ip.sh is a small shellscript for analyzing the settings of a SUN TCP stack.
Modifying the script turns it into a bootskript. See the comments in the script.

tunetcpstack.sh is a small shellscript for tuning the settings of a SUN TCP stack during booting.
Create a symlink from /etc/init.d/tunetcpstack.sh to /etc/rc2.d to have it always active. This script derives from analyze_ip.sh.

All new Sun Fire machines have one problem in common: Every device link contains the WWDN of the harddisk, a unique ID that makes a simple duplication by the "dd" command impossible. The second disk you duplicate the first on to will have as harddisk device links the links from the first harddisk. In case of a harddisk failure of your boot disk, last one is the rotten egg.
If you want to avoid using Solstice SDS Mirroring Suite in a high-availability environment, e.g. firewalls and you have to rely on a working second bootdisk without hoping the crash didn't affect any SDS config files, ddif_F280R.sh and swaplinks.sh are the scripts of your choice.
These two little helpers now copy the first disk to the second disk, finds out the device names from /etc/path_to_inst and swaps them on the second harddisk. After dd is finished, every partition is checked by "fsck". Finally, the second bootdisk is made bootable with the "installboot" command.
After the scripts are finished, which can take quite a long time, dependant on your harddisk sizes, you can simply got to the OPENBOOT prompt and enter

ok> boot disk:b
or
ok> boot disk1

0 4 * * * /root/cronbin/ddif_F280R.sh

analyze_sun.sh scans your SUN for certain components and looks for installed harddisks,
NIC cards, Netscape server installations, etc. The output files are in CSV format with ";" as separator.
After collecting, the script generates a tar-gz file with all of the rest in it. This script is a hack of 2 days,
therefore alphaware and HIGH RISK!! So use it on your own risk and don't blame me for disfunctional
parts. Asking the kernel debugger for its devices is always a tickly thing :)