diff --git a/Documentation/Models/Docbook/Tcpi-ug/Commons.ent b/Documentation/Models/Docbook/Tcpi-ug/Commons.ent deleted file mode 100755 index f5bcdd1..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/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/Documentation/Models/Docbook/Tcpi-ug/Connectivity.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity.docbook deleted file mode 100644 index fd0139b..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity.docbook +++ /dev/null @@ -1,16 +0,0 @@ -<part id="connectivity"> - - <title>Connectivity</title> - - <partintro> - <para> - This part of the book describes how to connect your computer - to the telephone network and configure the programs required - to establish the connection through which you will transmit - data using computers. - </para> - </partintro> - - &connectivity-ppp; - -</part> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity.ent b/Documentation/Models/Docbook/Tcpi-ug/Connectivity.ent deleted file mode 100644 index c0cee7e..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity.ent +++ /dev/null @@ -1,7 +0,0 @@ -<!ENTITY connectivity SYSTEM "Connectivity.docbook"> -<!ENTITY connectivity-ppp SYSTEM "Connectivity/Ppp.docbook"> -<!ENTITY connectivity-ppp-overview SYSTEM "Connectivity/Ppp/overview.docbook"> -<!ENTITY connectivity-ppp-modem SYSTEM "Connectivity/Ppp/modem.docbook"> -<!ENTITY connectivity-ppp-server SYSTEM "Connectivity/Ppp/server.docbook"> -<!ENTITY connectivity-ppp-client SYSTEM "Connectivity/Ppp/client.docbook"> -<!ENTITY connectivity-ppp-network SYSTEM "Connectivity/Ppp/network.docbook"> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp.docbook deleted file mode 100644 index 018d471..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp.docbook +++ /dev/null @@ -1,11 +0,0 @@ -<chapter id="connectivity-ppp"> - - <title>PPP</title> - - &connectivity-ppp-overview; - &connectivity-ppp-modem; - &connectivity-ppp-server; - &connectivity-ppp-client; - &connectivity-ppp-network; - -</chapter> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/client.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/client.docbook deleted file mode 100644 index 06405e0..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/client.docbook +++ /dev/null @@ -1,17 +0,0 @@ -<sect1 id="connectivity-ppp-client"> - - <title>The Client Computer</title> - - <para> - When you are configuring the client computer, you need to - install the <package>wvdial</package>, <package>pppd</package> - and <package>system-config-network</package> packages. From - these packages, to configure your Modem connection, you only - need to use the interface provided by the - <package>system-config-network</package> package. This - interface controls configuration files related to - <application>pppd</application> and - <application>wvdial</application> programs for you. - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/modem.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/modem.docbook deleted file mode 100644 index 3a168ee..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/modem.docbook +++ /dev/null @@ -1,194 +0,0 @@ -<sect1 id="connectivity-ppp-modem"> - - <title>The Modem Device</title> - - <para> - In order to establish a PPP link between two computers using - the telephone line as medium for data transmission, you will - need to install and configure a modem device in each computer - you plan to connect. On the other hand, if you're planning to - use PPP to connect the same computer to different networks - simultaneously (e.g., to build a proxy between them), you will - need to install and configure one modem device for each - different network you plan to establish such simultaneous - connection in the same computer. - </para> - - <sect2 id="connectivity-ppp-modem-install"> - <title>Installing Modem Devices</title> - <para> - To install a modem device in the computer, you need to attach - the modem hardware to the computer and later the telephone - line to the modem hardware. To attach the modem hardware 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 (whether serial or USB). To connect the modem - hardware to the telephone line, 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 through modem's data port. - </para> - - <para> - To be on the safe side, do everything related to hardware - installation with the computer turned off. Then, when - everthing has been put in place, turn the computer on. Once - the operating system is up and running, you can verify the - modem hardware using either the <command>lsusb</command> or - <command>lspci</command> commands, based on whether you - attached the modem device to an USB or serial port, - respectivly. These commands need to be run with - administrative privileges, thus, you probably need to do - <command>sudo</command> on them or login as <systemitem - class="username">root</systemitem> user in order to execute - them. For example, assuming you logged in as <systemitem - class="username">root</systemitem> user and you installed an - USB modem hardware as mentioned before, the output of - <command>lsusb</command> command would be similar to that - 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 in this output is that one mentioning the - existence of your modem. For example, <code>Multi-Tech System, - Inc. MT5634ZBA-USB MultimodemUSB (new - firmware</code>)<footnote> - <para> - I want to thank my friend Brians Suarez Alonso for - bringing this modem hardware to me and for his paitient, - resisting my repetitive calls at night to realize - connection tests. - </para> - </footnote>. This line confirms that your modem hardware is - supported by &TCD; and it is possible to transmit data through - it. Otherwise, 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> - Once you have confirmed the modem hardware has been installed - in the computer (either client or server), you need to - determine the device name the operating system assigned to it. - This information is required by programs like - <application>mgetty</application> and - <application>wvdial</application>, so they can know what - device to talk to. Assuming you've connected your modem - device through an USB port, the operating system will assign - the the <filename>/dev/ttyACM0</filename> device file to talk - to it. On the other hand, assuming you've connected your - modem device through a serial port, the operating system will - use the <filename>/dev/ttyS0</filename> device file to talk to - it. To be absolutly sure about what device name the operating - system assigned to your modem hardware, you can use the - <command>lshal</command> command from <package>hal</package> - package. - </para> - </sect2> - - <sect2 id="connectivity-ppp-modem-config"> - <title>Configuring Modem Devices</title> - - <para> - Inside &TCD;, modem devices can be configured using the - <command>system-config-network</command> tool. This tool is a - manages modem configuration files under the - <filename>/etc/sysconfig/network-scripts</filename> and - <filename>/etc/wvdial.conf</filename>. Inside - <filename>/etc/sysconfig/network-scripts</filename>, modem - configuration files can take different file names. To identify - them you need to open the file and checking the value set on - <varname>DEVICE</varname> variable. This variable can take - values like <code>ppp0</code> for the first modem device, - <code>ppp1</code> for the second modem device, and so on for - other modem devices. - </para> - - <para> - The configuration files of modem devices may vary based on - whether the computer is acting as server, client or both. - When you configure the modem device on the server computer, - you should take care of specifying both the IP address - (IPADDR) and the network mask (NETMASK) inside the - configuration file. Otherwise, the established connection - might end up having the wrong IP information you need to - transfer data correctly through it, assuming the other end - isn't configured to specify it. When you configure the modem - device on the server computer, there is no need for you to set - any configuration related to wvdial, unless you be thinking to - make your server computer to act as a client of another server - computer. In fact, in the server computer, you can create the - modem configuration file by yourself based on the information - provided at - <filename>/usr/share/doc/initscripts-*/sysconfig.txt - </filename> - </para> - - <para> - When you configure the modem device on the client computer, - you don't need to take care of specifying either the IP - address or network mask because the server computer will - assign them for you. The assignment of client computer IP - address is configured by <application>ppp</application> daemon - when it is executed by <application>mgetty</application> after - an incoming call has arrived to modem's port. - </para> - - <example id="connectivity-ppp-modem-config.fig-1"> - <title>Modem configuration file</title> - <screenshot> - <screeninfo>Modem configuration file</screeninfo> - <mediaobject> - <textobject> -<screen> -# Please read /usr/share/doc/initscripts-*/sysconfig.txt -# for the documentation of these parameters. -TYPE=modem -DEVICE=ppp0 -BOOTPROTO=none -ONBOOT=no -USERCTL=yes -PEERDNS=yes -AC=off -BSDCOMP=off -VJCCOMP=off -CCP=off -PC=off -VJ=off -LINESPEED=115200 -MODEMPORT=/dev/ttyACM0 -PROVIDER=ProviderName -DEFROUTE=yes -PERSIST=no -PAPNAME=faith -WVDIALSECT=ProviderName -MODEMNAME=Modem0 -DEMAND=no -IPV6INIT=no -IDLETIMEOUT=600 -NETMASK=255.255.255.0 -IPADDR=192.168.1.1 -</screen> - </textobject> - </mediaobject> - </screenshot> - </example> - - </sect2> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/network.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/network.docbook deleted file mode 100644 index 7fa47ba..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/network.docbook +++ /dev/null @@ -1,637 +0,0 @@ -<sect1 id="connectivity-ppp-network"> - - <title>The Network Of Computers</title> - - <para> - This section describes how you could distribute server and - client computers to create a collaborative network. - </para> - - <sect2 id="connectivity-ppp-policy-network"> - <title>One PPP Network Of Two Computers</title> - - <para> - The simpliest configuration we can achieve over the telephone - network involves two computers only, where one computer would - be acting as server and another as client. In this - configuration, the client computer establishes connection to - the server to make use of internet services provided therein. - </para> - - <para> - When the client computer calls the server computer, the call - is attended by <application>mgetty</application> and then - passed to <application>pppd</application> for establishing a - PPP conversation between the two computers. The first thing - in a PPP conversation is the user authentication and then - (after a sucessful athentication), the IPCP conversation takes - place to set IP addresses and start data transmission over the - link recently created. In this configuration, the client - computer can set its IP address when configuring the Modem - device (see <xref - linkend="connectivity-ppp-modem-config" />) or - leave the server computer to assign one (assuming you are - calling a server computer). If you are configuring a server - computer, then it is necessary that you set the IP address and - netmask of the IP network you are planning to set, using the - Modem device configuration file. - </para> - - <para> - Configuring the IP address and netmask information inside - Modem device configuration file is very important in order to - prevent errors when transmitting data across the link. When - the the netmask information isn't set in the Modem device - configuration file, the <systemitem - class="daemon">pppd</systemitem> daemon on the server computer - tries to retrive such information from the client computer and - if the client computer didn't specify one either, the network - recently created would end up having a wrong information - (e.g., <systemitem - class="netmask">255.255.255.255</systemitem>) which provokes - the point-to-point connection to fail when someone tries to - transfer data through it. - </para> - - <figure id="connectivity-ppp-policy-network-basic"> - <title>One PPP network of two computers</title> - <screenshot> - <screeninfo>One PPP network of two computers</screeninfo> - <mediaobject> - <textobject> -<screen> -Provice-A PPP Server Province-A PPP Client ---------------------------\ /-------------------------- -192.168.1.1/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.2/24 ---------------------------/ \-------------------------- -</screen> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para> - The <xref linkend="connectivity-ppp-policy-network-basic" /> - describes the simpliest configuration we can implement for a - point-to-point connection. This configuration involves two - computers only, one acting as server (the server computer) and - other acting as client (the client computer). The client - computer calls the server computer to establish a PPP - connection in order to use whatever internet service the - server computer provides. In the figure we can see that there - are two IP addresses involved (<systemitem - class="ipaddress">192.168.1.1</systemitem> and <systemitem - class="ipaddress">192.168.1.2</systemitem>) inside the same - newtork (<systemitem - class="netmask">255.255.255.0</systemitem>). - </para> - - <para> - This configuration might be convenient for people in the same - location, near one another. Here, the client computer - establishes connection by mean of a local telephone call and - can use whatever internet service the server computer - provides. Since the connection lifetime is limited (see <xref - linkend="connectivity-ppp-policy-lifetime" />) and only two - peers can be connected at the same time (assuming only one - Modem is attached to the server computer), the implementation - of some internet services like chat may be not a practical - offer for the server computer to provide. However, internet - services like e-mail fit perfectly on this environment where - more than one client computer would be struggling among - themselves for establishing connection with the server - computer (e.g., people connect to send/receive their e-mail - messages to/from the server computer). - </para> - - </sect2> - - <sect2 id="connectivity-ppp-policy-network-extended"> - <title>One PPP Network Of Several Computers</title> - - <para> - Based on <xref - linkend="connectivity-ppp-policy-network" />, it is - possible to provide an extended version including several - server computers that may communicate between themselves to - distribute data collected from client computers they serve to. - For example, consider the telephone network of a country which - is organized in provinces and each province is divided in - several municipalities. In such organization, it would be - possible to set one or more server computers for each province - and let near people to dial-up on them to use whatever - internet service they provide. Later, it could be possible - for each server computer to establish a dial-up connections - with other near server computers in order to share information - from one province to another, as it is illustrated in <xref - linkend="connectivity-ppp-policy-network-extended.fig-1" - />. - </para> - - <para> - When setting the IP information, it is important that each - server computer sets both IP address and IP network mask - information in the Modem device configuration file so - different IP address can be use between different server - computers. It is also important that they all be configured to - use authentication between themselves before transmitting any - data across a PPP established connection so the information - being transmitted can be protected. - </para> - - <para> - When making telephone calls, if someone in Province-A needs to - send a message to someone in Province-C (which is far away - from Province-A and making a telephone call there would imply - a considerable amount of money), there is no need (even it is - possible and sometimes prefered) for that person to realize a - direct telephone call from Province-A to Province-C. Instead, - that person in Province-A can send its messages to the server - computer on its province (the nearest server on its location) - making a local telephone call and then, such server computer - would take care of delivering the information using other - server computers, following the same concept of nearest - delivery. - </para> - - <figure id="connectivity-ppp-policy-network-extended.fig-1"> - <title>One PPP network of several computers</title> - <screenshot> - <screeninfo>One PPP network of several computers</screeninfo> - <mediaobject> - <textobject> -<screen> -Provice-A PPP Server Province-A PPP Client ---------------------------\ /-------------------------- -192.168.1.1/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.2/24 ---------------------------/ | \-------------------------- - | -Provice-B PPP Server | Province-B PPP Client ---------------------------\ | /-------------------------- -192.168.1.3/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.4/24 ---------------------------/ | \-------------------------- - | -Provice-C PPP Server | Province-C PPP Client ---------------------------\ | /-------------------------- -192.168.1.5/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.6/24 ---------------------------/ \-------------------------- -</screen> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para> - The more distant a telephone call is, the more expensive it - is. This way, to move information from one province to - another, each server computers must be configured to send - information to the nearest province until reaching its - destination. For example, if you are in Province-A and want to - send an e-mail message to Province-D, the server computer - configured in Province-A must sed the e-mail message to - Province-B, then server in Province-B must be configured to - send such message to Province-C, and finally C to D. This is - required because making a direct call from Province-A to - Province-D would be otherwise too much expensive to pay. - </para> - - <para> - Since telephone calls are required to establish connections - between computers and each call costs money based on the - location and the destination, it is required to set a - convenction in how telephone calls are realized from one - server computer to another, specially if you plan to establish - connection between server computer placed on different - provices in order to exchange data between them. - </para> - - <itemizedlist> - <listitem> - <para> - Do you make direct telephone calls to make direct data delivery? - — This configuration could be very expensive to maintain - (considering the telephone call distances), but data will be - delivered very fast to their destinations. - </para> - </listitem> - <listitem> - <para> - Do you call the nearest server computer and let it to deliver - your data to its destination? — This configuration could - be less expensive to maintain (considering the telephone call - distances), but data delivery will take much more time to - reach their destinations and there is no way to be sure it - will do. - </para> - - </listitem> - </itemizedlist> - - <para> - Whatever calling schema be chosen, the server computers will - always talk through UUCP to transfer data from one place to - another. The server computers will operate with two IP - addresses each, unless you plan to connect one of the server - computers to a different network (Internet, maybe?). One IP - address would identify the server computer itself and the - other would identify the client computer establishing PPP - connection to the server computer. In this configuration it - is very importat that each server and client computer does - have one unique IP address. This way it would be possible to - move the information from one computer to another. Notice that - the number of PPP clients is directly related to the number of - telephone lines a server computer has configured to receive - incomming calls on. If there is only one telephone line - attached to the server computer then, only one client computer - will be able to establish connection to that server computer. - Other PPP clients will need to wait until the telephone line - gets free in order to establish connection with that server - computer. On the other hand, if the server computer has two - (or more) attached telephone lines, it would be possible to - attend incoming calls from two (or more) PPP client at the - same time. As resume, we can say that: the more telephone - lines the server computer has attached in, the more - simultaneous connections that computer will be able to - attend/realize from/to other computers. - </para> - - </sect2> - - <sect2 id="connectivity-ppp-policy-network-eth"> - <title>One PPP+Ethernet Network Of Several Computers</title> - - <para> - Assuming all server computers with a Modem device have also - one (or more) Ethernet interface attached (which is very - common nowadays), it would be possible to extend the - configuration described in <xref - linkend="connectivity-ppp-policy-network-extended.fig-1" /> - creating one Ethernet network for each server computer in the - configuration. For this configuration to be implemented it is - required one or more switch devices (based on the amount of - computers such network needs to have) for each ethernet - network interface a server computer has, as described in <xref - linkend="connectivity-ppp-policy-network-extended.fig-2" - />. - </para> - - <figure id="connectivity-ppp-policy-network-extended.fig-2"> - <title>One PPP+Ethernet network of several computers</title> - <screenshot> - <screeninfo>One PPP+Ethernet network of several computers</screeninfo> - <mediaobject> - <textobject> -<screen> -Province-A PPP/ETH Server Province-A PPP Client ---------------------------\ /-------------------------- -192.168.1.1/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.2/24 ---------------------------/ | \-------------------------- -192.168.0.1/24 | Ethernet | ----------------------|---- | - | | - +--------+ | - | Switch | | - +--------+ | - | | ----------------------|-- | -LAN1: 192.168.0.2-254/24 | ------------------------- | -Province-A ETH Clients | - | -Province-B PPP/ETH Server | Province-B PPP Client ---------------------------\ | /-------------------------- -192.168.1.3/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.4/24 ---------------------------/ | \-------------------------- -192.168.2.1/24 | Ethernet | ----------------------|---- | - | | - +--------+ | - | Switch | | - +--------+ | - | | ----------------------|-- | -LAN2: 192.168.2.2-254/24 | ------------------------- | -Province-B ETH Clients | - | -Province-C PPP/ETH Server | Province-C PPP Client ---------------------------\ | /-------------------------- -192.168.1.5/24 | Modem ~~~ TelephoneLine ~~~ Modem | 192.168.1.6/24 ---------------------------/ \-------------------------- -192.168.3.1/24 | Ethernet ----------------------|---- - | - +--------+ - | Switch | - +--------+ - | ----------------------|-- -LAN3: 192.168.3.2-254/24 ------------------------- -Province-C ETH Clients -</screen> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para> - In this configuration, computers connected to the switch will - also be considered as client computers. It is necessary that a - coordination be implemented at time of setting IP addresses to - new server computers so no IP address be duplicated on the - computer network. The illustration above describes one main - network (<systemitem - class="ipaddress">192.168.1/24</systemitem>) which connects - all the server computers using the telephone lines as medium - for data transmission. The Modem interface connects just one - computer at a time either client or server (assuming only one - Modem device is installed and configured in - the computer acting as server). The telephone line is used by - client computers to establish PPP connections with the server - computer and by server computers to exchange data with other - server computers, as well. On the other hand, the ethernet - interface attached to each server computer let the - administrator of each server computer to connect up to 252 - computers simultaneously, assuming a class C network as shown - above be used.<footnote> - <para> - There are also class A and class B network types which can be - used to connect much more computers than a class C network - allows to. - </para> - </footnote> - </para> - - </sect2> - - <sect2 id="connectivity-ppp-policy-bridgedcall"> - <title>About Bridging Calls To Transfer Data</title> - - <para> - When the server computers call other server computers to - bridge data delivery, the server computer in, let's say, - Province-A (srv-1.a.domain.tld) will never know that there is - a server computer on Province-C (srv-1.c.domain.tld) or - Province-D (srv-1.d.domain.tld), but in Province-B - (srv-1.b.domain.tld) - only, its nearest location. So, when a message is sent from - srv-1.a.domain.tld to the server computer in - srv-1.d.domain.tld, the server computer in srv-1.a.domain.tld - contacts its nearest server computer (i.e., - srv-1.b.domain.tld) and delivers to it all messages sent to - srv-1.d.domain.tld. Later, since srv-1.b.domain.tld doesn't - know about srv-1.d.domain.tld server either, it delivers all - messages directed to srv-1.d.domain.tld to its nearest server - computer (i.e., srv-1.c.domain.tld). Later, the server - computer in srv-1.c.domain.tld, which knows about - srv-1.d.domain.tld, delivers to it all the messages it has for - it. Notice that, in order for this configuration to work, - system administrators attending the server computers must work - syncronized to garantee a well defined route for messages to - follow. Otherwise, if one of the server computers in the path - creates a route for a server computer that doesn't exist - (or doesn't define a route at all), the information will never - reach its destination when such computer is acting as a bridge - between other two server computers. - </para> - -<screen> -+------------------------+ +------------------------+ +------------------------+ +---------------------+ -| To: bob@d.domain.tld | | To: bob@d.domain.tld | | To: bob@d.domain.tld | | Bob's mailbox | -| From: mat@a.domain.tld | | From: ana@b.domain.tld | | From: jef@c.domain.tld | | (Final destination) | -| Body: 500KB | | Body: 500KB | | Body: 500KB | | | -+---|--------------------+ +---|--------------------+ +---|--------------------+ +------------------^--+ - | | | | -----v--------------|<~~~~~~~~~>|---v----------------|<~~~~~~~~~>|---v----------------|<~~~~~~~~~>|------------------|--- -srv-1.a.domain.tld | 75Km Call | srv-1.b.domain.tld | 75Km Call | srv-1.c.domain.tld | 75Km Call | srv-1.d.domain.tld --------------------|<~~~~~~~~~>|--------------------|<~~~~~~~~~>|--------------------|<~~~~~~~~~>|---------------------- -relay to: | 5 min | relay to: | 10 min | relay to: | 15 min | -srv-1.b.domain.tld | 500KB | srv-1.c.domain.tld | 1.0MB | srv-1.d.domain.tld | 1.5MB | -</screen> - </sect2> - - <sect2 id="connectivity-ppp-policy-directcalls"> - <title>About Directing Calls To Transfer Data</title> - - <para> - When the server computers make direct telephone calls (no - bridge in-between is used to transfer data), the server - computer in Province-A (srv-1.a.domain.tld) contacts the - server computer in Province-D (srv-1.d.domain.tld) making a - direct telephone call up to it. In this configuration, the - telephone call might cost more than those in a bridged - configuration where several smaller telephone calls are dialed - in-between the final server computer; or less, considering - that when server computers in a bridged configuration exchange - data they may move data accumulated from other server - computers, while a direct telephone call would transmit data - from one server computer to another without any accumulated - data from other server computers. There is no need to - overload the server computers with foreign data when each - server computer could call themselves to transfer data - directly. - </para> - -<screen> -+------------------------+ +---------------------+ -| To: bob@d.domain.tld | | Bob's mailbox | -| From: mat@a.domain.tld | | (Final destination) | -| Body: 500KB | | | -+--|---------------------+ +------------------^--+ - | | ----v---------------------|<~~~~~~~~~~>|-------------------|--- -srv-1.a.domain.tld | 225Km Call | srv-1.d.domain.tld --------------------------|<~~~~~~~~~~>|----------------------- -relay to: | 5 min | -srv-1.d.domain.tld | 500KB | -</screen> - - <para> - The elapsed time in a server-to-server conversation is - directly related to the amount of data that need to be moved - from one server to another and the baud rate of the connection - established between the two Modem devices. In a direct - telephone call configuration, telephone calls could result to - be less expensive than those in bridged configurations where - server computers may accumulate traffic from other server - computers in the path. The accumulation of traffic between - server computers increases the amount of time the last server - computer in the path before the final destination needs, in - order to transmit everything to the final destination. In a - bridged telephone call configuration, server computers acting - as bridges do act as servers as well and produce their own - traffic which is added to that one already accumulated in - them from other server computers. This may provoke a heugh - traffic in a server-to-server conversation (remarkably on the - last destination before the final destination), that could be - potentially increased with each new server computer added to - the string of server computers acting as bridges one another. - </para> - - </sect2> - - <sect2 id="connectivity-ppp-policy-auth"> - <title>About Authenticating PPP Users</title> - - <para> - The client computers will need to authenticate against the - server computer each time they intend to establish a PPP - connection. The username and password required by client - computers will be public and will be rarely changed. - </para> - - <example id="connectivity-ppp-policy-auth.fig-1"> - <title>Credentials for PPP authentication</title> - <screenshot> - <screeninfo>Credentials for PPP authentication</screeninfo> - <mediaobject> - <textobject> -<screen> - ISP Name: projects.centos.org -ISP Phone: +53043515094 - Username: faith - Password: mail4u.2k10 -</screen> - </textobject> - </mediaobject> - </screenshot> - </example> - - <para> - The server computer provides only one telephone line available - (e.g., +53043515094) to receive incoming calls. This affects - directly the possibilities a client computer has to establish - connection with the server computer in an environment where - several client computers are struggling among themselves to - establish a dial-up connection with the server computer. To - prevent this kind of issues 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 - expects to receive incoming calls from). - </para> - - </sect2> - - <sect2 id="connectivity-ppp-policy-lifetime"> - <title>About Restricting PPP Connections</title> - - <para> - The server computer restricts the lifetime of established - Modem 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 as described in <xref - linkend="connectivity-ppp-server-pppd-options" />. - </para> - - <para> - The server computer restricts the incoming calls from client - computers every night from 10:00PM to 12:00AM. Outside this - range of time, the telephone could be answered by a person, - not a computer. 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> - -<screen> -# Activate Modem to attend incoming calls. -59 21 * * * [ -f /etc/nologin.ttyACM0 ] && /bin/rm /etc/nologin.ttyACM0 -# Deactivate Modem to prevent incoming calls from being attended. -59 23 * * * [ ! -f /etc/nologin.ttyACM0 ] && /bin/touch /etc/nologin.ttyACM0 -</screen> - - </sect2> - - <sect2 id="connectivity-ppp-services"> - <title>About Providing Internet Services</title> - - <para> - The implementation of internet services which require - persistent connections (e.g., - <application>chats</application>) should not be considered as - a practical offer for PPP client computers. Instead, only - asynchronous services (e.g., - <application>e-mail</application>) should be supported for - them. This restriction is required to reduce the connection - times demanded such services. For example, consider an - environment where you establish connection with a server - computer to send/receive e-mails messages and then quickly - disconnect from it to free the telephone line so others be - able of using it. In this environment, there is no need for - you and others 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). Moreover, 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 on your mailbox 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> - - <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 - connected to the same network the server computer is connected - to. 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, an established connection must exist first - 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, nor receive any response from them. - </para> - - </sect2> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/overview.docbook deleted file mode 100644 index de2356f..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/overview.docbook +++ /dev/null @@ -1,55 +0,0 @@ -<sect1 id="connectivity-ppp-overview"> - - <title>Overview</title> - - <para> - This chapter describes how you can use the Point-to-Point - Protocol (PPP) to create collaborative networks in situations - where the telephone network is the only medium you and your - friends have access to. With PPP you can prepare a server - computer to provide internet services for client computers - that use the telephone network as medium for data transmition. - The configuration described here can be thought as one client - computer that establishes connection to a server computer in - order to use the internet services it provides, however, based - on this concept, other configuration are also possible to - satisfy situations where more than two computers need to be - involved. - </para> - - <para> - The operating system used by both server and client computers - will be &TCD; release 5.5<footnote> - <para> - Thank to my friend Manual Chavez Manzano (Manny) for - finding a way to download this release of &TCD; and bring - it to me as a gift when I was completly isolated from - Internet without any possibility of downloading it by - myself. - </para> - </footnote>. The configuration described in this book doesn't - use third party software. All the software needed in this - configuration is available inside &TCD;. In case you are - using a different operating system in your client computer, - you'll need to look the appropriate application your operating - system provides to establish PPP connections and configure it - to establish connection with the server computer described in - <xref linkend="connectivity-ppp-server" />. Generally, the - most you need to establish connection with the server computer - is a telephone number and the credentials for authentication, - if any. - </para> - - <para> - In this chapter you'll find how to configure your client - computer to dial-up the server computer automatically when - client applications (e.g., e-mail clients, web browsers, etc.) - request data transmition for the server computer at a moment - where no connection has been established with it, yet. Also, - this chapter covers different considerations you could take - into account to keep the telephone line as free as possible, - so different client computers be able of establishing - connection to the same server computer as quickly as possible. - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/policy.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/policy.docbook deleted file mode 100644 index 5bcef6c..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/policy.docbook +++ /dev/null @@ -1,5 +0,0 @@ -<sect1 id="connectivity-ppp-policy"> - - <title>Usage Convenctions</title> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/server.docbook b/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/server.docbook deleted file mode 100644 index 57160e0..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Connectivity/Ppp/server.docbook +++ /dev/null @@ -1,288 +0,0 @@ -<sect1 id="connectivity-ppp-server"> - - <title>The Server Computer</title> - - <para> - When you are configuring the server computer, you need to - install and configure both <application>mgetty</application> - and <application>pppd</application> programs. The - <application>mgetty</application> program lets you attend - incoming calls and must be configured to run through - <systemitem class="daemon">init</systemitem> daemon in order - to take control over the Modem device. By default, inside - &TCD; (release 5.5), <application>mgetty</application> isn't - configured to start with <systemitem - class="daemon">init</systemitem> daemon so you need to do it - yourself (see <xref - linkend="connectivity-ppp-server-mgetty-inittab" />). - Later, for attending connection requests, you need to - configure <application>mgetty</application> to use the - <application>pppd</application> program, so the Point-to-Point - Protocol (PPP) can be talked and IP packages can be exchange - between the client computer and the server computer. Later, - you need to configure <application>pppd</application> to - adjust it to your needs (see <xref - linkend="connectivity-ppp-server-pppd-options" />). Once - you've configured both <application>mgetty</application> and - <application>pppd</application> programs, the server computer - should be ready to attend incoming calls. - </para> - - <sect2 id="connectivity-ppp-server-mgetty"> - <title><package>mgetty</package></title> - <para> - Taken from <command>mgetty</command> man page: — Mgetty - is a <quote>smart</quote> getty replacement, designed to be - used with hayes compatible data and data/fax modems. Mgetty - knows about modem initialization, manual modem answering (so - your modem doesn’t answer if the machine isn’t ready), UUCP - locking (so you can use the same device for dial-in and - dial-out). Mgetty provides very extensive logging facilities - —. - </para> - <para> - Before using the configuration provided here, it would be - useful for you to read the documentation provided in the - <package>mgetty</package> and <package>SysVinit</package> - packages. This will let you to understand what you are - configuring. - </para> - - <sect3 id="connectivity-ppp-server-mgetty-inittab"> - <title><filename>/etc/inittab</filename></title> -<screen> -# Run mgetty to control a Multi-Tech (MT5634ZBA-USB) modem attached to -# `/dev/ttyAMC0' device. Incoming calls will be attended without fax -# initalization. -ACM0:2345:respawn:/sbin/mgetty -D ttyACM0 -</screen> - </sect3> - - <sect3 id="connectivity-ppp-server-mgetty-login"> - <title><filename>/etc/mgetty+sendfax/login.config</filename></title> -<screen> -# Automatic PPP startup on receipt of LCP configure request (AutoPPP). -# mgetty has to be compiled with "-DAUTO_PPP" for this to work. -# Warning: Case is significant, AUTOPPP or autoppp won't work! -# Consult the "pppd" man page to find pppd options that work for you. -# -# NOTE: for *some* users, the "-detach" option has been necessary, -# for others, not at all. If your pppd doesn't die after hangup, try -# it. -# -# NOTE2: "debug" creates lots of debugging info. LOOK AT IT if -# things do not work out of the box, most likely it's a ppp problem! -# -# NOTE3: "man pppd" is your friend! -# -# NOTE4: max. 9 arguments allowed. -# -#/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug -/AutoPPP/ - a_ppp /usr/sbin/pppd 192.168.1.1:192.168.1.2 -</screen> - - <para> - In this configuration, we set both local and remote IP - addresses to fix the IP information used by computers once the - PPP connection has been established. All other options are - taken from the <filename>options</filename> file (see <xref - linkend="connectivity-ppp-server-pppd-options" />). If we - don't specify both local and remote IP addresses when pppd is - initialized, pppd will try to take such information from the - first Modem device you configured (e.g., ppp0) and will expect - the remote peer to provide its IP address. This situation can - introduce some contraditions (e.g., the local and remote - address may be on a different network.) that would make the - connection to fail. - </para> - - <para> - Another issue we might face out would be the netmask - specification of the poin-to-point network established between - the two computers. Inside the pppd-2.4.4 man page there is no - reference to the <option>netmask</option> option, however, - there is a mention to it on the sample files installed with it - which is quiet confussing. It seems to be required that one of - the two computers establishing connection defines the netmask - information of the network they are creating. So, to do it on - the server computer (the one receiving calls), it is needed to - set the netmask definition in the Modem device configuration - file of it (<xref linkend="connectivity-ppp-modem-config" - />) along with the local IP address. Otherwise, even local and - remote IP addresses be specified through the pppd, the - connection will end up having the 255.255.255.255 netmask - which would let you ping the computer on the other end but - that will not last too long before it fails and iptables seems - to get very confused about it. - </para> - - <para> - Since we are already using <systemitem - class="daemon">pppd</systemitem> to attend login requests, - there is no need to invoke the - <application>login</application> program. So, comment the - related line as described below. - </para> - -<screen> -#* - - /bin/login @ -</screen> - - </sect3> - - <sect3 id="connectivity-ppp-server-mgetty-dialin"> - <title><filename>/etc/mgetty+sendfax/dialin.config</filename></title> - <para> - I didn't touch this file, but you might need to. - </para> - </sect3> - - <sect3 id="connectivity-ppp-server-mgetty-config"> - <title><filename>/etc/mgetty+sendfax/mgetty.config</filename></title> - <para> - I didn't touch this file, but you might need to. - </para> - </sect3> - - </sect2> - - <sect2 id="connectivity-ppp-server-pppd"> - <title><package>pppd</package></title> - <para> - Taken from pppd man page: — PPP is the protocol used for - establishing internet links over dial-up modems, DSL - connections, and many other types of point-to-point links. - The pppd daemon works together with the kernel PPP driver to - establish and maintain a PPP link with another system (called - the peer) and to negotiate Internet Protocol (IP) addresses - for each end of the link. Pppd can also authenticate the peer - and/or supply authentication information to the peer. PPP can - be used with other network protocols besides IP, but such use - is becoming increasingly rare —. - </para> - - <para> - Before using the configuration provided here, it would be - useful for you to read the documentation provided in the - <package>ppp</package> package. This will let you to - understand what you are configuring. - </para> - - <sect3 id="connectivity-ppp-server-pppd-options"> - <title><filename>/etc/pppd/options</filename></title> -<screen> -# Enables connection debugging facilities. If this option is given, -# pppd will log the contents of all control packets sent or received -# in a readable form. The packets are logged through syslog with -# facility daemon and level debug. This information can be directed -# to a file by setting up /etc/syslog.conf appropriately (see -# syslog.conf(5)). -debug - -# Require the peer to authenticate itself before allowing network -# packets to be sent or received. This option is the default if the -# system has a default route. If neither this option nor the noauth -# option is specified, pppd will only allow the peer to use IP -# addresses to which the system does not already have a route. -auth - -# Specifies that pppd should create a UUCP-style lock file for the -# serial device to ensure exclusive access to the device. By default, -# pppd will not create a lock file. -lock - -# Specify which DNS Servers the incoming Win95 or WinNT Connection -# should use Two Servers can be remotely configured. -ms-dns 192.168.1.1 - -# 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 - -# Specifies that pppd should disconnect if the link have been active -# for n seconds. -maxconnect 900 - -# Disable the IPXCP and IPX protocols. -noipx -</screen> - </sect3> - - <sect3 id="connectivity-ppp-server-pppd-cha"> - <title><filename>/etc/pppd/cha-secrets</filename></title> -<screen> -# Secrets for authentication using CHAP -# 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. By default, there is one line to -# verify client's identity with authenticating it and one line to let -# the server computer to authenticate itself with the client computer -# in case the client computer requires so. All client computers will -# be authenticated through the `faith' user. However, it is possible -# to provide anonymous authentication to client computers by using an -# empty client identity (as explained in pppd's man page) in order to -# restrict the IP address they can use. -# -"faith" "projects" "mail4u.2k10" "192.168.1.2" -#"" "projects" "" "192.168.1.2" -"projects" * "mail4u.2k10" -</screen> - - <para> - Assuming the hostname of the server computer is - <quote>projects</quote>, when a client computer uses the faith - username to login on it, the <systemitem - class="ipaddress">192.168.1.2</systemitem> IP address will be - assigned to that client computer after a successful - authentication. This configuration is just for one Modem - device attached to the server computer. In case you have more - than one Modem device attached to the server computer, it - would be necessary to add one username for each Modem device - you have, in order to permit the client computers to connect - simultaneously. It is not possible to have two or more - computers with the same IP address in the same network. - </para> - - </sect3> - - <sect3 id="connectivity-ppp-server-pppd-pap"> - <title><filename>/etc/pppd/pap-secrets</filename></title> - <para> - This file contains the same information of - <filename>cha-secrets</filename> file does. See <xref - linkend="connectivity-ppp-server-pppd-cha" />. - </para> - </sect3> - - </sect2> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Licenses.docbook b/Documentation/Models/Docbook/Tcpi-ug/Licenses.docbook deleted file mode 100755 index bcb5cec..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Licenses.docbook +++ /dev/null @@ -1,7 +0,0 @@ -<part id="licenses"> - - <title>Licenses</title> - - &licenses-gfdl; - -</part> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Licenses.ent b/Documentation/Models/Docbook/Tcpi-ug/Licenses.ent deleted file mode 100755 index dd7f27a..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Licenses.ent +++ /dev/null @@ -1,2 +0,0 @@ -<!ENTITY licenses SYSTEM "Licenses.docbook"> -<!ENTITY licenses-gfdl SYSTEM "Licenses/gfdl.docbook"> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Licenses/gfdl.docbook b/Documentation/Models/Docbook/Tcpi-ug/Licenses/gfdl.docbook deleted file mode 100755 index 33f6e8c..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/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/Documentation/Models/Docbook/Tcpi-ug/Preface.docbook b/Documentation/Models/Docbook/Tcpi-ug/Preface.docbook deleted file mode 100755 index 3291a2b..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Preface.docbook +++ /dev/null @@ -1,69 +0,0 @@ -<preface id="preface"> - - <title>Preface</title> - - <para> - Welcome to &TCPIUG;. - </para> - - <para> - This book describes how you can configure &TCD; to use the - telephone network as physical medium for data transmission - using computers, so you can create your own collaborative - networks to share information with your friends in freedom. - </para> - - <para> - To implement the configuration described in this book, you - need two or more computers connected to the telephone network - of your country by mean of modem devices. Optionally, you - could use Ethernet devices (e.g., switches) to create local - area networks (LANs) on both ends of each connection - established over the telephone network for sharing information - between them. For example, consider an infrastructure where - you have one LAN for each province in your country and then, - each of these LANs is connected one another to share - information between them using the country's telephone - network. This infrastructure would be as expensive as - telephone calls and consume of electrical power required by - computers and communication devices would be. - </para> - - <para> - To make the information of this book managable, it has been - organized in the following parts: - </para> - - <itemizedlist> - <listitem> - <para> - <xref linkend="connectivity" /> describes how to configure - server and client computers to transfer IP packages through - the telephone network. This is the first step you need to - setup in order to use the internet services described in <xref - linkend="services" />. - </para> - </listitem> - <listitem> - <para> - <xref linkend="services" /> describes how to configure server - and client computers to exchange information using internet - services over the telephone network. Once you complete this - part of the book, your collaborative network should be ready - for production. - </para> - </listitem> - <listitem> - <para> - <xref linkend="licenses" /> describes the lincense documents - mentioned in this book so you can know what you can and cannot - do with the information provided in this book. - </para> - </listitem> - </itemizedlist> - - &preface-overview; - &preface-docconvs; - &preface-feedback; - -</preface> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Preface.ent b/Documentation/Models/Docbook/Tcpi-ug/Preface.ent deleted file mode 100755 index 263be1d..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/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/Documentation/Models/Docbook/Tcpi-ug/Preface/docconvs.docbook b/Documentation/Models/Docbook/Tcpi-ug/Preface/docconvs.docbook deleted file mode 100755 index 1c2da7b..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Preface/docconvs.docbook +++ /dev/null @@ -1,68 +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> - - <itemizedlist> - <listitem> - <para> - ... - </para> - </listitem> - </itemizedlist> - - <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/Documentation/Models/Docbook/Tcpi-ug/Preface/feedback.docbook b/Documentation/Models/Docbook/Tcpi-ug/Preface/feedback.docbook deleted file mode 100755 index c532212..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Preface/feedback.docbook +++ /dev/null @@ -1,14 +0,0 @@ -<section id="preface-feedback"> - - <title>Send In Your Feedback</title> - - <para> - If you find a bug in this manual, we would like to hear about - it. To report bugs related to this manual, send an e-mail to - the <email>docs@projects.centos.org</email> mailing list - specifying the manual name, the section where you found the - bug, why you considered it a bug and anything that help us to - identify where the problem is exactly. - </para> - -</section> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Preface/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Preface/overview.docbook deleted file mode 100755 index 027aef8..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Preface/overview.docbook +++ /dev/null @@ -1,399 +0,0 @@ -<section id="preface-overview"> - - <title>Overview</title> - - <para> - Since 1999, I've been working for cuban State as Webmaster and - lately as system administrator. On April 2009, I decided to - stop working for cuban State due the increasing feeling of - repression I experimented with the restrictions impossed by - cuban State in the information area when I tried to find an - alternative way to express myself different from what such - restrictions impossed. This environment made me find that the - cuban political system lacks of such independent alternatives - for cubans to use. I don't pretend to use this book to detail - the political system I live on, but I do want to say that the - more I got involved with the cuban political system the more - distance I felt between the most pure of myself and the - actions the system expected from me to do as system - administrator, and what could be an alternative way for cubans - inside the island that, like me, feel the same need of - independent expression. - </para> - - <para> - Everything in the human life is directly related to - information. Our actions are based on the information we have. - The information is the base of education and evolution. It is - the only way we can know how to do the right thing for us and - others. I beleive that, in order to provide a good education, - the universal information must be accessable to everyone in a - transparent way, based on facts and without any manipulation - (i.e., in way others can reproduce or verify what the - information refers to). That kind of information is good - information to based our lives on. However, there are also bad - information that we need to differentiate from good - information using our own conscience, not that one from - others. I like the idea of structuring my life over pragmatic - fatcs that I can verify together with a deep faith on what I - am that help me to persist along the duty. The pragmatic fatcs - provides the steps of the stair of my life and the faith, the - force my body needs to climb up the stair. - </para> - - <para> - The years I worked for cuban State coincided with those years - I began to realized myself about the steps of my stair and the - faith on my movements. Lot of contradictions have been - appearing in front of me since then, but a magical thing - inside me (conscience) always tell me not to abandon the must - pure of my self and keep going with this travel I'm still - walking on; even when moving up one step in the stair feels - like rasping the skin of my body against a rough wall. I know - it will heal, but it hurts when happens. The only way to - support the pain is to have faith on the rightness of your - actions. That's the price of don't loosing oneself when - walking over pragmatic facts in a confussed and unarmed - society. That's the price of showing out that truth is inside - us, not outside us. It is the way of showing the truth is in - the one's faith, no matter what it be, but in feeling it - somehow, specially when it comes from understanding what we - are and the immense gift it is to have conscience of our - univeral existence as part of that unknown nature we, as - living humans, cannot ever have conscience of. - </para> - - <para> - I've experimented faith in free software and the philosophy - behind it by mean of &TCP;, but no possible way to manifest it - independently from cuban State. The cuban State controls all - the communication media and very few possibilities are - available for cubans to build up independent collaborative - networks using computers inside the island for sharing - information apart from cuban State restrictions and - conditions. One of these possibilities is the telepohne - network the cuban State provides, which has national scope. - Generally, cubans use the telephone network to talk among - themselves, but it is also possible to use this network to - transmit information that cannot be communicated using the - regular method of human talking. It is possible to attach - computers to the telephone network the cuban State provides to - transmit whatever information a computer can produce (e.g., - images, documents, programs, etc.) from one location in the - island to another and encrypting the information traveling - along the wire to garantee its privacy (e.g., the source - computer protects the information in a way that only the - target computer is able to unprotect. If the information is - intercepted by a computer located in the transmission middle, - it would be useless for that computer since only the target - can use it once it has been unprotected). We'll see more about - this later. - </para> - - <para> - In these last years (2009-2011), the cuban State has shown - signs to start using free software with the idea of - <quote>reaching a technological independency</quote> which is - quiet contradictory to me. What independency we are talking - about here? Independency for whom, and from whom? Based on - the meaning of the word, independency is the lack of any - dependency, so the only way I see the cuban State will be able - to reach such technological independency would be creating and - maintaining an entire technological infrastructure (e.g., - computers, communication devices, operating systems written - from scratch, etc.) inside its political boundaries without - any intervention from the outside world. Otherwise, the cuban - State would be inevitably dependent from someone else that can - differ at some point of the production string and that would - be something unacceptable, because it would compromise the - idea the cuban State had about independency in first place - (i.e., no dependency). - </para> - - <para> - If the vision described above about what the cuban State tries - to mean by <quote>reaching a technological - independency</quote> sounds appropriate to you, the cuban - State is misunderstanding or trying to distort the real - meaning of free software and the philosophy behind it. The - free software is built from people and dedicated to people who - might be in need of it, with the hope of being useful and - garantee the freedom of computer users paying or not a - monetary price for it. The cuban State, on the other hand, - introduces free software at convenience because there are - entire operating systems free of charge which the cuban State - can study and change as needed, not in the sense of - guaranteeing the freedom it provides to people, but as a way - to control what software does cubans use and the way they do - that. It is another impositions cubans should comply with, no - matter what they think about it.<footnote> - <para> - When I was working in the health sector of cuban State - (2003-2007), my superior told me once that I couldn't keep - using &TCD; on servers any longer, because system - administrators at central level stopped using Red Hat - related distribution and started to use Debian. I don't - want to enter in a debate why one or another distribution, - that's not the point. But I do want to mention that this - decision shouldn't be taken from one day to another - without any consideration about all the time people spent - studying (and working for) one specific GNU/Linux - distribution. My opinion was rejected and they kept - themselves showing me that it was a matter of politics one - should follow, no matter what one thought about it. I - couldn't accept that and fired up myself from that - institution. I cannot change from one operating system to - another just because someone else wants to. - </para> - </footnote> Some people might think that there is no problem - in that because it is free software anyway. Yes, that's true, - but think that again: Shouldn't you have the freedom to decide - what free software to use, and also what community you join - to? No one must impose you anything about which social - community you participate in, that is a decision you need to - take by yourself, not from someone else. - </para> - - <para> - The free software isn't free because of its name, but the - legal, social, economical and political environment it is used - in. If licenses used by software producers to release their - works (either freely or privatively) aren't protected somehow - in that environment, software producers wont be motivated to - create any software at all (either free or privative). - Consider what is happening in Cuba with Windows, the operating - system produced by Microsoft corporation: when someone install - the Windows operating system, one of the first screens in the - installation process is the License Agreement under which - Microsoft corporation releases its product. This agreement - relys on the copyright concept, a legal instrument that was - initially created to motivate authors to create more. - Likewise, the Free Software Foundation relys on the copyright - concept to distribute free software. The fact the License - Agreement of Windows operating system isn't complied in Cuba - (e.g., no cuban pays Microsoft corporation for using its - operating system) as Microsoft imposses in its License - Agreement, is a clear sign of international copyright - violation, no matter if Cuba can or cannot establish - commercial treatments with Microsoft corporation because of - the Embargo impossed by United States of America against Cuba. - It is an ethical matter cubans need to comply with in order to - help reducing the tension against both nations by showing - respect for their creators and the way they expect their - products to be distributed world-wide. Personally, I don't - use Windows operating system since 2003 when I discovered the - free software philosophy,<footnote> - <para> - I want to thank my teacher Jesús Aneiros Sosa for - intructing me in the free software philosophy and for - leading the Linux User Group (LUG) of Cienfuegos during so - many years and transmiting the feeling of freedom. - </para> - </footnote> but I am worried about the legal issues cubans - might face when developing free software. For example, will - the cuban State treat the free software license in the same - way it treats privative software licenses? If the cuban State - has no legal regulation to protect the international copyright - concept (i.e., letting authors to publish their works the way - they want to and provide the legal protections needed to - deprive people from using those creations in a way different - from that one conceived by their authors), it would be very - difficult to truly motivate people to create free software (or - anything else) in Cuba. The main problem here is that you can - write free software, but what instrument you have to protect - it from others to make your code privative and forbbid you, - this way, from using further improvements over the code you - wrote yourself. - </para> - - <para> - It is important to remember that the free software movement - was initiated by Richard Stallman in the United States of - America, based on the legal system of that country, - specifically in the copyright concept being in force. In order - to use free software, in the sense of freedom thought by - Richard Stallman, it is required that a similar underlaying - legal system in matters of copyright concepts be present in - Cuba, or an agreement be complied among all countries (e.g., - The Berna Treatment) for this matters. I've heard that Cuba - signed The Berna Treatment, however what is happening with - Windows operating system gives the impression that cuban State - is not complying with the agreement it signed on there. For - cuban society to understand what free software and the - philosophy behind it really are, it is required to force a - strong concept of copyright in the cuban legislation, even - when some authors might want to deny the cuban State from - using the work they produce or use it under conditions the - cuban State doesn't agree with. It is required to give that - legal power to cuban authors, the people who create. I wonder - if the cuban State is ready for that; and if not, why? I - really would like to know in order to find a solution. - </para> - - <para> - Free software communities are the place where free software is - produced. There are international, national and local - communities grouped under the free software philosophy. In - Cuba, because all the communication media are controlled by - the cuban State and conceived to its own benefit, it is - difficult for anyone differing from cuban State to have access - to communication media where the free software communities - live in. I strongly beleive that for the free software - philosophy to touch the heart of cubans, all free software - communities must be accessable to cubans. However, while the - cuban State keeps itself being inbetween, controlling how the - cubans can or cannot integrate any specific way of living, - there will not be free software in Cuba, nor any freedom for - cubans to make use of. - </para> - - <para> - Another frequent topic mentioned by the cuban State - information media is the migration from privative software to - free software. The migration from privative software to free - software must be initiated from people's deepest comprehension - of what they are doing, not from impositions of another - inquestionable order everybody needs to comply with. So, - cubans need to feel what freedom is and express it in order to - perceive a deep impact of free software in cuban society. We - cannot pretend that cubans will use free software based on a - lie or a distorted idea about the freedom it provides, an idea - like that wont last much before it falls itself into pieces. - People need a way of identifying themselves apart from any - social or political system in order for them to be able of - decide whether or not to be part of one. - </para> - - <para> - It is impossible to truly defend freedom if one doesn't have - felt what it is. The cuban State never talks (at least - officially) about introducing free software for freeing the - cuban society from privative software. In fact, if you compare - the privative software and the way cuban State restricts the - information management,<footnote> - <para> - See resolution 129 emitted by cuban Ministerium of - Informatics and Telecommunications (MIT). - </para> - </footnote> you may find them very similar. The resolutions - emitted by cuban State are specific to statal instituions that - use computers to share information. I don't know of any legal - estipulation about using information and communication - technologies by nautural people outside the statal sector and, - spite of it, I've heard of cubans that has been called by the - cuban State security departament to explain why they built a - computer network in the neighbourhood to share information - (isn't that obvious) and finally they were intimidated to stop - doing so. There isn't a legal instrument in either direction - that one can use as pattern to act legally. The cuban State - has all the legal power to condemn you as cuban, but you are - completly unarmed against it. If the cuban State really wants - to be democratic, it needs to give to cubans the arms they - need to fight against it without fear of being defeated. - Indeed, there would be no defeating at all, but evolution into - new political states based on cubans needs. It is the majority - of cubans who should define how The Cuban Tree evolves, not a - few minority that opresses the unarmed masses. - </para> - - <para> - Internet access is another obscured issue inside Cuba. Around - 2008, Cuba and Venezuela signed up an agreement to connect - both nation with a trasatlantic fiber optic cable for high - speed Internet access. In 2011 the cuban State announced the - arrival of such cable to cuban national territory, but nothing - more has been mentioned since then. There is a terrible - silence about it that make people woundering what happend with - that millionary invertion. Some people ask themselves why to - spend so much money on that if cubans cannot make use of it - and others prefer to think that the entire project failed. It - is difficult to know what happend exactly because, again, - there isn't any alternative way of communication but those - provided and controlled by the cuban State. The fact is that, - at present time (2011), there isn't a legal way for cubans to - contract an Internet service at home, nor even a viable way to - acquire a fixed telephone line at home either.<footnote> - <para> - I know of people that have requested a fixed telephone - line for their home and more than three years have passed - and they haven't the line yet. It is also known by - everyone that others don't even have to make any request - to have a fixed telephone line at home. - </para></footnote> However, the same isn't true for extrangers - coming from other countries who are visiting Cuba or staying - inhere as residents. The cuban State permits these persons to - access Internet paying a service in offices called Telepuntos - or from home using different fees. Some cubans cannot - understand this, nor the logic behind it either. Have cubans - to change their nationality in order to have Internt access - from their homes in Cuba? - </para> - - <para> - In Cuba there is only one telecommunication corporation named - ETECSA. This organization gives the impresion of being very - tied to cuban State and controlling everything related to - telephone networks and dedicated links for data transmistion - in the island.<footnote> - <para> - I heard of a case where someone tried to establish an - independent connection from Cuba to another country using - the air as phisical medium for data trasmission and that - person is pressently suffering years in a cuban prison - because the cuban State considered such action as illegal - actions. At this moment I haven't more information about - this case. It is very difficult to be accurate about such - things without an alternative information medium, apart - from those under cuban State control. - </para> - </footnote> Based on the fact that cuban telephone network is - the only communication medium most cubans have direct access - to, my attention is centered on it as phisical medium for - exchanging information using computers. It is important to - remark that, when using the telephone network as medium for - data transmission, there are limitations in the number of - simultaneous connections it is possible to phisically - establish between computers, it could be difficult to obtain - the Modem devices inside the island, and it could be too much - expencive to make international calls in order to exchange - information with public services available on different - networks outside Cuba's political boundaries. Besides all - these restrictions, the cuban telephone network has a national - scope that can be efficiently used by cubans inside the island - to share information using computers at a monetary cost of - national telephone calls and the electrical power consumed by - computers and communication devices (e.g., modems and - switches). - </para> - - <para> - I beleive that most of problems the cubans presently have are - caused by a lack of information we need to face in order to - understand what we are and where we are going to, in the sense - of an interdependent human being's society. To face the - information problem, it is needed to make available - independent ways for cubans to express themselves in freedom - and provide, this way, the base arguments needed to edificate - the solutions of those problems we face today. That's my goal - with this work: educating myself in the compromise of - providing an independent space for cubans to discuss and - coordinate how to create collaborative networks using the - cuban telephone network<footnote> - <para> - Considering that I and most cubans haven't access to - dedicated links or real IP addresses for data transmission - at present time. - </para> - </footnote> as phisical medium to transmit information using - computers in freedom. - </para> - - <para> - The motivation for this work was taken from the free software - philosophy exposed by Richard Stallman in his book - <citetitle>Free Sofware Free Society</citetitle> and my - personal experience from 2003 to 2009 as active member inside - &TCP; international community. - </para> - -</section> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services.docbook deleted file mode 100644 index 014d921..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services.docbook +++ /dev/null @@ -1,10 +0,0 @@ -<part id="services"> - - <title>Services</title> - - &services-dns; - &services-mail; - &services-http; - &services-ldap; - -</part> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services.ent b/Documentation/Models/Docbook/Tcpi-ug/Services.ent deleted file mode 100644 index b76c2c0..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services.ent +++ /dev/null @@ -1,13 +0,0 @@ -<!ENTITY services SYSTEM "Services.docbook"> -<!ENTITY services-dns SYSTEM "Services/Dns.docbook"> -<!ENTITY services-dns-overview SYSTEM "Services/Dns/overview.docbook"> -<!ENTITY services-mail SYSTEM "Services/Mail.docbook"> -<!ENTITY services-mail-overview SYSTEM "Services/Mail/overview.docbook"> -<!ENTITY services-mail-mta SYSTEM "Services/Mail/mta.docbook"> -<!ENTITY services-mail-mda SYSTEM "Services/Mail/mda.docbook"> -<!ENTITY services-mail-saslauthd SYSTEM "Services/Mail/saslauthd.docbook"> -<!ENTITY services-mail-mua SYSTEM "Services/Mail/mua.docbook"> -<!ENTITY services-http SYSTEM "Services/Http.docbook"> -<!ENTITY services-http-overview SYSTEM "Services/Http/overview.docbook"> -<!ENTITY services-ldap SYSTEM "Services/Ldap.docbook"> -<!ENTITY services-ldap-overview SYSTEM "Services/Ldap/overview.docbook"> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Dns.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Dns.docbook deleted file mode 100644 index 78dd877..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Dns.docbook +++ /dev/null @@ -1,11 +0,0 @@ -<chapter id="services-dns"> - - <title>Domain Name Service</title> - - <para> - ... - </para> - - &services-dns-overview; - -</chapter> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Dns/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Dns/overview.docbook deleted file mode 100644 index 2f57c37..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Dns/overview.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="services-dns-overview"> - - <title>Overview</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Http.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Http.docbook deleted file mode 100644 index ce85a8b..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Http.docbook +++ /dev/null @@ -1,11 +0,0 @@ -<chapter id="services-http"> - - <title>Web Service</title> - - <para> - ... - </para> - - &services-http-overview; - -</chapter> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Http/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Http/overview.docbook deleted file mode 100644 index 00335b6..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Http/overview.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="services-http-overview"> - - <title>Overview</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap.docbook deleted file mode 100644 index eba7579..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap.docbook +++ /dev/null @@ -1,11 +0,0 @@ -<chapter id="services-ldap"> - - <title>Directory Service</title> - - <para> - ... - </para> - - &services-ldap-overview; - -</chapter> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap/overview.docbook deleted file mode 100644 index f2af74e..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Ldap/overview.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="services-ldap-overview"> - - <title>Overview</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail.docbook deleted file mode 100644 index 04a47d2..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail.docbook +++ /dev/null @@ -1,10 +0,0 @@ -<chapter id="services-mail"> - - <title>Mail Service</title> - - &services-mail-overview; - &services-mail-mta; - &services-mail-mda; - &services-mail-mua; - -</chapter> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mda.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mda.docbook deleted file mode 100644 index 4b8971f..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mda.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="service-mail-mda"> - - <title>Mail Delivery Agent</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mta.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mta.docbook deleted file mode 100644 index eeabea3..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mta.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="service-mail-mta"> - - <title>Mail Transfer Agent</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mua.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mua.docbook deleted file mode 100644 index 319d167..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/mua.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="service-mail-mua"> - - <title>Mail User Agent</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/overview.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/overview.docbook deleted file mode 100644 index b9693a6..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/overview.docbook +++ /dev/null @@ -1,58 +0,0 @@ -<sect1 id="services-mail-overview"> - - <title>Overview</title> - - <para> - The mail service provides the software required to let you - send/receive mail messages to/from others. The mail service is - supported by three basic components: the Mail Transfer Agent - (MTA), the Mail Delivery Agent (MDA) and the Mail User Agent - (MUA). 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 lets you access your mailbox). The saslauthd daemon is - used by the MDA to authenticate user's credentials (e.g., the - information required to grant access to an specific mailbox) - and in some cases by the MTA to authenticate users before - sending mail to it. The MTA will listen on all network - interfaces it is attached to and will receive mail sent to - specific users inside specific domain names. - </para> - - <para> - Inside &TCD; there is support for different MTAs (e.g., - Sendmail, Postfix and Exim). By default, the - <application>Sendmail</application> program is used as mail - transfer agent, however, we want to use Postfix for our - configuration. This way, to use Postfix as default mail - transfer agent and not Sendmail, it is required to use the - <command>alternatives</command> command. This command will - present you a menu to chose between available mail transfer - agents installed in the system, so you can choose Posfix as - default option. Now that you've made Postfix the default mail - transfer agent, you can saftly remove the sendmail package to - avoid unused software to remain inside the computer. - </para> - - <para> - Inside &TCD; there is support for different MDA (e.g., Cyrus - IMPA and Dovecot). By default, the Dovecot program is used as - mail delivery agent (which doesn't require any intermediate - daemon for athentication), however, we want to use Cyrus IMAP - for our configuration (which does require an intermediate - daemon called saslauthd for authentication). - </para> - - <para> - Inside &TCD; there is support for different MUA (e.g., - Evolution, Thunderbird and Mutt). By default, the Evolution - program is used and we stay with it :). - </para> - - <para> - In this chapter we describe how to configure each one of these - components to let you send/receive e-mails to/from your - friends. - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/saslauthd.docbook b/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/saslauthd.docbook deleted file mode 100644 index 4211a1b..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/Services/Mail/saslauthd.docbook +++ /dev/null @@ -1,9 +0,0 @@ -<sect1 id="service-mail-saslauthd"> - - <title>Sasl Authentication Server</title> - - <para> - ... - </para> - -</sect1> diff --git a/Documentation/Models/Docbook/Tcpi-ug/tcpi-ug.docbook b/Documentation/Models/Docbook/Tcpi-ug/tcpi-ug.docbook deleted file mode 100755 index a677227..0000000 --- a/Documentation/Models/Docbook/Tcpi-ug/tcpi-ug.docbook +++ /dev/null @@ -1,80 +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 % Connectivity.ent SYSTEM "Connectivity.ent"> -<!ENTITY % Services.ent SYSTEM "Services.ent"> -<!ENTITY % Licenses.ent SYSTEM "Licenses.ent"> - -%Commons.ent; -%Preface.ent; -%Connectivity.ent; -%Services.ent; -%Licenses.ent; -]> - -<book lang="en_US"> - - <!-- Front matter --> - <title>The CentOS Project Infrastructure</title> - <subtitle>User's Guide</subtitle> - - <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 --> - &connectivity; - &services; - - <!-- Back matter --> - &licenses; - -</book>