source: chapter02/creatingpartition.xml@ c1fe047a

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since c1fe047a was b06ca36, checked in by Manuel Canales Esparcia <manuel@…>, 17 years ago

Updated book sources to use DocBook-XML DTD 4.5

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7970 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.0 KB
Line 
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
8<sect1 id="space-creatingpartition">
9 <?dbhtml filename="creatingpartition.html"?>
10
11 <title>Creating a New Partition</title>
12
13 <para>Like most other operating systems, LFS is usually installed on a
14 dedicated partition. The recommended approach to building an LFS system
15 is to use an available empty partition or, if you have enough unpartitioned
16 space, to create one. However, an LFS system (in fact even multiple LFS
17 systems) may also be installed on a partition already occupied by another
18 operating system and the different systems will co-exist peacefully. The
19 document <ulink url="&hints-root;lfs_next_to_existing_systems.txt"/>
20 explains how to implement this, whereas this book discusses the method of
21 using a fresh partition for the installation.</para>
22
23 <para>A minimal system requires a partition of around 1.3 gigabytes (GB).
24 This is enough to store all the source tarballs and compile the packages.
25 However, if the LFS system is intended to be the primary Linux system,
26 additional software will probably be installed which will require additional
27 space (2-3 GB). The LFS system itself will not take up this much room.
28 A large portion of this requirement is to provide sufficient free temporary
29 storage. Compiling packages can require a lot of disk space which will be
30 reclaimed after the package is installed.</para>
31
32 <para>Because there is not always enough Random Access Memory (RAM) available
33 for compilation processes, it is a good idea to use a small disk partition as
34 <systemitem class="filesystem">swap</systemitem> space. This is used by the
35 kernel to store seldom-used data and leave more memory available for active
36 processes. The <systemitem class="filesystem">swap</systemitem> partition for
37 an LFS system can be the same as the one used by the host system, in which
38 case it is not necessary to create another one.</para>
39
40 <para>Start a disk partitioning program such as <command>cfdisk</command>
41 or <command>fdisk</command> with a command line option naming the hard
42 disk on which the new partition will be created&mdash;for example
43 <filename class="devicefile">/dev/hda</filename> for the primary Integrated
44 Drive Electronics (IDE) disk. Create a Linux native partition and a
45 <systemitem class="filesystem">swap</systemitem> partition, if needed. Please
46 refer to <filename>cfdisk(8)</filename> or <filename>fdisk(8)</filename> if
47 you do not yet know how to use the programs.</para>
48
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
55</sect1>
Note: See TracBrowser for help on using the repository browser.