The final for CIS2230 is posted on blackboard and ready for students. You can take the exam early if you wish. Please work alone. The exam is open book and open note. Do not share answers or questions with other students. Select the BEST answer for the question. Good luck and please email me if you cannot see the exam on blackboard.
Any and all labs that I have in my possession are now graded and the grades are posted on Blackboard. Please review the information BEFORE taking the final exam and ensure that I have all the work you believe you have handed in to me.
Some caveats and hints about grades:
– Exams and quizzes are open. Take any and all of these that you did not take yet. Don’t stress out about late policies, just take the quiz. If you are locked out of blackboard you must tell me BEFORE Monday 4 May or I will have no choice but to give you zeros for missing exam/quiz/labs.
– If you worked on a lab with someone and your partner failed to write your name on the report, you must send me a report with your name on it. Please do not email me with, “I should have a grade on labs 1-12, I worked on them with Bob and Jeff”
Yes, I have had students in the past try to join lab partnerships in the last week of the semester in order to get a better grade. You must turn in a copy of the lab write up with your name on it.
I received this as an unanswered question in a lab and I wanted to respond to this before the close of the semester.
I teach old school C programming on UNIX because students will see this type of code in the real world. Sure, C++ and C# are popular. You’re learning Ruby and that’s cool too. In an academic setting you should explore the newest, cutting edge techniques and languages, but not to the detriment of learning how things used to be.
Once VTC students become technology workers, they may happen across 10Base2 networks, software systems written in C, they may be asked to covert a mainframe COBOL system into a Web 2.0 system. Teaching them what once was and how it once worked is something that will be very valuable to them in their future.
I always chafe when I hear about a teacher telling students that they MUST have an MSCE in order to succeed in the tech sector. I cringe when I hear teachers telling people that they only need to learn linux and they’ll have a job for life. I would argue that a solid understanding of linux and an MSEC would put a person in a great space for employment. In this economy it’s unwise to become embroiled in the zealotry surrounding company’s marketing or the FOSS movement.
So there’s your answer why I teach
printf and not
cout, odds are that you’ll find code (and lots of it still) where an understanding of the old ways will aide you.
It’s nearly the end of the semester. Please make sure you turn in any labs. You don’t need to write an apology or an excuse for why the labs are late, I care about getting your lab grades computed correctly, not why your PC ate lab 4 and you had to find it and re-write it. (Lab 4 here is just an example)
There is no lab #13. It’s not practical to have a lab then try to get it graded and returned before the final exam. I would encourage you use the free time on Tuesday to attend senior project presentations. It’s a good idea to see what you’ll be doing in the not too distant future.
Final exam will be on-line at you are not required to follow the scheduled time and place for the final. YOU MUST COMPLETE THE FINAL BY MIDNIGHT 5 MAY.
I take a quick look through the last few chapters of the book. We’ll return to the networking chapters in the next week.
In chapter 11 you’ll read all about backup and recovery.
Yes, I do know that you are all on break. I wanted to get ahead of the labs with the lectures so I’m posting this early. You don’t have to listen to this until you get back.
The web site I refer to is http://www.angelfire.com/myband/binusoman/Unix.html#start
Here’s a little levity that will dispel any left over lab #9 angst.
Many of the write-ups coming in for lab #9 are expressing angst and frustration. Lab #9 is one of those labs where I want you to mess around and experiment and explore. It’s one of those horrible vague lab handouts because in the real world you won’t be given a checklist of things to do in order to succeed at your job. Bosses never say things like, “please go to this site, download abc.tar.gz, use the command tar xzvf abc<TAB> to uncompress it into directory /usr/src/project9, then cd to that directory, type configure, then make, then make install, and edit the file /var/www/html/conf.php with the following…”
Bosses are going to lundberg up to your cube on a Friday afternoon and go, “hi Peter, what’s happening… yeah… we want a corporate blog server for our TPS reports… can you have that done by Monday… great…. bye”
That’s why there a few labs in my classes that are not formatted in the standard “follow the 12 steps and record your answer.” Yes, lab #9 is one of them. I want you to play around with fork(), exec(), system(), top, ps, and vmstat. I want you to experiment on your own and try different things. Try to break the OS. Try to freeze your machine. Play CSI with the child parent relationship in Linux processes. Who dies or zombies when you start killing things? Can you renice your way into a dog-slow system and can you renice your way to a recovery?
Please don’t fear for your grade on this lab. If you did some work and documented it, rest assured you will get credit. If you blew it off or just copy/paste my same code with little to no write up, then expect a lesser grade.
The purpose of the lab is to goof around with processes, parent/child relationships, and process priorities. If you did that, then you accomplished what I wanted you to do.