Linuxlab machines (accessible from console or over the network) are the standard, supported, development environment for the project. We will test by running your projects on a Linuxlab machine, without necessarily being there (e.g.remote connection with ssh).
So the good news is you don't have to physically be there to test it before submission; you can ssh, export DISPLAY, run bochs etc. The bad news is that you must test it on a linuxlab machine. "It runs on my bochs at home" is not an excuse for a project that doesn't run.
Once again, before submitting make sure your project *runs atop of a bochs running on a linuxlab machine*. It doesn't matter whether you are at UMD in the Linuxlab or at home to test that fact.
You should do your submit as follows:
cd project0/build gmake clean cd ../.. tar cvf proj0.tar project0 gzip proj0.tar /afs/csic.umd.edu/submit/fall2005/cmsc412/bin/submit 0 proj0.tar.gz
The submit script will print a confirmation message
The program "proj0.tar.gz" has been successfully submitted for user cs412XYZbut nevertheless, you can check it out using the command:
ls -l /afs/csic.umd.edu/submit/fall2005/cmsc412/MP0/cs412XYZ*
where XYZ is of course your account number. You should see one file that has the same size as your submitted file. Later submissions will not overwrite earlier ones. Rather, your first submission is named cs412XYZ.0, the next one cs412XYZ.1, etc.
We will grade your last submission. If your last submission is after 6PM on the due date, but before 9AM the next day, a late penalty will apply as instructed on the syllabus page. Any submission later than 9AM the next day will not be taken into consideration.
It is important to cleanup .o's before submitting by doing gmake
clean as shown above, otherwise the submit script may fail.
Also, make sure you submit a tar file that contains
project0 as the directory it creates. When you unpack this tar file, you
should be able to cd to project0/build, and then type
gmake to make the entire project build with no
problems.