diff options
-rw-r--r-- | chapter01/introduction.xml | 15 | ||||
-rw-r--r-- | preface/whonotread.xml | 22 |
2 files changed, 18 insertions, 19 deletions
diff --git a/chapter01/introduction.xml b/chapter01/introduction.xml index e5f08d1ea..2e4342c56 100644 --- a/chapter01/introduction.xml +++ b/chapter01/introduction.xml @@ -4,9 +4,9 @@ <para> Having used a number of different Linux distributions, I was never fully satisfied with any of those. I didn't like the way the bootscripts were -arranged, or I didn't like the way certain programs were configured by -default, and more of those things. I came to realize that when I want to -be totally satisfied with a Linux system, I have to build my own Linux +arranged, I didn't like the way certain programs were configured by +default, and more of those things. I came to realize that if I wanted to +be fully satisfied with a Linux system, I would have to build my own Linux system from scratch, ideally using only the source code. Not using precompiled packages of any kind. No help from some sort of CD-ROM or bootdisk that would install some basic utilities. I would use my current @@ -15,11 +15,10 @@ Linux system and use that one to build my own. <para> This, at one time, wild idea seemed very difficult and, at times, almost -impossible. The reason for most problems were due to my lack of knowledge -about certain programs and procedures. After sorting out all kinds of -dependency problems, compilation problems, etcetera, a custom-built Linux -system was created and fully operational. I called this system an LFS -system, which stands for Linux From Scratch. +impossible. After sorting out all kinds of dependency problems, compile +problems, etcetera, a custom-built Linux system was created and fully +operational. I called this system an LFS system, which stands for Linux +From Scratch. </para> </sect1> diff --git a/preface/whonotread.xml b/preface/whonotread.xml index fa313ff7b..6f83c6a24 100644 --- a/preface/whonotread.xml +++ b/preface/whonotread.xml @@ -3,27 +3,27 @@ <para> Users who don't want to build an entire Linux system from scratch -probably don't want to read this book. If a user, however, wants to learn +probably don't want to read this book. If you, however, want to learn more about what happens behind the scenes, in particular what happens -between turning on the computer and seeing the command prompt, he wants -to read the <quote>From Power Up To Bash Prompt</quote> (P2B) HOWTO. +between turning on the computer and seeing the command prompt, you may +want to read the <quote>From Power Up To Bash Prompt</quote> (P2B) HOWTO. This HOWTO builds a bare system, in way similar to the one this book uses, but it focusses more on just installing a bootable system instead of a complete system. </para> <para> -To decide whether to read this book or the P2B HOWTO, a user could -ask himself this question: "Is my main objective to get a working Linux -system that I'm going to build myself and, along the way, learn what -every component of a system is for, or is just the learning part my main -objective?" If he wants to build and learn, he reads this book. If he just -wants to learn, then the P2B HOWTO is probably better material to read. +To decide whether to read this book or the P2B HOWTO, ask yourself this +question: "Is my main objective to get a working Linux system that I'm +going to build myself and, along the way, learn what every component of +a system is for, or is just the learning part my main objective?" If +you want to build and learn, read this book. If you just want to learn, +then the P2B HOWTO is probably better material to read. </para> <para> -The <quote>From Power Up To Bash Prompt</quote> HOWTO can be downloaded -from <ulink url="http://www.netspace.net.au/~gok/power2bash/"> +The <quote>From Power Up To Bash Prompt</quote> HOWTO is located at +<ulink url="http://www.netspace.net.au/~gok/power2bash/"> http://www.netspace.net.au/~gok/power2bash/</ulink> </para> |