cvs commit: ALFS/nALFS/doc/users_guide/preface audience.xml foreword.xml prerequisites.xml

jwrober at linuxfromscratch.org jwrober at linuxfromscratch.org
Mon May 31 12:22:44 PDT 2004


jwrober     04/05/31 13:22:44

  Modified:    nALFS/doc/users_guide/book dedication.xml
               nALFS/doc/users_guide/chapter00 acknowledgements.xml
                        contactinfo.xml conventions.xml introduction.xml
               nALFS/doc/users_guide/preface audience.xml foreword.xml
                        prerequisites.xml
  Log:
  * Unused tag cleanup
  
  Revision  Changes    Path
  1.3       +1 -2      ALFS/nALFS/doc/users_guide/book/dedication.xml
  
  Index: dedication.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/book/dedication.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- dedication.xml	26 Sep 2003 20:50:34 -0000	1.2
  +++ dedication.xml	31 May 2004 19:22:43 -0000	1.3
  @@ -1,7 +1,6 @@
   <dedication role="dsssl">
   <title>Dedication</title>
   
  -<para>This book is dedicated to the <acronym>LFS</acronym> and 
  -<acronym>ALFS</acronym> communities.</para>
  +<para>This book is dedicated to the LFS and ALFS communities.</para>
   
   </dedication>
  
  
  
  1.10      +18 -18    ALFS/nALFS/doc/users_guide/chapter00/acknowledgements.xml
  
  Index: acknowledgements.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/chapter00/acknowledgements.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- acknowledgements.xml	10 Oct 2003 02:53:56 -0000	1.9
  +++ acknowledgements.xml	31 May 2004 19:22:43 -0000	1.10
  @@ -4,22 +4,23 @@
   
   <para>For an in depth look at "who did what", you can
   <filename>grep</filename> through the source code files containing the
  -program's changes. Below is just a list of people, in alphabetical order, that
  -had some involvement in the &book-product; code and/or documentation.</para>
  +program's changes. Below is just a list of people, in alphabetical order,
  +that had some involvement in the &book-product; code and/or
  +documentation.</para>
   
   <itemizedlist>
   
   <listitem><para><ulink url="mailto:mrbrown at 0xd6.org">Marcus R.
  -Brown</ulink>  <mrbrown at 0xd6.org>  &emdash;  
  -Project developer.</para></listitem>
  +Brown</ulink>  <mrbrown at 0xd6.org>  &emdash; 
  + Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:devine at cr0.net">Christophe
  -Devine</ulink>  <devine at cr0.net>  &emdash;  
  -Project developer.</para></listitem>
  +Devine</ulink>  <devine at cr0.net>  &emdash; 
  + Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:vassili at linuxfromscratch.org">Vassili
  -Dzuba</ulink>  <vassili at linuxfromscratch.org>  &emdash;
  -   Project developer.</para></listitem>
  +Dzuba</ulink>  <vassili at linuxfromscratch.org>  
  +&emdash;   Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:kpfleming at linuxfromscratch.org">Kevin P.
   Fleming</ulink>  <kpfleming at linuxfromscratch.org>  
  @@ -34,25 +35,24 @@
      &book-product; Creator, Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:pterk at datatailors.com">Peter van
  -Kampen</ulink>  <pterk at datatailors.com>  &emdash; 
  - Project developer.</para></listitem>
  +Kampen</ulink>  <pterk at datatailors.com>  &emdash;
  +  Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:jwrober at linuxfromscratch.org">James
   Robertson</ulink>  <jwrober at linuxfromscratch.org>  
   &emdash;  Documentation editor.</para></listitem>
   
   <listitem><para><ulink url="mailto:bZ at iq-computing.de">Maik
  -Schreiber</ulink>  <bZ at iq-
  -computing.de>  &emdash;  Project
  -developer.</para></listitem>
  +Schreiber</ulink>  <bZ at iq-computing.de>  &emdash;
  +  Project developer.</para></listitem>
   
   <listitem><para><ulink url="mailto:fabien.st at netcourrier.com">Fabien
  -Steinmetz</ulink>  <fabien.st at netcourrier.com>  &emdash;
  -  Project developer.</para></listitem>
  +Steinmetz</ulink>  <fabien.st at netcourrier.com>  
  +&emdash;  Project developer.</para></listitem>
   
  -<listitem><para>Countless other people on the <acronym>ALFS</acronym> mailing
  -lists who are making this project happen by giving their suggestions, testing
  -the tool and submitting bug reports.</para></listitem>
  +<listitem><para>Countless other people on the ALFS mailing lists who are
  +making this project happen by giving their suggestions, testing the tool
  +and submitting bug reports.</para></listitem>
   
   </itemizedlist>
   
  
  
  
  1.13      +23 -14    ALFS/nALFS/doc/users_guide/chapter00/contactinfo.xml
  
  Index: contactinfo.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/chapter00/contactinfo.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- contactinfo.xml	10 Oct 2003 03:06:23 -0000	1.12
  +++ contactinfo.xml	31 May 2004 19:22:43 -0000	1.13
  @@ -8,17 +8,24 @@
   <para>The &book-product; uses two mailing list hosted from the Linux From
   Scratch servers.</para>
   
  -<para>Please direct the majority of your emails to the <acronym>ALFS</acronym> mailing list at
  +<para>Please direct the majority of your emails to the ALFS mailing list at
  +
   <ulink url="mailto:alfs-discuss at linuxfromscratch.org">alfs-discuss at linuxfromscratch.org</ulink>.
  -This is an excellent place to post questions and bug reports. For complete mailing list information, refer to
  -<ulink url="&http-root;/mailman/listinfo/alfs-discuss">&http-root;/mailman/listinfo/alfs-discuss</ulink>.
  -</para>
   
  -<para>The second list is really for the development team's use and is available at
  +This is an excellent place to post questions and bug reports. For complete
  +mailing list information, refer to
  +
  +<ulink url="&http-root;/mailman/listinfo/alfs-discuss">&http-root;/mailman/listinfo/alfs-discuss</ulink>.</para>
  +
  +<para>The second list is really for the development team's use and is
  +available at
  +
   <ulink url="mailto:alfs-log at linuxfromscratch.org">alfs-log at linuxfromscratch.org</ulink>.
  -This is an excellent place to see the daily activity of the project. For complete mailing list information, refer to
  -<ulink url="&http-root;/mailman/listinfo/alfs-log">&http-root;/mailman/listinfo/alfs-log</ulink>
  -</para>
  +
  +This is an excellent place to see the daily activity of the project. For
  +complete mailing list information, refer to
  +
  +<ulink url="&http-root;/mailman/listinfo/alfs-log">&http-root;/mailman/listinfo/alfs-log</ulink>.</para>
   
   </sect2>
   
  @@ -26,8 +33,8 @@
   <title>News Server</title>
   
   <para>All the mailing lists hosted at linuxfromscratch.org are also
  -accessible via the <acronym>NNTP</acronym> server. All messages posted to a
  -mailing list will be copied to its correspondent newsgroup, and vice versa.</para>
  +accessible via the NNTP server. All messages posted to a mailing list will
  +be copied to its correspondent newsgroup, and vice versa.</para>
   
   <para>The news server can be reached at
   <ulink url="news:news.linuxfromscratch.org">news.linuxfromscratch.org</ulink>.
  @@ -53,12 +60,14 @@
   <sect2>
   <title>Other</title>
   
  -<para>The current &book-product; documentation maintainer is &book-maintainer-fullname;.
  -If you need to reach &book-maintainer-firstname;, send an email to
  +<para>The current &book-product; documentation maintainer is
  +&book-maintainer-fullname;.  If you need to reach
  +&book-maintainer-firstname;, send an email to 
   <ulink url="mailto:&book-maintainer-address;">&book-maintainer-address;</ulink>.</para>
   
  -<para>The current &book-product; source code owner is &product-maintainer-fullname;.
  -If you need to reach &product-maintainer-firstname;, send an email to
  +<para>The current &book-product; source code owner is
  +&product-maintainer-fullname;.  If you need to reach
  +&product-maintainer-firstname;, send an email to
   <ulink url="mailto:&product-maintainer-address;">&product-maintainer-address;</ulink>.</para>
   
   </sect2>
  
  
  
  1.9       +8 -8      ALFS/nALFS/doc/users_guide/chapter00/conventions.xml
  
  Index: conventions.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/chapter00/conventions.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- conventions.xml	31 May 2004 16:05:51 -0000	1.8
  +++ conventions.xml	31 May 2004 19:22:43 -0000	1.9
  @@ -7,8 +7,8 @@
   
   <screen><command>./configure --prefix=/usr</command></screen>
   
  -<blockquote><para>This form of text is designed to be typed in exactly as seen
  -unless otherwise noted in the surrounding text.</para></blockquote>
  +<blockquote><para>This form of text is designed to be typed in exactly as
  +seen unless otherwise noted in the surrounding text.</para></blockquote>
   
   <para><filename>install-info: unknown option
   `--dir-file=/mnt/lfs/usr/info/dir'</filename></para>
  @@ -26,8 +26,8 @@
   <para><ulink url="http://www.linuxfromscratch.org/alfs">http://www.linuxfromscratch.org/alfs</ulink></para>
   
   <blockquote><para>This form of text is used for hyperlinks, both within the
  -book and to external pages such as HowTo's, download locations,
  -websites, etc.</para></blockquote>
  +book and to external pages such as HowTo's, download locations, websites,
  +etc.</para></blockquote>
   
   <screen><command>cat > $LFS/etc/group << "EOF"</command>>
   	root:x:0:
  @@ -36,10 +36,10 @@
   <command>EOF</command></screen>
   
   <blockquote><para>This type of section is used mainly when creating
  -configuration files.  The first command (in bold) tells the system to create
  -the file <filename>$LFS/etc/group</filename> from whatever is typed on the
  -following lines until the sequence <acronym>EOF</acronym> is encountered.
  -Therefore, this whole section is generally typed as seen.</para></blockquote>
  +configuration files.  The first command (in bold) tells the system to
  +create the file <filename>$LFS/etc/group</filename> from whatever is typed
  +on the following lines until the sequence EOF is encountered.  Therefore,
  +this whole section is generally typed as seen.</para></blockquote>
   
   </sect1>
   
  
  
  
  1.11      +39 -36    ALFS/nALFS/doc/users_guide/chapter00/introduction.xml
  
  Index: introduction.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/chapter00/introduction.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- introduction.xml	8 Oct 2003 01:54:20 -0000	1.10
  +++ introduction.xml	31 May 2004 19:22:43 -0000	1.11
  @@ -2,34 +2,37 @@
   <?dbhtml filename="introduction.html" dir="chapter00"?>
   <title>Introduction</title>
   
  -<para><acronym>LFS</acronym> stands for Linux From Scratch and it's a project, 
  -led by <ulink url="mailto:gerard at linuxfromscratch.org">Gerard Beekmans</ulink> 
  -&emdash; <gerard at linuxfromscratch.org>, which helps you build your own 
  +<para>LFS stands for Linux From Scratch and it's a project, led by 
  +
  +<ulink url="mailto:gerard at linuxfromscratch.org">Gerard Beekmans</ulink> 
  +
  +&emdash;<gerard at linuxfromscratch.org>, which helps you build your own 
   Linux system.</para>
   
  -<para>What this means is that you will use nothing but the source code of 
  -various software packages needed for a fully functional Linux system. You will 
  -compile the packages one-by-one on your own computer. During this process, you 
  -will be able to tweak every single corner of your system, by editing a bunch 
  -of configuration files, creating your own boot scripts etc.</para>
  -
  -<para>All this might sound a bit complicated and require too much work. But 
  -even if it is, it's well worth it. One of the <acronym>LFS</acronym> project's 
  -secondary goals is education. Great care is taken in each step to explain what 
  -is occuring at each phase of the build procedure.</para>
  -
  -<para>Best of all it that it does not have to be that complicated or time 
  -consuming. With only a few keystrokes and the right software, you can just sit 
  -back and relax, while your system is being built &emdash; from scratch. This 
  -is where the <acronym>ALFS</acronym> project comes into play.</para>
  -
  -<para><acronym>ALFS</acronym> stands for Automated Linux From Scratch, and its 
  -aim is to provide a much simpler method for building a Linux system.</para>
  -
  -<para><acronym>ALFS</acronym> uses profiles (simple <acronym>XML</acronym> 
  -files) which describe what actions are to be taken and what commands executed. 
  -Feeding the program (like &book-product;) with those profiles, will make the 
  -program act upon them.</para>
  +<para>What this means is that you will use nothing but the source code of
  +various software packages needed for a fully functional Linux system. You
  +will compile the packages one-by-one on your own computer. During this
  +process, you will be able to tweak every single corner of your system, by
  +editing a bunch of configuration files, creating your own boot scripts
  +etc.</para>
  +
  +<para>All this might sound a bit complicated and require too much work. But
  +even if it is, it's well worth it. One of the LFS project's secondary goals
  +is education. Great care is taken in each step to explain what is occuring
  +at each phase of the build procedure.</para>
  +
  +<para>Best of all it that it does not have to be that complicated or time
  +consuming. With only a few keystrokes and the right software, you can just
  +sit back and relax, while your system is being built &emdash; from scratch.
  +This is where the ALFS project comes into play.</para>
  +
  +<para>ALFS stands for Automated Linux From Scratch, and its aim is to
  +provide a much simpler method for building a Linux system.</para>
  +
  +<para>ALFS uses profiles (simple XML files) which describe what actions are
  +to be taken and what commands executed.  Feeding the program (like
  +&book-product;) with those profiles, will make the program act upon
  +them.</para>
   
   <para>For example, if you want to create a directory, all you have to do is
   to put:</para>
  @@ -38,16 +41,16 @@
   	<name>/some/directory</name>
   </mkdir></command></screen>
   
  -<para>in the profile and leave the rest to the program. Of course, you are not 
  -limited to just compiling packages for <acronym>LFS</acronym>. You can do just 
  -about anything. All it takes is a little time to write a profile for it.</para>
  -
  -<para>This might seem very similar to ordinary shell scripting, but it has 
  -also a lot of advantages. With this approach &book-product; (after reading any 
  -properly formatted profile) can be instructed to pause execution, start 
  -execution from a selected element (by browsing a profile in a tree-like mode), 
  -enter special environments like <filename>chroot</filename>, and much much 
  -more.</para>
  +<para>in the profile and leave the rest to the program. Of course, you are
  +not limited to just compiling packages for LFS. You can do just about
  +anything. All it takes is a little time to write a profile for it.</para>
  +
  +<para>This might seem very similar to ordinary shell scripting, but it has
  +also a lot of advantages. With this approach &book-product; (after reading
  +any properly formatted profile) can be instructed to pause execution, start
  +execution from a selected element (by browsing a profile in a tree-like
  +mode), enter special environments like <filename>chroot</filename>, and
  +much much more.</para>
   
   </sect1>
   
  
  
  
  1.7       +6 -6      ALFS/nALFS/doc/users_guide/preface/audience.xml
  
  Index: audience.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/preface/audience.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- audience.xml	8 Oct 2003 02:25:20 -0000	1.6
  +++ audience.xml	31 May 2004 19:22:43 -0000	1.7
  @@ -3,12 +3,12 @@
   <title>Who Would Want To Read This Book</title>
   
   <para>This is the user's guide for &book-product; v&nalfs-version;. If you
  -have &book-product; installed on your computer and want to know how to use it,
  -then you have found the right place. &book-product; is a tool to automate the
  -build procedure for the <acronym>LFS</acronym> book. It can also be used to
  -automate software package installation steps or any other administrative task
  -you can think of. The <acronym>ALFS</acronym> <acronym>DTD</acronym> has many
  -features available for use inside the tool.</para>
  +have &book-product; installed on your computer and want to know how to use
  +it, then you have found the right place. &book-product; is a tool to
  +automate the build procedure for the LFS book. It can also be used to
  +automate software package installation steps or any other administrative
  +task you can think of. The ALFS DTD has many features available for use
  +inside the tool.</para>
   
   </sect1>
   
  
  
  
  1.10      +14 -11    ALFS/nALFS/doc/users_guide/preface/foreword.xml
  
  Index: foreword.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/preface/foreword.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- foreword.xml	31 May 2004 16:06:08 -0000	1.9
  +++ foreword.xml	31 May 2004 19:22:43 -0000	1.10
  @@ -4,18 +4,21 @@
   <para><emphasis>From the Editor</emphasis></para>
   
   <para>Being a Systems Engineer by trade and having used Linux From Scratch
  -(<acronym>LFS</acronym>) for about a year, I was looking for a way to automate
  -tasks on my Linux servers at work. One day, while surfing the
  -<acronym>LFS</acronym> website, I found the <acronym>ALFS</acronym> project
  -and then the nALFS implementation. After trying it out, I fell in love with
  -the tool. I have been able to completely automate server builds, software
  -package installation and administrative tasks across my data center. Since I
  -like the product so much, I wanted to give back to the project and decided to
  -take on the task of documentation. I hope you like the product as much as I do
  -and it provides the same utility to your environment as it has mine.</para>
  +(LFS) for about a year, I was looking for a way to automate tasks on my
  +Linux servers at work. One day, while surfing the LFS website, I found the
  +ALFS project and then the nALFS implementation. After trying it out, I fell
  +in love with the tool. I have been able to completely automate server
  +builds, software package installation and administrative tasks across my
  +data center. Since I like the product so much, I wanted to give back to the
  +project and decided to take on the task of documentation. I hope you like
  +the product as much as I do and it provides the same utility to your
  +environment as it has mine.</para>
   
  -<blockquote><literallayout>James Robertson
  -jwrober at linuxfromscratch.org</literallayout></blockquote>
  +<blockquote><literallayout>
  +--
  +James Robertson
  +jwrober at linuxfromscratch.org
  +</literallayout></blockquote>
   
   </sect1>
   
  
  
  
  1.6       +7 -7      ALFS/nALFS/doc/users_guide/preface/prerequisites.xml
  
  Index: prerequisites.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/users_guide/preface/prerequisites.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- prerequisites.xml	10 Oct 2003 03:00:10 -0000	1.5
  +++ prerequisites.xml	31 May 2004 19:22:44 -0000	1.6
  @@ -9,7 +9,7 @@
   <title>Ncurses</title>
   
   <para>Any recent version should work. If for some reason your system does not
  -have <filename>ncurses</filename> installed, the <acronym>LFS</acronym> book
  +have <filename>ncurses</filename> installed, the LFS book
   provides an excellent installation procedure at
   <ulink url="&http-root;/lfs/view/cvs/chapter06/ncurses.html">&http-root;/lfs/view/cvs/chapter06/ncurses.html</ulink>.
   </para>
  @@ -22,7 +22,7 @@
   <para>Any version greater than v2.5.1 should work.  One primary feature you
   are looking for is support for <command>XInclude</command>. If for some reason
   your system does not have <filename>libXML2</filename> installed or
  -<command>XInclude</command> compiled in, the <acronym>BLFS</acronym> book
  +<command>XInclude</command> compiled in, the BLFS book
   provides an excellent installation procedure at
   <ulink url="&http-root;/blfs/view/cvs/general/libxml2.html">&http-root;/blfs/view/cvs/general/libxml2.html</ulink>.
   </para>
  @@ -36,7 +36,7 @@
   
   <para>Any version greater than v7.10 should work. If for some reason your
   system does not have <filename>Curl</filename> installed, the
  -<acronym>BLFS</acronym> book provides an excellent installation procedure at
  +BLFS book provides an excellent installation procedure at
   <ulink url="&http-root;/blfs/view/cvs/basicnet/curl.html">&http-root;/blfs/view/cvs/basicnet/curl.html</ulink>.
   </para>
   
  @@ -49,7 +49,7 @@
   
   <para>Any version greater than v0.9.7 should work. If for some reason your
   system does not have <filename>OpenSSL</filename> installed, the
  -<acronym>BLFS</acronym> book provides an excellent installation procedure at
  +BLFS book provides an excellent installation procedure at
   <ulink url="&http-root;/blfs/view/cvs/general/openssl.html">&http-root;/blfs/view/cvs/general/openssl.html</ulink>.
   </para>
   
  @@ -58,9 +58,9 @@
   <sect2>
   <title>Other</title>
   
  -<para>Of course, any system needs to have the following packages installed for
  -the <acronym>XML</acronym> handlers to work and to even get the package
  -installed.  Links to install procedures are provided, just in case.</para>
  +<para>Of course, any system needs to have the following packages installed
  +for the XML handlers to work and to even get the package installed.  Links
  +to install procedures are provided, just in case.</para>
   
   <itemizedlist>
   
  
  
  



More information about the alfs-log mailing list