/etc/defaultrouter
/etc/inet/netmasks
/etc/nodename
/etc/hostname.e1000g0
/etc/resolv.conf
/etc/hosts

/etc/defaultrouter

172.16.0.1

/etc/inet/netmasks

172.16.0.0 255.255.255.0

/etc/nodename

solsrv

/etc/hostname.e1000g0

solsrv

/etc/resolv.conf

For my DNS server I use OpenDNS: http://www.opendns.org

nameserver 208.67.222.222

/etc/hosts

127.0.0.1 localhost
172.16.0.100 solsrv

---

IMPORTANT - Delete These Files

Finally remove these files using the following commands:

rm /etc/dhcp.e1000g0
rm /etc/dhcp/e1000g0.dhc

Login

To create a new session you need to put in your SSH or Telnet server's address, username, and password. In addition you need to put in your Sun Online Account information.

To login to an existing Shared Shell session you will first need an invitation key from the session. This must by obtained outside of shared shell, i.e. IM, phone, email. You will also need to put in you Sun Online Account information before you connect to the session.

The following window will show you the invite code for your session. A user's Sun Online account name will show up in this window when he or she connects allowing you to decide to allow then or deny access to the session.

Features

Shared Shell includes the ability for users to use a white board functionality on top of the active terminal.

As with any white board you can erase any marks that are made.

A great feature included in Shared Shell is that is colorizes each user's text. Not only does it colorize the text in the chat window but also in the terminal window, and cursors.

Permissions

Shared Shell allows you to give an invited user one of three permissions:

• Full Access

  Allows the user to type in the terminal and press enter to execute commands.

• No-Exec Access

  Allows the user to type in the terminal, but may not execute commands.

• View Only Access

  Allows the user only to view the terminal. The user cannot type commands nor execute them.

A full access user must press enter for the no-exec access user. This is useful if you want someone to show you the command but do not trust them enough to let them execute the command.

File Transfer

Shared Shell allows users to send files and receive files from other users. Users can even request a file from another user.

Sun Microsystems' Shared Shell is available freely for download at Sun Microsystems - Shared Shell.

Installation

Creating Required Directories

mkdir /opt/src

Download Ruby & Dependencies

cd /opt/src
wget ftp://ftp.cwru.edu/pub/bash/readline-5.2.tar.gz
wget ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.8.6.tar.gz

Extract Ruby

gunzip readline-5.2.tar.gz
gunzip ruby-1.8.6.tar.gz
tar xf readline-5.2.tar
tar xf ruby-1.8.6.tar

Compile Ruby & Dependencies

Readline

cd readline-5.2
./configure --prefix=/opt/local
make
sudo make install

Ruby

cd ../ruby-1.8.6
./configure --with-readline-dir=/opt/local --enable-pthread --prefix=/opt/local
make
sudo make install

Test Installation

Run the following command to make sure that ruby is installed

ruby -v

Troubleshooting

If this fails with a command not found error your path may not be set correctly.

echo $PATH

Make sure it looks like this

/opt/local/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin

Environment Requirements

• Boot Server
• Installer Server
• Profile Server

There are three corresponding services that match up the above requirements. Before I go into detail I will explain what each server does and the services that are required by that server and what part they play in the whole scheme of things.With an exception to the boot server some of the time these servers can all be housed on one single machine.

Boot Server

The boot server handles the communication with the SPARC machines on boot. The boot server needs three configuration files and also needs to be running in.rarpd.

/etc/bootparams

ultra60  root=192.168.0.253:/export/install/sparc_10/Solaris_10/Tools/Boot \
install=192.168.0.253:/export/install/sparc_10 boottype=:in \
sysid_config=192.168.0.253:/opt/SUNWjet/Clients/ultra60 \
install_config=192.168.0.253:/opt/SUNWjet rootopts=:rsize=8192  term=:vt100

/etc/ethers

88:02:23:b4:d1:6b ultra60

/etc/hosts

127.0.0.1       localhost
192.168.0.253   boot-srv loghost
192.168.0.100   ultra60

Setting up and Starting Boot Services Uncomment the line in /etc/inetd.conf that is referring to the tftp server. Restart the TFTP server. For debugging purposes running the tftp server in the foreground might be useful. Start the RARP Daemon in the foregroup for debugging purposes as well. Once those services are running the boot server setup is complete!

Install Server

The install server stores all the files that are used for installation. This server requires that NFS be running and exporting the files that are pulled from the CD/DVD. Run the following commands below to prepare the installation server for JumpStart.

mkdir -m 755 -p /export/install
mkdir -m 755 -p /export/jumpstart
cd /cdrom/SOL_10_1106_ARCH/s0/Solaris_10/Tools
./setup_install_server /export/install/sparc_10
share -F nfs -o ro,anon=0 /export/install
share -F nfs -o ro,anon=0 /export/jumpstart
shareall

Below is the listing of the shared directory with the install files.

boot-srv# ls /export/install 
TT_DB     media     patches   pkgs      sparc_10

You can check to see if the NFS directories are being shared with the following command:

showmount -e localhost

The install server should be all set now

Profile Server

The profile server stores the information that the client needs about itself. Scripts and rules files are stored on the profile server for use by the client. There are pre and post install scripts for further customization. A rules file must be created then tested with the check command which is copied from the CD.

/export/jumpstart/rules

any - - any_machine -

The rules file above will match any machine that initiates a ARP request on boot.

Once the rules file is created you must run the check script on this file. The script will create a file called rules.ok which is the file that is read from the client during the boot phase of the install. The check script lives on the first CD/DVD of the Solaris 10 set. Run the following command to get the files necessary:

cp /cdrom/SOL_10_1106_ARCH/s0/Solaris_10/Misc/* /export/jumpstart
cd /export/jumpstart/
./check

This script should return a message stating that the rules file is ok. Run the following command to make sure the file was created.

ls /export/jumpstart | grep rules.ok

Once you are complete here your JumpStart server should be completely operational. All that is left to do is to add clients and test them. Adding clients to a JumpStart server is very easy. Sun supplies a script in the Misc folder on the CD that was copied to the /export/jumpstart folder during the install. Run the following command to add a client:

cd /export/jumpstart
./add_install_client -e MAC_ADDRESS \
-s boot-srv:/export/install/sparc_10 \
-c boot-srv:/export/jumpstart \
ultra60 sun4u

Troubleshooting

• Make sure the /export/jumpstart folder is shared via NFS
• Make sure the /export/install folder is shared via NFS
• Make sure the TFTP server is up and running
• Make sure the RARP server is up and running
• If the clients are connected to a Cisco Switch or other managed switch make sure the ports that are connected to a computer are set to portfast or else the link will never come up in time for the RARP message to be received by the client.