This section will document any updates applied to the project since original release:

• revision #: <description> (DATESTAMP)

In this project, we get started with some course initialization activities.

You're reading this, so you've likely already found your way to the course homepage. It consists of the syllabus plus additional course resources.

Please familiarize yourself with it, bookmarking important resources as appropriate, so that you can refer back when needed.

I'd recommend knowing how to get to the projects page (where you found the link for this project), as new content will be posted there.

Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course.

Familiarize yourself with your Opus, and once there:

• customize it (title/subtitle)
• add an introduction
• create your first week content

NOTE: Week 1 opus entry will be due before Tuesday, the remainder of the intro Opus content will be due by this project's deadline.

Using the resources found on the course homepage (or the lab46 website in general), locate and subscribe a preferred and frequently checked e-mail address to the class mailing list (known as HPC).

We will use this for class discussions (along with irc, the notes wiki page, your Opus, etc.) and to disseminate announcements and other information.

Once subscribed, please send a message to the list introducing yourself (also so I can know to associate a particular e-mail address with you).

Using the tutorial, set up a screen session and join the #hpc channel on irc. This has proven useful for more interactive (debugging!) conversations.

Be sure you can still log into Lab46 and access related resources.

For any pertinent activity, I'd like for you to make regular commits and pushes to your Lab46 mercurial repository (again, where appropriate).

This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong.

As a first week exercise, I would like you to select, test, install, configure, and eventually use your own desktop Linux system.

I would recommend Debian or Ubuntu, but if you know what you are doing, feel free to use whatever distro you prefer.

Note that our next project will be to build a system from the ground up (Linux From Scratch), so you will need a functional system compatible with those aims.

To be successful in this project, the following criteria must be met:

• Project must be submit on time, by the posted deadline.
  • Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
• All code must compile cleanly (no warnings or errors)
  • all requested functions must be implemented in the related library or program
  • all requested functionality must conform to stated requirements (either on this project page or in comment banner in source code files themselves).
• Executed programs must display in a manner similar to provided output
  • output formatted, where applicable, must match that of project requirements
• Processing must be correct based on input given and output requested
• Output, if applicable, must be correct based on values input
• Code must be nicely and consistently indented (you may use the indent tool)
• Code must be commented
  • Any “to be implemented” comments MUST be removed
    • these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
  • Sufficient comments explaining the point of provided logic MUST be present
• Track/version the source code in a repository
• Submit a copy of your source code to me using the submit tool (make submit will do this) by the deadline.

Let's say you have completed work on the project, and are ready to submit, you would do the following (assuming you have a program called hello.c):

lab46:~/src/hpc0/int0$ submit hpc0 int0 hello.c
Submitting hpc0 project "int0":
    -> hello.c(OK) 

SUCCESSFULLY SUBMITTED
lab46:~/src/hpc0/int0$