Dotfile

• Linux hides files beginning with a "."
  • ls -l vs ls -la
• Refers to configuration files in your home directory
  • .bashrc
  • .bash_aliases
  • .vimrc

.bashrc vs .bash_profile

• ~/.bashrc executed when using interactive shell that is not a login shell
• ~/.bash_profile executed only during login shell
• http://hacktux.com/bash/bashrc/bash_profile

.bashrc

• Usually sources system default (/etc/bashrc)
• Used to setup:
  • aliases
  • environmental variables (e.g., PATH)
  • system commands (e.g., ls --> ls -h --color=auto)
  • shell prompts
  • functions

NOT a dotfile

Did you know GEO/SCC file system keeps snapshots of your work?

ls -l .snapshots/

Aliases

System Commands

• alias ls='ls -h --color=auto'
• alias topu='top -u $(id -un)'
• check out default SCC/GEO alias for rm

Aliases

Sun Grid Engine

• alias qstatu='qstat -u $(id -un)'
• alias qshv='qsh -V -l h_rt=24:00:00'

Aliases

Movement

• alias chris='cd /projectnb/landsat/users/ceholden'
• alias landsat='cd /projectnb/landsat'
• alias cms='cd /projectnb/landsat/projects/CMS/'

Modules

Not necessarily recommended (why?), but...

host=$(hostname)
if [[ "$host" == "geo" || "$host" == "scc1" || "$host" == "scc2" ]]; then
    . /usr/local/Modules/default/init/bash
    source ~/.module
fi

Modules

And ~/.module:

module load python/2.7.5
module load gdal/1.10.0
module load R_earth/3.1.0

module load CCDCTools/_beta

PATH

Call your own scripts or programs:

if [ -d "$HOME/bin" ]; then
    PATH="$PATH:$HOME/bin"
fi

Shell Prompts

Current prompt:

ceholden@ceholden-lhome:~/Documents/ceholden.github.io/present/tips$ echo $PS1
\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\u@\h:\w\$

Shell Prompts

export PS1="\[$(tput setaf 2)\]\u@\h:\W\\$ \[$(tput sgr0)\]"

Shell Prompts

See http://bashrcgenerator.com/ or https://www.kirsle.net/wizards/ps1.html for generators.

Functions

"abusers"

function abusers() {
    qstat | awk 'NR > 2 { if ($5 == "r") print $4 " " $9 }' | sort | \
        awk '{ sums[$1] += $2} END \
        { for (i in sums) printf("%s %s\n", i, sums[i])}' | \
        sort -k2 -n -r
}
export -f abusers

Functions

Cluster job ID matching pattern...

function jidof() {

    pattern=$1

    jid=""
    for j in $(qstat -u $USER | grep $pattern | awk '{ print $1 }'); do
        jid="$jid $j"
    done
    echo "$jid"
}
export -f jidof

Functions

GDAL - from https://github.com/dwtkns/gdal-cheat-sheet

function gdal_extent() {
    if [ -z "$1" ]; then
        echo "Missing arguments. Syntax:"
        echo "  gdal_extent <input_raster>"
        return
    fi
    EXTENT=$(gdalinfo $1 |\
        grep "Upper Left\|Lower Right" |\
        sed "s/Upper Left  //g;s/Lower Right //g;s/).*//g" |\
        tr "\n" " " |\
        sed 's/ *$//g' |\
        tr -d "[(]" | tr "," " ")
    echo -n "$EXTENT"
}
export -f gdal_extent

Git

After doing so much work, why not back up your dotfiles?

Git

Very popular practice - http://dotfiles.github.io/

• Steal/borrow/get inspired by others
• Sync across computers
• Backup and track
• Share with others

Git

In general,

1. Create repository and clone to GEO
2. Move all dotfiles into repo folder
3. Symlink (ln -s) the files to previous locations
4. Git add, commit, and push

Git

"Homeshick" - makes symbolic linking of dotfiles easy!

https://github.com/andsens/homeshick

Mine

https://github.com/ceholden/dotfiles

Yours?

If you think of any neat dotfile tricks for GEO, please let me know.