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

1 files changed, 80 insertions, 80 deletions

diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 0b7aedac2..31dbf6fa8 100644
--- a/po/pot/using-d-i.pot
+++ b/po/pot/using-d-i.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-06-10 22:49+0000\n"
+"POT-Creation-Date: 2007-07-26 04:01+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"
@@ -1796,125 +1796,125 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2276
 #, no-c-format
-msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use <phrase condition=\"etch\">devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names,</phrase> <phrase condition=\"lenny\">traditional device names</phrase> such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2288
+#: using-d-i.xml:2290
 #, no-c-format
 msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into Debian!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2304
+#: using-d-i.xml:2306
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2306
+#: using-d-i.xml:2308
 #, no-c-format
 msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2322
+#: using-d-i.xml:2324
 #, no-c-format
 msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2334
+#: using-d-i.xml:2336
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2336
+#: using-d-i.xml:2338
 #, no-c-format
 msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2351
+#: using-d-i.xml:2353
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2353
+#: using-d-i.xml:2355
 #, no-c-format
 msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2375
+#: using-d-i.xml:2377
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2376
+#: using-d-i.xml:2378
 #, no-c-format
 msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2385
+#: using-d-i.xml:2387
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2386
+#: using-d-i.xml:2388
 #, no-c-format
 msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2396
+#: using-d-i.xml:2398
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2397
+#: using-d-i.xml:2399
 #, no-c-format
 msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2409
+#: using-d-i.xml:2411
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2410
+#: using-d-i.xml:2412
 #, no-c-format
 msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2420
+#: using-d-i.xml:2422
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2421
+#: using-d-i.xml:2423
 #, no-c-format
 msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2441
+#: using-d-i.xml:2443
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2442
+#: using-d-i.xml:2444
 #, no-c-format
 msgid ""
       "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
@@ -1927,61 +1927,61 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2461
+#: using-d-i.xml:2463
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2462
+#: using-d-i.xml:2464
 #, no-c-format
 msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2470
+#: using-d-i.xml:2472
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2471
+#: using-d-i.xml:2473
 #, no-c-format
 msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2479 using-d-i.xml:2548
+#: using-d-i.xml:2481 using-d-i.xml:2550
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2480
+#: using-d-i.xml:2482
 #, no-c-format
 msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2488
+#: using-d-i.xml:2490
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2489
+#: using-d-i.xml:2491
 #, no-c-format
 msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2510
+#: using-d-i.xml:2512
 #, no-c-format
 msgid "<command>delo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2511
+#: using-d-i.xml:2513
 #, no-c-format
 msgid ""
       "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n"
@@ -1990,265 +1990,265 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2530
+#: using-d-i.xml:2532
 #, no-c-format
 msgid "<replaceable>#</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2531
+#: using-d-i.xml:2533
 #, no-c-format
 msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2539
+#: using-d-i.xml:2541
 #, no-c-format
 msgid "<replaceable>id</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2540
+#: using-d-i.xml:2542
 #, no-c-format
 msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2549
+#: using-d-i.xml:2551
 #, no-c-format
 msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2557
+#: using-d-i.xml:2559
 #, no-c-format
 msgid "name"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2558
+#: using-d-i.xml:2560
 #, no-c-format
 msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2568
+#: using-d-i.xml:2570
 #, no-c-format
 msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use"
 msgstr ""
 
 #. Tag: screen
-#: using-d-i.xml:2574
+#: using-d-i.xml:2576
 #, no-c-format
 msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2584
+#: using-d-i.xml:2586
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2585
+#: using-d-i.xml:2587
 #, no-c-format
 msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2603
+#: using-d-i.xml:2605
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2604
+#: using-d-i.xml:2606
 #, no-c-format
 msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2620
+#: using-d-i.xml:2622
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2621
+#: using-d-i.xml:2623
 #, no-c-format
 msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2638
+#: using-d-i.xml:2640
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2640
+#: using-d-i.xml:2642
 #, no-c-format
 msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2665
+#: using-d-i.xml:2667
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2667
+#: using-d-i.xml:2669
 #, no-c-format
 msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2676
+#: using-d-i.xml:2678
 #, no-c-format
 msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2693
+#: using-d-i.xml:2695
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2694
+#: using-d-i.xml:2696
 #, no-c-format
 msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2706
+#: using-d-i.xml:2708
 #, no-c-format
 msgid "Finish the Installation and Reboot"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2708
+#: using-d-i.xml:2710
 #, no-c-format
 msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2715
+#: using-d-i.xml:2717
 #, no-c-format
 msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2729
+#: using-d-i.xml:2731
 #, no-c-format
 msgid "Miscellaneous"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2730
+#: using-d-i.xml:2732
 #, no-c-format
 msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2743
+#: using-d-i.xml:2745
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2745
+#: using-d-i.xml:2747
 #, no-c-format
 msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2752
+#: using-d-i.xml:2754
 #, no-c-format
 msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2772
+#: using-d-i.xml:2774
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2774
+#: using-d-i.xml:2776
 #, no-c-format
 msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2792
+#: using-d-i.xml:2794
 #, no-c-format
 msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2800
+#: using-d-i.xml:2802
 #, no-c-format
 msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2809
+#: using-d-i.xml:2811
 #, no-c-format
 msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2816
+#: using-d-i.xml:2818
 #, no-c-format
 msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2822
+#: using-d-i.xml:2824
 #, no-c-format
 msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2837
+#: using-d-i.xml:2839
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2839
+#: using-d-i.xml:2841
 #, no-c-format
 msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2849
+#: using-d-i.xml:2851
 #, no-c-format
 msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2862
+#: using-d-i.xml:2864
 #, no-c-format
 msgid "For installations on &arch-title;, this is the default method after setting up the network."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2867
+#: using-d-i.xml:2869
 #, no-c-format
 msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2879
+#: using-d-i.xml:2881
 #, no-c-format
 msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2885
+#: using-d-i.xml:2887
 #, no-c-format
 msgid ""
       "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
@@ -2257,25 +2257,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2902
+#: using-d-i.xml:2904
 #, no-c-format
 msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2911
+#: using-d-i.xml:2913
 #, no-c-format
 msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2921
+#: using-d-i.xml:2923
 #, no-c-format
 msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2929
+#: using-d-i.xml:2931
 #, no-c-format
 msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated."
 msgstr ""