Commented out "LFS next to existing hints" until its viability can be established.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8936 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2009-05-28 04:15:15 +00:00
parent 171aae75ff
commit 8e3448a108
2 changed files with 20 additions and 4 deletions

View File

@ -40,6 +40,12 @@
<listitem>
<para>2009-05-27</para>
<itemizedlist>
<listitem>
<para>[gerard] - removed the reference to <quote>LFS next to
existing systems</quote> hint. Addresses <ulink
url="&lfs-ticket-root;2411">#2411</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update build sizes and SBU times for all
packages.

View File

@ -13,12 +13,22 @@
<para>Like most other operating systems, LFS is usually installed on a
dedicated partition. The recommended approach to building an LFS system
is to use an available empty partition or, if you have enough unpartitioned
space, to create one. However, an LFS system (in fact even multiple LFS
systems) may also be installed on a partition already occupied by another
space, to create one.</para>
<!--
<para>It is possible to install an LFS system (in fact even multiple LFS
systems) on a partition already occupied by another
operating system and the different systems will co-exist peacefully. The
document <ulink url="&hints-root;lfs_next_to_existing_systems.txt"/>
explains how to implement this, whereas this book discusses the method of
using a fresh partition for the installation.</para>
contains notes on how to implement this. This document was last updated
in 2004. It has not been updated since and it has not been tested with
recent versions of this LFS book. The document is more than likely not
usable as-is and you will need to account for changes made to the LFS
procedures since it was written. This is only recommended for expert LFS
users.</para>
-->
<para>A minimal system requires a partition of around 1.3 gigabytes (GB).
This is enough to store all the source tarballs and compile the packages.