YETIcode

Free Scripts and Dubious Miscellany

Download:
YETIcode v. 4.20.45.0
packaged on Friday May 09 2008 06:32:16 AM

YETI contains the following collections:

• CLAM Makefile System    -- Portable software build tools based on GNU Make.
• Perl Scripts    -- Supports recursive diff-ing and handy file archiving.
• Bash Scripts    -- Numerous other scripts for a variety of purposes.
• Javascript Code    -- A few scripts, plus a dynamic tree script from elsewhere.
• Example Configuration files    -- Unix configuration files for cron, dhcp, named (dns), and others.
• Quake3 Game Scripts    -- Example scripts for running a server with rotating game levels.
• Raw Yeti Shell Scripts Directory    -- For the curious; the folder where bash and perl scripts reside.

Setting up the Yeti: A Quick Start Guide in Four Steps (and a few sub-steps)

1. Get the YETIcode archive:
1. Option A: See way above for download link and unpack the archive to your ~/yeti folder (c:/yeti for windows).
   
2. Option B: Get YETI through cvs at SourceForge:  (hit Enter when asked for a password)
1. cvs -d:pserver:anonymous@hoople-org.cvs.sourceforge.net:/cvsroot/hoople-org login
2. cvs -z3 -d:pserver:anonymous@hoople-org.cvs.sourceforge.net:/cvsroot/hoople-org co -P yeti
2. Initialize the YETI support:
1. bash ~/yeti/shells/bootstrap_shells.sh
3. Hook up the yeti scripts: (enter the text lines verbatim)
   
1. Option A: Activate yeti automatically on shell startup (please do not do this for root):
   vi ~/.bashrc
   G
   :r ~/yeti/shells/bashrc_user
   :wq
   
2. Option B: Turn yeti on only when the yetime alias is invoked (it's okay for root to have this):
   vi ~/.bashrc
   G
   :r ~/yeti/shells/bashrc_root
   :wq
   
4. Restart your shell environment (quit bash or command or 4nt prompts):
   
1. Once you logout and log back in, the updated aliases and variables in the yeti startup scripts should be in effect.
2. If you chose approach 3.2 above, then entering the command "yetime" will enable all the aliases.
3. Windows shell users (4nt, cmd, etc) may have to configure the doslogin.bat to start automatically.  For example, 4nt users can set the 4start.bat file (in the option dialog) to the auto-generated $GENERADIR/4start.bat.