Week 0 (pre-2013/08/29): Account Initialization, Linux Shell, Text Editors


Account Initialization

Make sure everyone in the team has set a password for their CAE/CSC domain account. This will be used for vCenter and for version control. If you can log into, your password has been set. If not, see Luke Jackson (ltjackson42) in BR 415, Mike Renfro (renfro) in CH 314, or Joel Seber (jlseber) in CH 301.

Get familiar with the Linux command line

Depending on how long it's been since you took Linux lab, and how much you remember, you'll probably need a refresher. One free resource for this is Zed Shaw's The Command Line Crash Course. Read it and complete its exercises. We won't be using a GUI on Linux by default.

Get familiar with a (better) Linux console-mode text editor

If you ever tried to use nano to write code, you may have been frustrated with its lack of automatic indentation, parenthesis matching, and other coding-related features. We'll be writing a fair amount of code in the Puppet configuration management system, some shell scripts, and possibly some Perl/Python/Ruby scripts or other code. Learn a console-mode text editor that offers better coding support. This would probably be either emacs or vim.

emacs has a built-in tutorial; you can access it on or on OS X by typing emacs at a command prompt, and then pressing CTRL-h followed by t. Follow the tutorial instructions from there.

vim has an online tutorial at

Assignment due by start of first lab

Everything listed above:

  1. make sure you can log in to your CAE/CSC account
  2. make sure you've gone through Shaw's tutorial (or have enough experience to fake it)
  3. make sure you're familiar with emacs or vim. There will be minimal nano usage here, and no GUIs.
Last modified 4 years ago Last modified on Sep 2, 2013, 3:04:18 PM