All labs will be held in the Engineering Building, room G-7. The G-7 lab has badge access. Your BU ID should be coded to allow access. You may use the G-7 lab at any time, as long as another lab is not in session. (See the schedule outside the door.)
Lab Sections are as follows:
| Section | Schedule | Monitor |
|---|---|---|
| A51 | Tue 10:05 AM - 11:30 AM | Ozgur Kilic |
| A52 | Tue 11:40 AM - 1:05 PM | Ozgur Kilic |
| A53 | Tue 1:15 PM - 2:40 PM | Dinal Herath |
| B54 | Tue 2:50 PM - 4:15 PM | Dinal Herath |
| B55 | Tue 4:25 PM - 5:50 PM | Piush Sinha |
| B56 | Tue 6:00 PM - 7:25 PM | Piush Sinha |
You will need an LDAP userid and password to log on to the machines in the G-7 lab. Your LDAP userid is the same as your PODs userid (or bmail id). You should have received an initial LDAP system password via email. To change passwords or manage your LDAP account, start at the LDAP System Administration Page. (Note... there is an on-line G-7 Classroom Calendar link from this page as well.)
We prefer it if you use the desktop machines in G-7 to do the labs so that we are all working on the same base, but you may use your own laptop as long as you can run a version of UNIX, and you are responsible for any differences between your installation and the LDAP system UNIX available on the machines in G-7. However, even if you are not using the G-7 hardware, we still expect you to be present in G-7 so you can ask questions and get extra instructions from the TA's.
You will need a GIT userid for this course. If you do not already have a GIT userid, get one at https://github.com/join. You do not need a paid GitHub account for this class - a free account works fine. Here's a tutorial link for getting a GitHub account. You will need to let us know what your GitHub userid is so that we can register in myCourses (See Grade Center, GIT ID column). Contact the professor and/or your TA to registered or update your Git userid. Lab submissions will be considered late if you do not have a GitHub userid registered when the TA's grade a lab.
| Date | GitHub Classroom Invitation | Solutions |
|---|---|---|
| Jan 22 | Lab Cancelled - Too early | - |
| Jan 29 | Lab 01 - LeftBit | Solution |
| Feb 05 | Lab 02 - Float Multiplication | Solution |
| Feb 12 | Lab 03 - GDB Deep Dive | Solution |
| Feb 19 | Lab 04 - Linked Lists | Solution |
| Feb 26 | Lab 05 - Visualized Arrays | Solution |
| Mar 05 | Lab 06 - Hunting Wumpus | Solution |
| Mar 12 | Lab 07 - Encode/Decode Revisited | Solution |
| Mar 26 | Lab 08 - X86 Memory Access | Solution |
| Apr 02 | Lab 09 - X86 Switch | Solution |
| Apr 09 | Lab 10 - X86 Stack | Solution |
| Apr 16 | Lab 11 - Simple Buffer Overflow Attack | Solution |
| Apr 23 | Lab 12 - Rock/Paper/Scissors Tournament | Solution
Section A tournament Section A grand tournament Section B tournament Section B grand tournament |
| Apr 30 | Lab 13 - Cache Simulation | Solution |
If gitHub accept is not completing for a long time (like more than an hour or so), try the following:
This will not always resolve the problem, but often will get you back in the GitHub queue instead of staying in limbo and never completing.