Update of POT and PO files for the manual

1 files changed, 41 insertions, 41 deletions

diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index b4a5fad12..071a2c354 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-19 13:45+0000\n"
+"POT-Creation-Date: 2006-04-28 19:34+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"
@@ -617,14 +617,14 @@ msgstr ""
 #: partitioning.xml:572
 #, no-c-format
 #. Tag: para
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition a Hard Disk</guimenuitem>. If the one which is run by default isn't the one you want, quit the partitioner, go to the shell (<userinput>tty2</userinput>) by pressing <keycap>Alt</keycap> and <keycap>F2</keycap> keys together, and manually type in the name of the program you want to use (and arguments, if any). Then skip the <guimenuitem>Partition a Hard Disk</guimenuitem> step in <command>debian-installer</command> and continue to the next step."
+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 ""
 
-#: partitioning.xml:583
+#: partitioning.xml:579
 #, no-c-format
 #. Tag: para
 msgid ""
-      "If you will be working with more than 20 partitions on your ide disk, you will need to create devices for partitions 21 and beyond. The next step of initializing the partition will fail unless a proper device is present. As an example, here are commands you can use in <userinput>tty2</userinput> or under Execute A Shell to add a device so the 21st partition can be initialized: <informalexample><screen>\n"
+      "If you will be working with more than 20 partitions on your ide disk, you will need to create devices for partitions 21 and beyond. The next step of initializing the partition will fail unless a proper device is present. As an example, here are commands you can use in <userinput>tty2</userinput> or under <guimenuitem>Execute a shell</guimenuitem> to add a device so the 21st partition can be initialized: <informalexample><screen>\n"
       "# cd /dev\n"
       "# mknod hda21 b 3 21\n"
       "# chgrp disk hda21\n"
@@ -637,127 +637,127 @@ msgid ""
       "</screen></informalexample> <phrase arch=\"i386\">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase>"
 msgstr ""
 
-#: partitioning.xml:602
+#: partitioning.xml:598
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:618 partitioning.xml:678 partitioning.xml:702 partitioning.xml:798 partitioning.xml:917 partitioning.xml:994
+#: partitioning.xml:614 partitioning.xml:674 partitioning.xml:698 partitioning.xml:794 partitioning.xml:913 partitioning.xml:990
 #, no-c-format
 #. Tag: title
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
-#: partitioning.xml:619
+#: partitioning.xml:615
 #, no-c-format
 #. Tag: para
 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 partman can convert it to use a disk label."
 msgstr ""
 
-#: partitioning.xml:630
+#: partitioning.xml:626
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:637
+#: partitioning.xml:633
 #, no-c-format
 #. Tag: para
 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), it is suggested that you do <emphasis>not</emphasis> make the third partition contain the whole disk. This is not required by <command>aboot</command>, and in fact, it may lead to confusion since the <command>swriteboot</command> utility used to install <command>aboot</command> in the boot sector will complain about a partition overlapping with the boot block."
 msgstr ""
 
-#: partitioning.xml:648
+#: partitioning.xml:644
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:660
+#: partitioning.xml:656
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:679
+#: partitioning.xml:675
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:703
+#: partitioning.xml:699
 #, no-c-format
 #. Tag: para
 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 to partition manually and then simply select an existing partition and change its size."
 msgstr ""
 
-#: partitioning.xml:712
+#: partitioning.xml:708
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:723
+#: partitioning.xml:719
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:734
+#: partitioning.xml:730
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:744
+#: partitioning.xml:740
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:752
+#: partitioning.xml:748
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:766
+#: partitioning.xml:762
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:778
+#: partitioning.xml:774
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:800
+#: partitioning.xml:796
 #, no-c-format
 #. Tag: para
 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 is properly configured for a successful installation. It actually uses the <command>parted</command> to do the on-disk partitioning."
 msgstr ""
 
-#: partitioning.xml:812
+#: partitioning.xml:808
 #, no-c-format
 #. Tag: title
 msgid "EFI Recognized Formats"
 msgstr ""
 
-#: partitioning.xml:813
+#: partitioning.xml:809
 #, no-c-format
 #. Tag: para
 msgid "The IA64 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 IA64 systems. Although the installer also provides the <command>cfdisk</command>, you should only use the <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
 msgstr ""
 
-#: partitioning.xml:825
+#: partitioning.xml:821
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:833
+#: partitioning.xml:829
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -772,97 +772,97 @@ msgid ""
       "</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."
 msgstr ""
 
-#: partitioning.xml:858
+#: partitioning.xml:854
 #, no-c-format
 #. Tag: title
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
-#: partitioning.xml:860
+#: partitioning.xml:856
 #, no-c-format
 #. Tag: para
 msgid "ELILO, the ia64 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 ""
 
-#: partitioning.xml:869
+#: partitioning.xml:865
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:884
+#: partitioning.xml:880
 #, no-c-format
 #. Tag: para
 msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
-#: partitioning.xml:893
+#: partitioning.xml:889
 #, no-c-format
 #. Tag: title
 msgid "EFI Diagnostic Partitions"
 msgstr ""
 
-#: partitioning.xml:895
+#: partitioning.xml:891
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:918
+#: partitioning.xml:914
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:935
+#: partitioning.xml:931
 #, no-c-format
 #. Tag: title
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
-#: partitioning.xml:936
+#: partitioning.xml:932
 #, no-c-format
 #. Tag: para
 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 be 800KB 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 ""
 
-#: partitioning.xml:949
+#: partitioning.xml:945
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:956
+#: partitioning.xml:952
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:966
+#: partitioning.xml:962
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:978
+#: partitioning.xml:974
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:995
+#: partitioning.xml:991
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:1003
+#: partitioning.xml:999
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: partitioning.xml:1014
+#: partitioning.xml:1010
 #, no-c-format
 #. Tag: para
 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."