source: preface/foreword.xml@ eff3826

10.0 10.1 11.0 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 nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v5_1 v5_1-pre1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since eff3826 was eff3826, checked in by Larry Lawrence <larry@…>, 17 years ago

Added stylesheets for xsltproc processing

git-svn-id: svn:// af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 2.9 KB
1<sect1 id="preface-foreword">
2<?dbhtml filename="foreword.html"?>
5<para>Having helped out with Linux From Scratch for a short time, I
6noticed that we were getting many queries as to how to do things beyond
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>
14<para><acronym>BLFS</acronym> aims to be more than the
15<acronym>LFS</acronym>-hints converted to <acronym>XML</acronym> although
16much of our work is based around the hints and indeed some authors write
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
20system, but also that you will learn a lot about system configuration as
21you go.</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>
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 You can find more details about all of these in the
30<xref linkend="introduction"/> section of the book.</para>
32<para>Enjoy using <acronym>BLFS</acronym>.</para>
34<blockquote><literallayout>Mark Hymers
36BLFS Editor (July 2001 - March 2003)</literallayout></blockquote>
39<para>I still remember how I found the <acronym>BLFS</acronym> project
40and started using the instructions that were completed at the time. I could
41not believe how wonderful it was to get an application up and running very
42quickly, with explanations as to why things were done a certain way.
43Unfortunately, for me, it wasn't long before I was opening applications that
44had nothing more than "To be done" on the page. I did what most would do,
45I waited for someone else to do it. It wasn't too long before I am looking
46through <application>Bugzilla</application> for something easy to do.
47As with any learning experience, the definition of what was easy kept
50<para>We still encourage you to become involved as <acronym>BLFS</acronym> is
51never really finished. Contributing or just using, we hope you enjoy
52your <acronym>BLFS</acronym> experience.</para>
54<blockquote><literallayout>Larry Lawrence
56BLFS Editor (March 2003 - present)</literallayout></blockquote>
Note: See TracBrowser for help on using the repository browser.