Updated po|pot files after changings in en

1 files changed, 257 insertions, 141 deletions

diff --git a/po/hu/preparing.po b/po/hu/preparing.po
index 306f19663..ea9a05084 100644
--- a/po/hu/preparing.po
+++ b/po/hu/preparing.po
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-05-27 08:42+0000\n"
+"POT-Creation-Date: 2014-08-03 08:11+0000\n"
 "PO-Revision-Date: 2014-03-09 18:43+0100\n"
 "Last-Translator: Judit Gyimesi <judit.gyimesi.x@gmail.com>\n"
 "Language-Team: Hungarian <debian-l10n-hungarian@lists.debian>\n"
@@ -129,9 +129,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-#| msgid ""
-#| "Locate and/or download the installer software and any specialized driver "
-#| "files your machine requires (except &debian; CD users)."
 msgid ""
 "Locate and/or download the installer software and any specialized driver or "
 "firmware files your machine requires."
@@ -232,11 +229,6 @@ msgstr "Töltsd be az újonnan telepített rendszert az első alkalommal."
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-#| msgid ""
-#| "For &arch-title; you have the option of using <phrase arch=\"x86\">a</"
-#| "phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical "
-#| "version of the installation system. For more information about this "
-#| "graphical installer, see <xref linkend=\"graphical\"/>."
 msgid ""
 "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
 "phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
@@ -296,15 +288,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-#| msgid ""
-#| "One important option during the installation is whether or not to install "
-#| "a graphical desktop environment, consisting of the X Window System and "
-#| "one of the available graphical desktop environments. If you choose not to "
-#| "select the <quote>Desktop environment</quote> task, you will only have a "
-#| "relatively basic, command line driven system. Installing the Desktop "
-#| "environment task is optional because it requires a fairly large amount of "
-#| "disk space, and because many &debian-gnu; systems are servers which don't "
-#| "really have any need for a graphical user interface to do their job."
 msgid ""
 "One important option during the installation is whether or not to install a "
 "graphical desktop environment, consisting of the X Window System and one of "
@@ -327,11 +310,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-#| msgid ""
-#| "Just be aware that the X Window System is completely separate from "
-#| "<classname>debian-installer</classname>, and in fact is much more "
-#| "complicated. Installation and troubleshooting of the X Window System is "
-#| "not within the scope of this manual."
 msgid ""
 "Just be aware that the X Window System is completely separate from "
 "<classname>debian-installer</classname>, and in fact is much more "
@@ -352,17 +330,6 @@ msgstr "Mentsd el a meglévő adataidat!"
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-#| msgid ""
-#| "Before you start, make sure to back up every file that is now on your "
-#| "system. If this is the first time a non-native operating system has been "
-#| "installed on your computer, it's quite likely you will need to re-"
-#| "partition your disk to make room for &debian-gnu;. Anytime you partition "
-#| "your disk, you run a risk of losing everything on the disk, no matter "
-#| "what program you use to do it. The programs used in installation are "
-#| "quite reliable and most have seen years of use; but they are also quite "
-#| "powerful and a false move can cost you. Even after backing up, be careful "
-#| "and think about your answers and actions. Two minutes of thinking can "
-#| "save hours of unnecessary work."
 msgid ""
 "Before you start, make sure to back up every file that is now on your "
 "system. If this is the first time a non-native operating system is going to "
@@ -389,13 +356,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-#| msgid ""
-#| "If you are creating a multi-boot system, make sure that you have the "
-#| "distribution media of any other present operating systems on hand. "
-#| "Especially if you repartition your boot drive, you might find that you "
-#| "have to reinstall your operating system's boot loader, or in many cases "
-#| "the whole operating system itself and all files on the affected "
-#| "partitions."
 msgid ""
 "If you are creating a multi-boot system, make sure that you have the "
 "distribution media of any other present operating systems on hand. Even "
@@ -587,10 +547,6 @@ msgstr "Az egyes hardverekkel adott kézikönyvek."
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-#| msgid ""
-#| "The BIOS setup screens of your computer. You can view these screens when "
-#| "you start your computer by pressing a combination of keys. Check your "
-#| "manual for the combination. Often, it is the <keycap>Delete</keycap> key."
 msgid ""
 "The BIOS setup screens of your computer. You can view these screens when you "
 "start your computer by pressing a combination of keys. Check your manual for "
@@ -643,7 +599,6 @@ msgstr ""
 #. Tag: title
 #: preparing.xml:427
 #, no-c-format
-#| msgid "Hardware Information Needed for an Install"
 msgid "Hardware Information Helpful for an Install"
 msgstr "Egy telepítéshez szükséges hardver adatok"
 
@@ -704,14 +659,12 @@ msgstr "A más rendszereket tartalmazó partíciók."
 #. Tag: entry
 #: preparing.xml:475
 #, no-c-format
-#| msgid "Network Settings"
 msgid "Network interfaces"
 msgstr "Hálózati csatolók"
 
 #. Tag: entry
 #: preparing.xml:476
 #, no-c-format
-#| msgid "Configure one network interface."
 msgid "Type/model of available network interfaces."
 msgstr "Elérhető hálózati csatolók típusa/modellje."
 
@@ -736,7 +689,6 @@ msgstr "Videó kártya"
 #. Tag: entry
 #: preparing.xml:486
 #, no-c-format
-#| msgid "Model and manufacturer."
 msgid "Type/model and manufacturer."
 msgstr "Típus/modell és gyártó."
 
@@ -785,11 +737,6 @@ msgstr "Hardver kompatibilitás"
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-#| msgid ""
-#| "Many brand name products work without trouble on &arch-kernel;. Moreover, "
-#| "hardware support in &arch-kernel; is improving daily. However, &arch-"
-#| "kernel; still does not run as many different types of hardware as some "
-#| "operating systems."
 msgid ""
 "Many products work without trouble on &arch-kernel;. Moreover, hardware "
 "support in &arch-kernel; is improving daily. However, &arch-kernel; still "
@@ -1037,10 +984,6 @@ msgstr "Hálózati beállítások"
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-#| msgid ""
-#| "If your computer is connected to a network 24 hours a day (i.e., an "
-#| "Ethernet or equivalent connection &mdash; not a PPP connection), you "
-#| "should ask your network's system administrator for this information."
 msgid ""
 "If your computer is connected to a fixed network (i.e. an Ethernet or "
 "equivalent connection &mdash; not a dialup/PPP connection) which is "
@@ -1097,11 +1040,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-#| msgid ""
-#| "On the other hand, if your administrator tells you that a DHCP server is "
-#| "available and is recommended, then you don't need this information "
-#| "because the DHCP server will provide it directly to your computer during "
-#| "the installation process."
 msgid ""
 "If the network you are connected to uses DHCP (Dynamic Host Configuration "
 "Protocol) for configuring network settings, you don't need this information "
@@ -1142,21 +1080,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:707
 #, no-c-format
-#| msgid "If you use a wireless network, you should also find out:"
 msgid "If you use a WLAN/WiFi network, you should find out:"
 msgstr "Drótnélküli WLAN/WiFi hálózat esetén ezek is kellenek:"
 
 #. Tag: para
 #: preparing.xml:712
 #, no-c-format
-#| msgid "ESSID of your wireless network."
 msgid "The ESSID (<quote>network name</quote>) of your wireless network."
 msgstr "A drótnélküli hálózathoz tartozó ESSID (<quote>hálózat név</quote>)."
 
 #. Tag: para
 #: preparing.xml:717
 #, no-c-format
-#| msgid "WEP security key (if applicable)."
 msgid "The WEP or WPA/WPA2 security key to access the network (if applicable)."
 msgstr ""
 "WEP vagy WPA/WPA2 biztonsági kulcs a hálózat eléréséhez (ha alkalmazható)."
@@ -1267,7 +1202,6 @@ msgstr "Asztallal"
 #. Tag: entry
 #: preparing.xml:778
 #, no-c-format
-#| msgid "512 megabytes"
 msgid "128 megabytes"
 msgstr "128 megabájt"
 
@@ -1397,16 +1331,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:855
 #, no-c-format
-#| msgid ""
-#| "If you already have an operating system on your system <phrase arch="
-#| "\"x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, "
-#| "Solaris, FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, "
-#| "OS/390, &hellip;) </phrase> and want to stick Debian on the same disk, "
-#| "you will need to repartition the disk. Debian requires its own hard disk "
-#| "partitions. It cannot be installed on Windows or MacOS partitions. It may "
-#| "be able to share some partitions with other Unix systems, but that's not "
-#| "covered here. At the very least you will need a dedicated partition for "
-#| "the Debian root."
 msgid ""
 "If you already have an operating system on your system <phrase arch=\"any-"
 "x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, "
@@ -1431,13 +1355,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:874
 #, no-c-format
-#| msgid ""
-#| "You can find information about your current partition setup by using a "
-#| "partitioning tool for your current operating system<phrase arch=\"x86\">, "
-#| "such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such "
-#| "as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, "
-#| "such as the VM diskmap</phrase>. Partitioning tools always provide a way "
-#| "to show existing partitions without making changes."
 msgid ""
 "You can find information about your current partition setup by using a "
 "partitioning tool for your current operating system<phrase arch=\"any-"
@@ -1542,12 +1459,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-#| msgid ""
-#| "If you are going to install more than one operating system on the same "
-#| "machine, you should install all other system(s) before proceeding with "
-#| "Linux installation. Windows and other OS installations may destroy your "
-#| "ability to start Linux, or encourage you to reformat non-native "
-#| "partitions."
 msgid ""
 "If you are going to install more than one operating system on the same "
 "machine, you should install all other system(s) before proceeding with the "
@@ -1573,16 +1484,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:943
 #, no-c-format
-#| msgid ""
-#| "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-"
-#| "parttype; partitions should appear before all other partitions on the "
-#| "disk, especially MacOS boot partitions. This should be kept in mind when "
-#| "pre-partitioning; you should create a &arch-parttype; placeholder "
-#| "partition to come <emphasis>before</emphasis> the other bootable "
-#| "partitions on the disk. (The small partitions dedicated to Apple disk "
-#| "drivers are not bootable.) You can delete the placeholder with the Debian "
-#| "partition tools later during the actual install, and replace it with "
-#| "&arch-parttype; partitions."
 msgid ""
 "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-"
 "parttype; partitions should appear before all other partitions on the disk, "
@@ -1747,14 +1648,6 @@ msgstr "Telepítés-előtti hardver és operációs rendszer beállítás"
 #. Tag: para
 #: preparing.xml:1107
 #, no-c-format
-#| msgid ""
-#| "This section will walk you through pre-installation hardware setup, if "
-#| "any, that you will need to do prior to installing &debian;. Generally, "
-#| "this involves checking and possibly changing firmware settings for your "
-#| "system. The <quote>firmware</quote> is the core software used by the "
-#| "hardware; it is most critically invoked during the bootstrap process "
-#| "(after power-up). Known hardware issues affecting the reliability of "
-#| "&debian-gnu; on your system are also highlighted."
 msgid ""
 "This section will walk you through pre-installation hardware setup, if any, "
 "that you will need to do prior to installing &debian;. Generally, this "
@@ -1778,13 +1671,6 @@ msgstr "A BIOS beállító menü behívása"
 #. Tag: para
 #: preparing.xml:1124
 #, no-c-format
-#| msgid ""
-#| "BIOS provides the basic functions needed to boot your machine to allow "
-#| "your operating system to access your hardware. Your system probably "
-#| "provides a BIOS setup menu, which is used to configure the BIOS. Before "
-#| "installing, you <emphasis>must</emphasis> ensure that your BIOS is set up "
-#| "correctly; not doing so can lead to intermittent crashes or an inability "
-#| "to install &debian;."
 msgid ""
 "The BIOS provides the basic functions needed to boot your machine and to "
 "allow your operating system to access your hardware. Your system provides a "
@@ -2193,14 +2079,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1367
 #, no-c-format
-#| msgid ""
-#| "Linux on this platform runs either natively on the bare machine, in a so-"
-#| "called LPAR (Logical Partition) or in a virtual machine supplied by the "
-#| "VM system. You can use a boot tape on all of those systems; you may use "
-#| "some other boot media, too, but those may not be generally available. For "
-#| "example, you can use the virtual card reader of a virtual machine, or "
-#| "boot from the HMC (Hardware Management Console) of an LPAR if the HMC and "
-#| "this option is available for you."
 msgid ""
 "Linux on this platform runs either natively on the bare machine, in a so-"
 "called LPAR (Logical Partition) or in a virtual machine supplied by the VM "
@@ -2285,11 +2163,6 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1420
 #, no-c-format
-#| msgid ""
-#| "You need to copy all the files from the <filename>generic</filename> sub-"
-#| "directory to your CMS disk. Be sure to transfer <filename>kernel.debian</"
-#| "filename> and <filename>initrd.debian</filename> in binary mode with a "
-#| "fixed record length of 80 characters."
 msgid ""
 "You need to copy all the files from the <filename>generic</filename> sub-"
 "directory to your CMS disk. Be sure to transfer <filename>kernel.debian</"
@@ -2350,28 +2223,271 @@ msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr "FIXME (javítandó): több információ kell &mdash; egy Redbook-ból?"
 
 #. Tag: title
-#: preparing.xml:1463
+#: preparing.xml:1466
+#, no-c-format
+msgid "ARM firmware"
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1468
+#, no-c-format
+msgid ""
+"As already mentioned before, there is unfortunately no standard for system "
+"firmware on ARM systems. Even the behaviour of different systems which use "
+"nominally the same firmware can be quite different. This results from the "
+"fact that a large part of the devices using the ARM architecture are "
+"embedded systems, for which the manufacturers usually build heavily "
+"customized firmware versions and include device-specific patches. "
+"Unfortunately the manufacturers often do not submit their changes and "
+"extensions back to the mainline firmware developers, so their changes are "
+"not integrated into newer versions of the original firmware."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1480
+#, no-c-format
+msgid ""
+"As a result even newly sold systems often use a firmware that is based on a "
+"years-old manufacturer-modified version of a firmware whose mainline "
+"codebase has evolved a lot further in the meantime and offers additional "
+"features or shows different behaviour in certain aspects. In addition to "
+"that, the naming of onboard devices is not consistent between different "
+"manufacturer-modified versions of the same firmware, therefore it is nearly "
+"impossible to provide usable product-independend instructions for ARM-based "
+"systems."
+msgstr ""
+
+#. Tag: title
+#: preparing.xml:1493
+#, no-c-format
+msgid "Setting the ethernet MAC address in u-boot"
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1494
+#, no-c-format
+msgid ""
+"The MAC address of every ethernet interface should normally be globally "
+"unique, and it technically has to be unique within its ethernet broadcast "
+"domain. To achieve this, the manufacturer usually allocates a block of MAC "
+"addresses from a centrally-administered pool (for which a fee has to be "
+"paid) and preconfigures one of these addresses on each item sold."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1502
+#, no-c-format
+msgid ""
+"In the case of development boards, sometimes the manufacturer wants to avoid "
+"paying these fees and therefore provides no globally unique addresses. In "
+"these cases the users themselves have to define MAC addresses for their "
+"systems. When no MAC address is defined for an ethernet interface, some "
+"network drivers generate a random MAC address that can change on every boot, "
+"and if this happens, network access would be possible even when the user has "
+"not manually set an address, but e.g. assigning semi-static IP addresses by "
+"DHCP based on the MAC address of the requesting client would obviously not "
+"work reliably."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1513
+#, no-c-format
+msgid ""
+"To avoid conflicts with existing officially-assigned MAC addresses, there is "
+"an address pool which is reserved for so-called <quote>locally administered</"
+"quote> addresses. It is defined by the value of two specific bits in the "
+"first byte of the address (the article \"MAC address\" in the English "
+"language Wikipedia gives a good explanation). In practice this means that e."
+"g. any address starting with hexadecimal ca (such as ca:ff:ee:12:34:56) can "
+"be used as a locally administered address."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1523
+#, no-c-format
+msgid ""
+"On systems using u-boot as system firmware, the ethernet MAC address is "
+"placed in the <quote>ethaddr</quote> environment variable. It can be checked "
+"at the u-boot command prompt with the command <quote>printenv ethaddr</"
+"quote> and can be set with the command <quote>setenv ethaddr ca:ff:"
+"ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</"
+"quote> makes the assignment permanent."
+msgstr ""
+
+#. Tag: title
+#: preparing.xml:1534
+#, no-c-format
+msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot"
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1535
+#, no-c-format
+msgid ""
+"On some systems with older u-boot versions there can be problems with "
+"properly relocating the Linux kernel, the initial ramdisk and the device-"
+"tree blob in memory during the boot process. In this case, u-boot shows the "
+"message \"Starting kernel ...\", but the system freezes afterwards without "
+"further output. These issues have been solved with newer u-boot versions "
+"from v2014.07 onwards."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1543
+#, no-c-format
+msgid ""
+"If the system has originally used a u-boot version older than v2014.07 and "
+"has been upgraded to a newer version later, the problem might still occur "
+"even after upgrading u-boot. Upgrading u-boot usually does not modify the "
+"existing u-boot environment variables and the fix requires an additional "
+"environment variable (bootm_size) to be set, which u-boot does automatically "
+"only on fresh installations without existing environment data. It is "
+"possible to manually set bootm_size to the new u-boot's default value by "
+"running the command \"env default bootm_size; saveenv\" at the u-boot prompt."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1554
+#, no-c-format
+msgid ""
+"Another possibility to circumvent relocation-related problems is to run the "
+"command \"setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; saveenv\" "
+"at the u-boot prompt to completely disable the relocation of the initial "
+"ramdisk and the device-tree blob."
+msgstr ""
+
+#. Tag: title
+#: preparing.xml:1564
+#, no-c-format
+msgid "Systems with UEFI firmware"
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1565
+#, no-c-format
+msgid ""
+"UEFI (<quote>Unified Extensible Firmware Interface</quote>) is a new kind of "
+"system firmware that is used on many modern systems and is - among other "
+"uses - intended to replace the classic PC BIOS."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1571
+#, no-c-format
+msgid ""
+"Currently most PC systems that use UEFI also have a so-called "
+"<quote>Compatibility Support Module</quote> (CSM) in the firmware, which "
+"provides excatly the same interfaces to an operating system as a classic PC "
+"BIOS, so that software written for the classic PC BIOS can be used "
+"unchanged. Nonetheless UEFI is intended to one day completely replace the "
+"old PC BIOS without being fully backwards-compatible and there are already a "
+"few systems with UEFI but without CSM."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1581
+#, no-c-format
+msgid ""
+"On systems with UEFI there are a few things to take into consideration when "
+"installing an operating system. The way the firmware loads an operating "
+"system is fundamentally different between the classic BIOS (or UEFI in CSM "
+"mode) and native UEFI. One major difference is the way the harddisk "
+"partitions get recorded on the harddisk. While the classic BIOS and UEFI in "
+"CSM mode use a DOS partition table, native UEFI uses a different "
+"partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a "
+"single disk, for all practical purposes only one of the two can be used and "
+"in case of a multi-boot setup with different operating systems on one disk, "
+"all of them must therefore use the same type of partition table. Booting "
+"from a disk with GPT is only possible in native UEFI mode, but using GPT "
+"becomes more and more common as hard disk sizes grow, because the classic "
+"DOS partition table cannot address disks larger than about 2 Terabytes while "
+"GPT allows for by far larger disks. The other major difference between BIOS "
+"(or UEFI in CSM mode) and native UEFI is from where boot code is loaded and "
+"in which format it has to be, so that different bootloaders are needed for "
+"both systems."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1601
+#, no-c-format
+msgid ""
+"The latter becomes important when booting &d-i; on a UEFI system with CSM "
+"because &d-i; checks whether it was started on a BIOS- or on a native UEFI "
+"system and installs the corresponding bootloader. Normally this simply works "
+"but there can be a problem in multi-boot environments. On some UEFI systems "
+"with CSM the default boot mode for removable devices can be different from "
+"what is actually used when booting from hard disk, so when booting the "
+"installer from a USB stick in a different mode from what is used when "
+"booting another already installed operating system from the hard disk, the "
+"wrong bootloader might be installed and the system might be unbootable after "
+"finishing the installation. When choosing the boot device from a firmware "
+"boot menu, some systems offer two seperate choices for each device, so that "
+"the user can select whether booting shall happen in CSM or in native UEFI "
+"mode."
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1617
+#, no-c-format
+msgid ""
+"Another UEFI-related topic is the so-called <quote>secure boot</quote> "
+"mechanism. Secure boot means a function of UEFI implementations that allows "
+"the firmware to only load and execute code that is cryptographically signed "
+"with certain keys and thereby blocking any (potentially malicious) boot code "
+"that is unsigned or signed with unknown keys. In practice the only key "
+"accepted by default on most UEFI systems with secure boot is a key from "
+"Microsoft used for signing the Windows bootloader. As the boot code used by "
+"&d-i; is not signed by Microsoft, booting the installer requires prior "
+"deactivation of secure boot in case it is enabled. Secure boot is often "
+"enabled by default on systems that come preinstalled with a 64Bit version of "
+"Windows 8 and there is unfortunately no standard where in the UEFI setup it "
+"can be disabled. On some systems, the option to disable secure boot is only "
+"made visible when a BIOS password has been set by the user, so if you have a "
+"system with secure boot enabled, but cannot find an option to disable it, "
+"try setting a BIOS password, powercycle the machine and look again for an "
+"appropriate option."
+msgstr ""
+
+#. Tag: title
+#: preparing.xml:1639
+#, no-c-format
+msgid "Disabling the Windows 8 <quote>fast boot</quote> feature"
+msgstr ""
+
+#. Tag: para
+#: preparing.xml:1640
+#, no-c-format
+msgid ""
+"Windows 8 offers a feature called \"fast boot\" to cut down the time needed "
+"to boot itself. Technically, when this feature is enabled, Windows 8 does "
+"not do a real shutdown and a real cold boot afterwards when ordered to shut "
+"down, but instead does something resembling a partial suspend to disk to "
+"reduce the \"boot\" time. As long as Windows 8 is the only operating system "
+"on the machine, this is unproblematic, but it can result in problems and "
+"data loss when you have a dual boot setup in which another operating system "
+"accesses the same filesystems as Windows 8 does. In that case the real state "
+"of the filesystem can be different from what Windows 8 believes it to be "
+"after the \"boot\" and this could cause filesystem corruption upon further "
+"write accesses to the filesystem. Therefore in a dual boot setup, to avoid "
+"filesystem corruption the \"fast boot\" feature has to be disabled within "
+"Windows."
+msgstr ""
+
+#. Tag: title
+#: preparing.xml:1658
 #, no-c-format
 msgid "Hardware Issues to Watch Out For"
 msgstr "Kivédendő hardver gondok"
 
 #. Tag: title
-#: preparing.xml:1466
+#: preparing.xml:1661
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr "USB BIOS támogatás és billentyűzetek"
 
 #. Tag: para
-#: preparing.xml:1467
+#: preparing.xml:1662
 #, no-c-format
-#| msgid ""
-#| "If you have no AT-style keyboard and only a USB model, you may need to "
-#| "enable legacy AT keyboard emulation in your BIOS setup. Only do this if "
-#| "the installation system fails to use your keyboard in USB mode. "
-#| "Conversely, for some systems (especially laptops) you may need to disable "
-#| "legacy USB support if your keyboard does not respond. Consult your main "
-#| "board manual and look in the BIOS for <quote>Legacy keyboard emulation</"
-#| "quote> or <quote>USB keyboard support</quote> options."
 msgid ""
 "If you have no PS/2-style keyboard, but only a USB model, on some very old "
 "PCs you may need to enable legacy keyboard emulation in your BIOS setup to "
@@ -2389,13 +2505,13 @@ msgstr ""
 "támogatás</quote> opciókat."
 
 #. Tag: title
-#: preparing.xml:1480
+#: preparing.xml:1675
 #, no-c-format
 msgid "Display-visibility on OldWorld Powermacs"
 msgstr "Kijelző-láthatóság régi Powermaceken"
 
 #. Tag: para
-#: preparing.xml:1482
+#: preparing.xml:1677
 #, no-c-format
 msgid ""
 "Some OldWorld Powermacs, most notably those with the <quote>control</quote> "