Linux System Administration class
Current: We're studying IP Tables and secure server installation, admin, and configurations. Upcoming sessions should further explore iptables command arguments.
Potential Upcoming Classes:
- Understanding Log Files
- Partitioning and Filesystems 2: EFI and GUID/Gpt Partitions
- Man Pages efficient usage and navigation (when to 'man-up' and when to cheat with gui edibles)
- Open-ended review of network configuration files typically found in the /etc directory.
- Git : Fourth class exercising the use of git on our local machines in sync with an internet-accessible git repository.
- Introduction to Git continues
- January 29: SSH into remote box, change password, clone git repo to local machine, create file and check git status Notes on github
- Text files and their purposes along with an introduction to vi and vim features.
- December 11: Partitioning and File Systems
- December 4: X11/Xorg
Xorg is not a GUI! What is it? (and why the fuck do you have to compile it from source for FreeBSD???) Understanding X Server/Client Using Xnest, SSH, VNC Understanding framebuffers Users, Groups, Permissions
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 all GNU/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) may be presented from time to time.