Mark Dalton

• Background:
  • Worked at Cray/SGI since 9/1991 to 5/2010.
  • Prior to that: At the University of Minnesota Molecular Biology Computing Center and in various molecular biology labs.
  • Educated in genetics, specifically gene expression/regulation in humans (ETS-2), insects (74EF) and various virus' (RSV, HIV).
• Linkedin Profile

Senior Linux/Unix support for Geosciences, Electrical Engineering, HPC - Tigress, PiCSCiE

• MarkDaltonReports - December 2010 November 2010 October 2010

• System Administration (installs, patches, updates)
  • Currently involves:
    • Firewall Configuration
    • LDAP, DHCP, NFS, Mailing list server, DNS support
    • Migrating away from our own LDAP, DHCP, mailing list server and DNS support
    • Web server and web maintenance.
• Support users with Linux/Unix systems.
  • Help decide on workstation and computing resource configurations.
  • Install/maintain systems.
• Printing support.
• Mailing lists (migration to OIT listservers)
• Firewall configuration (and removal).
• Programming: C, C++, Fortran, MPI
• Scripting: Perl, Python, Ruby, shell, PHP, HTML
• To support users in the needs they have.

• Linux/Unix system administration.
• Linux/Unix programming: C, C++, Fortran.
• Application Parallel programming, debugging, and optimization.
• Kernel programming debugging.
• Software evaluation
• Web development

• Evaluation of Bibliography software (both bibtex and PDFs)
• Migrating services:
  • Migrate to use of HPC-Tigress/PiCSCiE clusters
  • Migrating linux servers/desktops to PU_IAS Princeton University version of RedHat Enterprise or to Fedora
  • Web migration to a New server
    • To provide services like a wiki(s)
    • Web based forms
    • Updated software/server
  • Removal of the firewall
    • Then remove our services:
      • DHCP - use the universities DHCP server (must happen)
      • LDAP server - for accounts and simplicity of accounts.
      • Email server - migrate to OITs listserv (also allows others to maintain lists).
      • Decide regarding print server(s). Currently we have our own cups server.
      • Printing: There are concerns of print jobs getting sent.
  • Migrate some work to central servers (computing)
  • Centralize as much of the resources and use the resources more efficiently.
  • Support new projects, like a new display monitor based on Xibo

• MarkDaltonTests