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