CPSC 405 Lab Submissions
Labs are designed to improve your computer science skills and knowledge. The labs are a learn by doing component of our course and involve significant programming.
We have two types of labs. The majority of our labs are Xv6-based Labs. These labs are completed by adding code to Xv6, building, running, and testing your Xv6 code. We have a few Linux-based Labs. These labs are completed by creating standalone C programs that run on Linux.
Lab Questions
Most of our labs have questions that you must answer. Questions are in boxes (like this) with a light orange background.
- Questions are worth 25 points on the lab. Solving the programming problems is with 75 points.
- If you handwrite the answers to questions in a notebook or tablet, you can earn the full 25 points.
- If you type the answers to questions is a file, you can earn 15 points.
- Your answers must include both the question and your answer. You can abbreviate some of the question, but you must write enough so that the question is understandable.
- I will not read and correct your answers to questions. If you cannot find the answer, you must ask me or another student.
- Additionally, in the directory of your xv6-labs, create two files: answers-LAB.txt and time.txt. For the answers-LAB.txt file, the string LAB
corresponds to the lab you are submitting, and For example, answer-util.txt is the file for the util lab. I may use these files
if I run your code using your zip file submission. The answers-firstlab.txt is a blank file. The time.txt file contains
the number of hours you spent on the lab. Create the files by the following.
$ echo > answers-util.txt $ echo 8 > time.txt
Submitting Labs
Each student must submit their lab material on Canvas.
Each lab has two Canvas assignments in which you submit your lab material.
- Text File Assignment - you submit your (for example) lab-util-handin.txt file, which is described below. The Text File submission must show that the code is run on each individual's computer system.
- Zip File Assignment - you submit your (for example) lab-util-handin.tar.gz file, which is described below.
Zip File
The Zip file contains the source code, Makefile, etc., of your lab. The Zip file is submitted in the lab's Zip File Assignment on Canvas.
- Xv6: A zipped tar file of you lab code. The name tar is short for Tape ARchive, and in the
past magnetic tapes were used to archive files for safe keeping. The Linux utility tar
creates tar files.
- To create the zipped tar file, run make tarball in your lab directory, which creates (for example) the file lab-util-handin.tar.gz, where util is the name of the lab. The name of the .tar.gz file depends upon the lab. Submit this file on Canvas.
- Linux A Zip file of your directory. Submit the resulting .zip file to Canvas.
The following image shows Ken Thompson (sitting) and Dennis Ritchie using a PDP-11 computer. They began Unix development on a PDP-7, which had 8K, 18-bit words of memory. After a few years, they continued development of Unix on a PDP-11. The orange lines encircle tapes that would have been used to backup code in an archive.
Text File
The text file contains your reflections and a copy/paste of you building, running, and testing the programming problems associated with the lab. The text file name shall be for example, lab-util-handin.txt, where util is the name of the lab. The text file is the same for both Xv6 and Linux labs. The text file is submitted in the lab's Text File Assignment on Canvas. The text file shall be neatly organized items in the following order.
- Name: Your name.
- Hours Spent: The number of hours you spent on the lab.
- Questions: An honor declaration that you have completed the questions in either a handwritten notebook or typewritten file.
Here are several sample honor declarations.
- I have handwritten 100% of the questions and answers in my notebook. - this earns 25 points.
- I have typewritten 100% of the questions and answers in a file. - this earns 15 points.
- I have handwritten 85% of the questions and answers in my notebook.
- Learning: An honor declaration of the percent of problems solved, followed by a list of at least five things you learned on this lab and the lecture material related to this lab The following shows a sample.
I have completed 100% of the problems.
- I learned ....
- I learned ....
- I learned ....
- I learned ....
- I learned ....
- Collaboration: If you helped someone or someone helped you, you can describe the help here. Collaboration is optional.
- Build, Run, and Test: A copy/paste of you building, running, and testing your lab problem program solutions. This should show that you are using your account. It should show you running and testing all of the lab problems - even those problems where I have provided the solution code.
Text File Sample
Name: Gusty Cooper
Hours Spent: 7
Questions: I have handwritten 100% of the questions and answers in my notebook.
Assessment: I have completed 100% of the problems.
1. I understand the Xv6 API.
2. I learned that fork() creates child process that is an identical copy of the parent.
3. I learned that exec() runs a program located on the disk.
4. I learned that exec() overwrites the calling process with the program that is executed.
5. I learned that pipe() returns two file descriptors.
6. I learned that a file descriptor is a small integer that can be used with read() and write().
7. ... more if you learned more ...
Collaboration:
I worked with Susan and Bobby to answer the questions. Susan was especially helpful.
I help Matilda with her programming problems. I easily completed mine and Matilda needed some help.
ecooper@cpsc:~/xv6-labs$ make clean
rm -f *.tex *.dvi *.idx *.aux *.log *.ind *.ilg xv6.out* \
*/*.o */*.d */*.asm */*.sym \
user/initcode user/initcode.out kernel/kernel fs.img \
mkfs/mkfs .gdbinit \
user/usys.S \
user/_cat user/_echo user/_forktest user/_grep user/_init user/_kill user/_ln user/_ls user/_mkdir user/_rm user/_sh user/_stressfs user/_usertests user/_grind user/_wc user/_zombie user/_hashprog \
ph barrier
ecooper@cpsc:~/xv6-labs$ make qemu
riscv64-linux-gnu-gcc -c -o kernel/entry.o kernel/entry.S
riscv64-linux-gnu-gcc -Wall -Werror -O -fno-omit-frame-pointer -ggdb -gdwarf-2 -DSOL_RISCV -DLAB_RISCV -MD -mcmodel=medany -ffreestanding -fno-common -nostdlib -mno-relax -I. -fno-stack-protector -fno-pie -no-pie -c -o kernel/kalloc.o kernel/kalloc.c
riscv64-linux-gnu-gcc -Wall -Werror -O -fno-omit-frame-pointer -ggdb -gdwarf-2 -DSOL_RISCV -DLAB_RISCV -MD -mcmodel=medany -ffreestanding -fno-common -nostdlib -mno-relax -I. -fno-stack-protector -fno-pie -no-pie -c -o kernel/string.o kernel/string.c
... more printout ...
riscv64-linux-gnu-ld -z max-page-size=4096 -T user/user.ld -o user/_hashprog user/hashprog.o user/ulib.o user/usys.o user/printf.o user/umalloc.o
riscv64-linux-gnu-objdump -S user/_hashprog > user/hashprog.asm
riscv64-linux-gnu-objdump -t user/_hashprog | sed '1,/SYMBOL TABLE/d; s/ .* / /; /^$/d' > user/hashprog.sym
mkfs/mkfs fs.img README user/_cat user/_echo user/_forktest user/_grep user/_init user/_kill user/_ln user/_ls user/_mkdir user/_rm user/_sh user/_stressfs user/_usertests user/_grind user/_wc user/_zombie user/_hashprog
nmeta 46 (boot, super, log blocks 30 inode blocks 13, bitmap blocks 1) blocks 1954 total 2000
balloc: first 784 blocks have been allocated
balloc: write bitmap block at sector 45
qemu-system-riscv64 -machine virt -bios none -kernel kernel/kernel -m 128M -smp 3 -nographic -global virtio-mmio.force-legacy=false -drive file=fs.img,if=none,format=raw,id=x0 -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0
xv6 kernel is booting
hart 2 starting
hart 1 starting
init: starting sh
$ show your running and testing here
... more ... more ... more ...
... more ... more ... more ...
... more ... more ... more ...
Questions or comments regarding CPSC 405? Send e-mail to Gusty at ecooper@umw.edu.
Top //
CPSC 405 home //
Last updated 8-Aug-2024 13:30 EST