Escolar Documentos
Profissional Documentos
Cultura Documentos
1. The CTDP Linux User's Guide - This document gives the user a
good organized overview of Linux including basic commands, file
structure, file systems, system configuration, managing users and
processes, networking and the respective services, including the
configuration of X. It explains how to set up filesystems, how to
set liLO and the kernel up, working with the init process, setting
up system logging, CRON, user accounting, user limits, printing,
setting up the network, Samba services, DNS, DHCP, BOOTP, IP
masquerading, using linux as a router, network file sharing (NFS)
and more.
2. How Linux Works CTDP Guide - This document explains in detail,
how the system operates from the kernel operation, and how it
locates the root filesystem to how many system and network
services work. This document explains the inner workings from
the BIOS, through the operation of the boot loader (liLO), loading
the kernel, and more. It continues with explanations of the various
system runlevels, the init process, and how the startup script files
are structured and operates. It explains the login process, the
shell, and system environment, filesystems, devices, keymapping,
system configuration, X, and various daemons, system and
networking services. This guide is an essential key in a complete
understanding of Linux.
3. CTDP Linux Files and Command Reference - This manual
explains in more detail the Linux file system and Linux
configuration file details. It also lists many commands by category
available in Linux giving a brief description of each one. Available
in PDF Format here.
4. Linux Brief CTDP How-tos - This document contains a multitude
of handy brief how-tos. The how-tos are organized by category
and they include, how to install and run a recent version of the
JAVA environment, how to perform diskless boots from client
computers using Linux as a server, and some tips on script
writing.
5. The CTDP Linux Startup Manual - This manual documents in
great detail how linux boots from the operation of BIOS, the LiLO
boot loader, the kernel, to intricate detail on each startup script
and beyond.
6. The CTDP Linux Programmer's Guide - This guide documents
much about programming on the Linux operating system, from
script writing, to C and more. This document is under
development. Currently it includes information about script writing
in Linux, with information about Linux structures and signals
required for programming. It includes script and C code examples.
This document will be expanded to include C++, and GUI tools as
time permits.
Please note that all user's material is written not only from a system
administrator point of view, but the system is considered to be a full
server configuration. The only possible reason for installing Linux as a
workstation rather than a server, would be due to hardware limitations
on the system it is being installed on. Other than that, perhaps a user is
sure the server functions will never be needed. In this case, if a user is
so severely limiting the capability of Linux, then why should they not run
a Windows workstation, except to save money? To me, running Linux
as a workstation is a waste since it was designed for so much more. A
friend of mine compared it to using a bus as a commuter vehicle with
the only rider being the driver.
Much of the problem with learning Linux is that there are so many
available commands and tools along with a variety of ways to
accomplish each task. The main goal of this documentation is to help
the reader more quickly discover what those tools and commands are
and thereby learn faster. This is done by categorizing capabilities into
various sections which describe various operating system functions.
This document attempts to give examples and reasonably full
explanations about the various tools involved but more emphasis has
been placed on having a reasonable listing of tools. As this
documentation is upgraded, where it is helpful, additional examples and
explanations will be added. One of the greatest problems in writing this
documentation is that many functional areas run over into other
functional areas. For instance filesystems and user quotas both deal
with filesystems. Therefore some information may be repeated in
various sections or documents in order to avoid the necessity of looking
in many areas for complete information.