Week One Agenda

1. Week One Agenda • Introduction • Administrative Announcements • Link of the Week • Expected Outcomes • This Week’s Topics • Next Week’s Lab Assignment • Upcoming Deadlines • Lab assistance, questions, and chat time

2. Introduction • Instructor: • Professor Gary Varney • Systems Engineer/Applications Analyst • Instructor at Franklin University for three years varneyg@franklin.edu • Program Chair of Information and Technology: • Mr. Todd Whittaker • Phone # 614.947.6110 • whittakt@franklin.edu

3. Administrative Announcements • Instructor commitment • I plan to respond daily to student emails • Post exam grades and lab assignments as quickly as possible in the electronic grade book • Post student mid-term and final exam status after the exam has been administered • cs.franklin.edu server • Does everyone have a login that works into cs.franklin.edu? • Does everyone have putty downloaded to interface with the cs.franklin.edu server? • Do you have the course CDs including Knoppix?

4. Administrative Announcements • Recorded Franklin Live Power Point Presentations • http://cs.franklin.edu/~varneyg/itec400/PowerPoints • Franklin Live file name format: • Example: Week_1.ppt (pptx) • Franklin Live Attendance: • Online class attendance is recorded for each session. • If you enter a session more than 15 minutes after it’s started, please sign-in using the text screen like this: • Example: gvarney logging on

5. Administrative Announcements • Email format for assignment notification • Email notification is requested when an assignment is submitted. The “Subject” line format is as follows: • <User name> <Course> <Lab 1-3> • Example: varneyg ITEC 400 V2WW Lab Assign. 2-1 • Email format for questions • <User name> <Section Number> <Question> • Example: varneyg V2WW Question • Scripts and text file suffix • All scripts and text files shall have a suffix (e.g. ,sh, .pl, .txt). • Homework assistance: • Please do not solicit help with lab assignments from the Internet. If you are caught, Franklin University will take action against you.

6. Administrative Announcements • I will post most outlines, status pages, and open source evaluation topics on my web page: http://cs.franklin.edu/~varneyg • Drop Box: • Drop box link is on your Web page named ITEC 400- V2WW Current Announcements, under the “Communications” tab. • cs.franklin.edu: • This is the official server name for lab scripts and text files, and the official place where all scripts will be graded.

7. Administrative Announcements • Turnitin.com Assignments • The Public Domain Open Source must be submitted to Turnitin.com. I will grade those assignments on Turnitin.com. If your paper indicates matches of 50 percent or more, I will not grade the paper and will recommend that you seek assistance from the Student Learning Center. • Proctor • Obtain a proctor for mid-term and final exams.

8. Administrative Announcements • UNIX System Administration Syllabus • Optional Materials • Refer to the following web sites throughout UNIX System Administration. They are excellent resources for UNIX and Linux: • UNIX Tutorial for Beginners • UNIX help for Users.

9. Administrative Announcements • APA style format: • Main emphasis on citing sources, spelling, punctuation, and capitalization • Link of the week: • New links are provided weekly to direct students to information that will aid them with class lab assignments and enhance their overall learning experience.

10. Administrative Announcements • VMware software: • Source for downloading Knoppix software is on Web page COMP/ITEC 400 – UNIX System Administration (Overview -> Resources -> Download Materials) • Demonstrate Knoppix icons • ftp from Knoppix to cs.franklin.edu • sftp://varneyg@cs.franklin.edu/export/home/varneyg

11. Administrative Announcements • Office hours • Every Saturday at 10am EST for about an hour. • On demand via e-mail • I would gladly do a personalized Franklin Live session with you if you have more detailed questions.

12. Administrivia Academic integrity Code on the Web that can serve as “inspiration” for your solutions if: You understand the solution as if you had written it yourself. You cite your source of inspiration Not citing your source can get you charged with cheating/plagiarism. You are responsible for your own work – copying from another student can get you charged with Academic Dishonesty.

13. Administrivia Academic integrity If you have a vague feeling that you wouldn’t want your instructor to know about what you’re doing… don’t do it. When in doubt, ask your instructor.

14. Link of the Week • Open Source Software: • http://en.wikipedia.org/wiki/Open_source • http://freshmeat.net • http://sourceforge.net • Definition of Open Source Software. • List of open source products. • Who benefits from open source products? • What is shared source?

15. Expected Outcomes • Upon successful completion of this course, students will be able to: • Create non-trivial shell scripts. • Perform appropriate UNIX system administration tasks. • Compose non-trivial scripts using Perl programming language. • Distinguish the roles of Linux and Open Source software. • Incorporate the make utility appropriately within programs. • This course moves very fast at the beginning… Remember to send email and ask questions early & often.

16. Review Shell syntax • $# - Number of positional parameters • $! - Background PID • $? - Return value • $$ - Process PID • $ - Provides the content of a variable ($NUMBER) • $1, $2, $3 … - The syntax represents the positional parameters on the command line. • exit 0 – The return values is a number from 0 to 255. A value of zero (0) indicates a normal exit. • exit 1 - Indicates a failure.

17. Review shell syntax • “ “ - Double quotes. Removes special meaning of all enclosed characters, except $, `, “, and \. • Example: print “The price is $Price.\n”; (interpolation) • ‘ ’ - Literal quotes. Removes the special meaning of all enclosed characters. A single quote cannot appear within single quotes because a single quote denotes the end of the string. • ` ` - Single Back Slash quotes. Used for command substitution. • Example: echo The date is `date` (interpolation) • LINES=`wc -l $ENTRY | cut -c 1-7` • LISTING=`ls -l | cut -f 9`

18. Review shell syntax • if [ -d "$1" ] • then • Action Statement • fi • wc –l - Word count with –l (line option). Print the new line counts • ~ - Tilde (~varneyg means /export/home/varneyg)

19. Review shell syntax for name in * do action statements done while [ condition] do action statements done

20. Next Weeks Lab Assignment • Quick Reference Links • Week One • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/ShellQuickReference.doc • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/vi Commands.doc • Week Three • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/PerlQuickReference.doc • Week Four • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/ISOQuickReference.doc • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/FlashMemQuickReference.doc • http://cs.franklin.edu/~varneyg/itec400/Quick_Reference/umaskQuickReference.doc • Week Five • http://cs.franklin.edu/~varneyg/itec400/Quick_Qeference/inittabQuickReference.doc

21. Next Weeks Lab Assignment • Review Lab Assignment 2-1 Simple Shell scripting. • Demonstrate where the lab assignments should be recorded on cs.franklin.edu (Einstein). • Demonstrate how to create a file using the “vi” editor • Demonstrate the execution of printnum.sh and maxlines.sh scripts on Einstein • Lab Assignment 2-1 script logic

22. Upcoming Deadlines • Lab Assignment 1-3, Introduction to Linux, due Jan. 8 (Need VMWare/Knoppix). • Lab Assignment 2-1, Simple Shell Scripting, due Jan. 22. • Lab Assignment 3-1, Advanced Scripting, due Jan. 29 • Read Chapters 1 and 2 in Essential System Administration text • Read Module One listed under the course Web site • Obtain a Proctor for Exams by Jan. 30. • Lab Assignment 13-1 requires a usable mic

23. Lab assistance, questions, and chat time • Questions? • Comments? • Concerns?