Changeset 0f065b2 for preface

Timestamp:

08/04/2003 03:24:09 AM (21 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

9079fba6

Parents:

ab8a3cb

Message:

added my foreword and tagged more acronyms

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@968 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:

preface

Files:

• foreword.xml (modified) (1 diff)
• whoread.xml (modified) (1 diff)

preface/foreword.xml

@@ -3 +3 @@
 <title>Foreword</title>
 
-<para>Having helped out with LinuxFromScratch for a short time, I
+<para>Having helped out with Linux From Scratch for a short time, I
 noticed that we were getting many queries as to how to do things beyond
-the base LFS system.  At the time, the only assistance specifically
-offered relating to LFS were the LFS hints (<ulink
-url="&hints-root;">&hints-root;</ulink>).  Most of the LFS hints are
-extremely good and well written but I (and others) could still see a
-need for more comprehensive help to go Beyond LFS - hence BLFS.</para>
+the base <acronym>LFS</acronym> system.  At the time, the only assistance 
+specifically offered relating to <acronym>LFS</acronym> were the
+<acronym>LFS</acronym> hints (<ulink url="&hints-root;">&hints-root;</ulink>). 
+Most of the <acronym>LFS</acronym> hints are extremely good and well written 
+but I (and others) could still see a need for more comprehensive help to 
+go Beyond <acronym>LFS</acronym> - hence <acronym>BLFS</acronym>.</para>
 
-<para>BLFS aims to be more than the LFS-hints converted to XML although
+<para><acronym>BLFS</acronym> aims to be more than the
+<acronym>LFS</acronym>-hints converted to <acronym>XML</acronym> although
 much of our work is based around the hints and indeed some authors write
-both hints and the relevant BLFS sections.  We hope that we can provide
-you with enough information to not only manage to build your system up
-to what you want, whether it be a web server or a multimedia desktop
+both hints and the relevant <acronym>BLFS</acronym> sections.  We hope that 
+we can provide you with enough information to not only manage to build your 
+system up to what you want, whether it be a web server or a multimedia desktop
 system, but also that you will learn a lot about system configuration as
 you go.</para>
 
-<para>Thanks as ever go to everyone in the LFS/BLFS community especially
-those who have contributed instructions, written text, answered
-questions and generally shouted when things were wrong!</para>
+<para>Thanks as ever go to everyone in the <acronym>LFS</acronym>/<acronym>BLFS</acronym> 
+community especially those who have contributed instructions, written text, 
+answered questions and generally shouted when things were wrong!</para>
 
-<para>Finally, we encourage you to become involved in the community; 
-ask questions on the mailing list or
-news gateway and join in the fun on #lfs at irc.linuxfromscratch.org.
-You can find more details about all of these in the <xref linkend="introduction"/> section of the book.</para>
+<para>Finally, we encourage you to become involved in the community; ask 
+questions on the mailing list or news gateway and join in the fun on #lfs at 
+irc.linuxfromscratch.org. You can find more details about all of these in the 
+<xref linkend="introduction"/> section of the book.</para>
 
-<para>Enjoy using BLFS.</para>
+<para>Enjoy using <acronym>BLFS</acronym>.</para>
 
 <para>Mark Hymers &lt;markh@linuxfromscratch.org&gt;
 BLFS Editor (July 2001 - March 2003)</para>
 
+
+<para>I still remember how I found the <acronym>BLFS</acronym> project
+and started using the instructions that were completed at the time.  I could 
+not believe how wonderful it was to get an application up and running very 
+quickly, with explanations as to why things were done a certain way.
+Unfortunately, for me, it wasn't long before I was opening applications that 
+had nothing more  than "To be done" on the page.  I did what most would do, 
+I waited for someone else to do it.  It wasn't too long before I am looking 
+through  <application>Bugzilla</application> for something easy to do.
+As with any learning experience, the definition of what was easy kept
+changing.</para>
+
+<para>We still encourage you to become involved as <acronym>BLFS</acronym> is 
+never really finished.  Contributing or just using, we hope you enjoy
+your <acronym>BLFS</acronym> experience.</para>
+
+<para>Larry Lawrence &lt;larry@linuxfromscratch.org&gt; BLFS Editor
+(March 2003 - present)</para>
+
 </sect1>
 

preface/whoread.xml

@@ -4 +4 @@
 
 <para>This book is mainly aimed at those who have built a system based
-on the LFS book.  It will also be useful for those who are using other
-distributions, but for one reason or another want to manually build
-software and are in need of some assistance.  BLFS can be used to create
-a range of diverse systems and so the target audience is probably nearly
-as wide as that of the LFS book.  If you found LFS useful, you should
-also like this!</para>
+on the <acronym>LFS</acronym> book.  It will also be useful for those who are 
+using other distributions, but for one reason or another want to manually build
+software and are in need of some assistance.  <acronym>BLFS</acronym> can be 
+used to create a range of diverse systems and so the target audience is 
+probably nearly as wide as that of the <acronym>LFS</acronym> book.  If you 
+found <acronym>LFS</acronym> useful, you should also like this!</para>
 
 </sect1>