diff --git a/Manuals/HowTos/Dialup/Administration.docbook b/Manuals/HowTos/Dialup/Administration.docbook
deleted file mode 100755
index a16f3df..0000000
--- a/Manuals/HowTos/Dialup/Administration.docbook
+++ /dev/null
@@ -1,13 +0,0 @@
-<part id="administration">
-
- <title>Administration</title>
-
- <partintro>
- <para>
- ...
- </para>
- </partintro>
-
- &administration-mail;
-
-</part>
diff --git a/Manuals/HowTos/Dialup/Administration.ent b/Manuals/HowTos/Dialup/Administration.ent
deleted file mode 100644
index 8feac9d..0000000
--- a/Manuals/HowTos/Dialup/Administration.ent
+++ /dev/null
@@ -1,2 +0,0 @@
-<!ENTITY administration SYSTEM "Administration.docbook">
-<!ENTITY administration-mail SYSTEM "Administration/Mail.docbook">
diff --git a/Manuals/HowTos/Dialup/Administration/Mail.docbook b/Manuals/HowTos/Dialup/Administration/Mail.docbook
deleted file mode 100644
index 04b9c1d..0000000
--- a/Manuals/HowTos/Dialup/Administration/Mail.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<chapter id="administration-mail">
-
- <title>Mail Server Administration</title>
-
- <para>
- ...
- </para>
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Client.docbook b/Manuals/HowTos/Dialup/Client.docbook
deleted file mode 100644
index 6a43d5a..0000000
--- a/Manuals/HowTos/Dialup/Client.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<part id="client">
-
- <title>The Client Computer</title>
-
- &client-usage;
- &client-install;
- &client-config;
-
-</part>
diff --git a/Manuals/HowTos/Dialup/Client.ent b/Manuals/HowTos/Dialup/Client.ent
deleted file mode 100644
index ad1d416..0000000
--- a/Manuals/HowTos/Dialup/Client.ent
+++ /dev/null
@@ -1,15 +0,0 @@
-<!ENTITY client SYSTEM "Client.docbook">
-<!ENTITY client-usage SYSTEM "Client/Usage.docbook">
-<!ENTITY client-usage-overview SYSTEM "Client/Usage/overview.docbook">
-<!ENTITY client-install SYSTEM "Client/Install.docbook">
-<!ENTITY client-install-overview SYSTEM "Client/Install/overview.docbook">
-<!ENTITY client-install-modem SYSTEM "Client/Install/modem.docbook">
-<!ENTITY client-install-pppd SYSTEM "Client/Install/pppd.docbook">
-<!ENTITY client-install-wvdial SYSTEM "Client/Install/wvdial.docbook">
-<!ENTITY client-install-scn SYSTEM "Client/Install/scn.docbook">
-<!ENTITY client-config SYSTEM "Client/Config.docbook">
-<!ENTITY client-config-overview SYSTEM "Client/Config/overview.docbook">
-<!ENTITY client-config-modem SYSTEM "Client/Config/modem.docbook">
-<!ENTITY client-config-pppd SYSTEM "Client/Config/pppd.docbook">
-<!ENTITY client-config-wvdial SYSTEM "Client/Config/wvdial.docbook">
-<!ENTITY client-config-scn SYSTEM "Client/Config/scn.docbook">
diff --git a/Manuals/HowTos/Dialup/Client/Config.docbook b/Manuals/HowTos/Dialup/Client/Config.docbook
deleted file mode 100644
index 3f8064c..0000000
--- a/Manuals/HowTos/Dialup/Client/Config.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="client-config">
-
- <title>Dial-Up Client Configuration</title>
-
- &client-config-overview;
- &client-config-modem;
- &client-config-pppd;
- &client-config-wvdial;
- &client-config-scn;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Client/Config/hardware.docbook b/Manuals/HowTos/Dialup/Client/Config/hardware.docbook
deleted file mode 100644
index 7fdf79c..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/hardware.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-config-hardware">
-
- <title>Configuring Client Hardware</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/modem.docbook b/Manuals/HowTos/Dialup/Client/Config/modem.docbook
deleted file mode 100644
index 21df06e..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/modem.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-config-hardware">
-
- <title>Configuring Modem Hardware</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/overview.docbook b/Manuals/HowTos/Dialup/Client/Config/overview.docbook
deleted file mode 100644
index 371a1d9..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/overview.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-config-overview">
-
- <title>Overview</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/pppd.docbook b/Manuals/HowTos/Dialup/Client/Config/pppd.docbook
deleted file mode 100644
index c46501e..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/pppd.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<sect1 id="client-config-pppd">
-
- <title>Configuring <package>pppd</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/scn.docbook b/Manuals/HowTos/Dialup/Client/Config/scn.docbook
deleted file mode 100644
index 63bc71a..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/scn.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<sect1 id="client-config-scn">
-
- <title>Configuring <package>system-config-network</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/software.docbook b/Manuals/HowTos/Dialup/Client/Config/software.docbook
deleted file mode 100644
index f374689..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/software.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-config-software">
-
- <title>Configuring Client Software</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Config/wvdial.docbook b/Manuals/HowTos/Dialup/Client/Config/wvdial.docbook
deleted file mode 100644
index bedda86..0000000
--- a/Manuals/HowTos/Dialup/Client/Config/wvdial.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-config-wvdial">
-
- <title>Configuring <package>wvdial</package> Package</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install.docbook b/Manuals/HowTos/Dialup/Client/Install.docbook
deleted file mode 100644
index fc1c470..0000000
--- a/Manuals/HowTos/Dialup/Client/Install.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="client-install">
-
- <title>Dial-Up Client Installation</title>
-
- &client-install-overview;
- &client-install-modem;
- &client-install-pppd;
- &client-install-wvdial;
- &client-install-scn;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Client/Install/hardware.docbook b/Manuals/HowTos/Dialup/Client/Install/hardware.docbook
deleted file mode 100644
index 53a4f84..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/hardware.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-hardware">
-
- <title>Installing Client Hardware</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/modem.docbook b/Manuals/HowTos/Dialup/Client/Install/modem.docbook
deleted file mode 100644
index c879194..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/modem.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-hardware">
-
- <title>Installing Modem Hardware</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/overview.docbook b/Manuals/HowTos/Dialup/Client/Install/overview.docbook
deleted file mode 100644
index b62e798..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/overview.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-overview">
-
- <title>Overview</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/pppd.docbook b/Manuals/HowTos/Dialup/Client/Install/pppd.docbook
deleted file mode 100644
index 0ac5fe4..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/pppd.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<sect1 id="client-install-pppd">
-
- <title>Installing <package>pppd</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/scn.docbook b/Manuals/HowTos/Dialup/Client/Install/scn.docbook
deleted file mode 100644
index 4215391..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/scn.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-scn">
-
- <title>Installing <package>system-config-network</package> Package</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/software.docbook b/Manuals/HowTos/Dialup/Client/Install/software.docbook
deleted file mode 100644
index e057cdf..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/software.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-software">
-
- <title>Installing Client Software</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Install/wvdial.docbook b/Manuals/HowTos/Dialup/Client/Install/wvdial.docbook
deleted file mode 100644
index 3f5813f..0000000
--- a/Manuals/HowTos/Dialup/Client/Install/wvdial.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-install-wvdial">
-
- <title>Installing <package>wvdial</package> Package</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Client/Usage.docbook b/Manuals/HowTos/Dialup/Client/Usage.docbook
deleted file mode 100644
index af40f42..0000000
--- a/Manuals/HowTos/Dialup/Client/Usage.docbook
+++ /dev/null
@@ -1,7 +0,0 @@
-<chapter id="client-usage">
-
- <title>Dial-Up Client Usage</title>
-
- &client-usage-overview;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Client/Usage/overview.docbook b/Manuals/HowTos/Dialup/Client/Usage/overview.docbook
deleted file mode 100644
index a8f32d8..0000000
--- a/Manuals/HowTos/Dialup/Client/Usage/overview.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="client-usage-overview">
-
- <title>Overview</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Commons.ent b/Manuals/HowTos/Dialup/Commons.ent
deleted file mode 100755
index f5bcdd1..0000000
--- a/Manuals/HowTos/Dialup/Commons.ent
+++ /dev/null
@@ -1,23 +0,0 @@
-<!--
- $Id$
- This file defines entities for words and phrases frequently used
- inside The CentOS Project Infrastructure manual. It is a way of
- normalizing the use of concepts inside the documentation and make
- their maintainance easier to realize.
--->
-
-<!-- About The CentOS Project -->
-
-<!ENTITY C "CentOS">
-<!ENTITY TC "The &C;">
-<!ENTITY TCP "<ulink type='http' url='http://www.centos.org'>&TC; Project</ulink>">
-<!ENTITY TCC "&TC; Community">
-<!ENTITY TCD "&TC; Distribution">
-<!ENTITY TCMIRRORS "<ulink url='http://mirrors.centos.org/'>&TC; Mirrors</ulink>">
-<!ENTITY TCWIKI "<ulink type='http' url='http://wiki.centos.org/'>&TC; Wiki</ulink>">
-
-<!-- About The CentOS Project Infrastructure -->
-
-<!ENTITY TCPI "The CentOS Project Infrastructure">
-<!ENTITY TCAR "<ulink url='https://projects.centos.org/svn/artwork'>The CentOS Artwork Repository</ulink>">
-<!ENTITY TCPIUG "<citetitle>&TCPI; User's Guide</citetitle>">
diff --git a/Manuals/HowTos/Dialup/Configurations.docbook b/Manuals/HowTos/Dialup/Configurations.docbook
deleted file mode 100755
index f470587..0000000
--- a/Manuals/HowTos/Dialup/Configurations.docbook
+++ /dev/null
@@ -1,20 +0,0 @@
-<part id="configurations">
-
- <title>Configurations</title>
-
- <partintro>
- <para>
- This part of the book discusses the configuration of specific
- infrastructures that may or may not be included inside &TCPI;.
- Each configuration described here is oriented to satisfy
- specific practical situations in a step-by-step fashion, so it
- can be implemented as straightforward as possible. The
- packages and documentation references related to each
- configuration are also mentioned so you can get deeper on each
- topic in case you need so.
- </para>
- </partintro>
-
- &configurations-dialup;
-
-</part>
diff --git a/Manuals/HowTos/Dialup/Configurations.ent b/Manuals/HowTos/Dialup/Configurations.ent
deleted file mode 100755
index 410c988..0000000
--- a/Manuals/HowTos/Dialup/Configurations.ent
+++ /dev/null
@@ -1,7 +0,0 @@
-<!ENTITY configurations SYSTEM "Configurations.docbook">
-<!ENTITY configurations-dialup SYSTEM "Configurations/Dialup.docbook">
-<!ENTITY configurations-dialup-intro SYSTEM "Configurations/Dialup/intro.docbook">
-<!ENTITY configurations-dialup-usage SYSTEM "Configurations/Dialup/usage.docbook">
-<!ENTITY configurations-dialup-modem SYSTEM "Configurations/Dialup/modem.docbook">
-<!ENTITY configurations-dialup-server SYSTEM "Configurations/Dialup/server.docbook">
-<!ENTITY configurations-dialup-client SYSTEM "Configurations/Dialup/client.docbook">
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup.docbook
deleted file mode 100644
index b336433..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="configurations-dialup">
-
- <title>IP Through Telephone Line</title>
-
- &configurations-dialup-intro;
- &configurations-dialup-usage;
- &configurations-dialup-modem;
- &configurations-dialup-server;
- &configurations-dialup-client;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup/client.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup/client.docbook
deleted file mode 100644
index 26adb42..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup/client.docbook
+++ /dev/null
@@ -1,97 +0,0 @@
-<sect1 id="configurations-dialup-client">
-
- <title>The Client Computer</title>
-
- <sect2 id="configurations-dialup-client-install">
- <title>Installing Client Computer</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2 id="configurations-dialup-client-config">
- <title>Configuring Client Computer</title>
-
- <para>
- ...
- </para>
-
- <sect3 id="server-config">
- <title>Establishing Dial-Up Connection</title>
-
- <para>
- To establish connection from the client computer to the server
- computer you should configure the client computer to dial-up
- the server computer, using the following information:
- </para>
-
-<screen>
- ISP Name: server.example.com
-ISP Phone: +53043515094
- Username: client.example.com
- Password: mail4u
-</screen>
-
- <para>
- To estabalish a dial-up connection from the client computer to
- the server computer, you need to determine the modem location
- assigned by the operating system, so you can instruct
- applications like <command>system-config-network</command> the
- correct device they will to talk to. This configuration
- process has been greatly simplified by the
- <command>wvdialconf</command> command distributed with the
- <package>wvdial</package>
- package. To do this, run the following command and pay
- attention to the three last lines of its output:
- </para>
-
- <screen>wvdialconf /etc/wvdial.conf</screen>
-
-<screen>
-Scanning your serial ports for a modem.
-
-ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
-ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
-ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
-Port Scan<*1>: S1 S2 S3
-WvModem<*1>: Cannot get information for serial port.
-ttyACM0<*1>: ATQ0 V1 E1 -- OK
-ttyACM0<*1>: ATQ0 V1 E1 Z -- OK
-ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK
-ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
-ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
-ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
-ttyACM0<*1>: Modem Identifier: ATI -- LT V.90 1.0 MT5634ZBA-USB
-Data/Fax Modem (Dual Config) Version 5.18e
-ttyACM0<*1>: Speed 4800: AT -- OK
-ttyACM0<*1>: Speed 9600: AT -- OK
-ttyACM0<*1>: Speed 19200: AT -- OK
-ttyACM0<*1>: Speed 38400: AT -- OK
-ttyACM0<*1>: Speed 57600: AT -- OK
-ttyACM0<*1>: Speed 115200: AT -- OK
-ttyACM0<*1>: Speed 230400: AT -- OK
-ttyACM0<*1>: Speed 460800: AT -- OK
-ttyACM0<*1>: Max speed is 460800; that should be safe.
-ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
-
-Found an USB modem on /dev/ttyACM0.
-Modem configuration written to /etc/wvdial.conf.
-ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
-</screen>
-
- <para>
- Now, using this information, configure a Modem connection
- using the interface provided by
- <command>system-config-network</command> command. Take care of
- replacing the <filename>/dev/modem</filename> device name by
- that one found by <command>wvdialconf</command>. At this
- point, you can use the button Activate from
- <command>system-config-network</command> to establish the
- Modem connection you just configured.
- </para>
-
- </sect3>
- </sect2>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup/intro.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup/intro.docbook
deleted file mode 100644
index cad9a6a..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup/intro.docbook
+++ /dev/null
@@ -1,24 +0,0 @@
-<sect1 id="configurations-dialup-intro">
-
- <title>Introduction</title>
-
- <para>
- This chapter describes two computers configuration, one acting
- as server and other as client. The server computer will be
- configured to provide internet services and the client to make
- use of those internet services provided by the server
- computer. The connection medium both client and server
- computer use is the telelphone line (i.e., the same medium you
- use to realize phone calls). In this configuration, both
- client and server computers use special devices named
- <quote>Modems</quote> to transmit data in form of sound across
- the telephone line.
- </para>
-
- <para>
- The configuration described in this chapter could be a good
- choise when the only communication medium you have access to
- is a telephone network.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup/modem.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup/modem.docbook
deleted file mode 100644
index fcbc030..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup/modem.docbook
+++ /dev/null
@@ -1,68 +0,0 @@
-<sect1 id="configurations-dialup-modem">
-
- <title>The Modem Hardware</title>
-
- <para>
- In order to establish a PPP link between two computers using
- the telephone line as medium for data transmission, you need
- to install (at least) one modem device in each computer.
- </para>
-
- <para>
- To install a modem device in computer you need to attach the
- modem hardware to the computer and later the telephone line to
- the modem hardware. To connect the modem to your computer, you
- need to connect the serial or USB cable that comes from the
- modem hardware to the appropriate input on your computer. To
- connect the modem to the telephone line system, you need to
- unplug the cable that connects your telephone device and plug
- it on the modem device, specifically in the port reserved for
- data transmission. Later, using a similar cable, you could
- connect your telephone device to the modem's telephone port,
- so you can realize telephone calls when no data transmition
- take place.
- </para>
-
- <para>
- To be on the safe side, do all the installation with the
- computer turned off. Then, when everthing has been put in
- place, turn it on. Once the system is up, you can verify the
- modem hardware using either the <command>lsusb</command> or
- <command>lspci</command> commands. These commands need to be
- run with administrative privileges, so probably need to
- <command>sudo</command> them or login as <systemitem
- class="username">root</systemitem> user in order to execute
- thme. For example, assuming you are logged in as root user,
- and you are using an USB modem like that one we mentioned
- before, the output of <command>lsusb</command> command would
- look like the following:
- </para>
-
-<screen>
-Bus 003 Device 001: ID 0000:0000
-Bus 001 Device 001: ID 0000:0000
-Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
-Bus 002 Device 001: ID 0000:0000
-Bus 005 Device 003: ID 06e0:f104 Multi-Tech Systems, Inc.
-MT5634ZBA-USB MultiModemUSB (new firmware)
-Bus 005 Device 001: ID 0000:0000
-Bus 005 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
-Bus 004 Device 001: ID 0000:0000
-</screen>
-
- <para>
- The relevant line here is that mentioning the existence of a
- <code>Multi-Tech System, Inc. MT5634ZBA-USB MultiModemUSB (new
- firmware)</code> device. If the modem you installed doesn't
- appear in this list, it is probably because such hardware is
- not supported by &TCD;, yet.
- </para>
-
- <para>
- At this point, everything is ready for you to install and
- configure the computer either as server (see <xref
- linkend="configurations-dialup-server" />) or client (see
- <xref linkend="configurations-dialup-client" />).
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup/server.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup/server.docbook
deleted file mode 100644
index 37042fe..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup/server.docbook
+++ /dev/null
@@ -1,789 +0,0 @@
-<sect1 id="configurations-dialup-server">
-
- <title>The Server Computer</title>
-
- <sect2 id="configurations-dialup-server-install">
- <title>Installing Server Computer</title>
-
- <para>
- Start with a minimal installation of &TCD;, bootup the
- operating system, and login as root user.
- </para>
-
- <sect3 id="configurations-dialup-server-install-ppp">
- <title>Installing Ppp Server</title>
- <para>
- The ppp server provides the software required to establish and
- maintain a PPP link with another system and negociate Internet
- Protocol addresses for each end of the link.
- </para>
-
- <screen>yum install ppp</screen>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-install-dns">
- <title>Installing Name Server</title>
- <para>
- The name server provides the software required to translate
- domain names into IP address and IP addresses into domain
- names. With this software you can rembember addresses like
- <ulink url="https://server.example.com/" /> instead of
- addresses like <ulink url="https://192.168.0.1/" />. There
- are other feautres (e.g., mail exchanger resolution, zone
- delegation, etc.) provided by this software that aren't used
- in the point-to-point configuration we describe in this
- chapter.
- </para>
- <screen>yum install bind</screen>
- <note>
- <para>
- There is a <package>bind-chroot</package> packages, however,
- we aren't using it because SELinux is already enforced on the
- &TCD; filesystem and it provides far more security than the
- idea of <package>bind-chroot</package> package itself does.
- </para>
- </note>
- </sect3>
-
- <sect3 id="configurations-dialup-server-install-mail">
- <title>Installing Mail Server</title>
- <para>
- The mail server provides the software required to let you
- send/receive mail messages to/from others. The mail server
- is splitted in three basic components: The Mail Transfer Agent
- (MTA), The Mail Delivery Agent (MDA) and an intermediary
- daemon named <systemitem class="daemon">saslauthd</systemitem>
- to handle user authentication. The MTA is the program your
- mail client sends mail messages to. The MDA, on the other
- hand, is the program your mail client reads mail message
- from (i.e., this is the program that let you access your
- mailbox). The saslauthd daemon is used by the MDA to
- authenticate user's credentials (e.g., the information that
- let you access an specific mailbox) and by the MTA to
- authenticate users before sending mail to it, however, in the
- configuration we are implementing, the MTA doesn't require
- that you authenticate to it in order to send mails through
- it. The MTA will listen on all network interfaces it is
- attached to and will receive mail sent to <systemitem
- class="fqdomainname">example.com</systemitem> domain name or
- <systemitem
- class="fqdomainname">server.example.com</systemitem> host
- name).
- </para>
-
- <screen>yum install postfix cyrus-{imapd{,-utils},sasl{,-ldap,-md5,-plain}}</screen>
-
- <para>
- By default, the <application>sendmail</application>
- program is used as mail transfer agent, not postfix. For the
- sake of that point-to-point configuration we are implementing,
- I decided to use postfix instead as default mail transfer
- agent, not sendmail. To effectively achieve this decition, it
- is required to use the <command>alternatives</command>
- command, as it shown below:
- </para>
-
- <screen>alternatives --config mta</screen>
-
- <para>
- This command will present you a menu to chose between
- available mail transfer agents, so it is there where you
- choose to use posfix as default option. Now that you've
- changed postfix the default mail transfer agent, you can
- saftly remove the sendmail package to avoid unused software
- to remain inside the computer. To do this, you can run the
- following command:
- </para>
-
- <screen>yum remove sendmail</screen>
-
- <para>
- In addition to mail server specific packages, we also provide
- mailing list support. Mailing lists provide mail addresses
- that users registered inside the ISP can write to. When you
- sed an mail to a mailing list, your message is distributed to
- all members of that list. In order for this to happen, people
- registered inside ISP need to subscribe themselves into that
- mailing list they want to receive messages from. The
- subscription of mailinglist will be available through a secured
- web application in the following url:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://example.com/lists/" />
- </para>
- </listitem>
- </itemizedlist>
-
- <screen>yum install mailman</screen>
- </sect3>
-
- <sect3 id="configurations-dialup-server-install-web">
- <title>Installing Web Server</title>
- <para>
- The web server provides the software required to support web
- interfaces like those one previously mention to register new
- users inside the ISP and subscribe mailing lists. The web
- server provided in this configuration will accept requests
- both unencrypted and encrypted.
- </para>
-
- <screen>yum install httpd mod_ssl crypto-utils</screen>
-
- <para>
- In addition to mailing lists support, the web server will
- provide access to Subversion. Subvesion provides a way to
- manage files through version control. The main purpose of
- providing Subversion support here is sharing the version of
- &TCAR; I've been working on.
- </para>
-
- <screen>yum install subversion mod_dav_svn</screen>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-install-ldap">
-
- <title>Installing Directory Server</title>
-
- <para>
- The directory server provides the software required to unify
- user information. This server is access by other server
- whenever user information is required. You, as end user, can
- also use this server from your workstation to retrive a list
- of all users registered in the ISP. This list can be retrived
- by the web interface the ISP provides, or any application your
- workstation provide (e.g., most mail clients provide a way
- to configure LDAP servers to build address book from it.).
- </para>
-
- <screen>yum openldap-servers python-ldap</screen>
-
- </sect3>
- </sect2>
-
- <sect2 id="configurations-dialup-server-config">
- <title>Configuring Server Computer</title>
- <para>
- Once all required packages have been installed inside the
- server computer, it is time to configure them. This section
- describes how to configure the server computer to provide a
- public mail system.
- </para>
-
- <sect3 id="configurations-dialup-server-install-network">
- <title>Configuring Network Internface</title>
- <variablelist>
- <varlistentry>
- <term><filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename></term>
- <listitem>
-<screen>
-# Please read /usr/share/doc/initscripts-*/sysconfig.txt
-# for the documentation of these parameters.
-TYPE=Ethernet
-DEVICE=eth0
-HWADDR=00:1c:c0:f0:aa:05
-BOOTPROTO=none
-NETMASK=255.255.255.0
-IPADDR=192.168.0.1
-ONBOOT=yes
-USERCTL=no
-IPV6INIT=no
-PEERDNS=yes
-</screen>
- </listitem>
- </varlistentry>
- </variablelist>
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-ppp">
- <title>Configuring Ppp Server</title>
- <para>
- This configuration specifies the way the server computer will
- handle incoming dial-up connections.
- </para>
- <variablelist>
- <varlistentry>
- <term><filename>/etc/ppp/options</filename></term>
- <listitem>
-<screen>
-# Enforce the use of the hostname as the name of the local system for
-# authentication purposes (overrides the name option).
-usehostname
-
-# Specify which DNS Servers the incoming Win95 or WinNT Connection
-# should use Two Servers can be remotely configured
-ms-dns 192.168.0.1
-
-# Increase debugging level (same as -d). The debug output is written
-# to syslog LOG_LOCAL2.
-debug
-
-# Require the peer to authenticate itself before allowing network
-# packets to be sent or received. Please do not disable this setting.
-# It is expected to be standard in future releases of pppd. Use the
-# call option (see manpage) to disable authentication for specific
-# peers.
-#auth
-
-# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
-# on the serial port.
-crtscts
-
-# Specifies that pppd should use a UUCP-style lock on the serial
-# device to ensure exclusive access to the device.
-lock
-
-# Use the modem control lines.
-modem
-
-# async character map -- 32-bit hex; each bit is a character that
-# needs to be escaped for pppd to receive it. 0x00000001 represents
-# '\x01', and 0x80000000 represents '\x1f'. To allow pppd to work
-# over a rlogin/telnet connection, ou should escape XON (^Q), XOFF
-# (^S) and ^]: (The peer should use "escape ff".)
-#asyncmap 200a0000
-asyncmap 0
-
-# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
-# notation (e.g. 255.255.255.0).
-netmask 255.255.255.0
-
-# Don't fork to become a background process (otherwise pppd will do so
-# if a serial device is specified).
-nodetach
-
-# Set the assumed name of the remote system for authentication
-# purposes to <n>.
-remotename client
-
-# If this option is given, pppd will send an LCP echo-request frame to
-# the peer every n seconds. Under Linux, the echo-request is sent when
-# no packets have been received from the peer for n seconds. Normally
-# the peer should respond to the echo-request by sending an
-# echo-reply. This option can be used with the lcp-echo-failure
-# option to detect that the peer is no longer connected.
-lcp-echo-interval 30
-
-# If this option is given, pppd will presume the peer to be dead if n
-# LCP echo-requests are sent without receiving a valid LCP echo-reply.
-# If this happens, pppd will terminate the connection. Use of this
-# option requires a non-zero value for the lcp-echo-interval
-# parameter. This option can be used to enable pppd to terminate
-# after the physical connection has been broken (e.g., the modem has
-# hung up) in situations where no hardware modem control lines are
-# available.
-lcp-echo-failure 4
-
-# Specifies that pppd should disconnect if the link is idle for n
-# seconds.
-idle 60
-</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>/etc/ppp/cha-secrets</filename></term>
- <term><filename>/etc/ppp/pap-secrets</filename></term>
- <listitem>
-<screen>
-# client server secret IP addresses
-
-# Specify the client configuration. This is when this manchine calls
-# someone's else machine and tries to establish a point-to-point
-# connection. Most of this configuration is handled by the
-# `system-config-network' utility.
-#
-####### redhat-config-network will overwrite this part!!! (begin) ##########
-####### redhat-config-network will overwrite this part!!! (end) ############
-
-# Specify the server configuration. This is when someone's else
-# machine calls this machine trying to establish a point-to-point
-# connection. This part of the configuration isn't handled by
-# `system-config-network' utility. To prenvent this configuration to
-# be lost the next time the `system-config-network' utility be used,
-# be sure to have this configuration backed up somewhere so it can be
-# resotred in such situations.
-#
-client server mail4u 192.168.0.2
-server client mail4u 192.168.0.1
-</screen>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- To make the modem respond to calls ...
- </para>
-
- <screen>pppd /dev/ttyACM0</screen>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-dns">
- <title>Configuring Name Server</title>
-
- <variablelist>
- <varlistentry>
- <term><filename>/etc/named.conf</filename></term>
- <listitem>
-<screen>
-# BIND DNS server 'named' configuration file for the Red Hat BIND
-# distribution. This file was initially taken from
-# `/usr/share/doc/bind-*/samples/named.conf' file and modified to fit
-# this server's needs.
-#
-# This machine exists to develop The CentOS Project Corporate Identity
-# through The CentOS Artwork Repository. Presently, this machine is
-# isolated from Internet. However, a modem has been attached[1] and
-# configured so people can establish point-to-point connections to
-# this machine and download working copies of The CentOS Artwork
-# Repository and help me to develop it.
-#
-# In this configuration there are only two IP addresses involved. The
-# one used in this server (192.168.0.1) and another for the client who
-# realize the point-to-point connection (192.168.0.2). This server is
-# named `server.example.com' and the client `client.example.com' or
-# something similar.
-# --------------------------------------------------------------------
-# See the BIND Administrator's Reference Manual (ARM) for details, in:
-# file:///usr/share/doc/bind-*/arm/Bv9ARM.html
-#
-# Also see the BIND Configuration GUI:
-# /usr/bin/system-config-bind and its manual.
-# --------------------------------------------------------------------
-
-options {
-
- # Those options should be used carefully because they disable port
- # randomization.
- // query-source port 53;
- // query-source-v6 port 53;
-
- # Put files that named is allowed to write in the data/ directory:
- directory "/var/named"; // the default
- dump-file "data/cache_dump.db";
- statistics-file "data/named_stats.txt";
- memstatistics-file "data/named_mem_stats.txt";
-};
-
-logging {
-
- # If you want to enable debugging, eg. using the 'rndc trace'
- # command, named will try to write the 'named.run' file in the
- # $directory (/var/named). By default, SELinux policy does not
- # allow named to modify the /var/named directory, so put the
- # default debug log file in data/ :
- channel default_debug {
- file "data/named.run" versions 5 size 20m;
- severity dynamic;
- };
-};
-
-# All BIND 9 zones are in a "view", which allow different zones to be
-# served to different types of client addresses, and for options to be
-# set for groups of zones. By default, if named.conf contains no
-# "view" clauses, all zones are in the "default" view, which matches
-# all clients. If named.conf contains any "view" clause, then all
-# zones MUST be in a view; so it is recommended to start off using
-# views to avoid having to restructure your configuration files in the
-# future.
-
-view "internal" {
-
- # This view will contain zones you want to serve only to
- # "internal" clients that connect via your directly attached LAN
- # interfaces - "localnets".
- match-clients { 192.168.0/24; };
- match-destinations { 192.168.0/24; };
- recursion no;
-
- # All views must contain the root hints zone. However, since this
- # machine is disconnected from Internet it is not possible for it
- # to reach root servers. So, this line is commented based that no
- # recursion is performed here.
- //include "named.rfc1912.zones";
-
- # These are your "authoritative" internal zones, and would
- # probably also be included in the "localhost_resolver" view
- # above:
- zone "example.com" IN {
- type master;
- file "example.com.zone";
- allow-update { none; };
- };
-
- zone "0.168.192.in-addr.arpa" IN {
- type master;
- file "example.com.rr.zone";
- allow-update { none; };
- };
-};
-
-# The localhost_resolver is already configured in `/etc/hosts' and set
-# as first choise in `/etc/hosts.conf' file. However, if you change
-# the order in `/etc/hosts.conf' file to make bind the first choise,
-# then you need to include here the localhost_resolver in order to
-# resolve localhost (127.0.0.1) address.
-
-key "rndckey" {
- algorithm hmac-md5;
- secret "JjsCg0VcCjZILGD8FR9nnw==";
-};
-
-controls {
- inet 127.0.0.1 port 953
- allow { 127.0.0.1; } keys { "rndckey"; };
-};
-</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>/var/named/example.com.zone</filename></term>
- <listitem>
-<screen>
-$ORIGIN example.com.
-$TTL 86400
-@ IN SOA example.com. hostmaster.example.com. (
- 2011100404 ; serial (d. adams)
- 3H ; refresh
- 15M ; retry
- 1W ; expiry
- 1D ) ; minimum
-
- IN NS dns.example.com.
- IN MX 10 mail.example.com.
-
-server IN A 192.168.0.1
-client IN A 192.168.0.2
-
-dns IN CNAME server
-mail IN CNAME server
-www IN CNAME server
-</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>/var/named/example.com.rr.zone</filename></term>
- <listitem>
-<screen>
-$ORIGIN 0.168.192.in-addr.arpa.
-$TTL 86400
-@ IN SOA example.com. hostmaster.example.com. (
- 2011100405 ; serial (d. adams)
- 3H ; refresh
- 15M ; retry
- 1W ; expiry
- 1D ) ; minimum
-
- IN NS 192.168.0.1
-
-1 IN PTR server.example.com.
-2 IN PTR client.example.com.
-</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>/etc/rndc.conf</filename></term>
- <listitem>
-<screen>
-include "/etc/rndc.key";
-options {
- default-key "rndckey";
- default-server 127.0.0.1;
- default-port 953;
-};
-</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>/etc/rndc.key</filename></term>
- <listitem>
-<screen>
-key "rndckey" {
- algorithm hmac-md5;
- secret "JjsCg0VcCjZILGD8FR9nnw==";
-};
-</screen>
- <para>
- When configuring <command>rndc</command> controls, don't use
- the same secret shown in the example above. If you do so, the
- secret information will not be a secret anymore (since we
- already used it here). Instead, use the
- <command>rndc-genconf</command> command to generate a new one,
- and be sure it be placed correctly both in
- <filename>/etc/rndc.conf</filename> and
- <filename>/etc/named.conf</filename> configuration files.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename>/etc/resolv.conf</filename></term>
- <listitem>
- <screen>nameserver 192.168.0.1</screen>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename>/etc/host.conf</filename></term>
- <listitem>
- <screen>order hosts,bind</screen>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- At this point you can start the named service and realize some
- tests to verify the named service is certainly working as
- expected. For example, consider the the following two
- commands:
- </para>
-
-<screen>
-[root@server ~]# service named start
-Starting named: [ OK ]
-[root@server ~]# dig example.com mx
-
-; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> example.com mx
-;; global options: printcmd
-;; Got answer:
-;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3540
-;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
-
-;; QUESTION SECTION:
-;example.com. IN MX
-
-;; ANSWER SECTION:
-example.com. 86400 IN MX 10 mail.example.com.
-
-;; AUTHORITY SECTION:
-example.com. 86400 IN NS dns.example.com.
-
-;; Query time: 0 msec
-;; SERVER: 192.168.0.1#53(192.168.0.1)
-;; WHEN: Wed Oct 5 10:33:24 2011
-;; MSG SIZE rcvd: 67
-</screen>
-
- <para>
- If everything is ok, configure the named service to start at
- boot time:
- </para>
-
- <screen>chkconfig --level 345 named on</screen>
-
- <para>
- If something goes wrong, look for <systemitem
- class="daemon">named</systemitem> daemon entries inside the
- <filename>/var/log/messages</filename> file to know what is
- going on. When you are configuring the name server, it could
- result useful to you keeping an always visible terminal,
- running the following command on it:
- </para>
-
- <screen>grep named /var/log/messages | tail -f -</screen>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-mta">
- <title>Configuring Mail Server (MTA)</title>
- <para>
- Based on default configuration provided by Postfix RPM inside
- &TCD; (release 5.5), look for the following options and leave
- the rest as is.
- </para>
-
- <variablelist>
- <varlistentry>
- <term><filename>/etc/postfix/main.cf</filename></term>
- <listitem>
-<screen>
-myhostname = server.example.com
-mydomain = example.org
-inet_interfaces = $myhostname, localhost
-mynetworks = 192.168.0.0/24, 127.0.0.0/8
-mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
-local_destination_recipient_limit = 300
-local_destination_concurrency_limit = 5
-</screen>
- </listitem>
- </varlistentry>
- </variablelist>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-mda">
- <title>Configuring Mail Server (MDA)</title>
- <variablelist>
- <varlistentry>
- <term><filename>/etc/cyrus.conf</filename></term>
- <listitem>
- <para>
- Leave it as is. There is nothing to touch here for a small and
- basic configuration like that one we are implementing in this
- chapter.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename>/etc/imapd.conf</filename></term>
- <listitem>
- <para>
- Leave it as is. There is nothing to touch here for a small and
- basic configuration like that one we are implementing in this
- chapter.
- </para>
- <para>
- The initial configuration of Cyrus IMAP server is set to use
- PLAIN authentication mechanisim (see
- <option>sasl_mech_list</option> option) against <systemitem
- class="daemon">saslauthd</systemitem> daemon. This makes the
- password information to be vulnerable for man in the middle
- attacks. In order to protect the user authentication, you can
- use other authentication mechanisms like CRAM-MD5 or
- DIGEST-MD5 in the mail client in order to send the password
- information encrypted. Another solution would be to create an
- encrypted channel for communication between the e-email client
- and Cyrus IMAP server by mean of SSL encryption.
- </para>
- <para>
- When you use authentication mechanisms that encrypt user
- information before passing them to saslauthd daemon (e.g.,
- DIGETS-MD5), you are protecting your data in the mail
- client before passing it to saslauthd daemon. Therefore, when
- the <systemitem class="daemon">saslauthd</systemitem> daemon
- tries to validate the credentials you passed in against PAM,
- it fails. At my personal understanding, this happens becase
- PAM must receive the user information as it was entered by the
- user (i.e., plainly, without any encryption) in order to
- realize the verification against the system default
- authentication database (e.g.,
- <filename>/etc/passwd</filename>,
- <filename>/etc/shadow</filename>), and <systemitem
- class="daemon">saslauthd</systemitem> daemon is passing an
- encrypted version of the plain user information which
- obviously cannot match the hash produced by plain user
- information in first place.
- </para>
-
- <para>
- One alternative to the situation mentioned above could be to
- use PLAIN authentication mechanism over an SSL encrypted
- communication or excluding PAM mechanism from saslauthd
- daemon, and use LDAP mechanism instead. When LDAP mechanism
- is used as default authentication mechanism inside saslauthd
- daemon, it is possible for mail clients to send encrypted
- passwords to saslauthd daemon. In this configuration, the
- password stored in LDAP server must be encrypted using the
- same algorithm used to send the encrypted password from mail
- client to saslauthd daemon. Therefore, you need to force the
- user to use just one authentication mechanism, that one used
- to stored encrypted passwords inside the LDAP server.
- Otherwise, it would be very difficult to authenticate users
- that send passwords encrypted in a way different to that one
- stored in the LDAP server.
- </para>
-
- <para>
- Another configuration could be to keep mail clients using
- PLAIN authentication over an SSL connection against saslauthd
- daemon, and saslauthd using a PAM. But this time, PAM would be
- configured to extend its default system authentication by
- using an LDAP server. This way, it would be possible to
- isolate user accound administration and greatly control the
- kind of information a user might have. For example, the root
- user account would be in the system default authentication,
- however all service-specific user information would be in the
- LDAP server. This permits us to create a web application that
- interact with LDAP server in order to manage service-specific
- user information only avoiding any contant with system default
- authentication, the place where the root user is stored in. In
- this PAM configuration, the first match that fails means that
- the whole authentication process fails.
- </para>
-
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename>/etc/pki/cyrus-imapd/cyrus-imapd.pem</filename></term>
- <listitem>
- <para>
- This file is a symbolic link to
- <filename>/etc/pki/tls/certs/cyrus-imapd.pem</filename>. This
- file contains a self-generated SSL certificate you probably
- want to update for setting your host name in the <quote>Common
- Name</quote> field of it. To create this file use the
- following command:
- </para>
- <screen>openssl req -new -x509 -nodes -out /etc/pki/tls/certs/cyrus-imapd.pem -keyout /etc/pki/tls/certs/cyrus-imapd.pem -days 365</screen>
-
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- To initiate the Cyrus IMAP server, run the following command:
- </para>
-
- <screen>service cyrus-imapd start</screen>
-
- <para>
- In case something fails, look into the
- <filename>/var/log/maillog</filename> file, specifically those
- entries containing <code>imap</code>, <code>pop</code>,
- <code>nntp</code> and <code>cyrus</code> strings. It could be
- useful if, before initiating Cyrus IMAP server, you open a
- terminal and run the following command in it, just to see what
- is happening once Cyrus IMAP server is initiated:
- </para>
-
- <screen>egrep '(cyrus|imap|pop)' /var/log/maillog | tail -f -</screen>
-
- <para>
- Later, to test the <code>STARTTLS</code> negociation, you can
- run the following command:
- </para>
-
- <screen>imtest -t "" server.example.com</screen>
-
- <para>
- To administer mailboxes inside Cyrus Imapd, set a password to
- cyrus user (e.g., <command>passwd cyrus</command>), do login
- with it, and connect to Cyrus IMAP server using the
- <command>cyradm</command> command, as shown below:
- </para>
-
- <screen>cyradm --user=cyrus --auth=login localhost</screen>
-
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-sasl">
- <title>Configuring Mail Server (SASL)</title>
- <para>
- ...
- </para>
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-web">
- <title>Configuring Web Server</title>
- <para>
- ...
- </para>
- </sect3>
-
- <sect3 id="configurations-dialup-server-config-ldap">
- <title>Configuring Directory Server</title>
- <para>
- ...
- </para>
- </sect3>
-
- </sect2>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Configurations/Dialup/usage.docbook b/Manuals/HowTos/Dialup/Configurations/Dialup/usage.docbook
deleted file mode 100644
index f6bc809..0000000
--- a/Manuals/HowTos/Dialup/Configurations/Dialup/usage.docbook
+++ /dev/null
@@ -1,6 +0,0 @@
-<sect1 id="configurations-dialup-usage">
-
- <title>Usage Convenctions</title>
-
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Licenses.docbook b/Manuals/HowTos/Dialup/Licenses.docbook
deleted file mode 100644
index bcb5cec..0000000
--- a/Manuals/HowTos/Dialup/Licenses.docbook
+++ /dev/null
@@ -1,7 +0,0 @@
-<part id="licenses">
-
- <title>Licenses</title>
-
- &licenses-gfdl;
-
-</part>
diff --git a/Manuals/HowTos/Dialup/Licenses.ent b/Manuals/HowTos/Dialup/Licenses.ent
deleted file mode 100644
index dd7f27a..0000000
--- a/Manuals/HowTos/Dialup/Licenses.ent
+++ /dev/null
@@ -1,2 +0,0 @@
-<!ENTITY licenses SYSTEM "Licenses.docbook">
-<!ENTITY licenses-gfdl SYSTEM "Licenses/gfdl.docbook">
diff --git a/Manuals/HowTos/Dialup/Licenses/gfdl.docbook b/Manuals/HowTos/Dialup/Licenses/gfdl.docbook
deleted file mode 100644
index 33f6e8c..0000000
--- a/Manuals/HowTos/Dialup/Licenses/gfdl.docbook
+++ /dev/null
@@ -1,591 +0,0 @@
-<appendix id="licenses-gfdl">
-
- <title>GNU Free Documentation License</title>
-
- <para>Version 1.2, November 2002</para>
-
- <para>Copyright © 2000, 2001, 2002 Free Software Foundation,
- Inc. 675 Mass Ave, Cambridge, MA 02139, USA</para>
-
- <para>Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.</para>
-
- <sect1 id="licenses-gfdl-section-1" xreflabel="Preamble">
-
- <title>Preamble</title>
-
- <para>The purpose of this License is to make a manual,
- textbook, or other functional and useful document
- <quote>free</quote> in the sense of freedom: to assure
- everyone the effective freedom to copy and redistribute it,
- with or without modifying it, either commercially or
- noncommercially. Secondarily, this License preserves for the
- author and publisher a way to get credit for their work, while
- not being considered responsible for modifications made by
- others.</para>
-
- <para>This License is a kind of <quote>copyleft</quote>, which
- means that derivative works of the document must themselves be
- free in the same sense. It complements the <xref
- linkend="licenses-gfdl" />, which is a copyleft license
- designed for free software.</para>
-
- <para>We have designed this License in order to use it for
- manuals for free software, because free software needs free
- documentation: a free program should come with manuals
- providing the same freedoms that the software does. But this
- License is not limited to software manuals; it can be used for
- any textual work, regardless of subject matter or whether it
- is published as a printed book. We recommend this License
- principally for works whose purpose is instruction or
- reference.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-2" xreflabel="Applicability and definitions">
-
- <title>Applicability and definitions</title>
-
- <para>This License applies to any manual or other work, in any
- medium, that contains a notice placed by the copyright holder
- saying it can be distributed under the terms of this License.
- Such a notice grants a world-wide, royalty-free license,
- unlimited in duration, to use that work under the conditions
- stated herein. The <quote>Document</quote>, below, refers to
- any such manual or work. Any member of the public is a
- licensee, and is addressed as <quote>you</quote>. You accept
- the license if you copy, modify or distribute the work in a
- way requiring permission under copyright law.</para>
-
- <para id="modified-version" xreflabel="Modified Version">A
- <quote>Modified Version</quote> of the Document means any work
- containing the Document or a portion of it, either copied
- verbatim, or with modifications and/or translated into another
- language.</para>
-
- <para id="secondary-section" xreflabel="Secondary Section">A
- <quote>Secondary Section</quote> is a named appendix or a
- front-matter section of the Document that deals exclusively
- with the relationship of the publishers or authors of the
- Document to the Document's overall subject (or to related
- matters) and contains nothing that could fall directly within
- that overall subject. (Thus, if the Document is in part a
- textbook of mathematics, a <xref linkend="secondary-section"
- /> may not explain any mathematics.) The relationship could be
- a matter of historical connection with the subject or with
- related matters, or of legal, commercial, philosophical,
- ethical or political position regarding them.</para>
-
- <para id="invariant-sections" xreflabel="Invariant
- Sections">The <quote>Invariant Sections</quote> are certain
- <xref linkend="secondary-section" /> whose titles are
- designated, as being those of Invariant Sections, in the
- notice that says that the Document is released under this
- License. If a section does not fit the above definition of
- Secondary then it is not allowed to be designated as
- Invariant. The Document may contain zero Invariant Sections.
- If the Document does not identify any Invariant Section then
- there are none.</para>
-
- <para id="cover-texts" xreflabel="Cover Texts">The
- <quote>Cover Texts</quote> are certain short passages of text
- that are listed, as Front-Cover Texts or Back-Cover Texts, in
- the notice that says that the Document is released under this
- License. A Front-Cover Text may be at most 5 words, and a
- Back-Cover Text may be at most 25 words.</para>
-
- <para id="transparent" xreflabel="Transparent">A
- <quote>Transparent</quote> copy of the Document means a
- machine-readable copy, represented in a format whose
- specification is available to the general public, that is
- suitable for revising the document straightforwardly with
- generic text editors or (for images composed of pixels)
- generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text
- formatters or for automatic translation to a variety of
- formats suitable for input to text formatters. A copy made in
- an otherwise <xref linkend="transparent" /> file format whose
- markup, or absence of markup, has been arranged to thwart or
- discourage subsequent modification by readers is not <xref
- linkend="transparent" />. An image format is not <xref
- linkend="transparent" /> if used for any substantial amount of
- text. A copy that is not <quote><xref linkend="transparent"
- /></quote> is called <quote>Opaque</quote>.</para>
-
- <para>Examples of suitable formats for <xref linkend="transparent" /> copies
- include plain ASCII without markup, Texinfo input format,
- LaTeX input format, SGML or XML using a publicly available
- DTD, and standard-conforming simple HTML, PostScript or PDF
- designed for human modification. Examples of transparent
- image formats include PNG, XCF and JPG. Opaque formats
- include proprietary formats that can be read and edited only
- by proprietary word processors, SGML or XML for which the DTD
- and/or processing tools are not generally available, and the
- machine-generated HTML, PostScript or PDF produced by some
- word processors for output purposes only.</para>
-
- <para id="title-page" xreflabel="Title Page">The <quote>Title
- Page</quote> means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the
- material this License requires to appear in the title page.
- For works in formats which do not have any title page as such,
- <quote>Title Page</quote> means the text near the most
- prominent appearance of the work's title, preceding the
- beginning of the body of the text.</para>
-
- <para>A section <quote>Entitled XYZ</quote> means a named
- subunit of the Document whose title either is precisely XYZ or
- contains XYZ in parentheses following text that translates XYZ
- in another language. (Here XYZ stands for a specific section
- name mentioned below, such as <quote>Acknowledgements</quote>,
- <quote>Dedications</quote>, <quote>Endorsements</quote>, or
- <quote>History</quote>.) To <quote>Preserve the Title</quote>
- of such a section when you modify the Document means that it
- remains a section <quote>Entitled XYZ</quote> according to
- this definition.</para>
-
- <para>The Document may include Warranty Disclaimers next to
- the notice which states that this License applies to the
- Document. These Warranty Disclaimers are considered to be
- included by reference in this License, but only as regards
- disclaiming warranties: any other implication that these
- Warranty Disclaimers may have is void and has no effect on the
- meaning of this License.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-3" xreflabel="Verbatim copying">
-
- <title>Verbatim copying</title>
-
- <para>You may copy and distribute the Document in any medium,
- either commercially or noncommercially, provided that this
- License, the copyright notices, and the license notice saying
- this License applies to the Document are reproduced in all
- copies, and that you add no other conditions whatsoever to
- those of this License. You may not use technical measures to
- obstruct or control the reading or further copying of the
- copies you make or distribute. However, you may accept
- compensation in exchange for copies. If you distribute a
- large enough number of copies you must also follow the
- conditions in section <xref linkend="licenses-gfdl-section-4"
- />.</para>
-
- <para>You may also lend copies, under the same conditions
- stated above, and you may publicly display copies.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-4" xreflabel="Copying in quantity">
-
- <title>Copying in quantity</title>
-
- <para>If you publish printed copies (or copies in media that
- commonly have printed covers) of the Document, numbering more
- than 100, and the Document's license notice requires Cover
- Texts, you must enclose the copies in covers that carry,
- clearly and legibly, all these <xref linkend="cover-texts" />:
- Front-Cover Texts on the front cover, and Back-Cover Texts on
- the back cover. Both covers must also clearly and legibly
- identify you as the publisher of these copies. The front
- cover must present the full title with all words of the title
- equally prominent and visible. You may add other material on
- the covers in addition. Copying with changes limited to the
- covers, as long as they preserve the title of the Document and
- satisfy these conditions, can be treated as verbatim copying
- in other respects.</para>
-
- <para>If the required texts for either cover are too
- voluminous to fit legibly, you should put the first ones
- listed (as many as fit reasonably) on the actual cover, and
- continue the rest onto adjacent pages.</para>
-
- <para>If you publish or distribute Opaque copies of the
- Document numbering more than 100, you must either include a
- machine-readable <xref linkend="transparent" /> copy along with each Opaque copy,
- or state in or with each Opaque copy a computer-network
- location from which the general network-using public has
- access to download using public-standard network protocols a
- complete <xref linkend="transparent" /> copy of the Document, free of added
- material. If you use the latter option, you must take
- reasonably prudent steps, when you begin distribution of
- Opaque copies in quantity, to ensure that this <xref linkend="transparent" />
- copy will remain thus accessible at the stated location until
- at least one year after the last time you distribute an Opaque
- copy (directly or through your agents or retailers) of that
- edition to the public.</para>
-
- <para>It is requested, but not required, that you contact the
- authors of the Document well before redistributing any large
- number of copies, to give them a chance to provide you with an
- updated version of the Document.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-5" xreflabel="Modification">
-
- <title>Modifications</title>
-
- <para>You may copy and distribute a <xref
- linkend="modified-version" /> of the Document under the
- conditions of sections <xref linkend="licenses-gfdl-section-3"
- /> and <xref linkend="licenses-gfdl-section-4" /> above,
- provided that you release the <xref linkend="modified-version"
- /> under precisely this License, with the <xref
- linkend="modified-version" /> filling the role of the
- Document, thus licensing distribution and modification of the
- <xref linkend="modified-version" /> to whoever possesses a
- copy of it. In addition, you must do these things in the
- <xref linkend="modified-version" />:
-
- <orderedlist numeration="upperalpha">
-
- <listitem>
- <para>Use in the <xref linkend="title-page" /> (and on
- the covers, if any) a title distinct from that of the
- Document, and from those of previous versions (which
- should, if there were any, be listed in the History
- section of the Document). You may use the same title
- as a previous version if the original publisher of
- that version gives permission.</para> </listitem>
-
- <listitem>
- <para>List on the <xref linkend="title-page" />, as
- authors, one or more persons or entities responsible
- for authorship of the modifications in the <xref
- linkend="modified-version" />, together with at least
- five of the principal authors of the Document (all of
- its principal authors, if it has fewer than five),
- unless they release you from this requirement.</para>
- </listitem>
-
- <listitem>
- <para>State on the <xref linkend="title-page" /> the
- name of the publisher of the <xref
- linkend="modified-version" />, as the
- publisher.</para>
- </listitem>
-
- <listitem>
- <para>Preserve all the copyright notices of the
- Document.</para>
- </listitem>
-
- <listitem>
- <para>Add an appropriate copyright notice for your
- modifications adjacent to the other copyright
- notices.</para>
- </listitem>
-
- <listitem>
- <para>Include, immediately after the copyright
- notices, a license notice giving the public permission
- to use the <xref linkend="modified-version" /> under the terms of this
- License, in the form shown in the Addendum
- below.</para>
- </listitem>
-
- <listitem>
- <para>Preserve in that license notice the full lists
- of <xref linkend="invariant-sections" /> and required
- <xref linkend="cover-texts" /> given in the Document's
- license notice.</para>
- </listitem>
-
- <listitem>
- <para>Include an unaltered copy of this License.</para>
- </listitem>
-
- <listitem>
- <para>Preserve the section Entitled
- <quote>History</quote>, Preserve its Title, and add to
- it an item stating at least the title, year, new
- authors, and publisher of the <xref
- linkend="modified-version" /> as given on the <xref
- linkend="title-page" />. If there is no section
- Entitled <quote>History</quote> in the Document, create
- one stating the title, year, authors, and publisher of
- the Document as given on its <xref linkend="title-page"
- />, then add an item describing the <xref
- linkend="modified-version" /> as stated in the previous
- sentence.</para>
- </listitem>
-
- <listitem>
- <para>Preserve the network location, if any, given in
- the Document for public access to a <xref
- linkend="transparent" /> copy of the Document, and
- likewise the network locations given in the Document
- for previous versions it was based on. These may be
- placed in the <quote>History</quote> section. You may
- omit a network location for a work that was published
- at least four years before the Document itself, or if
- the original publisher of the version it refers to
- gives permission.</para>
- </listitem>
-
- <listitem>
- <para>For any section Entitled
- <quote>Acknowledgements</quote> or
- <quote>Dedications</quote>, Preserve the Title of the
- section, and preserve in the section all the substance
- and tone of each of the contributor acknowledgements
- and/or dedications given therein.</para>
- </listitem>
-
- <listitem>
- <para>Preserve all the <xref
- linkend="invariant-sections" /> of the Document,
- unaltered in their text and in their titles. Section
- numbers or the equivalent are not considered part of
- the section titles.</para>
- </listitem>
-
- <listitem>
- <para>Delete any section Entitled
- <quote>Endorsements</quote>. Such a section may not
- be included in the <xref linkend="modified-version" />.</para>
- </listitem>
-
- <listitem>
- <para>Do not retitle any existing section to be
- Entitled <quote>Endorsements</quote> or to conflict in
- title with any <xref linkend="invariant-sections"
- />.</para> </listitem>
-
- <listitem>
- <para>Preserve any Warranty Disclaimers.</para>
- </listitem>
- </orderedlist>
- </para>
-
- <para>If the <xref linkend="modified-version" /> includes new
- front-matter sections or appendices that qualify as <xref
- linkend="secondary-section" /> and contain no material copied
- from the Document, you may at your option designate some or
- all of these sections as invariant. To do this, add their
- titles to the list of <xref linkend="invariant-sections"/> in the <xref
- linkend="modified-version" />'s license notice. These titles
- must be distinct from any other section titles.</para>
-
- <para>You may add a section Entitled
- <quote>Endorsements</quote>, provided it contains nothing but
- endorsements of your <xref linkend="modified-version" /> by various
- parties–for example, statements of peer review or that
- the text has been approved by an organization as the
- authoritative definition of a standard.</para>
-
- <para>You may add a passage of up to five words as a
- Front-Cover Text, and a passage of up to 25 words as a
- Back-Cover Text, to the end of the list of <xref
- linkend="cover-texts"/> in the <xref
- linkend="modified-version" />. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by
- (or through arrangements made by) any one entity. If the
- Document already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same
- entity you are acting on behalf of, you may not add another;
- but you may replace the old one, on explicit permission from
- the previous publisher that added the old one.</para>
-
- <para>The author(s) and publisher(s) of the Document do not by
- this License give permission to use their names for publicity
- for or to assert or imply endorsement of any <xref
- linkend="modified-version" />.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-6" xreflabel="Combining documents">
-
- <title>Combining documents</title>
-
- <para>You may combine the Document with other documents
- released under this License, under the terms defined in
- section <xref linkend="licenses-gfdl-section-5" /> above for
- modified versions, provided that you include in the
- combination all of the <xref linkend="invariant-sections"/> of
- all of the original documents, unmodified, and list them all
- as <xref linkend="invariant-sections"/> of your combined work
- in its license notice, and that you preserve all their
- Warranty Disclaimers.</para>
-
- <para>The combined work need only contain one copy of this
- License, and multiple identical <xref
- linkend="invariant-sections"/> may be replaced with a single
- copy. If there are multiple <xref
- linkend="invariant-sections" /> with the same name but
- different contents, make the title of each such section unique
- by adding at the end of it, in parentheses, the name of the
- original author or publisher of that section if known, or else
- a unique number. Make the same adjustment to the section
- titles in the list of <xref linkend="invariant-sections" /> in
- the license notice of the combined work.</para>
-
- <para>In the combination, you must combine any sections
- Entitled <quote>History</quote> in the various original
- documents, forming one section Entitled
- <quote>History</quote>; likewise combine any sections Entitled
- <quote>Acknowledgements</quote>, and any sections Entitled
- <quote>Dedications</quote>. You must delete all sections
- Entitled <quote>Endorsements</quote>.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-7" xreflabel="Collection of documents">
-
- <title>Collection of documents</title>
-
- <para>You may make a collection consisting of the Document and
- other documents released under this License, and replace the
- individual copies of this License in the various documents
- with a single copy that is included in the collection,
- provided that you follow the rules of this License for
- verbatim copying of each of the documents in all other
- respects.</para>
-
- <para>You may extract a single document from such a
- collection, and distribute it individually under this License,
- provided you insert a copy of this License into the extracted
- document, and follow this License in all other respects
- regarding verbatim copying of that document.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-8" xreflabel="Aggregation with independent works">
-
- <title>Aggregation with independent works</title>
-
- <para>A compilation of the Document or its derivatives with
- other separate and independent documents or works, in or on a
- volume of a storage or distribution medium, is called an
- <quote>aggregate</quote> if the copyright resulting from the
- compilation is not used to limit the legal rights of the
- compilation's users beyond what the individual works permit.
- When the Document is included in an aggregate, this License
- does not apply to the other works in the aggregate which are
- not themselves derivative works of the Document.</para>
-
- <para>If the Cover Text requirement of section <xref
- linkend="licenses-gfdl-section-4" /> is applicable to these
- copies of the Document, then if the Document is less than one
- half of the entire aggregate, the Document's <xref
- linkend="cover-texts" /> may be placed on covers that bracket
- the Document within the aggregate, or the electronic
- equivalent of covers if the Document is in electronic form.
- Otherwise they must appear on printed covers that bracket the
- whole aggregate.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-9" xreflabel="Translations">
-
- <title>Translations</title>
-
- <para>Translation is considered a kind of modification, so you
- may distribute translations of the Document under the terms of
- section <xref linkend="licenses-gfdl-section-5"/>. Replacing
- <xref linkend="invariant-sections" />with translations
- requires special permission from their copyright holders, but
- you may include translations of some or all <xref
- linkend="invariant-sections" /> in addition to the original
- versions of these <xref linkend="invariant-sections" />. You
- may include a translation of this License, and all the license
- notices in the Document, and any Warranty Disclaimers,
- provided that you also include the original English version of
- this License and the original versions of those notices and
- disclaimers. In case of a disagreement between the
- translation and the original version of this License or a
- notice or disclaimer, the original version will
- prevail.</para>
-
- <para>If a section in the Document is Entitled
- <quote>Acknowledgements</quote>, <quote>Dedications</quote>,
- or <quote>History</quote>, the requirement (section <xref
- linkend="licenses-gfdl-section-5" />) to Preserve its Title
- (section <xref linkend="licenses-gfdl-section-2" />) will
- typically require changing the actual title.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-10" xreflabel="Tremination">
-
- <title>Termination</title>
-
- <para>You may not copy, modify, sublicense, or distribute the
- Document except as expressly provided for under this License.
- Any other attempt to copy, modify, sublicense or distribute
- the Document is void, and will automatically terminate your
- rights under this License. However, parties who have received
- copies, or rights, from you under this License will not have
- their licenses terminated so long as such parties remain in
- full compliance.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-11" xreflabel="Future Revisions of this License">
-
- <title>Future Revisions of this License</title>
-
- <para>The Free Software Foundation may publish new, revised
- versions of the GNU Free Documentation License from time to
- time. Such new versions will be similar in spirit to the
- present version, but may differ in detail to address new
- problems or concerns. See <ulink
- url="http://www.gnu.org/copyleft/" />.</para>
-
- <para>Each version of the License is given a distinguishing
- version number. If the Document specifies that a particular
- numbered version of this License <quote>or any later
- version</quote> applies to it, you have the option of
- following the terms and conditions either of that specified
- version or of any later version that has been published (not
- as a draft) by the Free Software Foundation. If the Document
- does not specify a version number of this License, you may
- choose any version ever published (not as a draft) by the Free
- Software Foundation.</para>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-12" xreflabel="How to use this License for your documents">
-
- <title>How to use this License for your documents</title>
-
- <para>To use this License in a document you have written,
- include a copy of the License in the document and put the
- following copyright and license notices just after the title
- page:</para>
-
-<programlisting>
-Copyright (C) YEAR YOUR NAME.
-
-Permission is granted to copy, distribute and/or modify this
-document under the terms of the GNU Free Documentation License,
-Version 1.2 or any later version published by the Free Software
-Foundation; with no Invariant Sections, no Front-Cover Texts, and
-no Back-Cover Texts. A copy of the license is included in the
-section entitled <quote>GNU Free Documentation License</quote>.
-</programlisting>
-
- <para>If you have <xref linkend="invariant-sections" />,
- Front-Cover Texts and Back-Cover Texts, replace the
- <quote>with...Texts</quote>. line with this:</para>
-
-<programlisting>
-with the Invariant Sections being LIST THEIR TITLES, with the
-Front-Cover Texts being LIST, and with the Back-Cover Texts being
-LIST.
-</programlisting>
-
- <para>If you have <xref linkend="invariant-sections" />
- without <xref linkend="cover-texts" />, or some other
- combination of the three, merge those two alternatives to suit
- the situation.</para>
-
- <para>If your document contains nontrivial examples of program
- code, we recommend releasing these examples in parallel under
- your choice of free software license, such as the GNU General
- Public License, to permit their use in free software.</para>
-
- </sect1>
-
-</appendix>
diff --git a/Manuals/HowTos/Dialup/Preface.docbook b/Manuals/HowTos/Dialup/Preface.docbook
deleted file mode 100755
index 42c8578..0000000
--- a/Manuals/HowTos/Dialup/Preface.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<preface id="preface">
-
- <title>Preface</title>
-
- &preface-overview;
- &preface-docconvs;
- &preface-feedback;
-
-</preface>
diff --git a/Manuals/HowTos/Dialup/Preface.ent b/Manuals/HowTos/Dialup/Preface.ent
deleted file mode 100755
index 263be1d..0000000
--- a/Manuals/HowTos/Dialup/Preface.ent
+++ /dev/null
@@ -1,4 +0,0 @@
-<!ENTITY preface SYSTEM "Preface.docbook">
-<!ENTITY preface-overview SYSTEM "Preface/overview.docbook">
-<!ENTITY preface-docconvs SYSTEM "Preface/docconvs.docbook">
-<!ENTITY preface-feedback SYSTEM "Preface/feedback.docbook">
diff --git a/Manuals/HowTos/Dialup/Preface/docconvs.docbook b/Manuals/HowTos/Dialup/Preface/docconvs.docbook
deleted file mode 100644
index 8eda7bc..0000000
--- a/Manuals/HowTos/Dialup/Preface/docconvs.docbook
+++ /dev/null
@@ -1,225 +0,0 @@
-<section id="preface-docconvs">
-
- <title>Document Convenctions</title>
-
- <para>
- In this manual, certain words are represented in different
- fonts, typefaces, sizes, and weights. This highlighting is
- systematic; different words are represented in the same style
- to indicate their inclusion in a specific category. The types
- of words that are represented this way include the
- following:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><command>command</command></term>
- <listitem>
- <para>
- Linux commands (and other operating system commands, when
- used) are represented this way. This style should
- indicate to you that you can type the word or phrase on
- the command line and press <keycap>Enter</keycap> to
- invoke a command. Sometimes a command contains words that
- would be displayed in a different style on their own (such
- as file names). In these cases, they are considered to be
- part of the command, so the entire phrase is displayed as
- a command. For example:
- </para>
-
- <para>
- Use the <command>centos-art render
- trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda
- --filter="01-welcome"</command> command to produce the first
- slide image used by Anaconda in the branch 5 of &TCD;
- using the version 4 of TreeFlower artistic motif.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>file name</filename></term>
- <listitem>
- <para>
- File names, directory names, paths, and RPM package names
- are represented this way. This style indicates that a
- particular file or directory exists with that name on your
- system. Examples:
- </para>
-
- <para>
- The <filename>init.sh</filename> file in <filename
- class="directory">trunk/Scripts/Bash/Cli/</filename>
- directory is the initialization script, written in Bash,
- used to automate most of tasks in the repository.
- </para>
-
- <para>
- The <command>centos-art</command> command uses the
- <filename>ImageMagick</filename> RPM package to convert
- images from PNG format to other formats.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycap>key</keycap></term>
- <listitem>
- <para>
- A key on the keyboard is shown in this style. For
- example:
- </para>
-
- <para>
- To use <keycap>Tab</keycap> completion to list particular
- files in a directory, type <command>ls</command>, then a
- character, and finally the <keycap>Tab</keycap> key. Your
- terminal displays the list of files in the working
- directory that begin with that character.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
- <listitem>
- <para>
- A combination of keystrokes is represented in this way.
- For example:
- </para>
-
- <para>
- The <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo>
- key combination exits your graphical session and returns
- you to the graphical login screen or the console.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><computeroutput>computer output</computeroutput></term>
- <listitem>
- <para>
- Text in this style indicates text displayed to a shell
- prompt such as error messages and responses to commands.
- For example, the <command>ls</command> command displays
- the contents of a directory using this style:
- </para>
-
-<screen>
-render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
-render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
-render_getDirOutput.sh render.sh
-</screen>
-
- <para>
- The output returned in response to the command (in this
- case, the contents of the directory) is shown in this
- style.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><prompt>prompt</prompt></term>
- <listitem>
- <para>
- A prompt, which is a computer's way of signifying that it
- is ready for you to input something, is shown in this
- style. Examples:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <prompt>$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>#</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>[centos@projects centos]$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>projects login:</prompt>
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><userinput>user input</userinput></term>
- <listitem>
- <para>
- Text that the user types, either on the command line or
- into a text box on a GUI screen, is displayed in this
- style. In the following example,
- <userinput>text</userinput> is displayed in this style: To
- boot your system into the text based installation program,
- you must type in the <userinput>text</userinput> command
- at the <prompt>boot:</prompt> prompt.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>replaceable</replaceable></term>
- <listitem>
- <para>
- Text used in examples that is meant to be replaced with
- data provided by the user is displayed in this style. In
- the following example,
- <replaceable>version-number</replaceable> is displayed in
- this style: The directory for the kernel source is
- <filename
- class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
- where <replaceable>version-number</replaceable> is the
- version and type of kernel installed on this system.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>Additionally, we use several different strategies to draw
- your attention to certain pieces of information. In order of
- urgency, these items are marked as a note, tip, important,
- caution, or warning. For example:</para>
-
- <note>
- <para>Remember that Linux is case sensitive. In other words, a
- rose is not a ROSE is not a rOsE.</para>
- </note>
-
- <tip>
- <para>The directory <filename
- class="directory">/usr/share/doc/</filename> contains
- additional documentation for packages installed on your
- system.</para>
- </tip>
-
- <important>
- <para>If you modify the DHCP configuration file, the changes
- do not take effect until you restart the DHCP daemon.</para>
- </important>
-
- <caution>
- <para>Do not perform routine tasks as root — use a
- regular user account unless you need to use the root account
- for system administration tasks.</para>
- </caution>
-
- <warning>
- <para>Be careful to remove only the necessary partitions.
- Removing other partitions could result in data loss or a
- corrupted system environment.</para>
- </warning>
-
-</section>
diff --git a/Manuals/HowTos/Dialup/Preface/feedback.docbook b/Manuals/HowTos/Dialup/Preface/feedback.docbook
deleted file mode 100644
index 976502b..0000000
--- a/Manuals/HowTos/Dialup/Preface/feedback.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<section id="preface-feedback">
-
- <title>Send In Your Feedback</title>
-
- <para>
- If you find a bug in the infrastructure described in this
- manual, we would like to hear about it. To report bugs
- related to this manual, send an e-mail to the
- <email>centos-docs@centos.org</email> mailing list. When you
- write the bug report, take care of being specific about the
- problem you are reporting on (e.g., where it is, the section
- number, etc.) so we can found it easily.
- </para>
-
-</section>
diff --git a/Manuals/HowTos/Dialup/Preface/overview.docbook b/Manuals/HowTos/Dialup/Preface/overview.docbook
deleted file mode 100755
index 7eb91f9..0000000
--- a/Manuals/HowTos/Dialup/Preface/overview.docbook
+++ /dev/null
@@ -1,36 +0,0 @@
-<section id="preface-overview">
-
- <title>Overview</title>
-
- <para>
- This manual describes two computers configuration, one acting
- as server and other as client. The server computer will be
- configured to provide internet services and the client to make
- use of those internet services provided by the server
- computer. The connection medium both client and server
- computer use is the telelphone line (i.e., the same medium you
- use to realize phone calls). In this configuration, both
- client and server computers use special devices named
- <quote>Modems</quote> to transmit data in form of sound across
- the telephone line.
- </para>
-
- <para>
- The infrastructure described in this chapter is made available
- to you free of charge, however, you should know that
- maintaining it costs both money and time. For example, for
- each hour the server computer is on production there is an
- electrical consume that need to be paid every month.
- Likewise, each call that you establish from the client
- computer to the server computer will cost you money, based on
- the location you made the call from and the time you spend
- connected.
- </para>
-
- <para>
- The infrastructure described in this chapter could be a good
- choise when the only communication medium you have access to
- is a telephone network.
- </para>
-
-</section>
diff --git a/Manuals/HowTos/Dialup/Server.docbook b/Manuals/HowTos/Dialup/Server.docbook
deleted file mode 100644
index f934db3..0000000
--- a/Manuals/HowTos/Dialup/Server.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<part id="server">
-
- <title>The Server Computer</title>
-
- &server-usage;
- &server-install;
- &server-config;
-
-</part>
diff --git a/Manuals/HowTos/Dialup/Server.ent b/Manuals/HowTos/Dialup/Server.ent
deleted file mode 100644
index 8b9cafe..0000000
--- a/Manuals/HowTos/Dialup/Server.ent
+++ /dev/null
@@ -1,19 +0,0 @@
-<!ENTITY server SYSTEM "Server.docbook">
-<!ENTITY server-usage SYSTEM "Server/Usage.docbook">
-<!ENTITY server-usage-overview SYSTEM "Server/Usage/overview.docbook">
-<!ENTITY server-usage-lifetime SYSTEM "Server/Usage/lifetime.docbook">
-<!ENTITY server-usage-phonelines SYSTEM "Server/Usage/phonelines.docbook">
-<!ENTITY server-usage-auth SYSTEM "Server/Usage/auth.docbook">
-<!ENTITY server-usage-networking SYSTEM "Server/Usage/networking.docbook">
-<!ENTITY server-install SYSTEM "Server/Install.docbook">
-<!ENTITY server-install-overview SYSTEM "Server/Install/overview.docbook">
-<!ENTITY server-install-modem SYSTEM "Server/Install/modem.docbook">
-<!ENTITY server-install-mgetty SYSTEM "Server/Install/mgetty.docbook">
-<!ENTITY server-install-pppd SYSTEM "Server/Install/pppd.docbook">
-<!ENTITY server-install-wvdial SYSTEM "Server/Install/wvdial.docbook">
-<!ENTITY server-config SYSTEM "Server/Config.docbook">
-<!ENTITY server-config-overview SYSTEM "Server/Config/overview.docbook">
-<!ENTITY server-config-modem SYSTEM "Server/Config/modem.docbook">
-<!ENTITY server-config-mgetty SYSTEM "Server/Config/mgetty.docbook">
-<!ENTITY server-config-pppd SYSTEM "Server/Config/pppd.docbook">
-<!ENTITY server-config-wvdial SYSTEM "Server/Config/wvdial.docbook">
diff --git a/Manuals/HowTos/Dialup/Server/Config.docbook b/Manuals/HowTos/Dialup/Server/Config.docbook
deleted file mode 100644
index 88ebf36..0000000
--- a/Manuals/HowTos/Dialup/Server/Config.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="server-config">
-
- <title>Dial-Up Server Configuration</title>
-
- &server-config-overview;
- &server-config-modem;
- &server-config-mgetty;
- &server-config-pppd;
- &server-config-wvdial;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Server/Config/mgetty.docbook b/Manuals/HowTos/Dialup/Server/Config/mgetty.docbook
deleted file mode 100644
index 7b193df..0000000
--- a/Manuals/HowTos/Dialup/Server/Config/mgetty.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-config-mgetty">
-
- <title>Configuring <package>mgetty</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Server/Config/modem.docbook b/Manuals/HowTos/Dialup/Server/Config/modem.docbook
deleted file mode 100644
index 3cec53a..0000000
--- a/Manuals/HowTos/Dialup/Server/Config/modem.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-config-hardware">
-
- <title>Configuring Modem Hardware</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Config/overview.docbook b/Manuals/HowTos/Dialup/Server/Config/overview.docbook
deleted file mode 100644
index bcfcc4a..0000000
--- a/Manuals/HowTos/Dialup/Server/Config/overview.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-config-overview">
-
- <title>Overview</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Config/pppd.docbook b/Manuals/HowTos/Dialup/Server/Config/pppd.docbook
deleted file mode 100644
index fd3be5c..0000000
--- a/Manuals/HowTos/Dialup/Server/Config/pppd.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<sect1 id="server-config-pppd">
-
- <title>Configuring <package>pppd</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Config/wvdial.docbook b/Manuals/HowTos/Dialup/Server/Config/wvdial.docbook
deleted file mode 100644
index ee97a72..0000000
--- a/Manuals/HowTos/Dialup/Server/Config/wvdial.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-config-wvdial">
-
- <title>Configuring <package>wvdial</package> Package</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Install.docbook b/Manuals/HowTos/Dialup/Server/Install.docbook
deleted file mode 100644
index 80989b5..0000000
--- a/Manuals/HowTos/Dialup/Server/Install.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="server-install">
-
- <title>Dial-Up Server Installation</title>
-
- &server-install-overview;
- &server-install-modem;
- &server-install-mgetty;
- &server-install-pppd;
- &server-install-wvdial;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Server/Install/mgetty.docbook b/Manuals/HowTos/Dialup/Server/Install/mgetty.docbook
deleted file mode 100644
index 7901a59..0000000
--- a/Manuals/HowTos/Dialup/Server/Install/mgetty.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-install-mgetty">
-
- <title>Installing <package>mgetty</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Server/Install/modem.docbook b/Manuals/HowTos/Dialup/Server/Install/modem.docbook
deleted file mode 100644
index b68c3e0..0000000
--- a/Manuals/HowTos/Dialup/Server/Install/modem.docbook
+++ /dev/null
@@ -1,58 +0,0 @@
-<sect1 id="server-install-modem">
-
- <title>Installing Modem Hardware</title>
-
- <para>
- In order to establish a PPP link between two computers using
- the telephone line as medium for data transmission, you need
- to install (at least) one modem device in each computer. To
- install a modem device in computer you need to attach the
- modem hardware to the computer and later the telephone line to
- the modem hardware. To connect the modem to your computer, you
- need to connect the serial or USB cable that comes from the
- modem hardware to the appropriate input on your computer. To
- connect the modem to the telephone line system, you need to
- unplug the cable that connects your telephone device and plug
- it on the modem device, specifically in the port reserved for
- data transmission. Later, using a similar cable, you could
- connect your telephone device to the modem's telephone port,
- so you can realize telephone calls when no data transmition
- take place.
- </para>
-
- <para>
- To be on the safe side, do all the installation with the
- computer turned off. Then, when everthing has been put in
- place, turn it on. Once the system is up, you can verify the
- modem hardware using either the <command>lsusb</command> or
- <command>lspci</command> commands. These commands need to be
- run with administrative privileges, so probably need to
- <command>sudo</command> them or login as <systemitem
- class="username">root</systemitem> user in order to execute
- thme. For example, assuming you are logged in as root user,
- and you are using an USB modem like that one we mentioned
- before, the output of <command>lsusb</command> command would
- look like the following:
- </para>
-
-<screen>
-Bus 003 Device 001: ID 0000:0000
-Bus 001 Device 001: ID 0000:0000
-Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
-Bus 002 Device 001: ID 0000:0000
-Bus 005 Device 003: ID 06e0:f104 Multi-Tech Systems, Inc.
-MT5634ZBA-USB MultiModemUSB (new firmware)
-Bus 005 Device 001: ID 0000:0000
-Bus 005 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
-Bus 004 Device 001: ID 0000:0000
-</screen>
-
- <para>
- The relevant line here is that mentioning the existence of a
- <code>Multi-Tech System, Inc. MT5634ZBA-USB MultiModemUSB (new
- firmware)</code> device. If the modem you installed doesn't
- appear in this list, it is probably because such hardware is
- not supported by &TCD;, yet.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Install/overview.docbook b/Manuals/HowTos/Dialup/Server/Install/overview.docbook
deleted file mode 100644
index f7e99b1..0000000
--- a/Manuals/HowTos/Dialup/Server/Install/overview.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-install-overview">
-
- <title>Overview</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Install/pppd.docbook b/Manuals/HowTos/Dialup/Server/Install/pppd.docbook
deleted file mode 100644
index cf8882a..0000000
--- a/Manuals/HowTos/Dialup/Server/Install/pppd.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<sect1 id="server-install-pppd">
-
- <title>Installing <package>pppd</package> Package</title>
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Install/wvdial.docbook b/Manuals/HowTos/Dialup/Server/Install/wvdial.docbook
deleted file mode 100644
index b7f1591..0000000
--- a/Manuals/HowTos/Dialup/Server/Install/wvdial.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="server-install-wvdial">
-
- <title>Installing <package>wvdial</package> Package</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Usage.docbook b/Manuals/HowTos/Dialup/Server/Usage.docbook
deleted file mode 100644
index 2074872..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="server-usage">
-
- <title>Dial-Up Server Usage</title>
-
- &server-usage-overview;
- &server-usage-lifetime;
- &server-usage-phonelines;
- &server-usage-auth;
- &server-usage-networking;
-
-</chapter>
diff --git a/Manuals/HowTos/Dialup/Server/Usage/auth.docbook b/Manuals/HowTos/Dialup/Server/Usage/auth.docbook
deleted file mode 100644
index fde3908..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/auth.docbook
+++ /dev/null
@@ -1,28 +0,0 @@
-<sect1 id="server-usage-auth">
-
- <title>Dial-Up Authentication</title>
-
- <para>
- The credential required by the client computers to establish
- dial-up connection with the server computer are always the
- same. There is only one public username and password for all
- client computers that must be used in order to establish
- dial-up connection with the server computer. This information
- is the following:
- </para>
-
-<screen>
- ISP Name: projects.centos.org
-ISP Phone: +53043515094
- Username: faith
- Password: mail4u.2k10
-</screen>
-
- <para>
- The client computer can use this information to establish
- connection to the server computer using any telephone number
- from 10:00PM to 12:00AM.
- </para>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Server/Usage/connections.docbook b/Manuals/HowTos/Dialup/Server/Usage/connections.docbook
deleted file mode 100644
index e69de29..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/connections.docbook
+++ /dev/null
diff --git a/Manuals/HowTos/Dialup/Server/Usage/diskspace.docbook b/Manuals/HowTos/Dialup/Server/Usage/diskspace.docbook
deleted file mode 100644
index 950fc51..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/diskspace.docbook
+++ /dev/null
@@ -1,36 +0,0 @@
-<sect1 id="server-usage-diskspace">
-
- <title>Administering Disk Space</title>
-
- <para>
- The maximum number of registered user profiles is limited
- inside the server computer, based on the maximum disk space
- the server computer confines to such purpose. For example,
- consider an environment where users can get registered
- themselves using a web interface. In this case the web
- interface must know how much disk space is available before
- proceeding to register new mail accounts inside the server
- computer and this way preventing any disk writing when there
- isn't enough free space on disk to perform a new user
- registration. Considering the server computer has confined
- 1GB of disk space to handle the mail service (e.g., mail
- queues, mailboxes, etc.) and each user mailbox is 10MB, it
- will be possible to provide self-registration through the web
- interface for 100 users in total.
- </para>
-
- <para>
- Another measure related to save disk space might be to remove
- unused user accounts and their related files (e.g., mailboxes)
- from the server computer. For example, consider an environment
- where user accounts are automatically removed from the server
- computer when they don't establish a connection with the
- server computer in a period greater than 7 days since the last
- valid connection established to the server computer. Once the
- user account is removed, it is no longer functional of course,
- and the person whom lost the account will need to create a new
- one, assuming it want to have access to the mail service
- again.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Usage/lifetime.docbook b/Manuals/HowTos/Dialup/Server/Usage/lifetime.docbook
deleted file mode 100644
index ec67cb8..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/lifetime.docbook
+++ /dev/null
@@ -1,28 +0,0 @@
-<sect1 id="server-usage-lifetime">
-
- <title>Dial-Up Connection Lifetime</title>
-
- <para>
- The server computer restricts the lifetime of established
- dial-up connections to 15 minutes from the establishment
- moment on. Once the connection has been established, if the
- link is idle for 1 minute, the server computer will also close
- the established connection to free the telephone line. This
- control can be implemented through the
- <option>maxconnect</option> and <option>idle</option> options
- inside the <application>pppd</application>'s configuration
- file.
- </para>
-
- <para>
- The server computer allows incoming connections everyday from
- 10:00PM to 12:00AM. This control can be implemented through a
- cron job and the <filename>/etc/nologin.ttyxx</filename> file;
- where ttyxx represents the device name of your modem
- (e.g., <filename>/etc/nologin.ttyACM0</filename> would prevent
- the Modem device installed in
- <filename>/dev/ttyACM0</filename> from answering calls).
- </para>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Server/Usage/networking.docbook b/Manuals/HowTos/Dialup/Server/Usage/networking.docbook
deleted file mode 100644
index a37c9f4..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/networking.docbook
+++ /dev/null
@@ -1,35 +0,0 @@
-<sect1 id="server-usage-network">
-
- <title>Dial-Up Networking</title>
-
- <para>
- Once you establish connection with the server computer, you
- are assigned the <systemitem
- class="ipaddress">192.168.0.2</systemitem> IP address and the
- <systemitem class="fqdomainname">faith.centos.org</systemitem>
- name. On the other side, the server computer has the
- <systemitem class="ipaddress">192.168.0.1</systemitem> IP
- address and the <systemitem
- class="fqdomainname">projects.centos.org</systemitem> name. In
- both cases, the addresses provided are inside the <systemitem
- class="netmask">192.168.0/24</systemitem> network. The
- configuration would look as the following example illustrates:
- </para>
-
-<screen>
-The Server Computer The Client Computer
------------------------ -----------------------
-192.168.0.1/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.0.2/24
------------------------ -----------------------
-projects.centos.org faith.centos.org
-</screen>
-
- <para>
- Notice that, before you can use this IP addresses and names,
- they must be firstly configured that way by the system
- administrator. See ..., to know how to configure the IP
- addresses and names in the server computer.
- </para>
-
-</sect1>
-
diff --git a/Manuals/HowTos/Dialup/Server/Usage/overview.docbook b/Manuals/HowTos/Dialup/Server/Usage/overview.docbook
deleted file mode 100644
index c08791e..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/overview.docbook
+++ /dev/null
@@ -1,45 +0,0 @@
-<sect1 id="server-usage-overview">
-
- <title>Overview</title>
-
- <para>
- In this infrastructure, dial-up connections will always be
- established from the client computer to the server computer
- and never the other way around. The main purpose of a client
- computer to establish a dial-up connection with the server
- computer will be to use one or more internet services provided
- in the server computer through the telphone line.
- </para>
-
- <para>
- In order for the server computer to answer telephone calls, it
- is required to install a Modem device in it (see <xref
- linkend="server-install-modem" />). Once the Modem device has
- been installed, you need to install and configure both
- <application>mgetty</application> and
- <application>pppd</application> programs. The
- <application>mgetty</application> program must be run by
- <systemitem class="daemon">init</systemitem> daemon in order
- to take control over the Modem device. By default, inside
- &TCD; (release 5.5), mgetty isn't configured to start with
- <systemitem class="daemon">init</systemitem> daemon so you
- need to do it yourself (see ...). Later, for attending
- connection requests, you need to configure mgetty to use the
- <application>pppd</application> program, so the Point-to-Point
- Protocol (PPP) can be talked and IP packages can be
- interchanged between the client computer and the server
- computer. Later, you need to configure
- <application>pppd</application> to adjust it to your needs
- (see ...).
- </para>
-
- <para>
- Once you've configured both <application>mgetty</application>
- and <application>pppd</application> programs, the server
- computer should be ready to attend incoming calls. The
- remaining of this chapter describes the way incoming calls are
- attended by the server computer once they have arrived to its
- Modem device.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Usage/phonelines.docbook b/Manuals/HowTos/Dialup/Server/Usage/phonelines.docbook
deleted file mode 100644
index 7a52e97..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/phonelines.docbook
+++ /dev/null
@@ -1,20 +0,0 @@
-<sect1 id="server-usage-phonelines">
-
- <title>Dial-Up Telephone Lines</title>
-
- <para>
- In this configuration there is only one telephone line
- available (e.g., +53043515094) in the server computer to
- receive incoming calls. The number of telephone lines
- directly affects the possibilities a client computer has to
- establish connection with the server computer in an
- environment where more than one client computer are struggling
- among themselves to establish a dial-up connection with the
- server computer. To prevent this issue from happening, it is
- innevitable for the server computer to provide more telephone
- lines for incoming calls (at least one for each user the
- server computer expect to receive incoming calls from). Sadly,
- that is not possible at present time.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Usage/services.docbook b/Manuals/HowTos/Dialup/Server/Usage/services.docbook
deleted file mode 100644
index 2f89a6c..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/services.docbook
+++ /dev/null
@@ -1,81 +0,0 @@
-<sect1 id="server-usage-services">
-
- <title>Administering Internet Services</title>
-
- <para>
- The information generated inside the server computer is
- isolated from Internet. This way, any information generated
- inside the server computer will be available only to people
- registered inside the server computer. For example, don't ever
- expect to send/receive e-mails to/from Internet e-mail
- accounts like Gmail or Yahoo, nor visiting web sites like
- <ulink url="http://www.google.com/">Google</ulink> or <ulink
- url="http://www.wikipedia.org/">Wikipedia</ulink> either. For
- this to happen, it is required an established connection
- between the server computer you are establishing connection
- through and the Internet network those services are available
- in. Without that link, it is not possible to direct your
- requests to those sites.
- </para>
-
- <para>
- The implementation of services that required persistent
- connections (e.g., <application>chats</application>) will not
- be considered as a practical offer inside the server computer.
- Instead, only asynchronous services (e.g.,
- <application>e-mail</application>) will be supported. This
- restriction is required to reduce the amount of time demanded
- by services. For example, consider an environment where you
- connect to the server computer for sending/receiving e-mails
- messages and then quickly disconnect from it to free the
- telephone line for others to use. In this environment, there
- is no need for you and other person to be both connected at
- the same time to send/receive e-mail messages to/from each
- other. The e-mails sent from other person to you will be
- available in your mailbox the next time you get connected to
- the server computer and use your e-mail client to send/receive
- e-mail messages. Likewise, you don't need to be connected to
- the server computer in order to write your e-mail messages.
- You can write down your messages off-line and then establish
- connection once you've finished writing, just to send them
- out and receive new messages that could have been probably
- sent to you.
- </para>
-
- <para>
- Another issue related to e-mail exchange is the protocol used
- to receive messages. Presently, there are two popular ways to
- do this, one is through IMAP and another through POP3. When
- you use IMAP protocol, e-mail messages are retained in the
- server computer and aren't downloaded to client computer.
- Otherwise, when you use POP3 protocol, e-mail messages are
- downloaded to the client computer and removed from server
- computer. Based on the resources we have and the kind of link
- used by the client computer to connect the server computer,
- using POP3 is rather prefered than IMAP. However both are made
- available.
- </para>
-
- <para>
- Assuming you use IMAP protocol to read your mailbox, be aware
- that you need to be connected to the server computer. Once
- the connection is lost you won't be able to read your messages
- (unless your e-mail client possesses a feature that let you
- reading messages off-line). Morover, you run the risk of
- getting your mailbox out of space. If your mailbox gets out of
- space, new messages sent to you will not be deliver to your
- mailbox. Instead, they will be deferred for a period of time
- (e.g., about 5 days when using
- <application>Postfix</application> defaults) hoping you to
- free the space in your mailbox to deliver them. If you don't
- free space within this period of time, the deferred e-mails
- will be bounced back to their senders and you will never see
- them. On the other hand, assuming you are using POP3 protocol
- to read your mailbox, you always keep your mailbox free to
- receive new e-mails messages and keep them for you until the
- next time you establish connection with the server computer
- and download them to your client computer using your e-mail
- client.
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/Server/Usage/users.docbook b/Manuals/HowTos/Dialup/Server/Usage/users.docbook
deleted file mode 100644
index 2cdf646..0000000
--- a/Manuals/HowTos/Dialup/Server/Usage/users.docbook
+++ /dev/null
@@ -1,61 +0,0 @@
-<sect1 id="server-usage-users">
-
- <title>Administering Users Accounts</title>
-
- <para>
- In order for you to use any service provided by the server
- computer it is required that you register yourself inside the
- server computer creating a user profile. The user profile
- provides the user information required by services inside the
- server computer (e.g., username, password, e-mail address,
- telephone number, etc.). To register new user profiles, you
- need to use the web application provided by the server
- computer. For example, assuming the domain name of the server
- computer is <systemitem
- class="domainname">example.com</systemitem>, the web
- application would be accessable through the following URL:
- <ulink url="https://example.com/people/?action=register" />.
- </para>
-
- <para>
- To reach the web interface, the first thing you need to do is
- establishing a dial-up connection to the server computer as
- described in <xref
- linkend="server-config"/>. Once the
- dial-up connection has been established, you need to open a
- web browser (e.g., Firefox) and put the URL mentioned above in
- the address space, and press Enter to go. This will present
- you a web page with the instructions you need to follow in
- order to register your user profile. Other actions like
- updating or deleting your own user profile should be also
- possible from this web interface.
- </para>
-
- <important>
- <para>
- The web interface used to manage user profiles inside the
- server computer must be presented over an encrypted session in
- order to protect all the information passing through.
- </para>
- </important>
-
- <para>
- Inside the server computer, all related subsystems in need of
- user information (e.g., Postix, Cyrus-Imapd and Saslauthd)
- retrive user information from one single (LDAP) source. The
- web application provided by the server computer manages all
- these subsystems' configuration files in order to provide a
- pleasant experience for end users. The web interface must be
- as simple as possible in order to achieve all administration
- tasks in the range of time permitted by the server computer
- before it closes the connection established from the client
- computer.
- </para>
-
- <para>
- More information about the web interface you need to use to
- manage your user profile inside the server computer can be
- found in ....
- </para>
-
-</sect1>
diff --git a/Manuals/HowTos/Dialup/dialup.docbook b/Manuals/HowTos/Dialup/dialup.docbook
deleted file mode 100755
index af57010..0000000
--- a/Manuals/HowTos/Dialup/dialup.docbook
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
- [
-
-<!ENTITY % Commons.ent SYSTEM "Commons.ent">
-<!ENTITY % Preface.ent SYSTEM "Preface.ent">
-<!ENTITY % Server.ent SYSTEM "Server.ent">
-<!ENTITY % Client.ent SYSTEM "Client.ent">
-<!ENTITY % Licenses.ent SYSTEM "Licenses.ent">
-
-%Commons.ent;
-%Preface.ent;
-%Server.ent;
-%Client.ent;
-%Licenses.ent;
-]>
-
-<book lang="en_US">
-
- <!-- Front matter -->
- <title>Dial-Up Infrastructure</title>
-
- <bookinfo>
- <author>
- <firstname>Alain</firstname>
- <surname>Reguera Delgado</surname>
- </author>
-
- <!-- Copyright: The copyright page is verso and contains the
- copyright notice, the publishing/printing history, the country
- where printed, ISBN and/or CIP information. The page is
- usually typeset in a smaller font than the normal text. -->
- <copyright>
- <year>2011</year>
- <holder>&TCP;. All rights reserved.</holder>
- </copyright>
-
- <legalnotice>
- <para>
- Permission is granted to copy, distribute and/or modify
- this document under the terms of the GNU Free
- Documentation License, Version 1.2 or any later version
- published by the Free Software Foundation; with no
- Invariant Sections, no Front-Cover Texts, and no
- Back-Cover Texts. A copy of the license is included in
- <xref linkend="licenses-gfdl" />.
- </para>
- </legalnotice>
-
- <revhistory>
- <revision>
- <revnumber>1.0</revnumber>
- <date>Today</date>
- <author>
- <firstname>Alain</firstname>
- <surname>Reguera Delgado</surname>
- </author>
- <revdescription>
- <para>
- Under development.
- </para>
- </revdescription>
- </revision>
- </revhistory>
-
- </bookinfo>
-
- <!-- Front matter -->
- &preface;
-
- <!-- Main matter -->
- &server;
- &client;
-
- <!-- Back matter -->
- &licenses;
-
-</book>