Archive:Docs/Drafts/AdministrationGuide

From FedoraProject

Jump to: navigation, search
Important.png
Document relocated!
The Administration Guide content has been moved to here.

Contents

Administration Guide

Documentation Summary:

Purpose: Document covering how to accomplish specific administrative tasks.

Audience: Individuals responsible for managing one or more Fedora systems.

Assumptions: The reader has access to a Fedora installation, but no particular type may be assumed. The system has the default network services installed with all Fedora installation types (SMTP, SSH, NFS, CUPS, and mDNS). The reader has a user account with the default settings. The reader has access to the root password. It is assumed that the reader has a basic knowledge of TCP/IP.

Related Documents: The DesktopUserGuide documents tasks using the desktop applications. The GettingStartedGuide is a general introduction to using Fedora. A Command-Line Survival Guide has been proposed to cover process management, file handling etc. A tutorial on Managing Software with yum has already been released. Look at the seminal Red Hat Enterprise Linux Introduction to System Administration for good ideas.

Lead Writer: Bart Couvreur

All contributors and module assignments


Sections

Pages for individual chapters:

Summary of Sections

Brief description of the chapters:


Understanding the Directory Structure

Working with User Accounts

Permissions

Access Controls

Managing Storage and Partitions

LVM (Logical Volume Management) is the default for Fedora systems.


Working with Disks and Removable Storage

By default, attached storage should Just Work. Administrators may wish to modify the behavior of the mount system, or disable access to removable storage.

Managing Software

Managing Services

Modifying the Startup Process

Using the Network File System

NFS is effectively an extension of the filesystem. The complication is maintaining a consistent set of account information between systems - LDAP requires separate documentation.

Using the Common UNIX Printing System


Servers


Modifying the X Window System

Monitoring the System

Scheduling Tasks

Note that /etc/cron.* directories are sufficient for most tasks, but crontab ought to be mentioned for more precise control.