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

jwrober at jwrober at
Mon May 31 09:06:28 PDT 2004

jwrober     04/05/31 10:06:28

  Modified:    nALFS/doc/hackers_guide/book book.ent
               nALFS/doc/hackers_guide/preface audience.xml foreword.xml
  * Update
  Revision  Changes    Path
  1.4       +3 -3      ALFS/nALFS/doc/hackers_guide/book/book.ent
  Index: book.ent
  RCS file: /home/cvsroot/ALFS/nALFS/doc/hackers_guide/book/book.ent,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- book.ent	29 May 2004 21:21:46 -0000	1.3
  +++ book.ent	31 May 2004 16:06:28 -0000	1.4
  @@ -22,9 +22,9 @@
   <!ENTITY book-maintainer-firstname "James">
   <!ENTITY book-maintainer-address "jwrober at">
  -<!ENTITY product-maintainer-fullname "Neven Has">
  -<!ENTITY product-maintainer-firstname "Neven">
  -<!ENTITY product-maintainer-address "neven at">
  +<!ENTITY product-maintainer-fullname "Kevin Fleming">
  +<!ENTITY product-maintainer-firstname "Kevin">
  +<!ENTITY product-maintainer-address "kpfleming at">
   <!ENTITY ftp-root "">
   <!ENTITY http-root "">
  1.2       +7 -1      ALFS/nALFS/doc/hackers_guide/preface/audience.xml
  Index: audience.xml
  RCS file: /home/cvsroot/ALFS/nALFS/doc/hackers_guide/preface/audience.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- audience.xml	8 Oct 2003 02:43:36 -0000	1.1
  +++ audience.xml	31 May 2004 16:06:28 -0000	1.2
  @@ -2,7 +2,13 @@
   <?dbhtml filename="audience.html" dir="preface"?>
   <title>Who Would Want To Read This Book</title>
  -<para>PAGE TO BE WRITTEN</para>
  +<para>If you are planning on writing code, updating profiles or the
  +documentation for the nALFS implementation of the ALFS DTD, then this book
  +is for you. If this is not what you want to do, then this book is not for
  +you.  If all you want to do is to understand how to use nALFS, then please
  +direct your attention to the <filename>README</filename> file in the root
  +of the source tarball or the Users Guide in the <filename>doc</filename>
  +directory. </para>
  1.3       +15 -1     ALFS/nALFS/doc/hackers_guide/preface/foreword.xml
  Index: foreword.xml
  RCS file: /home/cvsroot/ALFS/nALFS/doc/hackers_guide/preface/foreword.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- foreword.xml	29 May 2004 20:37:16 -0000	1.2
  +++ foreword.xml	31 May 2004 16:06:28 -0000	1.3
  @@ -1,7 +1,21 @@
   <sect1 id="preface-foreword" xreflabel="Foreword">
  -<para>PAGE TO BE WRITTEN</para>
  +<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>
  +<blockquote><literallayout>James Robertson
  +jwrober at</literallayout></blockquote>
  1.2       +2 -1      ALFS/nALFS/doc/hackers_guide/preface/prerequisites.xml
  Index: prerequisites.xml
  RCS file: /home/cvsroot/ALFS/nALFS/doc/hackers_guide/preface/prerequisites.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- prerequisites.xml	8 Oct 2003 02:45:30 -0000	1.1
  +++ prerequisites.xml	31 May 2004 16:06:28 -0000	1.2
  @@ -2,6 +2,7 @@
   <?dbhtml filename="prerequisites.html" dir="preface"?>
  -<para>PAGE TO BE WRITTEN</para>
  +<para>There not that many true prerequisites to be able to hack on the
  +consituent nALFS components. </para>

More information about the alfs-log mailing list