A. Solaris 2.5 General Installation Notes
  1. Boot off of the CDROM and click "continue" in the installation window when Open Windows appears.

  2. System Setup

    1. Identify the system.

      hostname: an unique name for your workstation.
      networked: YES
      IP addr: w.x.y.z

    2. Name Service

      Select "other" to use DNS. Avoid NIS and NIS+.

    3. Subnets

      System part of a subnet: YES

    4. Netmask

      Netmask: 255.255.255.0

    5. Timezone

      Choose by geographic region: United States, Eastern
      Date: Set the current time and date.

    6. Install either a server or client.

    7. Engage!

    8. When prompted as to whether you want to reboot, choose not to since you have a lot of stuff to setup before it is net-ready.

  3. Setup DNS.

    1. Edit /etc/nsswitch.conf. Add "dns" after "files" in row "hosts".

    2. Edit /etc/resolv.conf. Add: 
      domain pas.rochester.edu
nameserver 128.151.144.13
nameserver 128.151.224.6

  4. Start up NFS.

    /etc/init.d/nfs.server start

    You may need to do this more than once. Check to see if the nfs server is running with: rpcinfo -u localhost nfs.

  5. Install OW patches from /cdrom/cdrom0/s0/Patches/OW.

  6. Setup mail to automatically mount at boot time. Edit /etc/vfstab and add the following line:

    savoirfaire:/var/spool/mail - /var/mail - no rw,hard,noac

    NOTE: /var/spool/mail will change to /var/mail when savoirfaire is upgraded.

  7. Get and install the security stuff (into /applic/nir/security). For tcp_wrappers, edit the /etc/inetd.conf file for tcpd. touch /var/log/tcpdlog. Setup /etc/hosts.[deny,allow] for our site (check one of the other machines and copy it).

  8. Kill the current sendmail process: /etc/init.d/sendmail stop, install the latest version of sendmail (don't forget to regenerate the sendmail.cf file). The new sendmail executable goes in /usr/lib and the new sendmail.cf goes in /etc/mail. Permissions for sendmail binary should be 4511. A link should exist between /etc/mail/sendmail.cf and /etc/sendmail.cf. Now restart sendmail: /etc/init.d/sendmail start.

  9. Set the /.forward file to "root@machine name".

  10. In /etc/inetd.conf, comment out unneeded lines: echo,discard,daytime,chargen,tftpd (don't forget to HUP inetd).

  11. Setup automounting. Easiest way to do this is to copy our files. In general you need an auto_master file which automountd (the daemon) will run when you refresh it with automount.

    /etc/auto_master: 

        #Mount-point    Map             Mount-options
    /-              /etc/auto.app           -rw,soft
    /-              /etc/auto.u-nir         -rw,soft
    /-              /etc/auto.u-other       -rw,soft
    Since the NIR group is currently using a complex user mounting scheme, it gets its own file. Links in each file look like:

    /etc/auto.app: 

        #key            mount-options   location
    /applic/ath                     callisto:/applic/ath

  12. Now install the software you need.

  13. Notes on upgrading sendmail to new versions.

    1. First compile sendmail in the src directory.
    2. Next, compile the sendmail restricted shell in the smrsh directory.
    3. Now create the sendmail.cf file:
      1. Add FEATURE(smrsh) before MAILER in cf/cf/generic-solaris2.mc.
      2. Generate the cf file: m4 ../m4/cf.m4 generic-solaris2.mc > foo.cf
      3. Modify the Mprog line in foo.cf so that the path to smrsh is correct. We have it in /applic/nir/security/bin.
      4. Add to foo.cf after CP.: 
            # NOT SURE IF THESE ARE NEEDED
    # UUCP relay host
    DYuunet.uu.net
    CPUUCP
    #BITNET relay host
    DBdb1.cc.rochester.edu
    CPBITNET
    4. Create the directory /usr/adm/sm.bin and make links in here to programs you want sendmail to have access to (i.e. vacation).
    5. Install the new sendmail in /usr/lib, smrsh in /applic/nir/security/bin, and sendmail.cf in /etc.
    6. Stop the current sendmail: /etc/init.d/sendmail stop
    7. Start using the new sendmail: /etc/init.d/sendmail start

  14. Here is how I setup WABI. It will allow multiple users to share the same wabi installation. Users should be aware that their actions may mess up the installation. Files which should not be overwritten should probably be changed to r-x by hand.

    1. Create a user and group named wabi and have its home directory be something like /applic/nir/wabi.
    2. Follow the instructions for installing WABI.
    3. Install Windows 3.1 and all your applications as user wabi in /applic/nir/wabi/wabi.
    4. When finished, all users should have the following envionment variable set:

      setenv WABIUSER /applic/nir/wabi/wabi

    5. The /applic/nir/wabi/wabi directory should have its permissions set to 775 (rwx, rwx, r-x).
    6. All users who wish to use wabi should create a Wabi directory in their home directory and then use Main->Control_Panel->Wabi_Config->Drives to point a letter to it. You should make sure no one has write permission (group and other) to your local Wabi directory.
    7. Setting up printing. The default selection when printing is postscript to the default printer.
    8. To add a wabi client (i.e. a machine which automounts the /applic/SUNWwabi directory), you need to run:

      /applic/SUNWwabi/bin/wabiclientinstall

      on the new machine.

    ©1996 kevin mcfadden