[http://freeengineer.org/learnUNIXin10minutes.html Learn UNIX in 10 Minutes] is a quick overview of the most commonly used Linux commands.

+

+

[http://lifehacker.com/5935869/top-10-tools-that-are-better-in-the-command-line?utm_campaign=socialflow_lifehacker_twitter&utm_source=lifehacker_twitter&utm_medium=socialflow Top 10 Tools] is a nice summary of 10 of the most useful Linux commands.

=== Quick Tips ===

=== Quick Tips ===

Line 12:

Line 33:

! Description

! Description

|-

|-

−

| <pre>$ gnome-open</pre>

+

|

+

beagle$ '''gnome-open'''

| Open a file or directory using the default program

| Open a file or directory using the default program

|-

|-

Line 21:

Line 43:

| If you invoke gdb with the command line argument -tui, it will show a built-in GUI

| If you invoke gdb with the command line argument -tui, it will show a built-in GUI

|-

|-

−

| <pre>$ ntpdate pool.ntp.org</pre>

+

|

−

| This will go to a '''n'''etwork '''t'''ime '''p'''rotocol server and get the current time and set the Beagle to it.

| This will go to a '''n'''etwork '''t'''ime '''p'''rotocol server and get the current time and set the Beagle to it and set the local time zone. [http://derekmolloy.ie/automatically-setting-the-beaglebone-black-time-using-ntp/]

+

|-

+

|

+

beagle$ '''mount -t debugfs debugfs /sys/kernel/debug/'''

+

beagle$ '''cd /sys/kernel/debug'''

+

beagle$ '''ls'''

+

| Kernel Debug Info

|}

|}

+

+

=== Connecting to RHIT wifi ===

+

+

There is a discussion in the [https://groups.google.com/forum/?fromgroups=#!topic/beaglebone/9PEUmcsLXLU Beagle Google Group] about getting wireless working with the bone.

+

+

Use these settings for connecting to the Rose-Hulman wireless network:

+

+

* '''SSID:''' RHIT-1X

+

* '''Security:''' WPA & WPA2 Enterprise

+

* Leave "anonymous identity" blank

+

* '''CA Certificate''': (None)

+

* '''PEAP version''': Version 0

+

* '''Inner authentication''': MSCHAPv2

+

* Use your Rose username and password

=== bash ===

=== bash ===

Line 52:

Line 98:

When using ssh between to X-windows systems try

When using ssh between to X-windows systems try

−

<pre>

+

host$ '''ssh -CX root@beagle'''

−

host$ ssh -CY root@beagle

+

−

</pre>

+

The -X set the DISPLAY variable on the remote machine so you can open windows from the beagle on your host machine.

−

The -Y set the DISPLAY variable on the remote machine so you can open windows from the beagle on your host machine.

+

The -C compressed the data over the link. Good for slow connections.

The -C compressed the data over the link. Good for slow connections.

Line 62:

Line 107:

You can run a vnc server on the Beagle. Install it with:

You can run a vnc server on the Beagle. Install it with:

−

$ opkg update

+

beagle$ '''opkg update'''

−

$ opkg install x11vnc

+

beagle$ '''opkg install x11vnc'''

Install a password with

Install a password with

−

$ x11vnc -storepasswd

+

beagle$ '''x11vnc -storepasswd'''

Run it on the Beagle with

Run it on the Beagle with

−

$ x11vnc -display :0 -ssl -usepw -forever -q &

+

beagle$ '''x11vnc -display :0 -ssl -usepw -forever -q &'''

On your host, connect to it with:

On your host, connect to it with:

−

host $ vinagre

+

host$ '''vinagre'''

or '''Applications:Internet:Remote Desktop Viewer'''

or '''Applications:Internet:Remote Desktop Viewer'''

==== Authorizing ssh ====

==== Authorizing ssh ====

−

<span style="color:red">Note: This isn't currently working for me.</span>

+

'''ssh''' and '''scp''' can be set up for automatic authorization so you don't have to enter your password when using these commands. Here's how to do it.

+

First let's see what's already there:

−

'''ssh''' and '''scp''' can be set up for automatic authorization so you don't have to enter your password when using these commands. Here's how to do it:

+

* On your Beagle run

+

+

beagle$ '''ls ~/.ssh'''

+

+

'''~/.ssh''' may not exist, if not, it will be created. If it's there, check the files in it.

* On your host computer run

* On your host computer run

−

<pre>

−

host $ ssh-keygen

−

host $ cd ~/.ssh

−

host $ scp id_rsa root@beagle:.

−

host $ ssh beagle

−

</pre>

−

The first command creates an authorization key and places it in your .ssh directory. Remember the pass phrase you enter here. You'll use it below. The next two commands copy that key to your Beagle. The last command connects to your Beagle.

−

* On your Beagle run

−

<pre>

−

beagle $ mkdir ~/.ssh

−

beagle $ cd ~/.ssh

−

beagle $ mv ../id_rsa.pub .

−

beagle $ cp id_rsa.pub authorized_keys

−

beagle $ exit

−

</pre>

−

Here we create a '''.ssh''' directory and copy the public key into it. The authorized_keys folder contains a list of all the machines that are authorized to connect to your Beagle without a password.

−

* Back on the host computer:

−

<pre>

−

host $ ssh Beagle

−

</pre>

−

This time you should see a window pop up. Enter your pass phrase from above. You should be logged into your Beagle. Log out and log in again. This time you should get access without having to enter your pass phrase.

You'll see a command prompt. You'll also see some status information on the bottom two lines. Type Ctrl-A ? for help. Type Ctrl-A Ctrl-D to detach from the session. Running byobu again will reattach you to the session. Try running byobu in two windows at the same time. You should see the same session in both.

You'll see a command prompt. You'll also see some status information on the bottom two lines. Type Ctrl-A ? for help. Type Ctrl-A Ctrl-D to detach from the session. Running byobu again will reattach you to the session. Try running byobu in two windows at the same time. You should see the same session in both.

Line 187:

Line 290:

=== Finding what opkg installed ===

=== Finding what opkg installed ===

−

Once you've run opkg, how do you know what's been installed? Take a look in '''/usr/lib/opkg/info'''. The files that end in .list contain a list of what's been installed. ''bs'' is the block size and ''count'' is the number of blocks to copy. I've selected 4M*1000=4G.

+

Once you've run opkg, how do you know what's been installed? Take a look in '''/var/lib/opkg/info''' or '''/usr/lib/opkg/info'''. The files that end in .list contain a list of what's been installed.

=== Backing up an SD card with dd ===

=== Backing up an SD card with dd ===

Line 193:

Line 296:

Here's the command I use to backup an SD card. I use '''System:Administration:Disk Utility''' to figure out the path to the card. In this case it's ''/dev/sdc''

Here's the command I use to backup an SD card. I use '''System:Administration:Disk Utility''' to figure out the path to the card. In this case it's ''/dev/sdc''

The text and further instructions are available [http://csse.rose-hulman.edu/news-mainmenu-2/27-linux-distros/102-ubuntu here].

The text and further instructions are available [http://csse.rose-hulman.edu/news-mainmenu-2/27-linux-distros/102-ubuntu here].

The script makes a backup of the updates file and replaces it with links to our mirror. The $DISTRIB_CODENAME is replaced by whatever distro you are running (eg. lucid, maverick, natty etc.). I wish I could take credit for it, but it was a joint effort with Mike McLeish :-)

The script makes a backup of the updates file and replaces it with links to our mirror. The $DISTRIB_CODENAME is replaced by whatever distro you are running (eg. lucid, maverick, natty etc.). I wish I could take credit for it, but it was a joint effort with Mike McLeish :-)

+

+

=== Using pico DLP with BBB ===

+

+

Put this in uEnv.txt to use the BBB with a pico DLP.

+

optargs=video=HDMI-A-1:640x480@60

+

+

=== systemd journal taking too much time/space ===

+

+

If you are running out of space because of the systemd journal try [https://groups.google.com/forum/#!searchin/beagleboard/systemd-journal/beagleboard/1NguS-SK-G8/NGhAVlTerkkJ this Google Group Suggestion]

+

+

=== More tips ===

+

+

[http://www.gigamegablog.com/2012/01/29/beaglebone-linux-101-configuring-angstrom-linux/ GigaMegaBlog] has some nice tips for the BeagleBone, many of which apply to the -xM.

== Windows ==

== Windows ==

Line 231:

Line 350:

Most of the work is done under Linux; however there are some handy Windows-based tools.

Most of the work is done under Linux; however there are some handy Windows-based tools.

−

=== Tera Term ===

+

=== Serial Port ===

+

+

[http://www.vandyke.com/products/securecrt/ SecureCRT] is a good program that gives you both access to a serial port and is also an ssh client. Rose has a license for [http://www.rose-hulman.edu/tsc/software/documentation/applications/securecrt-secureFX/installation/ SecureCRT].

−

[http://www.tucows.com/preview/195282 Tera Term] give you access to the serial port.

+

[http://www.tucows.com/preview/195282 Tera Term] also gives you access to the serial port and it's free.

=== Notepad++ ===

=== Notepad++ ===

Line 240:

Line 361:

== Set up on the BeagleBoard ==

== Set up on the BeagleBoard ==

+

+

=== Setup stuff on github ===

+

If you've cloned the course github site ([EBC Exercise 05 Getting Exercise Support Materials]]) you will find set up things in '''exercises/setup'''. '''install.sh''' is a list of various things I to to a fresh SD card to 'move in'. For example, the bone will mount a filesystem on the host computer if it's connected via USB. You can turn this off and have the eithernet over USB run at boot time with:

+

+

# Turn off storage gadget, turn on network at boot time.

+

cd /lib/systemd/system/basic.target.wants

+

rm storage-gadget-init.service

+

ln -s ../network-gadget-init.service .

+

+

=== Accessing the Beagle via the Serial Port ===

+

+

During boot up the Beagle logs various messages on the serial port. You can see these messages by:

+

+

* See what USB/tty devices are already attached to your host

+

host$ '''ls /dev/ttyU*'''

+

* Attach a serial to USB converter to your host computer and the Beagle's serial port.

+

* See what new USB/tty devices appeared

+

host$ '''ls /dev/ttyU*'''

+

* On my host, '''/dev/ttyUSB1''' appeared. On the host computer run

+

+

host$ '''byobu /dev/ttyUSB''1'' 115200'''

+

where '''ttyUSB1''' is what appeared when you plugged in your converter.

+

+

You are now talking to your Beagle's serial port. Login quickly. There appears to be a bug that makes garbage appear on your screen if you wait too long. Try

+

beagle$ '''shutdown -r now'''

+

+

You will see the shutdown messages, followed by the U-boot messages. After a 3 second (or so) delay you will see the kernel booting.

+

+

'''Tip 1''': Ctrl-a H will cause the data on the serial port to be logged. See

+

host$ '''man byobu'''

+

for help.

+

+

'''Tip 2''': <F6> will disconnect from the session. You can reconnect later.

# On the 'Wired' tab, select 'Auto eth0' and click 'Edit' (Note: name may be other than 'eth0'. If nothing exists in this list, then make sure there is '''not''' an entry starting with 'auto eth0' in your /etc/network/interfaces file; such an entry prevents Network Manager from managing that interface.)

+

−

# Click the 'IPv4 Settings' tab and change 'Method' to 'Shared to other computers'

+

−

# Click apply

+

−

# Restart Ubuntu

+

−

# Connect the BeagleBoard to the laptop with the crossover Ethernet cable

+

−

# Boot the BeagleBoard - if Ubuntu was already running and the Ethernet cable was already plugged in, the BeagleBoard should automatically get assigned an IP address and you should be able to access the Internet on the BeagleBoard via the laptop's wireless connection

+

−

+

−

==== Option 2 - Modifying Things Yourself (DHCP Server) ====

+

−

+

−

This will setup a DHCP server on the host machine that will listen to the Ethernet port and assign an IP address to the BeagleBoard when it is connected with an Ethernet crossover cable. The host machine will then act as a router using NAT to send packets out the wifi interface.<br />

+

−

A number of steps were taken from the [https://help.ubuntu.com/community/Internet/ConnectionSharing Ubuntu Community Documentation].<br />

+

−

Notes:

+

−

* 'eth0' will refer to the internal interface (connected to the BeagleBoard) and 'wlan0' will refer to the external interface (connected to the Internet). Your interface names may differ.

+

−

* A number of configuration files are changed. It's a good idea to save a backup copy of these before modifying them.

+

−

+

−

On the host machine, configure eth0 for a static IP:

+

−

<pre>sudo ifconfig eth0 192.168.1.13</pre>

+

−

If you don't want to configure this after every boot, add an entry to /etc/network/interfaces with the following:

+

−

<pre>

+

−

auto eth0

+

−

address 192.168.1.13

+

−

netmask 255.255.255.0

+

−

network 192.168.1.0

+

−

broadcast 192.168.1.255

+

−

</pre>

+

−

+

−

On the host machine, configure the IP tables to use NAT translation for routing packets:

range 192.168.1.14 192.168.1.14; #<--You can specify a larger range; I used this to force my BeagleBoard to always have the same IP so I could add an entry for that IP in /etc/hosts

+

−

}

+

−

</pre>

+

−

You may need to edit /etc/default/dhcp3-server to specify the interface for the DHCP server

+

−

<pre>INTERFACES="eth0"</pre>

+

−

Then restart the DHCP server service

+

−

<pre>sudo service dhcp3-server restart</pre>

+

−

+

−

You may need to reboot your host machine, and it may be necessary to run the command above to restart the DHCP server every time you boot (I'm not sure if it starts appropriately at boot).

+

−

+

−

Now connect the BeagleBoard to the host machine with a crossover Ethernet cable and boot the Beagle. After booting, run 'ifconfig' to see if the Beagle was assigned an IP address. If it does not have an IP address, try running the command 'dhclient usb0'.

+

−

+

−

Once the Beagle does have an IP address, try

+

−

<pre>ping -c 3 -W 10 www.google.com</pre>

+

−

to test if the setup is working correctly. If it complains about a bad name, the DNS servers are incorrect; try pinging a specific IP such as 8.8.8.8 to see if packets get through (though unless you want to rely on all IP addresses, you will need to get some DNS servers that work).

+

−

+

−

==== Option 3 - Manual Routing, Static Beagle IP ====

+

−

+

−

This will setup the routing on Ubuntu (sending all eth0 traffic out wlan0). It will then set a static IP address on the BeagleBoard (so you can stick an entry for your BeagleBoard in /etc/hosts for convenience). The key difference from Option 2 is that the DHCP server in that option supplied the BeagleBoard with DNS servers. In this option, we add a script that gives the BeagleBoard some static DNS server addresses every time it boots.

+

−

+

−

First, follow through the steps in Option 2 right up until it starts talking about installing the DHCP server. Instead of installing the DHCP server, do the following.

+

−

+

−

On your BeagleBoard, add the following entry to <code>/etc/network/interfaces</code> (comment out any pre-existing entries regarding 'usb0')

+

−

<pre>

+

−

auto usb0

+

−

iface usb0 inet static

+

−

address 192.168.1.14 # This is the static IP address of your choice

+

−

netmask 255.255.255.0

+

−

network 192.168.1.0

+

−

gateway 192.168.1.13 # This must match the static IP address you assigned to eth0 on your host machine

+

−

</pre>

+

−

After booting, the BeagleBoard is now configured with a static IP address and knows the gateway for all its traffic is the address of your host machine. The last thing to do is to make sure your BeagleBoard knows what DNS servers to use. This information is stored in the <code>/etc/resolv.conf</code> file. You could add it manually every time after boot, but we'll make a script to do it at boot instead.

+

−

+

−

On your BeagleBoard, navigate to the /etc/rc5.d/ directory. In this directory, create a file named <code>S99<name></code> where <code><name></code> can be anything you prefer. My file was named <code>S99SetRoseHulmanNameServers</code>. Add the following inside that file:

echo "nameserver 137.112.5.28" >> /etc/resolv.conf # Replace them with whatever DNS servers you are using

+

−

echo "nameserver 137.112.12.11" >> /etc/resolv.conf

+

−

</pre>

+

−

That should be it. Assuming all cables are connected properly and you have a WiFi connection on the host machine, after booting the BeagleBoard should have a usable Internet connection.

+

=== Using u-boot to specify a MAC address at boot ===

=== Using u-boot to specify a MAC address at boot ===

−

The BeagleBoard has a problem where Linux will randomly select a MAC address at boot. In order to get around this, [http://maxgalemin.blogspot.com/2010/11/patch-for-fixing-random-mac-address-on.html one blogger] provides a patch to enable a kernel command line parameter to set a MAC address. Below is one way to apply, your mileage may vary.

+

The BeagleBoard has a problem where Linux will randomly select a MAC address at boot. In order to get around this, [http://blog.galemin.com/tag/random-mac-address/ one blogger] provides a patch to enable a kernel command line parameter to set a MAC address. Below is one way to apply, your mileage may vary.

([http://embeddedgeeks.wordpress.com/2012/01/03/belkin-micro-wifi-usb-dongle-on-the-beagleboard/ Here] are instructions on setting up a Belkin USB dongle.)

+

+

The device I used to setup a wireless connection on the Beagle Board was the Linksys Compact Wireless-G USB Network Adapter with SpeedBooster.

+

+

I first opened the wpa_supplicant.conf file to setup my networks:

+

+

beagle$ '''cd /etc'''

+

beagle$ '''gedit wpa_supplicant.conf &'''

+

+

This file is filled with numerous examples of possible wireless configurations for you to basically fill in. After looking at the examples, I scrolled down to the bottom of the page and set up two networks: one for home and one for school. Here are examples of my setup networks:

+

<pre>

+

#Home Network

+

network={

+

ssid="YourHomeNetworkName"

+

psk="YourHomeNetworkPassword"

+

}

+

+

#School Network

+

network={

+

ssid="RHIT-1X"

+

proto=WPA

+

key_mgmt=WPA-EAP

+

pairwise=CCMP

+

group=TKIP

+

eap=PEAP

+

phase1="peapver=0 peaplabel=0"

+

phase2="auth=MSCHAPV2"

+

scan_ssid=1

+

identity="YourSchoolUsername"

+

password="YourSchoolPassword"

+

}

+

</pre>

+

For the network examples above,the quotation marks actually belong there but replace the Your.... areas with your corresponding information. No <space> before the first quotation mark.When finished editing save and exit this file.

+

The information for the RHIT school network was found here:[http://lug.rose-hulman.edu/wiki/RHIT-1X RHLUG]

+

+

Now you must specify that this is the file to use for the wireless device:

+

+

beagle$ '''cd network'''

+

beagle$ '''gedit interfaces &'''

+

+

This file will display all of the different types of Internet connections you have setup.

+

To use the wpa_supplicant.conf file, scroll down to around line 42 of the code and uncomment the configuration for wpasupplicant. After doing this make sure all of the above lines mentioning anything about wlan0 are commented out. Return back to where it says "iface wlan0 inet dhcp" that you uncommented around line 42.

+

Add "auto wlan0" above this line, make sure the line "wpa-conf /etc/wpa_supplicant.conf" is uncommented below the iface line, and change the wpa-driver line below that line to wext. So after all of that the code in this file for the wireless device should be the following:

+

<pre>

+

auto wlan0

+

iface wlan0 inet dhcp

+

wpa-conf /etc/wpa_supplicant.conf

+

wpa-driver wext

+

</pre>

+

NOTE: the auto wlan0 command in this file means that this device will load at boot time. You can take the time in here now to comment out any interfaces you don't use like auto usb0 to make these devices not load at boot time, which will increase the speed at which you boot up.

+

Save and exit this file

+

+

Once you have finished this you can either restart the Beagle Board or:

+

+

beagle$ '''cd'''

+

beagle$ '''/etc/init.d/networking restart'''

+

+

I've found that a lot of the time the interface doesn't receive an IP address when it boots up. If you run ifconfig in the terminal you should see your wireless device connected to a network. If it is connected but no IP address I do the following:

+

+

beagle$ '''ifdown wlan0'''

+

# it will report messages here and then

+

beagle$ '''ifup wlan0'''

+

# more messages and it should report connecting and having an IP address

+

+

This ifdown ifup method has worked every time for me so far but if anyone can find a way to prevent having to do this almost every time please feel free to edit this

The green dot in the S column says the package is installed. libncurses5-dev isn't installed. Install it with:

host$ sudo apt-get install libncurses5-dev

And now your make should work.

byobu - A Screen Manager

For years Unix has had screen which is a screen manager. byobu is wrapper for screen that puts a nice face on it. You can run byobu on your host computer and on the Beagle. With byobu you can start a long running program (bitbake for example) in one terminal and detach from the terminal and the program will keeping running in the background. Using byobu you can later attach to the program (possibly from another terminal) and see how the program is progressing.

You'll see a command prompt. You'll also see some status information on the bottom two lines. Type Ctrl-A ? for help. Type Ctrl-A Ctrl-D to detach from the session. Running byobu again will reattach you to the session. Try running byobu in two windows at the same time. You should see the same session in both.

Hmmm.... I had to reinstall and it doesn't seem to be working now.

Finding what opkg installed

Once you've run opkg, how do you know what's been installed? Take a look in /var/lib/opkg/info or /usr/lib/opkg/info. The files that end in .list contain a list of what's been installed.

Backing up an SD card with dd

Here's the command I use to backup an SD card. I use System:Administration:Disk Utility to figure out the path to the card. In this case it's /dev/sdc

The script makes a backup of the updates file and replaces it with links to our mirror. The $DISTRIB_CODENAME is replaced by whatever distro you are running (eg. lucid, maverick, natty etc.). I wish I could take credit for it, but it was a joint effort with Mike McLeish :-)

Notepad++

Set up on the BeagleBoard

Setup stuff on github

If you've cloned the course github site ([EBC Exercise 05 Getting Exercise Support Materials]]) you will find set up things in exercises/setup. install.sh is a list of various things I to to a fresh SD card to 'move in'. For example, the bone will mount a filesystem on the host computer if it's connected via USB. You can turn this off and have the eithernet over USB run at boot time with:

Installing Ubuntu

The first link references a Ubuntu wiki which details how to install a netbook edition of Ubuntu on ARM/OMAP processor-based systems. It is not beagle-specific. This image runs a little slowly, but not much slower than the SPEd image.

The second link references instructions for installing another image. This image is very minimal, and doesn't have a gui. There are instructions for installing a gui, which I did, with good success. As far as I can tell, even with the gui, this is the fastest image so far.

Installing Always Innovating's Super Jumbo

Always Innovating works with branded products and services companies that are looking to deliver great touch devices as part of their offerings. They have published a free SD card image for the BeagleBoard that runs Angstrom, Android, Ubuntu, and ChromiumOS. Here's a video showing what it can do.

I've put a copy of the compressed image on my DFS site. Feal free to play with it. Here's a wiki that shows how to switch between OS's on the fly.

Resizing an SD card partition via the Beagle

The following is a slick way to boot the Beagle so it isn't using the SD, then repartition the SD card. It came from [2]

Jason Kridner says ...
I got a related question from Mark about how to perform the partition
resizing, so I figured I'd address that here. I don't believe you'd
be able to resize a mounted partition and that this operation would
require another file system to mount. Because this image does not
have the ramdisk, I downloaded the one used being shipped with the xM
boards today [3].

Sharing Laptop Internet Connection with BeagleBoard

Using u-boot to specify a MAC address at boot

The BeagleBoard has a problem where Linux will randomly select a MAC address at boot. In order to get around this, one blogger provides a patch to enable a kernel command line parameter to set a MAC address. Below is one way to apply, your mileage may vary.

Make sure your kernel compiles and boots.

Grab the patch, and open it with gedit

Open .../git/drivers/net/usb/smsc95xx.c

Go to line 64-ish, and look for a place to insert the first code with plus signs preceding each line. Remove the plus signs.

Go to 656-ish, and repeat for the other block of code.

Save and re-compile.

Install the new kernel as normal.

Edit the kernel command line. There are two ways to do this:

Edit the uBoot source and recompile

Go to u-boot, and edit ../include/configs/omap3_beagle.h

Change mmcargs, nandargs, and ramargs to include a parameter for "ethaddr=...", where ... is your MAC address.

Rename an External Storage Device

I ran out of space on my Linux (Ubuntu) partition, so I opted to do all my development on an external hard drive. This works just fine, except that the drive is labeled "Expansion Drive" and the space in there causes problems in some of the setup scripts. It is possible to add an entry in /etc/fstab that mounts the device with a certain name, but this is very cumbersome, for many reasons. Instead, I used this [1] very helpful guide to change the label on my external drive.

Setup a USB Wireless Device on Beagle

The device I used to setup a wireless connection on the Beagle Board was the Linksys Compact Wireless-G USB Network Adapter with SpeedBooster.

I first opened the wpa_supplicant.conf file to setup my networks:

beagle$ cd /etc
beagle$ gedit wpa_supplicant.conf &

This file is filled with numerous examples of possible wireless configurations for you to basically fill in. After looking at the examples, I scrolled down to the bottom of the page and set up two networks: one for home and one for school. Here are examples of my setup networks:

For the network examples above,the quotation marks actually belong there but replace the Your.... areas with your corresponding information. No <space> before the first quotation mark.When finished editing save and exit this file.
The information for the RHIT school network was found here:RHLUG

Now you must specify that this is the file to use for the wireless device:

beagle$ cd network
beagle$ gedit interfaces &

This file will display all of the different types of Internet connections you have setup.
To use the wpa_supplicant.conf file, scroll down to around line 42 of the code and uncomment the configuration for wpasupplicant. After doing this make sure all of the above lines mentioning anything about wlan0 are commented out. Return back to where it says "iface wlan0 inet dhcp" that you uncommented around line 42.
Add "auto wlan0" above this line, make sure the line "wpa-conf /etc/wpa_supplicant.conf" is uncommented below the iface line, and change the wpa-driver line below that line to wext. So after all of that the code in this file for the wireless device should be the following:

NOTE: the auto wlan0 command in this file means that this device will load at boot time. You can take the time in here now to comment out any interfaces you don't use like auto usb0 to make these devices not load at boot time, which will increase the speed at which you boot up.
Save and exit this file

Once you have finished this you can either restart the Beagle Board or:

beagle$ cd
beagle$ /etc/init.d/networking restart

I've found that a lot of the time the interface doesn't receive an IP address when it boots up. If you run ifconfig in the terminal you should see your wireless device connected to a network. If it is connected but no IP address I do the following:

beagle$ ifdown wlan0
# it will report messages here and then
beagle$ ifup wlan0
# more messages and it should report connecting and having an IP address

This ifdown ifup method has worked every time for me so far but if anyone can find a way to prevent having to do this almost every time please feel free to edit this

Run this git command to get access to this repository. (It took about 2 minutes at 6:20am.) Line 21 shows the hash tag for the build.

ANGSTROM_REPO_ID=24805033b1205acc35f8b4d75cc42f8b9c2a1b38

If we pull from this tag we will have the same files as were used to generate the SD image. So do the following

host$ git checkout 24805033b1205acc35f8b4d75cc42f8b9c2a1b38

This takes about 10 seconds.

Fixing Problems

Kernel Boot Problems

Here is a link with some suggestions of what to do if your kernel isn't booting properly.

Serial port garbage

If you are having trouble with garbage on the console, this might help. Sometimes the serial port times out. Most of the time it just generates some junk which can be cleared with CTRL-U or backspace. However, if it happens at the login prompt then getty thinks the terminal is 7-bit with parity (rather than 8-bit raw). If this happens and you continue to login the whole session appears to be scrambled - if you press CTRL-D you can login again provided you don't stop typing... :]
I have simply added the following two lines to root's .profile: