Ignore:
Timestamp:
Jul 13, 2006, 10:13:15 AM (18 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
a5b01a51
Parents:
036cbc7
Message:

r4564@server: jim | 2006-07-13 10:12:58 -0700
Text Updates

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/partitioning/common/creatingpartition.xml

    r036cbc7 ra266616  
    1111  <title>Creating a New Partition</title>
    1212
    13   <para os="a">Like most other operating systems, CLFS is usually installed on
    14   a dedicated partition. The recommended approach to building a CLFS
     13  <para os="a">Like most other operating systems, CLFS is usually installed
     14  on a dedicated partition. The recommended approach to building a CLFS
    1515  system is to use an available empty partition or, if you have enough
    16   unpartitioned space, to create one. However, a CLFS system (in fact
    17   even multiple CLFS systems) may also be installed on a partition already
    18   occupied by another operating system and the different systems will
    19   co-exist peacefully. The document <ulink
    20   url="&hints-root;lfs_next_to_existing_systems.txt"/> explains how to
    21   implement this, whereas this book discusses the method of using a fresh
    22   partition for the installation.</para>
     16  unpartitioned space, to create one. However, if your building for a different
     17  architecture you can simply build everyting in <quote>/mnt/clfs</quote>
     18  and transfer it to your target machine.</para>
    2319
    24   <para os="b">A minimal system requires a partition of around 1.3 gigabytes (GB).
     20  <para os="b">A minimal system requires around 1.5 gigabytes (GB).
    2521  This is enough to store all the source tarballs and compile the packages.
    2622  However, if the CLFS system is intended to be the primary Linux system,
Note: See TracChangeset for help on using the changeset viewer.