diff options
Diffstat (limited to 'en/partitioning')
| -rw-r--r-- | en/partitioning/device-names.xml | 9 | ||||
| -rw-r--r-- | en/partitioning/partition-programs.xml | 4 | ||||
| -rw-r--r-- | en/partitioning/partition/hppa.xml | 22 | ||||
| -rw-r--r-- | en/partitioning/partition/ia64.xml | 120 | ||||
| -rw-r--r-- | en/partitioning/partition/mips.xml | 16 | ||||
| -rw-r--r-- | en/partitioning/partition/powerpc.xml | 2 | ||||
| -rw-r--r-- | en/partitioning/partition/sparc.xml | 33 |
7 files changed, 4 insertions, 202 deletions
diff --git a/en/partitioning/device-names.xml b/en/partitioning/device-names.xml index 9c68ff013..308b75a16 100644 --- a/en/partitioning/device-names.xml +++ b/en/partitioning/device-names.xml @@ -81,14 +81,9 @@ drive is <filename>/dev/sda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. -</para><para arch="sparc"> - -Sun disk partitions allow for 8 separate partitions (or slices). The -third partition is usually (and is preferred to have) the <quote>Whole -Disk</quote> partition. This partition references all of the sectors of the -disk, and is used by the boot loader (either SILO, or Sun's). +</para> -</para><para arch="s390"> +<para arch="s390"> The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml index cb63a3489..dad9a4307 100644 --- a/en/partitioning/partition-programs.xml +++ b/en/partitioning/partition-programs.xml @@ -128,11 +128,7 @@ includes steps you should take if you are sharing your disk with MacOS. </para> -&partition-hppa.xml; &partition-x86.xml; -&partition-ia64.xml; -&partition-mips.xml; &partition-powerpc.xml; -&partition-sparc.xml; </sect1> diff --git a/en/partitioning/partition/hppa.xml b/en/partitioning/partition/hppa.xml deleted file mode 100644 index 9f4443312..000000000 --- a/en/partitioning/partition/hppa.xml +++ /dev/null @@ -1,22 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="hppa"><title>Partitioning for &arch-title;</title> -<para> - -PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere -in the first 2GB. This is where the boot loader and an optional kernel -and RAMdisk will be stored, so make it big enough for that — at least -4Mb (I like 8–16MB). An additional requirement of the firmware is that -the Linux kernel must reside within the first 2GB of the disk. This -is typically achieved by making the root ext2 partition fit entirely -within the first 2GB of the disk. Alternatively you can create a small -ext2 partition near the start of the disk and mount that on -<filename>/boot</filename>, since that is the directory where the Linux -kernel(s) will be stored. <filename>/boot</filename> needs to be big enough -to hold whatever kernels (and backups) you might wish to load; 25–50MB -is generally sufficient. - -</para> - </sect2> diff --git a/en/partitioning/partition/ia64.xml b/en/partitioning/partition/ia64.xml deleted file mode 100644 index c4b3b6a3a..000000000 --- a/en/partitioning/partition/ia64.xml +++ /dev/null @@ -1,120 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="ia64"><title>Partitioning for &arch-title;</title> -<para> - -The <command>partman</command> disk partitioner is the default -partitioning tool for the installer. -It manages the set of partitions and their mount points to ensure -that the disks and filesystems are properly configured for a successful -installation. It actually uses <command>parted</command> to do the -on-disk partitioning. - -</para> - - <note> - <title>EFI Recognized Formats</title> -<para> - -The IA-64 EFI firmware supports two partition table (or disk label) -formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 -PCs, is no longer recommended for IA-64 systems. Although -the installer also provides <command>cfdisk</command>, -you should only use <ulink url="parted.txt"> -<command>parted</command></ulink> because only it can manage both GPT -and MS-DOS tables correctly. - -</para></note> - -<para> - -The automatic partitioning recipes for <command>partman</command> -allocate an EFI partition as the first partition on the disk. -You can also set up the partition under the <guimenuitem>Guided -partitioning</guimenuitem> from the main menu in a manner similar to -setting up a <emphasis>swap</emphasis> partition. - -</para><para> - -The <command>partman</command> partitioner will handle most disk -layouts. -For those rare cases where it is necessary to manually set up a disk, -you can use the shell as described above and run the -<command>parted</command> utility directly using its command line interface. -Assuming that you want to erase your whole disk and create a GPT table -and some partitions, then something similar to the following command -sequence could be used: - -<informalexample><screen> - mklabel gpt - mkpartfs primary fat 0 50 - mkpartfs primary linux-swap 51 1000 - mkpartfs primary ext2 1001 3000 - set 1 boot on - print - quit -</screen></informalexample> - -This creates a new partition table, and three partitions to be used as -an EFI boot partition, swap space, and a root file system. Finally it -sets the boot flag on the EFI partition. Partitions are specified in -Megabytes, with start and end offsets from the beginning of the disk. -So, for example, above we created a 1999MB ext2 file system starting -at offset 1001MB from the start of the disk. Note that formatting swap -space with <command>parted</command> can take a few minutes to -complete, as it scans the partition for bad blocks. - -</para> - </sect2> - - <sect2 arch="ia64"><title>Boot Loader Partition Requirements</title> -<para> - -ELILO, the IA-64 boot loader, requires a partition containing a FAT -file system with the <userinput>boot</userinput> flag set. -The partition must be big enough to hold the boot loader and any -kernels or RAMdisks you may wish to boot. A minimum size would be -about 20MB, but if you expect to run with multiple kernels, then -128MB might be a better size. - -</para><para> - -The EFI Boot Manager and the EFI Shell fully support the GPT table -so the boot partition does not necessarily have to be the first -partition or even on the same disk. -This is convenient if you should forget to allocate the partition and -only find out after you have formatted the other partitions on your disk(s). -The <command>partman</command> partitioner checks for an EFI partition -at the same time it checks for a properly set up <emphasis>root</emphasis> -partition. -This gives you an opportunity to correct the disk layout before the -package install begins. -The easiest way to correct this omission is to shrink the last partition -of the disk to make enough free space for adding an EFI partition. - -</para><para> - -It is strongly recommended that you allocate the EFI boot partition -on the same disk as the <emphasis>root</emphasis> filesystem. - -</para> - </sect2> - - <sect2 arch="ia64"><title>EFI Diagnostic Partitions</title> -<para> - -The EFI firmware is significantly more sophisticated than the usual -BIOS seen on most x86 PCs. -Some system vendors take advantage of the ability of the EFI to -access files and run programs from a hard disk filesystem to store diagnostics -and EFI based system management utilities on the hard disk. -This is a separate FAT format filesystem on the system disk. -Consult the system documentation and accessories that come with the -system for details. -The easiest time to set up a diagnostics partition is at the same time you -set up the EFI boot partition. - -</para> - </sect2> diff --git a/en/partitioning/partition/mips.xml b/en/partitioning/partition/mips.xml deleted file mode 100644 index fa1f01fc5..000000000 --- a/en/partitioning/partition/mips.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips"><title>Partitioning for &arch-title;</title> -<para> - -SGI machines require an SGI disk label in order to make the system bootable -from hard disk. It can be created in the fdisk expert menu. The thereby -created volume header (partition number 9) should be at least 3MB large. -If the volume header created is too small, you can simply delete -partition number 9 and re-add it with a different size. Note that the -volume header must start at sector 0. - -</para> - </sect2> diff --git a/en/partitioning/partition/powerpc.xml b/en/partitioning/partition/powerpc.xml index ae28f24c7..ebeda02c1 100644 --- a/en/partitioning/partition/powerpc.xml +++ b/en/partitioning/partition/powerpc.xml @@ -2,6 +2,7 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc"><title>Partitioning Newer PowerMacs</title> <para> @@ -55,3 +56,4 @@ not have active MacOS partitions and driver partitions. </para> </sect2> +--> diff --git a/en/partitioning/partition/sparc.xml b/en/partitioning/partition/sparc.xml deleted file mode 100644 index 8e861025e..000000000 --- a/en/partitioning/partition/sparc.xml +++ /dev/null @@ -1,33 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="sparc"><title>Partitioning for &arch-title;</title> -<para> - -Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is -the only kind of partition scheme that the OpenBoot PROM understands, -and so it's the only scheme from which you can boot. The -<keycap>s</keycap> key is used in <command>fdisk</command> to -create Sun disk labels. - -</para><para> - -Furthermore, on &arch-title; disks, make sure your first partition on -your boot disk starts at cylinder 0. While this is required, it also -means that the first partition will contain the partition table and -the boot block, which are the first two sectors of the disk. You must -<emphasis>not</emphasis> put swap on the first partition of the boot -drive, since swap partitions do not preserve the first few sectors of -the partition. You can put Ext2 or UFS partitions there; these will -leave the partition table and the boot block alone. - -</para><para> - -It is also advised that the third partition should be of type <quote>Whole -disk</quote> (type 5), and contain the entire disk (from the first cylinder -to the last). This is simply a convention of Sun disk labels, and -helps the <command>SILO</command> boot loader keep its bearings. - -</para> - </sect2>
\ No newline at end of file |