Note: This year we'd like you to concentrate on enabling/creating software and hardware resources that fellow students can actually use in their projects. If there is a particular piece of hardware (within reason) you'd like to use, ask us, and we may be able to get it. The how-to draft should help you determine if a particular topic is feasible for you. For equipment we haven't received yet, gather the background material for the draft proposal and explain why the technology is important. This is not a reproduce-the-tech-manual exercise, but rather a install or test deploy-and-show-how-to-access-it-effectively from your own code. 30M disk space for each of you has been reserved on the CoC clusters under /users/projects/class/7470/. CoC clusters include SGI's, Suns, Linux, and NT. Kent will have info on how to request more quota and group permissions shortly.

Some software may already be installed (for those doing software)

Then it is your job to show how it can be helpful. Officially supported stuff should have an entry in /usr/local/bin, and the whole installation, if it involves multiple binaries/libraries, would be in /usr/local. For example, /usr/local/bin/newelm is the binary for Elm 2.5.2; since the whole package consists of multiple files, that binary is really installed in /usr/local/elm2.5.2/bin (along with the other related files). There's a /usr/local/elm2.5.2/man for all the manual pages, etc.

Things that are supported by faculty/students are in /usr/local/public; there are subdirectories and README files to document the version that is installed, etc.

Of course, some of these suggestions are better than others. Remember you can do something similar to a HowTo from last year if you improve upon it significantly

How to...