creatingpartition.xml 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4. <!ENTITY % general-entities SYSTEM "../general.ent">
  5. %general-entities;
  6. ]>
  7. <sect1 id="space-creatingpartition">
  8. <?dbhtml filename="creatingpartition.html"?>
  9. <title>Creating a New Partition</title>
  10. <para>Like most other operating systems, LFS is usually installed on a
  11. dedicated partition. The recommended approach to building an LFS system
  12. is to use an available empty partition or, if you have enough unpartitioned
  13. space, to create one.</para>
  14. <!--
  15. <para>It is possible to install an LFS system (in fact even multiple LFS
  16. systems) on a partition already occupied by another
  17. operating system and the different systems will co-exist peacefully. The
  18. document <ulink url="&hints-root;lfs_next_to_existing_systems.txt"/>
  19. contains notes on how to implement this. This document was last updated
  20. in 2004. It has not been updated since and it has not been tested with
  21. recent versions of this LFS book. The document is more than likely not
  22. usable as-is and you will need to account for changes made to the LFS
  23. procedures since it was written. This is only recommended for expert LFS
  24. users.</para>
  25. -->
  26. <para>A minimal system requires a partition of around 1.3 gigabytes (GB).
  27. This is enough to store all the source tarballs and compile the packages.
  28. However, if the LFS system is intended to be the primary Linux system,
  29. additional software will probably be installed which will require additional
  30. space (2-3 GB). The LFS system itself will not take up this much room.
  31. A large portion of this requirement is to provide sufficient free temporary
  32. storage. Compiling packages can require a lot of disk space which will be
  33. reclaimed after the package is installed.</para>
  34. <para>Because there is not always enough Random Access Memory (RAM) available
  35. for compilation processes, it is a good idea to use a small disk partition as
  36. <systemitem class="filesystem">swap</systemitem> space. This is used by the
  37. kernel to store seldom-used data and leave more memory available for active
  38. processes. The <systemitem class="filesystem">swap</systemitem> partition for
  39. an LFS system can be the same as the one used by the host system, in which
  40. case it is not necessary to create another one.</para>
  41. <para>Start a disk partitioning program such as <command>cfdisk</command>
  42. or <command>fdisk</command> with a command line option naming the hard
  43. disk on which the new partition will be created&mdash;for example
  44. <filename class="devicefile">/dev/hda</filename> for the primary Integrated
  45. Drive Electronics (IDE) disk. Create a Linux native partition and a
  46. <systemitem class="filesystem">swap</systemitem> partition, if needed. Please
  47. refer to <filename>cfdisk(8)</filename> or <filename>fdisk(8)</filename> if
  48. you do not yet know how to use the programs.</para>
  49. <para>Remember the designation of the new partition (e.g., <filename
  50. class="devicefile">hda5</filename>). This book will refer to this as
  51. the LFS partition. Also remember the designation of the <systemitem
  52. class="filesystem">swap</systemitem> partition. These names will be
  53. needed later for the <filename>/etc/fstab</filename> file.</para>
  54. </sect1>