Open main menu

CDOT Wiki β

Changes

User:Chris Tyler/OPS235 Updates

2,687 bytes added, 11:32, 18 December 2011
Created page with '{{Chris Tyler Draft}} = Intro = OPS235 is due for another update, to Fedora 16 + current practices. This page is a scratchpad for recording proposed changes. = Course Structur…'
{{Chris Tyler Draft}}

= Intro =

OPS235 is due for another update, to Fedora 16 + current practices. This page is a scratchpad for recording proposed changes.

= Course Structure =

Brian has proposed a number of changes to the course structure. Unfortunately, at the time of writing, Mercury is down so I can't check them, but IIRC:

== Tests ==

Drop written test #2.

== Assignments ==

Use one larger assignment.

== Labs ==

Drop lab #1.

= Course Content =

== SysVInit -> Systemd ==

Systemd has replaced the sysvinit system. Since systemd has been accepted by other distros, we should teach it as the primary way of managing the init system. However, we should touch on the POSIX/sysvinit tools as well.

* Add:
** systemctl
** unit files
** service levels
* Reduce:
** chkconfig
** service
* Discuss:
** Bind mounts (ugly mount table)

== Interface Names ==

Interface names are now named according to the BIOS device label. This is important for server-class systems which are rackmounted. In the past, "eth0", "eth1", "eth2" were hard to line up with back-panel connectors; now, if the BIOS says that the ports are labelled "network-A", "network-B", and "network-C", that's what the interface names are. If there are no names in the BIOS, embedded ports come up as emX and PCI ports come up as pXpN (PCI slot X port N).

== Loopback Mount Option ==

No longer required -- loopback is assumed if the mount source is not a block device.

== netstat ==

Command is obsolete according to the documentation. Change coverage to the 'ip' command.

== git ==

Add coverage of the '''git''' version-control system.

= Course Page Layout =

== Refactor Web Pages ==

Students are doing the labs without, in some cases, really understanding what they're supposed to be understanding from the lab. Proposed structure:

# Challenge - outline the task that needs to be performed
# Background - background information for the task
# Resources - links to resources related to the task
# Before You Begin - preparation and warnings before starting
# Steps - how to perform the task
# Debugging - debugging guidelines for this type of task (e.g., for network connectivity issues, guide through "IP, routing, nameservice" debugging)
# Observations - things which the student should note or think through
# Submitting the Lab - how to get the lab marked -- '''Question:''' Should this be based more on the Observations and less on the Steps section above?
# Preparing for the Quizzes - additional questions to be answered

== Use graphics more extensively ==

* Create some templates for graphics for sections and notes
* Break the page up visually so that it's not one massive bunch'o'scrolling