| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- original version: 18917 untranslated -->
|
| 3 |
|
| 4 |
|
| 5 |
<sect1>
|
| 6 |
<title>Recommended Partitioning Scheme</title>
|
| 7 |
<para>
|
| 8 |
|
| 9 |
For new users, personal Debian boxes, home systems, and other
|
| 10 |
single-user setups, a single <filename>/</filename> partition (plus
|
| 11 |
swap) is probably the easiest, simplest way to go. However, if your
|
| 12 |
partition is larger than around 6GB, choose ext3 as your partition
|
| 13 |
type. Ext2 partitions need periodic file system integrity checking,
|
| 14 |
and this can cause delays during booting when the partition is large.
|
| 15 |
|
| 16 |
</para><para>
|
| 17 |
|
| 18 |
For multi-user systems or systems with lots of disk space, it's best
|
| 19 |
to put <filename>/usr</filename>, <filename>/var</filename>,
|
| 20 |
<filename>/tmp</filename>, and <filename>/home</filename> each on
|
| 21 |
their own partitions separate from the <filename>/</filename>
|
| 22 |
partition.
|
| 23 |
|
| 24 |
</para><para>
|
| 25 |
|
| 26 |
You might need a separate <filename>/usr/local</filename> partition if
|
| 27 |
you plan to install many programs that are not part of the Debian
|
| 28 |
distribution. If your machine will be a mail server, you might need
|
| 29 |
to make <filename>/var/mail</filename> a separate partition. Often,
|
| 30 |
putting <filename>/tmp</filename> on its own partition, for instance
|
| 31 |
20 to 50MB, is a good idea. If you are setting up a server with lots
|
| 32 |
of user accounts, it's generally good to have a separate, large
|
| 33 |
<filename>/home</filename> partition. In general, the partitioning
|
| 34 |
situation varies from computer to computer depending on its uses.
|
| 35 |
|
| 36 |
</para><para>
|
| 37 |
|
| 38 |
For very complex systems, you should see the
|
| 39 |
<ulink url="&url-multidisk-howto;">
|
| 40 |
Multi Disk HOWTO</ulink>. This contains in-depth information, mostly
|
| 41 |
of interest to ISPs and people setting up servers.
|
| 42 |
|
| 43 |
</para><para>
|
| 44 |
|
| 45 |
With respect to the issue of swap partition size, there are many
|
| 46 |
views. One rule of thumb which works well is to use as much swap as
|
| 47 |
you have system memory. It also shouldn't be smaller than 16MB, in
|
| 48 |
most cases. Of course, there are exceptions to these rules. If you
|
| 49 |
are trying to solve 10000 simultaneous equations on a machine with
|
| 50 |
256MB of memory, you may need a gigabyte (or more) of swap.
|
| 51 |
|
| 52 |
</para><para arch="m68k">
|
| 53 |
|
| 54 |
On the other hand, Atari Falcons and Macs feel pain when swapping, so
|
| 55 |
instead of making a large swap partition, get as much RAM as possible.
|
| 56 |
|
| 57 |
</para><para>
|
| 58 |
|
| 59 |
On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the
|
| 60 |
maximum size of a swap partition is 2GB. That should be enough for
|
| 61 |
nearly any installation. However, if your swap requirements are this
|
| 62 |
high, you should probably try to spread the swap across different
|
| 63 |
disks (also called <quote>spindles</quote>) and, if possible, different SCSI or
|
| 64 |
IDE channels. The kernel will balance swap usage between multiple
|
| 65 |
swap partitions, giving better performance.
|
| 66 |
|
| 67 |
</para><para>
|
| 68 |
|
| 69 |
As an example, an older home machine might have 32MB of RAM and a
|
| 70 |
1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a
|
| 71 |
500MB partition for another operating system on
|
| 72 |
<filename>/dev/hda1</filename>, a 32MB swap partition on
|
| 73 |
<filename>/dev/hda3</filename> and about 1.2GB on
|
| 74 |
<filename>/dev/hda2</filename>) as the Linux partition.
|
| 75 |
|
| 76 |
</para><para>
|
| 77 |
|
| 78 |
For an idea of the space taken by tasks
|
| 79 |
you might be interested in adding after your system installation is
|
| 80 |
complete, check <xref linkend="tasksel-size-list"/>.
|
| 81 |
|
| 82 |
</para>
|
| 83 |
|
| 84 |
</sect1>
|
Parent Directory
| 
Revision Log