PLD-Guide concept.xml,1.4,1.5, cvs.xml,1.4,1.5, developer.xml,1.2,1.3, welcome.xml,1.3,1.4

[Rafał Kleger-Rudomin]

Module name:    PLD-Guide
Changes by:     klakier

Changed RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/concept.xml,v
----------------------------
revision 1.5
date: 2002/06/02 20:58:12;  author: klakier;  state: Exp;  lines: +48 -70
- minor and major corrections of text
 

Index: concept.xml
===================================================================
RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/concept.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- concept.xml	2 May 2002 08:56:00 -0000	1.4
+++ concept.xml	2 Jun 2002 20:58:12 -0000	1.5
@@ -7,7 +7,7 @@
 			mainly in Poland.
 			It is a product of bevy of Linux enthusiasts. We have
 			around 200 people expressing their interests in 
-			developing PLD, however number of actively working 
+			developing PLD, however, number of actively working 
 			developers is approximately 50.
 		</para>
 		<para>
@@ -16,38 +16,49 @@
 		<para>
 			How is PLD different from other Linux distributions?
 		</para>
-		<para>
-			In PLD one does, what one needs, or wants to do. This
-			simple fact, multiplied by number of developers
-			involved, gives good picture how does PLD look like.
-		</para>
 		<orderedlist>
 			<listitem>
 				<para>
+					Large software packages are split into 
+					functional subbpackages providing the opportunity
+					to install only those pieces of software that are really necessay.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					Packages very often come in reasonable
 					default configuration, with bunch
-					of useful patches applied -- that's
-					because packagers use packages
-					themselves very extensively
+					of useful patches applied.
 				</para>
 			</listitem>
 			<listitem>
 				<para>
 					PLD has the best IPv6 support among
-					all Linux distributions (and yes,
-					that's because some of us are using
-					it)
+					all Linux distributions.
 				</para>
 			</listitem>
 			<listitem>
 				<para>
-					In general PLD is very sysadmin
-					friendly, several choices of crucial
-					servers is one example, highly
-					modularized kernel from distribution
-					suitable for most machines is another 
-					(sysadmins with 20+ machines tends not to 
-					bother compiling kernel over and over again :^)
+					Several choices of crucial servers are available.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					System comes with highly modularized kernel suitable for most machines.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					PLD contains rc-inetd - interface for managing inetd services.
+					Packages providing inetd servers (e.g. telnetd, cvs-pserver) 
+					use this feature to automatically add particular server to inetd configuration.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Similar feature to rc-inetd is rc-boot - a system that allows
+					for easy managing of bootloaders (changing bootloader, updating
+					after kernel upgrade etc).
 				</para>
 			</listitem>
 			<listitem>
@@ -60,37 +71,18 @@
 				  standard things like two implementations of SML and 
 				  Prolog, OCaml with several utility programs and 
 				  libraries and even experimental compilers, like 
-				  Cyclone or Ksi. As with other packages they are often
-				  much better packaged then in other distribution, 
-				  especially with respect to splitting them into 
-				  subpackages
+				  Cyclone or Ksi.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Apart for plain rpm, PLD provides two specialized
+					and powerfull RPM managers: clone of Debian apt,
+					and our own poldek.
 				</para>
 			</listitem>
 		</orderedlist>
 		<para>
-			<emphasis>Some other features</emphasis>
-		</para>
-		<para>
-			It is common in PLD to simplify and cleanup things.
-			We have very strict packaging standards. However it 
-			goes far beyond that. Installing package
-			in PLD is often enough to make it work in some default
-			configuration. For example installing telnetd or 
-			cvs-pserver adds it to configuration of
-			current inetd server (this is done through rc-inetd
-			common interface to all inetd servers in PLD), 
-			installing kernel generates initrd image for
-			it (with geninitrd script), adds it to current
-			bootloader configuration (through rc-boot interface), 
-			and reinstalls bootloader.
-		</para>
-		<para>
-			PLD is fully prepared for automatic system upgrade. We
-			supply indexes for RPM's apt-get port, we also have other 
-			upgrade tool, named <emphasis>poldek</emphasis>, 
-			with similar functionality.
-		</para>
-		<para>
 			<emphasis>Common myths about PLD</emphasis>
 		</para>
 		<para>
@@ -112,33 +104,28 @@
 		</listitem>
 		<listitem>
 			<para>
-				termcap and libtermcap usage avoided (no
+				Termcap and libtermcap usage is avoided (no
 				package in PLD requires termcap any more)
 			</para>
 		</listitem>
 		<listitem>
 			<para>
-				fantastic rc-inetd package provided, which is very simple, but also much more elastic than others. (unification of inet-services management)
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				automatic system updates supported and ready, including restarting updated services, proper handling of config files, even modified ones
+				Support for automatic system upgrades, including restarting upgraded services, proper handling of config files, even modified ones
 			</para>
 		</listitem>
 		<listitem>
 			<para>
-				no packages are forced during installation (eg. MTAs and other daemons). We assume that some packages may be preferred over others, user decides on which program to use.
+				No packages are mandatory during installation (eg. MTAs and other daemons). We assume that some packages may be preferred over others, user decides which program to use.
 			</para>
 		</listitem>
 		<listitem>
 			<para>
-				iproute2 as a basic tool for network interfaces manipulation. PLD runtime scripts are simpler and shorter then, offering larger functionality compared	to RedHat. This version of initscripts can be easily localized, accordingly to the tastes of the user
+				The iproute2 tool as a basic tool for network interfaces manipulation. PLD runtime scripts are simpler and shorter then, offering larger functionality compared	to RedHat. Initscripts can be easily localized.
 			</para>
 		</listitem>
 		<listitem>
 			<para>
-				support for easy switching to alternative
+				Support for easy switching to alternative
 				authentication methods (and, if you need it,
 				ciphering) for network communication, such as
 				PAM, GASPI, TSL/SSL etc. It's quite possible
@@ -152,29 +139,20 @@
 		</listitem>
 		<listitem>
 			<para>
-				descriptions and documentation are in other 
-				languages provided and easily configured. 
-				It is mostly done "on the fly".  Everybody 
-				can configure and install chosen software 
-				with support for selected languages  only,
-				i.e. English and
-				German or English and  Polish (resources
-				linked to other languages will not be
-				installed then). We provide such feature by 
-				marking  national resources with %lang()
-				macro of RPM packages.
+				Descriptions of packages and documentation comes in many languages
+				but only choosen language versions will be installed.
 			</para>
 		</listitem>
 		<listitem>
 			<para>
-				many different frequently repeated tasks can be automatically done (with regards to current work methodology and package contents)
+				Many different frequently repeated tasks can be automatically done (with regards to current work methodology and package contents)
 			</para>
 		</listitem>
 	</orderedlist>
 	</section>
 	<section id="assumptions"><title>Assumptions</title>
 	<para>
-		There are a few assumptions which follow from package
+		There are a few assumptions that are in use during package
 		preparation procedures:
 	</para>
 	<orderedlist inheritnum="ignore" continuation="restarts">
@@ -192,7 +170,7 @@
 		<listitem>
 			<para>
 				dynamically linked libraries are stripped
-				(debug information is found in static
+				(debug information can be found in static
 				libraries only)
 			</para>
 		</listitem>

Changed RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/cvs.xml,v
----------------------------
revision 1.5
date: 2002/06/02 20:58:12;  author: klakier;  state: Exp;  lines: +8 -10
- minor and major corrections of text
 

Index: cvs.xml
===================================================================
RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/cvs.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- cvs.xml	2 May 2002 08:56:00 -0000	1.4
+++ cvs.xml	2 Jun 2002 20:58:12 -0000	1.5
@@ -7,12 +7,12 @@
     remove resources - they are only moved to other directory (to junk yard
     :-). Also every version is being kept, so you can download distribution
     in state from last month or last hour. Resources marked by STABLE flag
-    are being built by correct people with many different optimization
-    (i386, i586, i686 etc.) and you can find them as rpm packages on 
+    are built with many different optimization
+    (i386, i586, i686 etc.) and you placed as rpm packages on 
     <link linkend="ftp">FTP</link> Server.
   </para>
   <para>
-    Read-only access to repository (repo) you can establish in two
+    Read-only access to repository (repo) can be established in two
     different methods: 
   </para>
   <itemizedlist>
@@ -41,12 +41,11 @@
     Next, get the module(s) you need: 
   </para>
   <screen format="linespecific">
-    <prompt>bash$</prompt> <command>cvs -d :pserver:cvs w cvs.pld.org.pl:/cvsroot 
-          get module_name</command>
+    <prompt>bash$</prompt> <command>cvs -d :pserver:cvs w cvs.pld.org.pl:/cvsroot get module_name</command>
   </screen>
   <para>
-    All resources are grouped in modules. For now in repository
-    are among others these modules: 
+    All resources are grouped in modules. Repository contains several
+    modules, some of them are: 
   </para>
   <table>
     <title>Major modules in PLD CVS Repository</title>
@@ -102,7 +101,7 @@
     </tgroup>
   </table>
   <para>
-    There are also several other modules in PLD repo. Most of them 
+    There are also other modules in PLD repo. Most of them 
     are open source project of PLD developers, more or less connected
     with PLD itself. You can use CVSWeb to view complete list.
   </para>
@@ -110,8 +109,7 @@
     To download contents of some module you should use command: 
   </para>
   <screen format="linespecific">
-    <prompt>bash$</prompt> <command>cvs -d :pserver:cvs w cvs.pld.org.pl:/cvsroot 
-          get "module" ["module2" ...]</command><footnote><para>Specify module name without the quotes</para></footnote>
+    <prompt>bash$</prompt> <command>cvs -d :pserver:cvs w cvs.pld.org.pl:/cvsroot get "module" ["module2" ...]</command>
   </screen>
 </section>
 <!-- Keep this comment at the end of the file

Changed RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/developer.xml,v
----------------------------
revision 1.3
date: 2002/06/02 20:58:12;  author: klakier;  state: Exp;  lines: +3 -3
- minor and major corrections of text
 

Index: developer.xml
===================================================================
RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/developer.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- developer.xml	30 Apr 2002 09:40:58 -0000	1.2
+++ developer.xml	2 Jun 2002 20:58:12 -0000	1.3
@@ -1,10 +1,10 @@
 <section id="developer">
 	<title>Developing PLD</title>
 	<para>
-		Our philosophy I can shorten to one word: cooperative. 
+		Our philosophy can br shorten to one word: cooperation. 
 		We are mostly sysadmins, which need stable and
-		simultaneously flexible distro - and there is no better way
-		to achieve it than do it by ourselves! So we maintain open
+		also flexible distro - and there is no better way
+		to achieve it than do it ourselves! So we maintain open
 		distribution, everyone is encouraged to take a part in
 		developing it.
 	</para>

Changed RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/welcome.xml,v
----------------------------
revision 1.4
date: 2002/06/02 20:58:12;  author: klakier;  state: Exp;  lines: +2 -2
- minor and major corrections of text
 

Index: welcome.xml
===================================================================
RCS file: /cvsroot/LDP/guide/docbook/PLD-Guide/welcome.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- welcome.xml	19 May 2002 12:11:35 -0000	1.3
+++ welcome.xml	2 Jun 2002 20:58:12 -0000	1.4
@@ -9,8 +9,8 @@
     Welcome to PLD Linux Distribution webpages!
   </para>
   <para>
-    PLD is the biggest RPM-based distribution in the world. If you 
-    want to share this experience of developing a distribution made 
+    PLD is big RPM-based Linux distribution. If you 
+    want to share experience of developing a distribution made 
     by over a hundred volunteers, taking part in shaping the system,
     or if you just want to use PLD -- read on.
   </para>