@  
[ Hardware | Software Setup | Configuration Details | Specific Config Files | The Chicken | Emergency ]


Hardware

The following machines are available for the machine translation group. The machines c1-c6, m1, and box11 are currently (as of Aug'05) our console user machines and will usually be running X.
Machine Name Processor Location OS Cache size Memory Hard Drive Motherboard Memory Type Video Driver
c1.cs.nyu.edu AMD Athlon(TM) XP 1800+ 719 Broadway Room 716 (machine room) Redhat Enterprise Linux 4 WS 256 KB 2 x 512MB PC2100 DDR SDRAM = 1GB total (FULL) Single Disk (/ partition 10GB, /data partition 27GB) FIC AD11 review 2X 184-pin DIMM 1Gb DDR SDRAM PC1600(?)-PC2100 nv
c2.cs.nyu.edu AMD Athlon(TM) XP 1800+ 719 Broadway Room 716 (machine room) Redhat Enterprise Linux 4 WS 256 KB 2 x 512MB PC2100 DDR SDRAM = 1GB total (2 of 3 slots used) Single Disk (/ partition 10GB, /data partition 46GB) ASUS A7v266-E review 3X 184-pin DIMM 3Gb DDR SDRAM PC1600 - PC2100 radeon
c3.cs.nyu.edu AMD Athlon(TM) XP 1800+ 719 Broadway Room 712 Redhat Enterprise Linux 4 WS 256 KB 2 x 512MB PC2100 DDR SDRAM = 1GB total (FULL) Single Disk (/ partition 22GB, /data partition 15GB) FIC AD11 review 2X 184-pin DIMM 1Gb DDR SDRAM PC1600(?)-PC2100 nvidia
c4.cs.nyu.edu AMD Athlon(TM) XP 1800+ 719 Broadway Room 716 (machine room) Redhat Enterprise Linux 4 WS 256 KB 2 x 512MB PC2100 DDR SDRAM = 1GB total (FULL) Single Disk (/ partition 37 GB, /data shares this space) FIC AD11 review 2X 184-pin DIMM 1Gb DDR SDRAM PC1600(?)-PC2100 nv
c5.cs.nyu.edu AMD Athlon(TM) XP 1800+ 715 Broadway Room 707 Redhat Enterprise Linux 4 WS 256 KB 2 x 512MB PC2100 DDR SDRAM = 1GB total (2 of 3 slots used) Single Disk (/ partition 10GB), /data partition 107GB) ASUS A7v266-E review 3X 184-pin DIMM 3Gb DDR SDRAM PC1600 - PC2100 radeon
c6.cs.nyu.edu Pentium 4 3GHz 719 Broadway Room 701 Redhat Enterprise Linux 4 WS 1Mb Cache 2 x 512MB PC2700 DDR DDR, 333MHz, Non-ECC (2 of 4 slots used) Single Disk (/ partition 10 GB, /data partition 62GB) ASUS, P4P800-MX, Intel 865GV 4X 184-pin DDR 400 i810
c7 and c17.cs.nyu.edu Pentium 4 3GHz 719 Broadway Room 716 (Machine Room) Redhat Enterprise Linux 4 WS 1Mb Cache 4 x 1GB PC2700 DDR DDR, 333MHz, Non-ECC (4 of 4 slots used) Single Disk (/ partition 10 GB, /data partition 62GB) ASUS, P4P800-MX, Intel 865GV 4X 184-pin DDR 400 i810
c8-c16.cs.nyu.edu Pentium 4 3GHz 719 Broadway Room 716 (Machine Room) Redhat Enterprise Linux 4 WS 1Mb Cache 2 x 512MB PC2700 DDR DDR, 333MHz, Non-ECC (2 of 4 slots used) Single Disk (/ partition 10 GB, /data partition 62GB) ASUS, P4P800-MX, Intel 865GV 4X 184-pin DDR 400 i810
csstupc53.cs.nyu.edu Intel(R) Pentium III (Coppermine) CPU 1.00GHz 719 Broadway Room 712 Redhat Enterprise Linux 4 WS 256 KB 1 x 256MB 133Mhz 168-pin DIMM = 256MB total (1 of 2 slots used) Single Disk (/ partition 10GB, /data partition 107GB) Dell Dimension 4100 2X 168-pin DIMM 512Mb 100(?)-133Mhz nv
box11.cs.nyu.edu Intel(R) Pentium(R) 4 CPU 2.80GHz 719 Broadway Room 712 Redhat Enterprise Linux 3 WS 1 Mb 1GB DDR Single Disk (/ partition 145GB, /data shares this space) Dell Optiplex GX 280 ? vga
m1.cs.nyu.edu 2 X Intel(R) Pentium(R) III 1133MHz 715 Broadway Room 706 Redhat Enterprise Linux 4 WS 32 KB 2 x 133Mhz 168-pin DIMM = 2GB total (FULL) 2 Disks with RAID 1 (/ partition 9GB, /data partition 55GB) Dell Server 2SLZY01 2X 168-pin DIMM 2Gb 100(?)-133Mhz ati
s1.cs.nyu.edu 4 CPU Sparc Server Somewhere on WWH 2nd floor Sun Solaris 8   8 GB 5 Disks with RAID 5 (/ partition 160GB, /data shares this space)      
coop.pdsg.cs.nyu.edu controls the 32 processor diskless cluster called "chicken" 719 Broadway Room 716 Redhat 8.0   1 x 512Mb 133Mhz DIMM per chicken     2X 133Mhz DIMM 1Gb per chicken  

Software Setup

This setup is currently being used on c1-c17, m1, and csstupc53

  • Start with the "everything" install of Redhat Enterprise Linux 4 WS .
  • Run up2date
  • The latest kde packages (via yum)
  • Kernel version >= 2.6.9-11.EL
  • java - j2re and j2sdk version 1.5
  • gcc version 3.4.5 and 4.0.2
  • ssh & sshd - OpenSSH SSH client & deamon
  • acroread - Adobe Acrobat Reader 7.0
  • dvipdfm - Produce PDF files directly from DVI files
  • valgrind version 3.0.1 - An open-source memory debugger for x86-GNU/Linux
  • mozilla - Browser full version 1.7.13 with the following plugins:
    • MozPlugger 1.7.1
    • DjVuLibre-3.5.14
    • Java(TM) Plug-in 1.5.0
    • Acrobat plugin - nppdf.so
    • Shockwave Flash plugin - libflashplayer.so
    • RealPlayer G2 plugin
    • QuickTime Plug-in
  • Condor - A specialized workload management system for compute-intensive jobs.
    Version: 6.6.6 or better
  • Additional LaTeX styles (e.g. qtree.sty)
  • The latest Python install with the following modules:
  • Install uptimed
  • lush
  • ocaml
  • apache-ant-1.6.2
  • gsl libraries for lush
  • mysql-3.23
  • perl-DBI-1.32
  • perl-DBD-MySQL-2
  • disstcc client, server, and gui rpms
  • ghostview - gv-3.5.8-22
  • dia-0.94
  • boost-1.33.1 and boost-devel


Manual Configuration Details

These configuration specifics can be used to configure a machine that does not have access to the kickstart post-install script. They can also be useful when modifying any of the configurations or configuring a single service. All of these configurations are done automatically during the post-install run of install_all.sh.
  • User Accounts
    • All linux home directories live on s1.cs.nyu.edu at: s1:/s1/export/home/[username]
    • The linux machines mount these home directories via NFS.
    • /etc/fstab needs to be edited to contain the intended mount points for each user:
             Ex ( s1:/s1/export/home/someuser     /home/someuser    nfs     defaults      0 0 )
             
    • User account names/id's (uids) and group names/id's (gids) must match those on s1.cs.nyu.edu if the user intends to mount their home directory off s1.
  • Printer Setup
    • access to all the 7th floor printers
    • access to any local printers that might be connected to the machine.
    • Setup Samba if any windows machines need access to the local printer.
  • Condor Setup
    • Before installing Condor, you need to create a user with username 'condor'
    • install into /usr/local/condor
    • s1.cs.nyu.edu should be defined as the condor master
    • make sure condor starts at boot time by placing a start file in the appropriate rc directory (usually rc5.d/S96condor)
    • It is important for condor that each machine have a full /etc/hosts file with the names of each machine in the pool in lowercase!!!
    • A symlink to the config file must be placed in /home/condor
             ln -s /usr/local/condor/etc/condor_config /home/condor
             
    • Once condor is up and running, minor changes to START, SUSPEND, etc conditions might need to be modified in the condor_config.local file.
  • Update Setup
    • Set updates to be executed automatically every night and allow the updates to follow dependencies automatically.
  • Yum Setup
    • Edit the config file to update kde packages:
      [kde-redhat-kde-stable]
      name=kde-redhat.org (kde-stable)
      baseurl=http://apt.kde-redhat.org/apt/kde-redhat/redhat/el3/stable
      
      [kde-redhat-kde-stable-all]
      name=kde-redhat.org (kde-stable-all)
      baseurl=http://apt.kde-redhat.org/apt/kde-redhat/all/stable
           
    • Set yum update to be executed automatically every night.
  • Tripwire Setup
      This will need to be installed manually. Nothing special in the rules. I still hav not found a good way to automatically update the configurations as the specifics of each machine change.
  • Backups
    • Back-up scripts for non /home-dir locations should be placed in the user's home directory. (Ex:c5:/private)
    • I will run a check script for your private back-up if you ask me to.
  • Sendmail Config
    • Add the following line in /etc/sendmail.cf:
      DMcs.nyu.edu
      This ensures that your machine will masqerade as cs.nyu.edu instead of machine.cs.nyu.edu for any mail send from the local machine. This is very usefull if you like to send email from the command line on your local machine.
  • Graphics Card Setup
    • Machine c2 has a newer NVIDIA graphics card that needs some special software to work under linux. Go to their driver page at:
      http://www.nvidia.com/content/drivers/drivers.asp
      Get the latest Linux Display Driver - IA32 as a run file, and follow the instruction included from there.
    • All other cards in the lab are happy with the drivers provided in the RedHat install.


Specific Configuration Files + Kickstart Files

  1. Retrieve the floppy disks labeled "ks" and "net" in the box labeled "software" on the shelf in room 712 @ 719 Broadway. Once you have these 2 disks you may want to modify the file called ks.cfg on the "ks" disk so that it gives the new machine an appropriate IP address (set this to the one the machine has been assigned)
  2. shutdown the machine
  3. put the disk labeled "ks" in the floppy drive
  4. turn the machine on
  5. at the boot prompt type linux ks=floppy
  6. come back in about 20-30 minutes
  7. now that you have a basic install you will need to run the post-install script


The Chicken

We have been fortunate enough to borrow cycles from the renowned "Chicken". The Chicken is a cluster of 32 diskless machines and you will need to get special permission to obtain an account. There are a few basic facts that will enable you to get started using this resource.
  • Only the head machine of the chicken is accessable from the general internet and then only from machines that have been given access. This machine is named coop.cs.nyu.edu This machine has the only harddisk in the cluster and contains the directories that the diskless machines use.
  • The root directory for the diskless machines is located on coop in /clusterRoot.
  • Each of the diskless machines is named c1-c32 and can be located at the corresponding ip address


Emergency Instructions

If you are unfortunate enough to have a harddisk failure while Ali is away, she has created a backup installation that can be swapped in at a moments notice. The only thing you will probably need to change is the ip address/hostname of the install. The following instructions should help you get the job completed without incident:
  1. Have Lourdes let you into room 712 at 719 Broadway.
  2. On the desk directly in front of the door sits a hard disk labeled 'Emergency'. Next to the disk is a note pointing you to this page for further instructions. Get the disk.
  3. You will probably need a screwdriver to do the swap; get one from the box on the shelf labeled 'tools'.
  4. Take your machine down as safely as possible.
  5. Unplug the machine
  6. Open the case by removing the side panel
  7. Ground yourself by touching the metal part of the case with both hands
  8. Remove the ide cable and the power cable from your disk, unscrew it, take it out.
  9. Put the new one in the case, screw it in (don't bother putting screws on both sides one will work just fine.)
  10. Attach the cables just as they were before (red stripe on the ide cable always points toward the power cable)
  11. Replace case side, plug in, and reboot
  12. The disk is currently configured to be c3.cs.nyu.edu, so unless you happen to be replacing a disk on c3 you will need to change the ip address and hostname.
  13. edit /etc/sysconfig/network to contain the correct hostname
  14. edit /etc/sysconfig/network-scripts/ifcfg-eth0 to contain the correct ipaddress. If you are not sure what it should be do a ping of the hostname on another machine, it will do a reverse dns lookup and show you the ip address it is trying to ping. Of course the ping will fail, but that doesn't matter.
  15. Plug the cable back in and issue the commands : /sbin/ifdown eth0; /sbin/ifup eth0
  16. Your network will work fine now. There are a few programs that need to know the correct host/ip info at install time, condor is one of these and hence will have the wrong configuration at this point.