1. http://www.cs.ucr.edu/~weesan/cs183/ CS183 Unix System Administration Spring ‘08 WeeSan Lee

2. http://www.cs.ucr.edu/~weesan/cs183/ WARNING! Unix/Linux can be additive Can’t win a cash prize and a laptop   http://dvlabs.tippingpoint.com/blog/2008/03/28/pw n-to-own-final-day-and-wrap-up Lots of MS jokes Lots of fun

3. http://www.cs.ucr.edu/~weesan/cs183/ Who are Unix System Administrators? Those who tell you to reboot your machine?  1 st line technical supports Those who manage their own machines running heavy duty OS without Internet access?  Windows users who fear the virus infection from the Internet

4. http://www.cs.ucr.edu/~weesan/cs183/ Course Information 10-week course  3 lectures / week *  1 lab / week Lecture  MWF 5:10 - 6:00pm @ WAT 2240  Office hours: Thursday 1-3pm @ Bourns B246 or by appt. Lab  TW 2:10pm - 5:00pm @ Engr2 135  TA: Glenn M. Bernstein & Inci Cetindil  Office hours: TBA

5. http://www.cs.ucr.edu/~weesan/cs183/ Course Information (cont) Textbook  Linux Administration Handbook (2 nd edition)  By Evi Nemeth, Garth Snyder, Trent R. Hein  ISBN: 0131480049 Reference (optional)  Programming Perl (3 rd edition)  By Larry Wall, Tom Christiansen, Jon Orwant  ISBN: 0596000278 Moodle (https://moodle.cs.ucr.edu/)

6. http://www.cs.ucr.edu/~weesan/cs183/ Topics Linux on a single machine  Installation and kernel recompilation  Boot and shutdown sequence  User account management  Process monitor and management  File systems  Package management  Periodic processes (crontab)  Security  Logging  Backups

7. http://www.cs.ucr.edu/~weesan/cs183/ Topics (cont) Linux on multiple machines  TCP/IP networking  Routing  HTTP, Web Cache, FTP, DNS, SMTP, NIS (Yellow Page), NFS, Samba, SSH, …  Security Misc  Shell (Bash) programming  Perl programming

8. http://www.cs.ucr.edu/~weesan/cs183/ Grading Labs 40% Programming Assignments (2)30% Final Project 20% Pop Quizzes & Attendance10% Final 0% Total:100% I reserve the right to make any changes!

9. http://www.cs.ucr.edu/~weesan/cs183/ Labs Reports are in HTML format  Objective  Introduction  Procedures  Conclusion  Further Reading  Glossary  Questions & Answers Will be graded based on the quality of the report Sample report  http://www.cs.ucr.edu/~weesan/cs183/lab_report_sample.html

10. http://www.cs.ucr.edu/~weesan/cs183/ Labs (cont) Collect as many outputs & screenshots as possible during the lab Feel free to google answers for the questions, but make sure to paraphrase them Due on Friday before midnight (11:55pm) Late turn-ins will be marked down 20% for 1 st day, and additional 30% the day after For example, max. score is:  100% on Fri by 11:55pm  80% on Sat  50% on Sun

11. http://www.cs.ucr.edu/~weesan/cs183/ Programming Assignments PA 1 - Shell programming  Poor-man package management  Given at the beginning of the 4 th week  Due on Friday of the same week PA 2 - Perl programming  Web log analysis/accounting  Given at the beginning of the 6 th week  Due on Friday of the same week

12. http://www.cs.ucr.edu/~weesan/cs183/ Final Project Individual or group of 2 Related to Unix System Administration Proposal  1 page (at most) in PDF Problem description Proposed solution Expected deliverables  Latex & bibtex  Due on the beginning of 5 th week

13. http://www.cs.ucr.edu/~weesan/cs183/ Final Project (cont) Report  4 pages (at least) in PDF Introduction Related work Technical details Result Conclusion References  Latex & bibtex  Due in last class (6/6) 8-10 mins in-class presentation  About 6-8 slides

14. http://www.cs.ucr.edu/~weesan/cs183/ Final Project Examples Automation  Kick-start install  Package management/update Scripting  Web front-end of user account management Network  Web cache performance enhancement using multiple network interfaces Security  How to setup a secure network? Misc  Asterisk PBX (http://www.asterisk.org/)http://www.asterisk.org/  Linux PVR (http://www.mythtv.org/)

15. http://www.cs.ucr.edu/~weesan/cs183/ No Cheating! Cheating will result 0% on the assignment or ‘F’ in this class So get your hands dirty  Do your own lab  Write your own report  Paraphrase in your lab report Having said that, I encourage group study/discussion, but …  Don’t read/debug somebody else scripts

16. Bottom Line No more calls to the technical support Geek-only party conversation Power-Linux users Resume looks good Get a job easier! Homepage looks professional Know some hackings Will be able to do this Have fun Source: http://www.ex-parrot.com/~pete/upside-down-ternet.html

17. http://www.cs.ucr.edu/~weesan/cs183/ Question?