Changeset 0f065b2


Ignore:
Timestamp:
08/04/2003 03:24:09 AM (19 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 11.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, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/test-20220226
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:
2 edited

Legend:

Unmodified
Added
Removed
  • preface/foreword.xml

    rab8a3cb r0f065b2  
    33<title>Foreword</title>
    44
    5 <para>Having helped out with LinuxFromScratch for a short time, I
     5<para>Having helped out with Linux From Scratch for a short time, I
    66noticed that we were getting many queries as to how to do things beyond
    7 the base LFS system.  At the time, the only assistance specifically
    8 offered relating to LFS were the LFS hints (<ulink
    9 url="&hints-root;">&hints-root;</ulink>).  Most of the LFS hints are
    10 extremely good and well written but I (and others) could still see a
    11 need for more comprehensive help to go Beyond LFS - hence BLFS.</para>
     7the base <acronym>LFS</acronym> system.  At the time, the only assistance
     8specifically offered relating to <acronym>LFS</acronym> were the
     9<acronym>LFS</acronym> hints (<ulink url="&hints-root;">&hints-root;</ulink>).
     10Most of the <acronym>LFS</acronym> hints are extremely good and well written
     11but I (and others) could still see a need for more comprehensive help to
     12go Beyond <acronym>LFS</acronym> - hence <acronym>BLFS</acronym>.</para>
    1213
    13 <para>BLFS aims to be more than the LFS-hints converted to XML although
     14<para><acronym>BLFS</acronym> aims to be more than the
     15<acronym>LFS</acronym>-hints converted to <acronym>XML</acronym> although
    1416much of our work is based around the hints and indeed some authors write
    15 both hints and the relevant BLFS sections.  We hope that we can provide
    16 you with enough information to not only manage to build your system up
    17 to what you want, whether it be a web server or a multimedia desktop
     17both hints and the relevant <acronym>BLFS</acronym> sections.  We hope that
     18we can provide you with enough information to not only manage to build your
     19system up to what you want, whether it be a web server or a multimedia desktop
    1820system, but also that you will learn a lot about system configuration as
    1921you go.</para>
    2022
    21 <para>Thanks as ever go to everyone in the LFS/BLFS community especially
    22 those who have contributed instructions, written text, answered
    23 questions and generally shouted when things were wrong!</para>
     23<para>Thanks as ever go to everyone in the <acronym>LFS</acronym>/<acronym>BLFS</acronym>
     24community especially those who have contributed instructions, written text,
     25answered questions and generally shouted when things were wrong!</para>
    2426
    25 <para>Finally, we encourage you to become involved in the community;
    26 ask questions on the mailing list or
    27 news gateway and join in the fun on #lfs at irc.linuxfromscratch.org.
    28 You can find more details about all of these in the <xref linkend="introduction"/> section of the book.</para>
     27<para>Finally, we encourage you to become involved in the community; ask
     28questions on the mailing list or news gateway and join in the fun on #lfs at
     29irc.linuxfromscratch.org. You can find more details about all of these in the
     30<xref linkend="introduction"/> section of the book.</para>
    2931
    30 <para>Enjoy using BLFS.</para>
     32<para>Enjoy using <acronym>BLFS</acronym>.</para>
    3133
    3234<para>Mark Hymers &lt;markh@linuxfromscratch.org&gt;
    3335BLFS Editor (July 2001 - March 2003)</para>
    3436
     37
     38<para>I still remember how I found the <acronym>BLFS</acronym> project
     39and started using the instructions that were completed at the time.  I could
     40not believe how wonderful it was to get an application up and running very
     41quickly, with explanations as to why things were done a certain way.
     42Unfortunately, for me, it wasn't long before I was opening applications that
     43had nothing more  than "To be done" on the page.  I did what most would do,
     44I waited for someone else to do it.  It wasn't too long before I am looking
     45through  <application>Bugzilla</application> for something easy to do.
     46As with any learning experience, the definition of what was easy kept
     47changing.</para>
     48
     49<para>We still encourage you to become involved as <acronym>BLFS</acronym> is
     50never really finished.  Contributing or just using, we hope you enjoy
     51your <acronym>BLFS</acronym> experience.</para>
     52
     53<para>Larry Lawrence &lt;larry@linuxfromscratch.org&gt; BLFS Editor
     54(March 2003 - present)</para>
     55
    3556</sect1>
    3657
  • preface/whoread.xml

    rab8a3cb r0f065b2  
    44
    55<para>This book is mainly aimed at those who have built a system based
    6 on the LFS book.  It will also be useful for those who are using other
    7 distributions, but for one reason or another want to manually build
    8 software and are in need of some assistance.  BLFS can be used to create
    9 a range of diverse systems and so the target audience is probably nearly
    10 as wide as that of the LFS book.  If you found LFS useful, you should
    11 also like this!</para>
     6on the <acronym>LFS</acronym> book.  It will also be useful for those who are
     7using other distributions, but for one reason or another want to manually build
     8software and are in need of some assistance.  <acronym>BLFS</acronym> can be
     9used to create a range of diverse systems and so the target audience is
     10probably nearly as wide as that of the <acronym>LFS</acronym> book.  If you
     11found <acronym>LFS</acronym> useful, you should also like this!</para>
    1212
    1313</sect1>
Note: See TracChangeset for help on using the changeset viewer.