Changeset 2eeb8695 for book/preface.xml
- Timestamp:
- 03/09/2020 03:02:12 PM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2aff70f
- Parents:
- 22618785
- File:
-
- 1 edited
-
book/preface.xml (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
book/preface.xml
r22618785 r2eeb8695 14 14 <title>Preface</title> 15 15 16 <para>Having helped out with Linux From Scratch for a short time, I 17 noticed that we were getting many queries as to how to do things beyond 18 the base LFS system. At the time, the only assistance specifically offered 19 relating to LFS were the LFS hints (<ulink url="&hints-root;"/>). 20 Most of the LFS hints are extremely good and well written 21 but I (and others) could still see a need for more comprehensive help to 22 go Beyond LFS — hence BLFS.</para> 16 <para> 17 Having helped out with Linux From Scratch for a short time, I 18 noticed that we were getting many queries as to how to do things beyond 19 the base LFS system. At the time, the only assistance specifically offered 20 relating to LFS were the LFS hints (<ulink url="&hints-root;"/>). 21 Most of the LFS hints are extremely good and well written 22 but I (and others) could still see a need for more comprehensive help to 23 go Beyond LFS — hence BLFS. 24 </para> 23 25 24 <para>BLFS aims to be more than the LFS-hints converted to XML although 25 much of our work is based around the hints and indeed some authors write 26 both hints and the relevant BLFS sections. We hope that we can provide 27 you with enough information to not only manage to build your system up to 28 what you want, whether it be a web server or a multimedia desktop system, 29 but also that you will learn a lot about system configuration as you go.</para> 26 <para> 27 BLFS aims to be more than the LFS-hints converted to XML although 28 much of our work is based around the hints and indeed some authors write 29 both hints and the relevant BLFS sections. We hope that we can provide 30 you with enough information to not only manage to build your system up to 31 what you want, whether it be a web server or a multimedia desktop system, 32 but also that you will learn a lot about system configuration as you go. 33 </para> 30 34 31 <para>Thanks as ever go to everyone in the LFS/BLFS 32 community; especially those who have contributed instructions, written text, 33 answered questions and generally shouted when things were wrong!</para> 35 <para> 36 Thanks as ever go to everyone in the LFS/BLFS 37 community; especially those who have contributed instructions, written text, 38 answered questions and generally shouted when things were wrong! 39 </para> 34 40 35 <para>Finally, we encourage you to become involved in the community; ask 36 questions on the mailing list or news gateway and join in the fun on #lfs and 37 #lfs-support at freenode. You can find more details about all of these in 38 the <xref linkend="introduction"/> section of the book.</para> 41 <para> 42 Finally, we encourage you to become involved in the community; ask 43 questions on the mailing list or news gateway and join in the fun on #lfs 44 and #lfs-support at freenode. You can find more details about all of these 45 in the <xref linkend="introduction"/> section of the book. 46 </para> 39 47 40 <para>Enjoy using BLFS.</para> 48 <para> 49 Enjoy using BLFS. 50 </para> 41 51 42 52 <blockquote> … … 46 56 </blockquote> 47 57 48 <para>I still remember how I found the BLFS project 49 and started using the instructions that were completed at the time. I could 50 not believe how wonderful it was to get an application up and running very 51 quickly, with explanations as to why things were done a certain way. 52 Unfortunately, for me, it wasn't long before I was opening applications that 53 had nothing more than "To be done" on the page. I did what most would do, 54 I waited for someone else to do it. It wasn't too long before I am looking 55 through <application>Bugzilla</application> for something easy to do. 56 As with any learning experience, the definition of what was easy kept 57 changing.</para> 58 <para> 59 I still remember how I found the BLFS project 60 and started using the instructions that were completed at the time. I could 61 not believe how wonderful it was to get an application up and running very 62 quickly, with explanations as to why things were done a certain way. 63 Unfortunately, for me, it wasn't long before I was opening applications that 64 had nothing more than "To be done" on the page. I did what most would do, 65 I waited for someone else to do it. It wasn't too long before I am looking 66 through <application>Bugzilla</application> for something easy to do. 67 As with any learning experience, the definition of what was easy kept 68 changing. 69 </para> 58 70 59 <para>We still encourage you to become involved as BLFS is 60 never really finished. Contributing or just using, we hope you enjoy 61 your BLFS experience.</para> 71 <para> 72 We still encourage you to become involved as BLFS is 73 never really finished. Contributing or just using, we hope you enjoy 74 your BLFS experience. 75 </para> 62 76 63 77 <blockquote> … … 67 81 </blockquote> 68 82 69 <para>The BLFS project is a natural progression of 70 LFS. Together, these projects provide a unique resource for 71 the Open Source Community. They take the mystery out of the process of 72 building a complete, functional software system from the source code contributed 73 by many talented individuals throughout the world. They truly allow users 74 to implement the slogan 75 <quote><emphasis>Your distro, your rules</emphasis></quote>.</para> 83 <para> 84 The BLFS project is a natural progression of 85 LFS. Together, these projects provide a unique resource for 86 the Open Source Community. They take the mystery out of the process of 87 building a complete, functional software system from the source code 88 contributed by many talented individuals throughout the world. They truly 89 allow users to implement the slogan 90 <quote><emphasis>Your distro, your rules</emphasis></quote>. 91 </para> 76 92 77 <para>Our goal is to continue to provide the best resource available that shows 78 you how to integrate many significant Open Source applications. Since these 79 applications are constantly updated and new applications are developed, this 80 book will never be complete. Additionally, there is always room for 81 improvement in explaining the nuances of how to install the different packages. 82 To make these improvements, we need your feedback. I encourage you to 83 participate on the different mailing lists, news groups, and 84 IRC channels to help meet these goals.</para> 93 <para> 94 Our goal is to continue to provide the best resource available that shows 95 you how to integrate many significant Open Source applications. Since these 96 applications are constantly updated and new applications are developed, this 97 book will never be complete. Additionally, there is always room for 98 improvement in explaining the nuances of how to install the different 99 packages. To make these improvements, we need your feedback. I encourage 100 you to participate on the different mailing lists, news groups, and 101 IRC channels to help meet these goals. 102 </para> 85 103 86 104 <blockquote> … … 90 108 </blockquote> 91 109 92 <para>My introduction to the [B]LFS project was actually by accident. I 93 was trying to build a <application>GNOME</application> environment using 94 some how-tos and other information I found on the web. A couple of times 95 I ran into some build issues and Googling pulled up some old BLFS mailing 96 list messages. Out for curiosity, I visited the Linux From Scratch web site 97 and shortly thereafter was hooked. I've not used any other Linux 98 distribution for personal use since.</para> 110 <para> 111 My introduction to the [B]LFS project was actually by accident. I 112 was trying to build a <application>GNOME</application> environment using 113 some how-tos and other information I found on the web. A couple of times 114 I ran into some build issues and Googling pulled up some old BLFS mailing 115 list messages. Out for curiosity, I visited the Linux From Scratch web site 116 and shortly thereafter was hooked. I've not used any other Linux 117 distribution for personal use since. 118 </para> 99 119 100 <para>I can't promise anyone will feel the sense of satisfaction I felt 101 after building my first few systems using [B]LFS instructions, but I 102 sincerely hope that your BLFS experience is as rewarding for you as it has 103 been for me.</para> 120 <para> 121 I can't promise anyone will feel the sense of satisfaction I felt 122 after building my first few systems using [B]LFS instructions, but I 123 sincerely hope that your BLFS experience is as rewarding for you as it has 124 been for me. 125 </para> 104 126 105 <para>The BLFS project has grown significantly the last couple of years. 106 There are more package instructions and related dependencies than ever 107 before. The project requires your input for continued success. If you 108 discover that you enjoy building BLFS, please consider helping out in any 109 way you can. BLFS requires hundreds of hours of maintenance to keep it 110 even semi-current. If you feel confident enough in your editing skills, 111 please consider joining the BLFS team. Simply contributing to the mailing 112 list discussions with sound advice and/or providing patches to the book's 113 XML will probably result in you receiving an invitation to join the 114 team.</para> 127 <para> 128 The BLFS project has grown significantly the last couple of years. 129 There are more package instructions and related dependencies than ever 130 before. The project requires your input for continued success. If you 131 discover that you enjoy building BLFS, please consider helping out in any 132 way you can. BLFS requires hundreds of hours of maintenance to keep it 133 even semi-current. If you feel confident enough in your editing skills, 134 please consider joining the BLFS team. Simply contributing to the mailing 135 list discussions with sound advice and/or providing patches to the book's 136 XML will probably result in you receiving an invitation to join the 137 team. 138 </para> 115 139 116 140 <blockquote>
Note:
See TracChangeset
for help on using the changeset viewer.
