InstallFest 44 will be on Saturday, April 3rd, 2010, in Skiles room 257 from 11 AM to 5 PM.
Directions
The Skiles Classroom Building is off of Cherry Street, near the Georgia Tech Library. A map (provided by the Georgia Tech Alumni Association) can be found below.

Parking for the InstallFest is becoming more and more difficult, with the closure of several useful nearby parking lots. If you have a GT parking permit, the W01, E41, E44, and E40 (Klaus deck) lots are the closest to the Skiles building. If you do not have a GT parking permit, the best place to park is in the Area 2 visitor parking, next to the Student Center, or, if you only need to stop by for a moment, there are nearby parking meters.

Skiles room 257 is in the northeast corner of the building. Signs will be posted to direct people to this room.
Distributions
Linux comes in many “flavors” called distributions, each geared towards a different type of user. This article has more information about Linux basics, including what a distribution is. Below is a list of distributions available. For more information about the various distributions, try the following outside links:
Linux.com
LinuxLookup
Linux.org
At the InstallFest, we will have most major distributions available. However, if you are not sure if we will have what you want, it cannot hurt to burn the bootable ISO for that distribution to a CD before coming. We will have recordable media at the Installfest, too, so if you do not have time to burn it, we can do it for you.

If you are unsure of which distribution you want, don’t worry! We will set you up with an easy-to-learn distribution of Linux (most likely Ubuntu or Red Hat). If you require Linux for a class, you will most likely need Red Hat Enterprise Linux. However, you should still check with your professor or TA to make sure.

Getting Ready
To learn how to prepare your system for the InstallFest, click here (don’t worry, it’s not difficult!). The most important thing to do is back up your data beforehand (in the unlikely event that something goes wrong).

Bip

• Bip
• Setup

IRSSI

• IRSSI
• IRSSI Scripts
• Twitter for IRSSI

Other

• Bitlbee
• Eggdrop

“svn”
by Matthew Amidon

March 3rd, 2010, 7:00 PM
College of Computing Building, room 16

Overview:

Subversion, aka SVN, is a popular open source version control project. Used in
many many open and closed source projects. Tonight’s presentation will focus on
how to properly set up, manage, and use SVN across a network with optional SSH
encryption.

Upcoming meetings:

– 2010.03.10: IRC
– 2010.03.17: Music Encoding
– 2010.04.03: Installfest 45

Hope to see you there!

1. Overview:

git is a free and open source, distributed version control system designed to
handle everything from small to very large projects with speed and efficiency.
It was originally designed for Linux kernel development, but is now used on all
sorts of projects. It is very different from conventional version control
systems like cvs or svn, and this presentation will explain the differences, as
well as give a tutorial on how to use git to its full potential. Topics that
will be covered will include basic usage of git, git emulation of cvs servers,
integration with Eclipse, and more advanced use of git.

2. Basic git commands

• $ git init .

  create a git repository in the current directory

• $ git add .

  add files to repository (before commit)

• $ git commit [-a]

  commit files; -a flag specifies to include all modified files

• $ git log

  get the log of a particular file (if specified)

• $ git diff [--stat --summary -p]

  get diffs of files; given options increase output

• $ git show

  get information on most recent revision set

• $ git show $revision

  get information on given revision (e.g. HEAD)

It was discovered that the –color option is applicable to all of these commands, which could be useful if you are a Gentoo ricer. It is also important to note that ‘git commit’ will only commit files which you have told it to; when you modify a file, you have to run ‘git add $modified_file’ so that it gets checked in. The ‘-a’ flag to ‘git commit’ will automatically add all modified files.

For revision arguments, you can add modifiers to the end. For instance, HEAD^ refers to the revision before head, and HEAD^^ refers to the revision before that, and so on. There are more shortcuts, that is just one useful one.

3. Branching projects

One of the things git is known for is how easy it is to branch projects. Here is a list of commands useful for related tasks:

• git branch

  list branches currently available (‘*’ next to currently used branch)

• git branch $name

  create a branch with name $name

• git checkout $name

  switch working environment to branch $name

The ‘git checkout’ command will update all of the files in your project to the newly selected branch. Once you have two divergent branches, you can merge back together with

git merge $branchname

which will merge $branchname into the current working branch.

Once you are done with a branch, you can delete it with

git branch -d $name

git branch -D $name

where the ‘-D’ option will not prompt you if the branch has not yet been merged back in.

Now, suppose you are using ‘git show HEAD^’ right after a merge, which gives you the history of the last revision… but only in the main branch. You can do ‘git show HEAD^2′ to show the other parent revision. The ‘gitk’ program provides a neat interface for looking at branching and merging tree hierarchies.

4. Cloning repositories

Most projects that use git do not use a strictly peer-to-peer distributed model but instead have one main repository that contains the most up-to-date code. You will see commands like

git clone $repositorylocation

which will get the most up to date version of that repository (similar to ’svn checkout $repolocation’). Once you have cloned and made modifications locally, you can push them back to the origin with

git push origin

but only if you have write permissions to that repository. If you do not, someone who does will have to pull with

git pull $remoterepolocation

A long interactive tutorial was given on how to set up environments like this.

Visualization Software

There are many programs that make viewing git trees neat.

• $ git instaweb

• gitweb
• gitk
• gource
• and so on…

See this neat video of gource in action: