This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
haas:spring2015:unix:projects [2014/12/08 16:59] – external edit 127.0.0.1 | haas:spring2015:unix:projects [2015/04/19 14:01] (current) – [Projects] wedge | ||
---|---|---|---|
Line 6: | Line 6: | ||
======Projects====== | ======Projects====== | ||
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/haas/fall2014/ | + | * [[/haas/spring2015/ |
- | * [[/ | + | * EoCE - bottom of Opus (due 20150514 by 4:30pm) |
- | * [[/ | + | |
+ | |||
+ | |||
- | ======Week 13====== | ||
- | * 12/08/2014 11:45am - UNIX projects, attendance, and opus entries have been updated! Be sure to check **status** output to verify everything is in order. | ||
- | * if I missed anything (especially notes project entries you might have done for bonus), shoot me an e-mail and let me know the date(s), so I can record them appropriately. | ||
- | * as I had to update week 12 opus entries due to my "week after break" bug, everyone had plenty of time to get their opus entries up to date. At this point I am considering the window for updating past opus entries for credit to be **closed**. Note that you still have one Opus entry remaining, for week 13 (due before it is Tuesday). | ||
- | * all projects prior to the **statuscalc** project have been closed to submissions; | ||
- | * the **statuscalc** project itself is getting a little long in the tooth; it may still be open, but there will be considerable late penalties applied- the aim is to get everyone focused on **timeonline** and the **eoce**. | ||
- | * Reminder: if you have any borrowed books from the LAIRbrary, be sure to return them before the end of the semester! | ||
======Week 12====== | ======Week 12====== | ||
- | * Unveiled | + | * EoCE(s) have been deployed to your Opus. Check there (be sure you are signed in to the wiki, otherwise |
- | * no attendance | + | * Reminder: |
- | * one more Opus entry will be recorded | + | * Please do keep e-mailing me questions. |
======Week 11====== | ======Week 11====== | ||
- | * Congratulations to **user** | + | * I have put together the End of Course Experience (EoCE) |
- | * Class notes roles for **[[/ | + | * It is open resource, but closed person. |
- | * author: **user** | + | * You are expected to work on this by yourself (you may ask me for clarification). |
- | * designer: **user** | + | * It, along with anything else outstanding that you'd like to receive credit for (even if just for consideration), |
- | * reviewer: **user** | + | |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
======Week 10====== | ======Week 10====== | ||
- | * Congratulations | + | * A couple people have experienced problems updating their Opus (a failure " |
- | * Class notes roles for **[[/ | + | * Covered signals and process management, looking at: |
- | * author: **tiwari1** | + | * ps |
- | * designer: **acarson1** | + | |
- | * reviewer: **ssmit133** | + | * top |
- | * Be sure to check the notes project for role-specific deadlines. | + | * whowatch |
- | * Class notes roles for **[[/notes/unix# | + | * kill |
- | * author: | + | * jobs/fg/bg/CTRL-z |
- | * designer: **dshadeck** | + | |
- | * reviewer: | + | |
- | * Be sure to check the notes project | + | ======Week 9====== |
+ | | ||
+ | * I made a tweak to **bgrep** to allow for better start of address reporting on displayed results. Let me know if anything seems out of whack. | ||
======Week 8====== | ======Week 8====== | ||
- | * Congratulations to **tmosgrov** for winning | + | * **udr2** is out.. continuing our data recovery and exploration theme, we enter the realm of data acquisition and analysis. |
- | * Class notes roles for **[[/ | + | * As I've said all along, the sooner you start on this, the better. |
- | * author: **ahoover3** | + | * So far, nobody who hasn't asked me questions has gotten through udr1 on their own... not that it is hard, we just make it hard (mental blocks). I've been e-mailing back and forth with the successful |
- | * designer: **rhenggel** | + | * The big stumbling block is conceptual: not understanding the difference between text and binary data (not understanding that all text is binary data, but not all binary data is text). Not realizing that one cannot effectively use text processing tools on non-textual binary data (I cringe everytime I see someone straight catting or nanoing/vi'ing data.file)... |
- | * reviewer: **jjacobs7** | + | * Reading through the project |
- | * Be sure to check the notes project | + | |
- | * I'd like to give a knowledge assessment next Thursday | + | |
======Week 7====== | ======Week 7====== | ||
- | * Congratulations to **ahoover3** for winning the Week 6 bonus point drawing | + | * **udr1** is out! It continues our UNIX file innards explorations, |
- | * Class notes roles for **[[/ | + | * Once again, the intent is to get people to ask more questions. |
- | * author: **nsano** | + | |
- | * designer: **jcliteur** | + | |
- | * reviewer: **stiwari1** | + | |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
- | * dataproc project deadline extended until after break. Those who submit it by original due date will receive a bonus point. | + | |
======Week 6====== | ======Week 6====== | ||
- | * Congratulations to **tmosgrov** | + | * Class was canceled? Yeah, campus closed, apparently- although you wouldn' |
- | | + | * The big problem with **udr0** was that people didn't know where to start. Very few (ie 2) actually took my advice and asked questions: I designed this assignment to force you to ask questions. Instead, all I got was a lot of panic that people didn't know where to start. So if you hadn't asked me questions, you were effectively making the project far more difficult. |
- | | + | * I identified 2 typos (they actually didn't seem to stop a fair number of people), and have issued corrections and a memdump file update. Check the assignments page for details. |
- | * designer: | + | * I have extended the deadline |
- | * reviewer: **ddewert1** | + | * It was brought to my attention that the manual pages for **gcc** and related commands had NOT been installed on lab46! This grievous error has now been rectified. You may now peruse the seemingly endless pages of gcc options to your heart' |
- | * Be sure to check the notes project | + | |
- | * Class notes roles for **[[/ | + | |
- | * author: | + | |
- | * designer: **dsoutha3** | + | |
- | * reviewer: **nvitull1** | + | |
+ | C code to display " | ||
+ | |||
+ | <code c 1> | ||
+ | /* hello.c - a UNIX-style " | ||
+ | * | ||
+ | * To compile: gcc -o hello hello.c | ||
+ | * To execute: ./hello | ||
+ | */ | ||
+ | #include < | ||
+ | |||
+ | int main() // everything needs a starting point, in C, that is a function called main() | ||
+ | { // when you have a group of statements, wrap them in a code block using the curly braces | ||
+ | int | ||
+ | char *msg = " | ||
+ | |||
+ | while (*(msg+i) != ' | ||
+ | fputc(*(msg+i++), | ||
+ | |||
+ | return (0); // all done, notify the system all went according to plan | ||
+ | } // close code block | ||
+ | </ | ||
+ | |||
+ | Memory variables are merely variables whose purpose is to contain a memory address. If we want to see what is inside the memory address contained within our memory variable, we have to dereference it, with the < | ||
+ | |||
+ | The key takeaway here is that, even if you don't know C enough to write a program on your own, you should be able to identify organizational structures, and even tweak minor things to enable the program to perform in a more optimal way. There are manual pages that can be referenced for many STDIO C functions (including **fputc**), and I would highly recommend perusing some of them to get a better handle on what is going on. | ||
======Week 5====== | ======Week 5====== | ||
- | * Congratulations to **ssmit133** for winning | + | * Between the most excellent puzzle boxes and your ongoing explorations in general, you're likely chomping at the bit for increased excitement. I am not one to let you down! Fresh off the project |
- | * Class notes roles for **[[/ | + | |
- | * author: **nvitull1** | + | |
- | * designer: **tarnold4** | + | |
- | * reviewer: **jcliteur** | + | |
- | * Be sure to check the notes project | + | |
- | | + | |
- | * author: **rhenggel** | + | |
- | * designer: **nvitul1** | + | |
- | * reviewer: **ahoover3** | + | |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
======Week 4====== | ======Week 4====== | ||
- | * Congratulations to **dsaunde6** for winning | + | * Because you had so much fun and life-redefining discovery on the puzzlebox, I have polished off the next exciting entry in the series: **pbx1** |
- | * Class notes roles for **[[/ | + | * A little more abstract, yet still a little bit familiar. Promising hours of mind-expanding fun. |
- | * author: **mgleaso7** | + | |
- | * designer: **nvitull1** | + | |
- | * reviewer: **skramer1** | + | |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
- | * Class notes roles for **[[/ | + | |
- | * author: **mquesad1** | + | |
- | * designer: **mp010784** | + | |
- | * reviewer: **tmosgrov** | + | |
- | * If you are not sure if you submitted an assignment, I have updated | + | |
- | * Simply run: **submit unix** | + | |
- | * You will see upcoming yet-to-be-submitted projects, submitted projects, and past due projects | + | |
- | * If you have already started on the **Puzzle Box**, in the very last step (action 2 of the final step, actually), there is a command for you to type: | + | |
- | * cat results | mail -s " | + | |
- | * This apparently doesn' | + | |
- | * cat results | mail -s " | + | |
======Week 3====== | ======Week 3====== | ||
- | * Congratulations to **dsoutha3** for winning | + | * Our third week of the semester started with a snow day! YES!!! After spending some time playing out in the snow, we can relax with some extra UNIX time playing around on lab46 and working on the project. |
- | * Class notes roles for **[[/ | + | * As we gear up for week 3 activities, I have released the next project, the famous |
- | | + | * You'll want to have finished the **arc0** project before starting |
- | * designer: **dshadeck** | + | * Don't forget to participate in the class mailing list! And update your Opus with all your exciting UNIX adventures |
- | * reviewer: **mp010784** | + | |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
- | * I wrote a new **status** script | + | |
- | * At this point I am still loading in all the information... so not everything may be present. | + | |
- | * Of the data present, please report to me (via e-mail) any errors | + | |
- | * The aim is to update this each WEEK. | + | |
- | * Class notes roles for **[[/ | + | |
- | * author: **acarson1** | + | |
- | * designer: **tmosgrov** | + | |
- | * reviewer: **abuck4** | + | |
======Week 2====== | ======Week 2====== | ||
- | * Lab46 was reset on Friday, so we'll need to [[/ | + | * I hope everyone took the time to read through the Mages book- and are increasingly convinced that is is "the best course you've ever taken" |
- | * Time to set up our [[/ | + | * The first project is due before it becomes Thursday. There are several actions you need to perform, so be sure that you tend to them. |
- | * Congratulations to **mgleaso7** for winning | + | * Remember that there' |
- | * Class notes roles for **[[/notes/unix# | + | * Just to be clear, I do expect you to send an introduction message |
- | | + | * If you're holding off to increase your chances of reception (good catch!) please be sure to do the deed before Thursday. Those who miss out, miss out. Their loss. |
- | * designer: **ddewert1** | + | * The next project, |
- | * reviewer: **dshadeck** | + | * Two more labs available |
- | * Be sure to check the notes project for role-specific deadlines. | + | |
- | * Class notes roles for **[[/notes/unix# | + | * [[/haas/ |
- | * author: | + | * you may want to specifically look at the **I/O redirection** section of this lab to help with your **arc0** project. |
- | | + | |
- | * reviewer: **mquesad1** | + | |
======Week 1====== | ======Week 1====== | ||
- | + | | |
- | | + | * On Lab46, we'll be getting familiar with logging into the pod systems, and once there: |
- | * Read over the syllabus | + | |
- | | + | |
- | | + | |
- | * In Lab46, we'll be getting familiar with logging into the pod systems, and once there: | + | |
* opening up a terminal | * opening up a terminal | ||
* logging that terminal onto Lab46 for class work and in-class attendance | * logging that terminal onto Lab46 for class work and in-class attendance | ||
Line 152: | Line 122: | ||
* start working on the labs and other class activities | * start working on the labs and other class activities | ||
* start exploring | * start exploring | ||
- | * Familiarize yourself with your Opus, and once there: | ||
- | * customize it (title/ | ||
- | * add an introduction | ||
- | * create your first week content | ||
* Be sure to do the reading (located in the individual labs below)! There may be many pages, but there are many concepts to encounter. | * Be sure to do the reading (located in the individual labs below)! There may be many pages, but there are many concepts to encounter. | ||
* The following labs are now available for you to work through: | * The following labs are now available for you to work through: | ||
- | * [[/ | + | * [[/ |
- | * [[/ | + | * [[/ |
- | * [[/ | + | * [[/ |