Linux System Administration class: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(update class info, various small rewrites and formatting)
(updated info for December 18 class topic)
Line 1: Line 1:
'''Current (Tuesday 20121218):'''  
'''Current (Tuesday 20121218):'''  
* TBD
* A Tour of Linux Information--on-line help, man pages, /usr/share/doc and more.


'''Potential Upcoming Classes:
'''Potential Upcoming Classes:

Revision as of 17:08, 15 December 2012

Current (Tuesday 20121218):

  • A Tour of Linux Information--on-line help, man pages, /usr/share/doc and more.

Potential Upcoming Classes:

  • Man Pages
  • Understanding Log Files
  • Introduction to Git
  • Partitioning and Filesystems 2: EFI and GUID/Gpt Partitions

Previous:

  • December 11: Partitioning and File Systems
  • December 4: X11/Xorg
               Xorg is not a GUI!  What is it?
               Understanding X Server/Client
               Using Xnest, SSH, VNC
               Understanding framebuffers
  • November 27: Users, Groups, Permissions


General Info:

System administration topics include

  • managing users, groups, and permissions
  • monitoring and managing storage and file systems
  • understanding the Filesystem Hierarchical Standard as a global namespace
  • a tour of the Linux directory tree, with emphasis on commands
  • monitoring and managing processes
  • installing and configuring server software
  • configuring and updating XOrg X11 GUI systems
  • installing and configuring devices, firmware, and modules
  • kernel tuning
  • network configuration
  • introduction to compiling a C program and using make, using chkrootkit.c as the example
  • writing shell scripts
  • command-line essentials

The principles are the same across Linux distributions, but some distributions share common configuration approaches. The examples in these classes will generally reference both the Debian and the Red Hat approaches.

Most of the above topics require a sequence of two or more classes for completion. Such class sequences are progressive, and success requires attendance for all classes in the sequence.

Each topic stands alone; there are no dependencies among them. The assumption is that attendees are at least familiar with command-line shells.

Because command-line skills are generally required, the command-line essentials class (a one-class introduction) will be repeated.