Lab00, CISC105, Spring 2006

Welcome

Welcome to CISC105! The purpose of this first lab, "lab zero", is to familiarize you with some of the knowledge and skills you will need to complete the remaining labs in this course. In particular, this lab will introduce you to the Sun Rays.

The Sun Rays are computer workstations that you can use to access the machine called Strauss. Strauss is where you will do your actual programming in this course. In lab, you'll access Strauss via the Sun Rays. The SunRays are a specific brand name for a type of system called an "X Terminal".

Note: Outside of lab, you may access Strauss from any computer connected to the Internet, provided you have the right access software (e.g., a secure shell client program.) Your instructor will say more about that in lecture. Some work for this course you can do from any computer, provided you can use that computer to access Strauss. Other work you might have to do directly on the Sun Rays. There are Sun Rays in Willard Hall 009, and also in some other locations on campus, including the basement of Smith Hall.

Goals for Lab Zero

This lab is kind of a "warm up" for the semester. We want to make sure that you are comfortable with the environment before we get into the heavy lifting, which starts next week.

AFTER the lab:

Make sure you know how to log in and out of the Sun Rays, and set up your account for this course.
Make sure you know how to access the web on the Sun Rays.
Make sure you can find the CISC105 home page.
Your instructor is using a course management system called MyCourses, that allows you to track your assignments, submit assignments online, and track your grades in the course (among other things). You need to make sure you can find MyCourses, login to MyCourses, and find CISC105 among your courses.
Make sure you know how to create a text file with the text editor known as emacs.
Chapter 15 in your Andersen textbook covers emacs, and there is also some material below. In this lab, you'll create a text file, and submit it both online via MyCourses and on paper.
Make sure you can create a C program, compile it, run it, script the results, and submit it to your TA on paper, and if requested, also via MyCourses.
Make sure you understand the lab policies.

If you can do all those things and your lab is complete, you are all set for this week, and you can start on reading Chapters 1 through 2.4 in your Hanly & Koffman text.

Reference Materials for Lab 00

In your Andersen textbook (Just Enough Unix, 5th Edition), Chapters 1,2,3,15,32,33. These are short chapters, but you are not expected to know all this material off the top of your head; instead, find what you need to know to accomplish the task at hand.

Goals 1 and 2: Login/Logout and Web on the Sun Rays, and account setup

Info on logging in and out and accessing the web on the Sun Rays is at the following link:

http://copland.udel.edu/~pconrad/UnixAtUD/SunRay.html

That link also has information on what to do if you don't yet have a UDelNet Id. Finally, there is also information on that page that will help you pull up an "XTerm on Strauss"; you'll need that when you get to Goals 5 and 6.

In addition, you should do the following steps:

Go to the page http://www.udel.edu/network, log in, and access the option to change your "Unix Default Group". Change your default group to the one that corresponds to CISC105 (2115).
On that same page, access the option to change your "Unix Default Shell". Change it to /bin/tcsh.

Here is a special note only for those who have used Unix (or Linux) before (everyone else, just ignore this!)
If you already understand what a "shell" is and you prefer the "bash" shell, you may choose /bin/bash as an alternative to /bin/tcsh. Note, however, that some course assignments may require the use of tcsh; you can always select tcsh by typing "tcsh" at the Unix Command prompt.)

Goals 3 and 4: CISC105 homepage and MyCourses

Once you've managed to get logged on to the SunRay system, and you've found the Web Browser, use a search engine to find the course web page if you have not already done so. This is important because all your assignments will be there.

Then, click on the link:
http://www.udel.edu/MyCourses

Click "log on". This should take you to a login screen, and then to a menu showing the MyCourses page for this course. Find the assignment Lab00 and review it (it is a very short version of this document, and makes a good checklist).

You now have found two important links for your success in 105, the class webpage and MyCourses.

Goal 5: Creating a text file with emacs

Open an XTerm on strauss (If you don't know how and/or are not sure what "Xterm on Strauss" means, follow this link to the Sun Ray documentation: http://copland.udel.edu/~pconrad/UnixAtUD/SunRay.html).

Now it's time to start learning emacs. Emacs is a "text editor", that is, a program that helps you create files on strauss. Go to an xterm on strauss, and type "emacs &". If you get a command not found message, you may have to type "/opt/bin/emacs &" until you correct your path variable.

The "&" is a special command suffix to let Strauss know that you want emacs to open in a new window and let you keep using the old xterm window, too.

When you see Emacs, the paragraph of text will tell you how to start running a self-directed tutorial. Do this. The option to run the tutorial appears every time you open emacs. You can run the tutorial as many times as you like until all the material is familiar or you become bored out of your gourd.

Once you are comfortable with using emacs, go ahead and use emacs to create a text file called "lab00.dat" containing the following, each on a separate line: your name, your hometown, your favorite US state other than the one in which your hometown is located, and your unix userid.) For example:

Your Namehere

Wilmington, DE

Arizona

ynamehe

When you are finished, send the file to the printer in Willard 009 with the following Unix command typed into an xterm:

qpr -q whlps lab00.dat

Also, upload this file as part of your submission for Lab00 in MyCourses. But DON'T SUBMIT YET! That is, don't press the "submit" button. Just upload for now. You'll hit submit at the end of lab, after you've also uploaded your C program and script file. You will wait until all of your files are uploaded before clicking submit once.

If you aren't sure how to do this, check the following link for help, or ask your TA:

http://www.udel.edu/MyCourses/students/assignments.html

(If you accidently hit submit before you get your C program uploaded, don't freak out; your TA can reset the assignment so that you can try it again. Your TA might not be able to fix it immediately, because its the first week of the semester and her TA account might not be active yet. But if not, she can fix it up for you by next lab, and you can make it up then without penalty.)

Goal 6: C programming on Strauss

Create a file lab00.c that contains the following (except substitute your name and Unix user id for those of Jane Doe, and use today's date.)

DO NOT include your student number (NEVER include that number in anything you submit in this class!)

// lab00.c Jane Doe doej@udel.edu 3/1/06
// traditional first program (hello.c from Andersen, p. 369)

#include <stdio.h>

int main(void)
{
  printf("Hello, world!\n");
  return 0;
}

Once you've created this program, determine which, if any, compiler you have available.

which cc

and

which gcc

The "which" command will either return a path (characters separated by slashes) or "command not found". If neither is found, consult your TA for how to set up your .localenv file so that you can use a compiler.

Use the following command typed into an xterm to compile it (compile means: translate from C into machine language, or if it cannot be translated because of errors, report the errors) with one of the following commands. At this point in the semester, you may use either one (later on, I may tell you to use one or the other.)

cc lab00.c

gcc lab00.c

The first command (cc) is a commercial compiler, supplied by Sun Microsystems. The second command, gcc is an open source compiler, supplied by the GNU project, which is staffed by volunteer programmers. From time to time, we may discover differences, but for now, I don't care which one you use. Sometimes if you have a tricky syntax error it is useful to try both, because sometimes one gives you more useful error messages than the other.

In both cases, a new file is produced called "a.out". To execute this file (run your program), type the following:

./a.out

You might be able to get away with just typing a.out without the leading ./, or you might not; it all depends on how your account is set up. (It has to do with the Unix concept of the "path"; you'll read about that in the Andersen text later on.)

If all goes well, you should see something like the following:

> cc lab00.c
> ./a.out 
Hello, world!
>

You are now ready to use the "script" command to make a record of your work.

Note that you must be careful when using the script command. The script command will wipe out your work if you are not careful! Script works by writing into whatever filename you specify, so don't specify a filename that has good stuff in it (like your program).

The thing to remember is: on the command line, type "script" followed by the name of a .txt file; for example:

script lab00.txt

This is correct!!!!

Never put "script" followed by the name of a .c file. It will wipe out your .c file where your code is!

Ok, now that we have that out of the way...

Type "script lab00.txt". Then go through the following steps at an xterm:

list your program (type "cat lab00.c" to do this.)
compile your program (type "cc lab00.c" or "gcc lab00.c" to do this)
run your program (type "./a.out")
exit from the script (type "exit").

Now, use "cat lab00.txt" to make sure your script looks ok, and use the following command to print both your .c file and your .txt file. (Yes, I want you to print both of them, and submit both of them, even though the .c file is contained inside the .txt. file.)

qpr -q whlps lab00.txt

qpr -q whlps lab00.c

And finally, you are done with Goal 6!

Goal 7: Understanding Lab Policies

First, lets get this out of the way: Lab attendance is mandatory.

Attendance will be recorded. Be sure you are on time so the TA does not miss you.

Lab attendance is reported on MyCourses as, for example, lab00p (lab attendance for Lab0.) Grades are marked as P, A, E, or L for "Present", "Absent", "Excused", or "Late". Only the instructor can excuse you from attending lab.

Your lab has two components: paper submission and MyCourses submission. Paper is due at the start of Friday labs the following week (not two minutes after lab starts!). Hint: The printer at the lab is often overcrowded just before a lab starts, so print your lab somewhere else that morning or the night before.

The MyCourses part of your lab is due at 11:55 p.m. Thursday night of the following week So this lab is due, for all students, Feb 16th at 11:55 p.m. on MyCourses, and the following day for paper assignments.

Late penalties apply as noted on the class web page.

Finishing up: What to turn in for this lab

Be sure that you have a printed copy of your three files: lab00.dat, lab00.c, and lab00.txt (script file).. Hand these to your TA before leaving the room. If you are making up this lab, hand it to him/her before Lab01.)
Be sure that you uploaded ONLY ONCE a copy of all three files to MyCourses (lab00.dat, lab00.c, and lab00.txt). Do not try to upload the files separately, upload them together. Then, click submit to send these to your TA.
Grading:
- printing each of the three files is 10 points each (30 points total)
- submitting each of the three files is 10 points each (30 points total)
- the correctness of the content is worth 40 points

Adapted from Phill Conrad