[SILENT_COMMIT] Update of POT and PO files for the manual

1 files changed, 69 insertions, 81 deletions

diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index f740f293d..b791cbef9 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2007-08-06 18:17+0000\n"
+"POT-Creation-Date: 2008-09-28 00:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -437,329 +437,317 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:372
 #, no-c-format
-msgid "The first XT disk is named <filename>/dev/xda</filename>."
-msgstr ""
-
-#. Tag: para
-#: partitioning.xml:377
-#, no-c-format
-msgid "The second XT disk is named <filename>/dev/xdb</filename>."
-msgstr ""
-
-#. Tag: para
-#: partitioning.xml:382
-#, no-c-format
 msgid "The first ACSI device is named <filename>/dev/ada</filename>, the second is named <filename>/dev/adb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:391
+#: partitioning.xml:381
 #, no-c-format
 msgid "The first DASD device is named <filename>/dev/dasda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:397
+#: partitioning.xml:387
 #, no-c-format
 msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:405
+#: partitioning.xml:395
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:412
+#: partitioning.xml:402
 #, no-c-format
 msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:423
+#: partitioning.xml:413
 #, no-c-format
 msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:430
+#: partitioning.xml:420
 #, no-c-format
 msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:441
+#: partitioning.xml:431
 #, no-c-format
 msgid "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal SCSI disk. To make identification of the drive simpler the installation software will create a symbolic link to the appropriate device and name it <filename>/dev/sfd0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:448
+#: partitioning.xml:438
 #, no-c-format
 msgid "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)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:455
+#: partitioning.xml:445
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:470
+#: partitioning.xml:460
 #, no-c-format
 msgid "Debian Partitioning Programs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:471
+#: partitioning.xml:461
 #, no-c-format
 msgid "Several varieties of partitioning programs have been adapted by Debian developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:483
+#: partitioning.xml:473
 #, no-c-format
 msgid "partman"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:484
+#: partitioning.xml:474
 #, no-c-format
 msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:495
+#: partitioning.xml:485
 #, no-c-format
 msgid "fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:496
+#: partitioning.xml:486
 #, no-c-format
 msgid "The original Linux disk partitioner, good for gurus."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:500
+#: partitioning.xml:490
 #, no-c-format
 msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:512
+#: partitioning.xml:502
 #, no-c-format
 msgid "cfdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:513
+#: partitioning.xml:503
 #, no-c-format
 msgid "A simple-to-use, full-screen disk partitioner for the rest of us."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:517
+#: partitioning.xml:507
 #, no-c-format
 msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:526
+#: partitioning.xml:516
 #, no-c-format
 msgid "atari-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:527
+#: partitioning.xml:517
 #, no-c-format
 msgid "Atari-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:535
+#: partitioning.xml:525
 #, no-c-format
 msgid "amiga-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:536
+#: partitioning.xml:526
 #, no-c-format
 msgid "Amiga-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:544
+#: partitioning.xml:534
 #, no-c-format
 msgid "mac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:545
+#: partitioning.xml:535
 #, no-c-format
 msgid "Mac-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:553
+#: partitioning.xml:543
 #, no-c-format
 msgid "pmac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:554
+#: partitioning.xml:544
 #, no-c-format
 msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:563
+#: partitioning.xml:553
 #, no-c-format
 msgid "fdasd"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:564
+#: partitioning.xml:554
 #, no-c-format
 msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:575
+#: partitioning.xml:565
 #, no-c-format
 msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:582
+#: partitioning.xml:572
 #, no-c-format
 msgid "Remember to mark your boot partition as <quote>Bootable</quote>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:585
+#: partitioning.xml:575
 #, no-c-format
 msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:601 partitioning.xml:662 partitioning.xml:686 partitioning.xml:783 partitioning.xml:897 partitioning.xml:974
+#: partitioning.xml:591 partitioning.xml:652 partitioning.xml:676 partitioning.xml:773 partitioning.xml:887 partitioning.xml:964
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:602
+#: partitioning.xml:592
 #, no-c-format
 msgid "Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables &mdash; see <xref linkend=\"alpha-firmware\"/>.) As a result, <command>partman</command> creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before <command>partman</command> can convert it to use a disk label."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:613
+#: partitioning.xml:603
 #, no-c-format
 msgid "If you have chosen to use <command>fdisk</command> to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the <quote>b</quote> command to enter disk label mode."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:620
+#: partitioning.xml:610
 #, no-c-format
 msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the third partition as a <quote>whole disk</quote> partition (i.e. with start and end sectors to span the whole disk), as this renders the disk incompatible with the tools used to make it bootable with aboot. This means that the disk configured by the installer for use as the Debian boot disk will be inaccessible to the operating systems mentioned earlier."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:632
+#: partitioning.xml:622
 #, no-c-format
 msgid "Also, because <command>aboot</command> is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you <emphasis>must</emphasis> leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using <command>partman</command>, a small partition will still be created for <command>aboot</command> for convenience reasons."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:644
+#: partitioning.xml:634
 #, no-c-format
 msgid "For ARC installations, you should make a small FAT partition at the beginning of the disk to contain <command>MILO</command> and <command>linload.exe</command> &mdash; 5 megabytes should be sufficient, see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using <command>mkdosfs</command> before attempting to install the boot loader."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:663
+#: partitioning.xml:653
 #, no-c-format
 msgid "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 &mdash; at least 4Mb (I like 8&ndash;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&ndash;50MB is generally sufficient."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:687
+#: partitioning.xml:677
 #, no-c-format
 msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:697
+#: partitioning.xml:687
 #, no-c-format
 msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief overview to help you plan most situations."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:708
+#: partitioning.xml:698
 #, no-c-format
 msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:719
+#: partitioning.xml:709
 #, no-c-format
 msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:729
+#: partitioning.xml:719
 #, no-c-format
 msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:737
+#: partitioning.xml:727
 #, no-c-format
 msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:751
+#: partitioning.xml:741
 #, no-c-format
 msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:763
+#: partitioning.xml:753
 #, no-c-format
 msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:784
+#: partitioning.xml:774
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:796
+#: partitioning.xml:786
 #, no-c-format
 msgid "EFI Recognized Formats"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:797
+#: partitioning.xml:787
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:809
+#: partitioning.xml:799
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:817
+#: partitioning.xml:807
 #, no-c-format
 msgid ""
       "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>\n"
@@ -774,97 +762,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:842
+#: partitioning.xml:832
 #, no-c-format
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:843
+#: partitioning.xml:833
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:852
+#: partitioning.xml:842
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:867
+#: partitioning.xml:857
 #, no-c-format
 msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:875
+#: partitioning.xml:865
 #, no-c-format
 msgid "EFI Diagnostic Partitions"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:876
+#: partitioning.xml:866
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:898
+#: partitioning.xml:888
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:915
+#: partitioning.xml:905
 #, no-c-format
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:916
+#: partitioning.xml:906
 #, no-c-format
 msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:929
+#: partitioning.xml:919
 #, no-c-format
 msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:936
+#: partitioning.xml:926
 #, no-c-format
 msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:946
+#: partitioning.xml:936
 #, no-c-format
 msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:958
+#: partitioning.xml:948
 #, no-c-format
 msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:975
+#: partitioning.xml:965
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:983
+#: partitioning.xml:973
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:994
+#: partitioning.xml:984
 #, no-c-format
 msgid "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."
 msgstr ""