1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <sect1 id="space-creatingpartition">
|
---|
7 | <title>Creating a New Partition</title>
|
---|
8 | <?dbhtml filename="creatingpartition.html"?>
|
---|
9 |
|
---|
10 | <!--Edit Me-->
|
---|
11 | <para>Like most other operating systems, LFS is usually installed on
|
---|
12 | a dedicated partition. If you have an empty partition or enough
|
---|
13 | unpartitioned space on one of your hard disks to make one, using this
|
---|
14 | for your LFS installation is recommended. However, an LFS system (in
|
---|
15 | fact even multiple LFS systems) may also be installed on a partition
|
---|
16 | already occupied by another operating system and the different systems
|
---|
17 | will co-exist peacefully. The document
|
---|
18 | <ulink url="&hints-root;/lfs_next_to_existing_systems.txt"/> explains
|
---|
19 | how to implement this, whereas this book discusses the method of
|
---|
20 | using a fresh partition for the installation.</para>
|
---|
21 | <!--End Edit Me-->
|
---|
22 |
|
---|
23 | <para>A minimal system requires a partition of around 1.3 gigabytes
|
---|
24 | (GB). This is enough to store all the source tarballs and compile
|
---|
25 | the packages. However, if the LFS system is intended to be the primary
|
---|
26 | Linux system, additional software will probably be installed which
|
---|
27 | will require additional space (2 or 3 GB). The LFS system itself will
|
---|
28 | not take up this much space. A large portion of this required amount
|
---|
29 | of space is to provide sufficient free temporary space. Compiling
|
---|
30 | packages can require a lot of disk space which will be reclaimed after
|
---|
31 | the package is installed.</para>
|
---|
32 |
|
---|
33 | <para>Because there is not always enough Random Access Memory (RAM)
|
---|
34 | available for compilation processes, it is a good idea to use a small
|
---|
35 | disk partition as swap space. This space is used by the kernel to
|
---|
36 | store seldom-used data to make room in memory for active processes.
|
---|
37 | The swap partition for an LFS system can be the same as the one used
|
---|
38 | by the host system, so another swap partition will not need to be
|
---|
39 | created if your host system already has one setup.</para>
|
---|
40 |
|
---|
41 | <para>Start a disk partitioning program such as
|
---|
42 | <command>cfdisk</command> or <command>fdisk</command> with a command
|
---|
43 | line option naming the hard disk on which the new partition will be
|
---|
44 | created—for example <filename class="devicefile">/dev/hda</filename> for
|
---|
45 | the primary Integrated Drive Electronics (IDE) disk. Create a Linux native
|
---|
46 | partition and a swap partition, if needed. Please refer to the man
|
---|
47 | pages of <command>cfdisk</command> or <command>fdisk</command> if you
|
---|
48 | do not yet know how to use the programs.</para>
|
---|
49 |
|
---|
50 | <para>Remember the designation of the new partition (e.g.,
|
---|
51 | <filename class="devicefile">hda5</filename>). This book will refer to this as the LFS
|
---|
52 | partition. Also remember the designation of the swap partition. These
|
---|
53 | names will be needed later for the <filename>/etc/fstab</filename>
|
---|
54 | file.</para>
|
---|
55 |
|
---|
56 | <para arch="raq2">On a Cobalt RaQ2/Cube2 we use the existing firmware for a boot loader,
|
---|
57 | it requires an ext2 revision 0 partition to boot from. So here is the
|
---|
58 | recommended partition for a Cobalt RaQ2/Cube2 system:</para>
|
---|
59 |
|
---|
60 | <itemizedlist arch="raq2">
|
---|
61 | <listitem><para>The first partition should be 50-100 MB.</para></listitem>
|
---|
62 | <listitem><para>The second partition should be all the remaining space minus the
|
---|
63 | amount of RAM in the system.</para></listitem>
|
---|
64 | <listitem><para>The third partition is going to be your swap partition, which will
|
---|
65 | be the same amount as the RAM installed in the system.</para></listitem>
|
---|
66 | </itemizedlist>
|
---|
67 |
|
---|
68 | <para arch="alpha">Alphas have one of 2 BIOSes, Alphaboot or SRM. Some models have both
|
---|
69 | and you can switch between them at powerup. Each bios has a different
|
---|
70 | boot method. Milo is cool because it can be blown into flash for a
|
---|
71 | FAST boot, but its built against an older linux kernel and crashes
|
---|
72 | with some hardware, like a SCSI controller. aboot is simple if you
|
---|
73 | can use it, but needs BSD partitions. aboot doesn't really let you do
|
---|
74 | much at boot time that crosses devices. If you load aboot from hda,
|
---|
75 | your root needs to be on hda. install aboot on hdb if you want to move
|
---|
76 | your root to hdb. Once linux is loaded, you can do whatever you want.
|
---|
77 | Milo can handle loading the kernel from one disk and the root on
|
---|
78 | another.</para>
|
---|
79 |
|
---|
80 | <para arch="alpha">If you boot with SRM and aboot, you *MUST* use BSD style partitions.
|
---|
81 | You *MUST* also leave the first 2 cylinders unused as they will
|
---|
82 | contain your boot loader. I've read that partition 3 should always be
|
---|
83 | the full disk even though it overlaps with other partitions, but in my
|
---|
84 | experience that doesn't matter. If you choose to not use an EXT2 or
|
---|
85 | EXT3 root filesystem, you'll need to go through some extra hoops to
|
---|
86 | install aboot.</para>
|
---|
87 |
|
---|
88 | <para arch="alpha">If you boot with Milo, use msdos partitions, and make the first
|
---|
89 | partition large enough for at least 2 kernels (I would use about
|
---|
90 | 500Megs) and make it a FAT filesystem.</para>
|
---|
91 |
|
---|
92 | </sect1>
|
---|
93 |
|
---|