LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-11-13 16:02:41 +00:00
parent 4a3a9af2c8
commit b470d06dbd
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
LDP/howto/docbook/Partition.sgml
View File

@ -4,7 +4,7 @@
<artheader>
<title>Linux Partition HOWTO</title>
<author><firstname>Tony</firstname><surname>Harris</surname></author>
<author><firstname>Kristan</firstname><surname>Koehntopp</surname></author>
<author><firstname>Kristian</firstname><surname>Koehntopp</surname></author>
<revhistory>
<revision>
<revnumber>3.2</revnumber>
@ -27,12 +27,12 @@
<revision>
<revnumber>3.0</revnumber>
<date>1 May 2000</date>
<revremark>First revision by <ulink url="mailto:tony@nmr.mgh.harvard.edu">Tony Harris</ulink> based on Linux Partition HOWTO by Kristan Koehntopp.</revremark>
<revremark>First revision by <ulink url="mailto:tony@nmr.mgh.harvard.edu">Tony Harris</ulink> based on Linux Partition HOWTO by Kristian Koehntopp.</revremark>
</revision>
<revision>
<revnumber>2.4</revnumber>
<date>3 November 1997</date>
<revremark>Last revision by Kristan Koehntopp.
<revremark>Last revision by Kristian Koehntopp.
</revremark>
</revision>
</revhistory>
@ -286,8 +286,8 @@ block devices only.
<sect3 id="NamingConvention"><title>Naming Convention</title>
<para>
By convention, IDE drives will be given device names like
<filename>/dev/hda</filename> and <filename>/dev/hdd</filename>. The first drive is
By convention, IDE drives will be given device names
<filename>/dev/hda</filename> to <filename>/dev/hdd</filename>. The first drive is
'a' the second drive 'b' and so on. For example, <filename>/dev/hda</filename>
is the first drive on the first IDE controller and
<filename>/dev/hdd</filename> is the second drive on the second controller
@ -327,14 +327,14 @@ controller might have all its drives renamed. Grrr...
</para>
<para>
This is all you have to know to deal with linux disk devices. For the
sake of completeness, see Kristan's discussion of device numbers
sake of completeness, see Kristian's discussion of device numbers
below.
</para>
</sect3>
</sect2>
<sect2 id="numbers"><title>Device numbers</title><!--Kristan 3 Nov 97-->
<sect2 id="numbers"><title>Device numbers</title><!--Kristian 3 Nov 97-->
<para>
The only important thing with a device file are its major and minor
@ -433,7 +433,7 @@ different partition types.
</para>
<para>
<!-- Kristan 3 Nov 97-->
<!-- Kristian 3 Nov 97-->
OS/2 marks its partitions with a <literal>0x07</literal> type and so
does Windows NT's NTFS. MS-DOS allocates several type codes for its
various flavors of FAT file systems: 0x01, <literal>0x04</literal> and <literal>0x06</literal> are known.
@ -478,7 +478,7 @@ disk and 63 total on an IDE disk.
<sect2 id="swap-partitions"><title>Swap Partitions</title>
<para>
Every process running on your computer is allocated a number of blocks
of RAM. These blocks (1k in linux) are called pages. The set of
of RAM. These blocks are called pages. The set of
in-memory pages which will be referenced by the processor in the very
near future is called a "working set." Linux tries to predict these
memory accesses (assuming that recently used pages will be used again
@ -703,7 +703,7 @@ partition.
<sect2>
<title>Swap Partitions</title>
<!-- Kristan 3 Nov 97-->
<!-- Kristian 3 Nov 97-->
<sect3 id="SwapSize">
<title>How large should my swap space be?</title>
@ -729,7 +729,7 @@ larger than 128 MB, but excess space is never used. If you want more
than 128 MB of swap for a 2.1 and earlier kernel, you have to create
multiple swap partitions. See the man page for mkswap for details.</para></listitem>
<!--Kristan 3 Nov 97-->
<!--Kristian 3 Nov 97-->
<listitem><para> When sizing swap space, keep in mind that too much swap space
may not be useful at all.</para></listitem>
</itemizedlist>
@ -1567,10 +1567,11 @@ to choose large blocks for large file systems, except for very large
file systems in the 0.5 TB range (that's terabytes with 1 TB equaling
1024 GB) and above, where small block sizes become inefficient. So
unlike DOS there is no need to split up large disks into multiple
partitions to keep block size down. Use the 1 KB default block size if
possible. You may want to experiment with a block size of 2 KB for
some partitions, but expect to meet some seldom exercised bugs: Most
people use the default.
partitions to keep block size down.
</para>
<para>
Use a 1Kb block size if you have many small files. For large
partitions, 4Kb blocks are fine.
</para>
</sect2>
</sect1>