DCSLIB Software Library

How to tell if DCSLIB is already mounted

You can see if DCSLIB is already mounted on your system by using the df command:

   % df -k /dcs /dcslib
   Filesystem            kbytes    used   avail capacity  Mounted on
   dcslib1.nacs.uci.edu:/dcspdb/sun4-5
                        25065216 19814744 2743952    88%    /dcs
   dcslib1.nacs.uci.edu:/dcspda
                        25065216 19814744 2743952    88%    /dcslib

If you get output similar to the above, you already have dcslib mounted.

Requesting access to DCSLIB

To use DCSLIB, you have to let us know what system(s) you want to be able to mount DCSLIB on so we can give those system(s) access. To do this, send email to dcs@uci.edu listing what system(s) you want to have access to DCSLIB. Please make sure you specify the fully-qualified name (e.g. sun1.ps.uci.edu) of your system, in case there is more than one "sun1" system on campus. You can usually get the fully-qualified name of your system from the hostname command.

You will have to stop here until you get a response back saying that your system has access to DCSLIB.

Mounting DCSLIB

Picking a server

First, you need to pick a DCSLIB server to mount from. There are three servers: dcslib1.nacs.uci.edu, dcslib2.nacs.uci.edu, and dcslib3.nacs.uci.edu. you can either pick one, or see if one is "closer" to your system (fewer hops thru the campus network).

To see which server is closer to you, you can use the traceroute program. Some systems may not have traceroute installed on them by the software vendor. Red Hat Enterprise Linux, Tru64 UNIX and IRIX do, Solaris does not. If you do not have a copy of traceroute available, you can pick one of the DCSLIB servers, mount the partitions, and get a copy of traceroute from /dcs/etc.

Here is an example of using traceroute

    % traceroute dcslib1.nacs.uci.edu
    traceroute to dcslib1.nacs.uci.edu (128.200.15.15), 30 hops max, 40 byte packets
     1  egw3.gw.ucinet.uci.edu (128.200.16.1)  2.784 ms  6.394 ms  1.693 ms
     2  dcslib1.nacs.uci.edu (128.200.15.15)  1.846 ms  1.974 ms  2.038 ms

    % traceroute dcslib2.nacs.uci.edu
    traceroute to dcslib2.nacs.uci.edu (128.195.135.138), 30 hops max, 40 byte packets
     1  egw3.gw.ucinet.uci.edu (128.200.16.1)  2.783 ms  1.811 ms  11.61 ms
     2  so2-8510-vl452.ucinet.uci.edu (128.195.250.5)  2.667 ms  2.562 ms  6.259 ms
     3  cpl-core--so2-8510.ucinet.uci.edu (128.195.248.209)  2.407 ms  2.152 ms  1.997 ms
     4  cpl-cdl-rsm1-vl401--cpl-core.ucinet.uci.edu (128.195.249.2)  6.313 ms  2.874 ms  2.429 ms
     5  dcslib2.nacs.uci.edu (128.195.135.138)  2.366 ms  3.799 ms  5.566 ms

    % traceroute dcslib3.nacs.uci.edu
    traceroute to dcslib3.nacs.uci.edu (128.200.205.146), 30 hops max, 40 byte packets
     1  egw3.gw.ucinet.uci.edu (128.200.16.1)  2.806 ms  1.69 ms  11.273 ms
     2  cs1-8510-vl438.ucinet.uci.edu (128.195.249.177)  1.777 ms  1.721 ms  1.652 ms
     3  row-rsm-vl435.ucinet.uci.edu (128.195.249.170)  2.201 ms  2.429 ms  2.233 ms
     4  dcslib3.nacs.uci.edu (128.200.205.146)  1.993 ms  1.938 ms  1.822 ms

In the example above, dcslib1.nacs.uci.edu is closer than the others, so you would pick dcslib1.nacs.uci.edu.

Editing /etc/fstab or /etc/vfstab

Now that you have a server picked out, you can add entries to your /etc/fstab (for Tru64 UNIX, Linux, IRIX) or /etc/vfstab (for Solaris) file. In the examples below, replace server with the name of the DCSLIB server you picked above (make sure you use the fully qualified hostname of the server e.g. dcslib1.nacs.uci.edu not dcslib1).

For Solaris 2.7 and above, add these lines to /etc/vfstab:

server:/dcspdb/sun4-5 - /dcs    nfs - yes -
server:/dcspda        - /dcslib nfs - yes -

For Red Hat Enterprise Linux 3, add these lines to /etc/fstab:

server:/dcspdb/rhel-3-i686 /dcs    nfs ro,intr 0 0
server:/dcspda             /dcslib nfs ro,intr 0 0

For IRIX 6.5.x, add these lines to /etc/fstab:

server:/dcspdb/sgi-n32 /dcs    nfs ro,intr 0 0
server:/dcspda         /dcslib nfs ro,intr 0 0

For Tru64 UNIX, add these lines to /etc/fstab:

server:/dcspdb/decalpha /dcs    nfs ro,intr 0 0
server:/dcspda          /dcslib nfs ro,intr 0 0

Creating directories

You will need to create two directories for your system to use as mount points for DCSLIB, /dcs and /dcslib.

   % mkdir /dcs /dcslib

Testing your work

Now you can try mounting DCSLIB:

   % mount /dcs
   % mount /dcslib

If you did not get any error messages from the mounts, you are all set to start using DCSLIB. If you did get errors, recheck your work to make sure there are not any typos in the lines you added to /etc/fstab or /etc/vfstab. If you are still having problems please contact us at dcs@uci.edu. Please include the complete error message you are getting, what system you were trying to mount DCSLIB on, etc. The more information you give us the better.

Mounting licensed software in DCSLIB

If you have arranaged for access to licensed software such as Matlab, you will need run a script to mount the licensed software in DCSLIB on your system (you will want to do this if you have a Sun so you can get access to the Sun compilers). To do this, you need to run /dcs/etc/mount-map:

   % sh /dcs/etc/mount-map

You may want to setup a script in your system startup area to do this each time your system boots. Put the above line in a file called S95dcslib and put it in the directory listed below for the operating system you are running.

Make sure the file is executable:

   % chmod 755 S95dcslib

Changing your default path to include DCSLIB

Now that you have DCSLIB mounted, you will want to include the DCSLIB binary directories in your default PATH. Take a look at /dcs/skel/newuser.cshrc, /dcs/skel/newuser.login, and /dcs/skel/newuser.profile. These are files you can use as a starting point for your own .cshrc, .login, and .profile. Most of the real work is done in the /dcs/skel/syswide.cshrc, /dcs/skel/syswide.login, and /dcs/skel/syswide.profile files. They setup the default path and may set some other environment variables that are necessary for DCSLIB software to run correctly.

If you want to use the /dcs/skel/newuser.* files as a starting point for your own files, you will need to make a link (as root) before you can do this:

   % ln -s /dcs/skel /usr/skel

If /usr/skel already exists, you will need to rename it before you can make the link.

Where to look for software in DCSLIB

Most software packages are located in /dcs/packages/package-name.
Look at the DCSLIB Software List. It will tell you the location and version number of the software package.