r618 - html/trunk/clfs

justin at linuxfromscratch.org justin at linuxfromscratch.org
Sun Oct 30 22:50:58 PST 2005

Author: justin
Date: 2005-10-30 23:50:58 -0700 (Sun, 30 Oct 2005)
New Revision: 618

Updated CLFS index.html.

Modified: html/trunk/clfs/index.html
--- html/trunk/clfs/index.html	2005-10-31 06:37:38 UTC (rev 617)
+++ html/trunk/clfs/index.html	2005-10-31 06:50:58 UTC (rev 618)
@@ -3,19 +3,61 @@
 <!--#include virtual="menu.html" -->
     <div class="main">
      <h1>What is Cross Linux From Scratch?</h1>
-     <!-- <p>Linux From Scratch (LFS) is a project that provides you with
-        step-by-step instructions for building your own customized Linux system
-        entirely from source.
-     </p> -->
+     <p>Cross Linux From Scratch (CLFS) is a project that provides you with 
+        step-by-step instructions for building your own customized Linux 
+        system entirely from source.</p>
-     <!--
      <h2>Why would I want an CLFS system?</h2>
-     TODO -->
+     <p>Many wonder why they should go through the hassle of building a Linux
+        system from scratch when they could just download an existing Linux
+        distribution. However, there are several benefits of building CLFS.
+        Consider the following:</p>
+     <p><em>CLFS teaches people how to build a cross compiler</em>
+        Building CLFS teaches you how to make a cross-compiler and the 
+        necessary tools, to build a basic system on a different
+        architecture. For example you would be able to build a Sparc toolchain
+        on an x86 machine, and utilize that toolchain to build a Linux system
+        from source codes.</p>
+     <p><em>CLFS teaches people how to utilize a multilib system</em>
+        CLFS takes advantage of the target systems capability, by utilizing a
+        mulitlib capable build system.</p>
+     <p><em>CLFS teaches people how a Linux system works internally</em>
+        Building CLFS teaches you about all that makes Linux tick, how things
+        work together and depend on each other. And most importantly, how to
+        customize it to your own tastes and needs.</p>
+     <p><em>Building CLFS produces a very compact Linux system</em>
+        When you install a regular distribution, you often end up installing a
+        lot of programs that you would probably never use. They're just sitting
+        there taking up (precious) disk space. It's not hard to get an CLFS
+        system installed under 100 MB. Does that still sound like a lot? A few
+        of us have been working on creating a very small embedded CLFS system.
+        We installed a system that was just enough to run the Apache web server;
+        total disk space usage was approximately 8 MB. With further stripping,
+        that can be brought down to 5 MB or less. Try that with a regular
+        distribution.</p>
+     <p><em>CLFS is extremely flexible</em>
+        Building CLFS could be compared to a finished house. CLFS will give you
+        the skeleton of a house, but it's up to you to install plumbing,
+        electrical outlets, kitchen, bath, wallpaper, etc. You have the ability
+        to turn it into whatever type of system you need it to be, customized
+        completely for you.</p>
+     <p><em>CLFS offers you added security</em>
+        You will compile the entire system from source, thus allowing you to
+        audit everything, if you wish to do so, and apply all the security
+        patches you want or need to apply. You don't have to wait for someone
+        else to provide a new binary package that (hopefully) fixes a security
+        hole. Often, you never truly know whether a security hole is fixed or
+        not unless you do it yourself.</p>
+     <h2>What can I do with my CLFS system?</h2>
+     <p>A by-the-book CLFS system is fairly minimal, but is designed to provide
+        a strong base on which you can add any packages you want. See the
+        <a href="/blfs/">BLFS project</a> for a selection of commonly used
+        packages.</p>
      <h2>Who's who:</h2>
-        <li>Project Leader: Jim Gifford</li>
-        <li>Maintainer: Ryan Oliver</li>
+        <li>Project Leadership: Jim Gifford and Ryan Oliver</li>
         <li>Plus numerous people who contribute to the book and its side projects.</li>

More information about the website mailing list