0123456789
----------
         t =sticky bit, executable for others
         T =sticky bit, not executable for others
         x =executeable for others.
        w  =writable for others
       r   =readable for others
      s    =sgid bit, executable for group owner
      S    =sgid bit, not executable for group owner
      x    =executeable for group owner
     w     =writable for group owner
    r      =readable for group owner
   s       =suid bit, executable for owner
   S       =suid bit, not executable for owner
   x       =executeable for owner
  w        =writable for owner
 r         =readable for owner
d          =directory

Sticky Bit on Directories
=========================
files inside the directory may be renamed or removed only by the owner of the file, the owner of the directory, 

or the superuser (even if the modes of the directory would otherwise allow such an operation). (HP-UX)

Sticky Bit on Executable Files
==============================
the file does not leave swap space once it terminates upon its next execution. when it is executed again by any 

user, it is read from the swap space, thus speeding up its execution. (HP-UX)

Sticky Bit on Non-Executable Files
==================================
?

Sticky Bit on Remote Executable Files
=====================================
tells the system to page the text to the local disk. Otherwise, it is "retrieved" across the network. Of course, 

this would only apply when there is actual paging occurring. (HP-UX)

Sticky Bit on Symbolic Links
============================
A symbolic link sticky bit set'd is called a transition link (i.e. links to ease the transition to the new
SVR4 filesystem layout).  Transition links are a bit faster, because  the linked-to filename is stored in the 

inode itself, instead of using an allocation unit to store the link. In order to set the sticky bit on a symlink, 

one must use the undocumented lchmod system call (i.e. lchmod("/bin", 041777)).

SUID bit on Direcotries
=======================
Nothing

SUID bit on Executable Files
============================
execute with the permissions of the owner of the file.

SUID bit on Non-Executable Files
================================
Nothing

SGID bit on Direcotries
=======================
new files and direcotries created within will be owned by the group who owns the directory

SGID bit on Executable Files
============================
File executes with group permissions of the group owner

SGID bit on Non-Executable Files
================================
Nothing

Executable bit on Direcotries
=============================
Ability to read or modify contents

Write bit on Direcotries
========================
Ability to add or Delete Files

Read bit on Direcotries
=======================
Ability to arbitarily list/modify/read/remove contents without full path names