diff options
44 files changed, 331 insertions, 331 deletions
diff --git a/build/entities/tftp-images.ent b/build/entities/tftp-images.ent index c1ae58a32..d304a230a 100644 --- a/build/entities/tftp-images.ent +++ b/build/entities/tftp-images.ent @@ -65,7 +65,7 @@ '> <!ENTITY armmp-uboot-img ' -<ulink url="&downloadable-file;images/u-boot/">.../images/u-boot/</ulink> +<ulink url="&downloadable-file;images/U-Boot/">.../images/U-Boot/</ulink> '> <!ENTITY armmp-netboot-sd-img ' diff --git a/cs/hardware/supported/arm.xml b/cs/hardware/supported/arm.xml index c61545ae1..bae8407aa 100644 --- a/cs/hardware/supported/arm.xml +++ b/cs/hardware/supported/arm.xml @@ -253,8 +253,8 @@ sun<replaceable>X</replaceable>i. Použití lokálního displeje bez nativních ovladačů je technicky možné přes infrastrukturu <quote>simplefb</quote>, která spoléhá na to, že -se o inicializaci zobrazovacího hardwaru postará zavaděč u-boot. To -ale verze u-bootu dodávaná s &debian;em 8 nepodporuje. +se o inicializaci zobrazovacího hardwaru postará zavaděč U-Boot. To +ale verze U-Bootu dodávaná s &debian;em 8 nepodporuje. </para></listitem> </varlistentry> diff --git a/cs/install-methods/download/arm.xml b/cs/install-methods/download/arm.xml index 10a184d99..07f2fe558 100644 --- a/cs/install-methods/download/arm.xml +++ b/cs/install-methods/download/arm.xml @@ -106,7 +106,7 @@ získat z &armmp-hd-media-tarball; </para><para> -Obrazy u-bootu pro nejrůznější armhf platformy jsou dostupné na +Obrazy U-Bootu pro nejrůznější armhf platformy jsou dostupné na &armmp-uboot-img;. </para> diff --git a/cs/using-d-i/modules/arm/flash-kernel-installer.xml b/cs/using-d-i/modules/arm/flash-kernel-installer.xml index bcdc54fb8..3296f2b2b 100644 --- a/cs/using-d-i/modules/arm/flash-kernel-installer.xml +++ b/cs/using-d-i/modules/arm/flash-kernel-installer.xml @@ -24,7 +24,7 @@ flash paměti! </para><para> -Systémy ARM, které používají jako systémový firmware u-boot, zavádí +Systémy ARM, které používají jako systémový firmware U-Boot, zavádí jádro a ramdisk z externího média, jako jsou MMC/SD karty, zařízení USB mass storage nebo pevné disky IDE/SATA. V těchto případech vygeneruje flash-kernel příslušný zaváděcí skript, který umožní diff --git a/de/boot-installer/arm.xml b/de/boot-installer/arm.xml index 4dfef6726..fc64aa770 100644 --- a/de/boot-installer/arm.xml +++ b/de/boot-installer/arm.xml @@ -13,11 +13,11 @@ Initial-Ramdisk (<quote>uInitrd</quote>). </para> <para> - uImage/uInitrd sind Image-Formate, die für die u-boot-Firmware + uImage/uInitrd sind Image-Formate, die für die U-Boot-Firmware ausgelegt wurden, welche auf vielen ARM-basierten Systemen - eingesetzt ist. Ältere u-boot-Versionen können nur Dateien + eingesetzt ist. Ältere U-Boot-Versionen können nur Dateien im uImage-/uInitrd-Format booten, daher werden diese Formate oft - auf älteren armel-Systemen genutzt. Neuere u-boot-Versionen können - + auf älteren armel-Systemen genutzt. Neuere U-Boot-Versionen können - neben uImage/uInitrd - auch Standard-Linux-Kernel- und Ramdisk-Images booten, aber die Befehlssyntax dafür ist etwas anders als beim Booten von uImages. @@ -37,9 +37,9 @@ &boot-installer-intro-net.xml; <sect3 arch="arm" id="boot-tftp-uboot"> - <title>TFTP-Boot in u-boot</title> + <title>TFTP-Boot in U-Boot</title> <para> - Das Booten von Systemen über das Netzwerk mittels der u-boot-Firmware + Das Booten von Systemen über das Netzwerk mittels der U-Boot-Firmware erfordert drei Schritte: a) Konfigurieren des Netzwerks, b) Laden der Images (Kernel/Initial-Ramdisk/dtb) in den Speicher und c) das eigentliche Ausführen des vorher geladenen Codes. @@ -75,7 +75,7 @@ saveenv Regel, welche Adresse hierfür verwendet werden muss. </para> <para> - Auf einigen Systemen legt u-boot einige Umgebungsvariablen mit + Auf einigen Systemen legt U-Boot einige Umgebungsvariablen mit passenden Ladeadressen an: kernel_addr_r, ramdisk_addr_r und fdt_addr_r. Sie können überprüfen, ob diese definiert sind, indem Sie dies ausführen: @@ -107,7 +107,7 @@ tftpboot ${ramdisk_addr_r} <dateiname des initial-ramdisk-images> </para> <para> Der dritte Schritt ist das Setzen der Kernel-Befehlszeile - und das eigentliche Ausführen des geladenen Codes. u-boot + und das eigentliche Ausführen des geladenen Codes. U-Boot übergibt den Inhalt der Umgebungsvariable <quote>bootargs</quote> als Befehlszeile an den Kernel; also können alle Parameter für den Kernel und den Installer - wie z.B. die Konsolen-Gerätedatei @@ -131,7 +131,7 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} <para> Beachten Sie: wenn Sie Standard-Linux-Images booten, ist es wichtig, dass das Initial-Ramdisk-Image nach dem Kernel und der - DTB geladen wird, da u-boot die filesize-Variable (Dateigröße) + DTB geladen wird, da U-Boot die filesize-Variable (Dateigröße) auf die Größe der letzten geladenen Datei setzt und der bootz-Befehl benötigt die Größe des Ramdisk-Images, um korrekt zu arbeiten. Beim Booten eines plattformspezifischen Kernels, also @@ -142,15 +142,15 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} </sect2> <sect2 arch="arm" id="boot-hd-media"> - <title>Booten von USB-Stick in u-boot</title> + <title>Booten von USB-Stick in U-Boot</title> <para> - Viele moderne Versionen von u-boot haben USB-Unterstützung und + Viele moderne Versionen von U-Boot haben USB-Unterstützung und erlauben das Booten von USB-Massenspeicher-Geräten wie z.B. USB-Sticks. Unglücklicherweise können sich die genauen Schritte, die dazu nötig sind, von Gerät zu Gerät ein wenig unterscheiden. </para> <para> - In u-boot v2014.10 wurde das grundlegende Handling für eine + In U-Boot v2014.10 wurde das grundlegende Handling für eine Kommandozeile sowie ein Rahmenwerk für automatisches Booten (autoboot) eingeführt. Dies erlaubt die Erzeugung generischer Boot-Images, die auf jedem System funktionieren, das dieses Rahmenwerk @@ -163,28 +163,28 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} zu erstellen, entpacken Sie das hd-media-Tarball-Archiv (Näheres in <xref linkend="where-files"/>) auf einen USB-Stick, der mit einem Dateisystem formatiert ist, welches von der - u-boot-Version auf Ihrem Gerät unterstützt wird. - Bei neueren u-boot-Versionen sollten FAT16, FAT32, ext2, ext3 + U-Boot-Version auf Ihrem Gerät unterstützt wird. + Bei neueren U-Boot-Versionen sollten FAT16, FAT32, ext2, ext3 und ext4 normalerweise funktionieren. Kopieren Sie dann auch die ISO-Image-Datei der ersten &debian;-Installations-CD oder -DVD auf den Stick. </para> <para> - Das autoboot-Rahmenwerk in modernen u-boot-Versionen funktioniert + Das autoboot-Rahmenwerk in modernen U-Boot-Versionen funktioniert ähnlich wie die Optionen für die Bootreihenfolge in einem PC-Bios, d.h. auf verschiedenen möglichen Boot-Geräten wird der Reihe nach nach einem gültigen Boot-Image gesucht und das erste gefundene wird gestartet. Wenn kein Betriebssystem installiert ist, sollte das Starten des Systems mit eingestecktem USB-Stick den Installer booten. Sie können den USB-Boot-Prozess auch zu jeder Zeit vom - u-boot-Prompt aus anstoßen, indem Sie den + U-Boot-Prompt aus anstoßen, indem Sie den <quote>run bootcmd_usb0</quote>-Befehl ausführen. </para> <para> Ein Problem, das beim Booten von einem USB-Stick bei Nutzung der seriellen Konsole auftreten könnte, ist eine nicht passende - Konsolenbaudrate. Wenn die console-Variable in u-boot definiert + Konsolenbaudrate. Wenn die console-Variable in U-Boot definiert ist, wird das Boot-Skript des &d-i; diese automatisch an den Kernel weiterleiten, um das primäre Konsolengerät und - falls anwendbar - die Baudrate einzustellen. Unglücklicherweise @@ -194,8 +194,8 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} anderen hingegen lediglich den Gerätenamen (z.B. <quote>console=ttyS0</quote>). In letzterem Fall kann es zu einer verstümmelten Konsolenausgabe - kommen, wenn die Standard-Baudrate bei u-boot und dem Kernel - nicht übereinstimmt. Moderne u-boot-Versionen verwenden oft + kommen, wenn die Standard-Baudrate bei U-Boot und dem Kernel + nicht übereinstimmt. Moderne U-Boot-Versionen verwenden oft eine Geschwindigkeit von 115200 Baud, während beim Kernel noch der alte traditionelle Wert von 9600 Baud voreingestellt ist. Falls dies passiert, sollten Sie die console-Variable händisch @@ -209,7 +209,7 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} <title>Verwenden von vorbereiteten (pre-built) SD-Karten-Images mit dem Installer</title> <para> Für eine Reihe von Systemen bietet Debian SD-Karten-Images an, - die sowohl u-boot wie auch den &d-i; enthalten. Diese Images gibt es + die sowohl U-Boot wie auch den &d-i; enthalten. Diese Images gibt es in zwei Varianten - eine für das Herunterladen der Software-Pakete über das Netzwerk (verfügbar unter &armmp-netboot-sd-img;) und die andere für Offline-Installationen ohne Internet-Verbindung, die diff --git a/de/hardware/supported/arm.xml b/de/hardware/supported/arm.xml index 036213416..b14176ba8 100644 --- a/de/hardware/supported/arm.xml +++ b/de/hardware/supported/arm.xml @@ -281,8 +281,8 @@ Verwendung des Multiplattform-Kernels (armmp): <quote>simplefb</quote>-Infrastruktur im Mainline-Kernel technisch gesehen auch ohne native Display-Treiber möglich. <quote>simplefb</quote> ist dabei für die Initialisierung - der Display-Hardware auf den <quote>u-boot</quote>-Bootloader - angewiesen, allerdings wird dies durch die u-boot-Version in + der Display-Hardware auf den <quote>U-Boot</quote>-Bootloader + angewiesen, allerdings wird dies durch die U-Boot-Version in &debian; 8 nicht unterstützt. </para> </listitem> diff --git a/de/using-d-i/modules/arm/flash-kernel-installer.xml b/de/using-d-i/modules/arm/flash-kernel-installer.xml index b67a8bb93..53c79fe99 100644 --- a/de/using-d-i/modules/arm/flash-kernel-installer.xml +++ b/de/using-d-i/modules/arm/flash-kernel-installer.xml @@ -28,7 +28,7 @@ auszuführen bedeutet, dass der vorherige Inhalt des Flash-Speichers </para><para> -Bei ARM-Systemen, die u-boot als System-Firmware nutzen und Kernel +Bei ARM-Systemen, die U-Boot als System-Firmware nutzen und Kernel sowie Initial-Ramdisk von einem externen Speichermedium (wie MMC-/SD-Karte, USB-Speicher oder IDE-/SATA-Festplatte) booten, generiert flash-kernel ein passendes Boot-Skript, um das automatische Booten ohne manuelles diff --git a/debian/changelog b/debian/changelog index 1e72f841c..e525ae2fe 100644 --- a/debian/changelog +++ b/debian/changelog @@ -5,9 +5,9 @@ installation-guide (20150324) UNRELEASED; urgency=medium * Add missing "warning" icon. [ Karsten Merker ] - * Add a "Debian-provided u-boot (system firmware) images" subsection + * Add a "Debian-provided U-Boot (system firmware) images" subsection in the "Pre-Installation Hardware and Operating System Setup" section - and add a link to the u-boot images in the "Downloading Files from + and add a link to the U-Boot images in the "Downloading Files from Debian Mirrors" section. * Add a "Using pre-built SD-card images with the installer" subsection in the "Booting the Installer on ARM" section. @@ -64,8 +64,8 @@ installation-guide (20150323) unstable; urgency=medium [ Karsten Merker ] * Update the armhf platform support status. - * Update the u-boot USB boot command in the "Booting from a USB stick in - u-boot" section as required by newer u-boot versions. + * Update the U-Boot USB boot command in the "Booting from a USB stick in + U-Boot" section as required by newer U-Boot versions. [ Holger Wansing ] * Make year for copyright an entity. @@ -85,7 +85,7 @@ installation-guide (20141230) unstable; urgency=medium Support for it has been reenabled with kernel 3.16. * List the Wandboard Quad as supported armhf platform (based on installation report #773127). - * Add a "Booting from a USB stick in u-boot" subsection in the + * Add a "Booting from a USB stick in U-Boot" subsection in the "Booting the Installer on ARM" section. [ Ben Hutchings ] @@ -142,10 +142,10 @@ installation-guide (20140916) unstable; urgency=low "Where to Find Installation Images" section. Both are Intel iop32-based systems which are not supported in Jessie anymore. * Add an "ARM firmware", a "Setting the ethernet MAC address - in u-boot" and a "Kernel/Initrd/Device-Tree relocation issues in - u-boot" subsection in the "Pre-Installation Hardware and + in U-Boot" and a "Kernel/Initrd/Device-Tree relocation issues in + U-Boot" subsection in the "Pre-Installation Hardware and Operating System Setup" section. - * Add a "Boot image formats" and a "TFTP-booting in u-boot" subsection + * Add a "Boot image formats" and a "TFTP-booting in U-Boot" subsection in the "Booting the Installer on ARM" section. * Add location information for the armmp flavor to the "Where to Find Installation Images" section. diff --git a/en/using-d-i/modules/arm/flash-kernel-installer.xml b/en/using-d-i/modules/arm/flash-kernel-installer.xml index 7bc71ad4c..b1f30d3f1 100644 --- a/en/using-d-i/modules/arm/flash-kernel-installer.xml +++ b/en/using-d-i/modules/arm/flash-kernel-installer.xml @@ -26,7 +26,7 @@ memory! </para><para> -For ARM systems that use u-boot as their system firmware and boot the +For ARM systems that use U-Boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting diff --git a/it/boot-installer/arm.xml b/it/boot-installer/arm.xml index 9ab79f4bd..4d62641bb 100644 --- a/it/boot-installer/arm.xml +++ b/it/boot-installer/arm.xml @@ -24,19 +24,19 @@ insieme al suo ramdisk iniziale (<quote>uInitrd</quote>). </para><para> <!-- -uImage/uInitrd are image formats designed for the u-boot firmware that -is used on many ARM-based systems. Older u-boot versions can only +uImage/uInitrd are image formats designed for the U-Boot firmware that +is used on many ARM-based systems. Older U-Boot versions can only boot files in uImage/uInitrd format, so these are often used on -older armel systems. Newer u-boot versions can - besides booting +older armel systems. Newer U-Boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, but the command syntax to do that is slightly different from that for booting uImages. --> -uImage/uInitrd sono formati pensati per il firmware u-boot, presente -su molti sistemi ARM. Le versioni di u-boot più vecchie possono avviare +uImage/uInitrd sono formati pensati per il firmware U-Boot, presente +su molti sistemi ARM. Le versioni di U-Boot più vecchie possono avviare solo file nel formato uImage/uInitrd, quindi spesso sono usate sui -sistemi armel più vecchi. Le versioni di u-boot più recenti sono in +sistemi armel più vecchi. Le versioni di U-Boot più recenti sono in grado di avviare ovviamente le immagini uImages/uInitrds ma riescono ad avviare anche i kernel e i ramdisk in formato Linux, la sintassi del comando per avviare le immagini in formato Linux è leggermente diversa @@ -67,18 +67,18 @@ dell'hardware. &boot-installer-intro-net.xml; <sect3 arch="arm" id="boot-tftp-uboot"> - <!-- <title>TFTP-booting in u-boot</title> --> - <title>Avvio da TFTP con u-boot</title> + <!-- <title>TFTP-booting in U-Boot</title> --> + <title>Avvio da TFTP con U-Boot</title> <para> <!-- -Network booting on systems using the u-boot firmware consists of +Network booting on systems using the U-Boot firmware consists of three steps: a) configuring the network, b) loading the images (kernel/initial ramdisk/dtb) into memory and c) actually executing the previosly loaded code. --> -L'avvio da rete per i sistemi che usano il firmware u-boot consiste di +L'avvio da rete per i sistemi che usano il firmware U-Boot consiste di tre passi: a) configurazione della rete b) caricamento delle immagini (kernel, ramdisk e dtb) in memoria c) l'esecuzione del codice appena caricato. @@ -141,12 +141,12 @@ sistema e non esiste una regola generale su quale indirizzo utilizzare. </para><para> <!-- -On some systems, u-boot predefines a set of environment variables +On some systems, U-Boot predefines a set of environment variables with suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You can check whether they are defined by running --> -Su alcuni sistemi, u-boot predefinisce una serie di varibili d'ambiente +Su alcuni sistemi, U-Boot predefinisce una serie di varibili d'ambiente con gli indirizzi da usare: kernel_addr_r, ramdisk_addr_r e fdt_addr_r. È possibile verificare se tali variabili sono state definite con @@ -243,7 +243,7 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} <!-- Note: When booting standard linux images, it is important to load -the initial ramdisk image after the kernel and the dtb as u-boot +the initial ramdisk image after the kernel and the dtb as U-Boot sets the filesize variable to the size of the last file loaded and the bootz command requires the size of the ramdisk image to work correctly. In case of booting a platform-specific kernel, i.e. a @@ -251,7 +251,7 @@ kernel without device-tree, simply omit the ${fdt_addr_r} parameter. --> Nota: quando si avviano immagini linux è importante caricare l'immagine -del ramdisk iniziale dopo il kernel e il dtb poiché u-boot imposta il +del ramdisk iniziale dopo il kernel e il dtb poiché U-Boot imposta il valore della variabile filesize pari alla dimensione dell'ultimo file caricato e il comando bootz ha bisogno di conoscere la dimensione dell'immagine del ramdisk per funzionare correttamente. Per avviare un @@ -263,17 +263,17 @@ device-tree, è sufficiente omettere il parametro ${fdt_addr_r}. </sect2> <sect2 arch="arm" id="boot-hd-media"> - <!-- <title>Booting from a USB stick in u-boot</title> --> - <title>Avvio da chiavetta USB in u-boot</title> + <!-- <title>Booting from a USB stick in U-Boot</title> --> + <title>Avvio da chiavetta USB in U-Boot</title> <para> <!-- -Many modern u-boot versions have USB support and allow booting from +Many modern U-Boot versions have USB support and allow booting from USB mass storage devices such as USB sticks. Unfortunately the exact steps required to do that can vary quite a bit from device to device. --> -Molte delle versioni moderne di u-boot hanno il supporto per USB e +Molte delle versioni moderne di U-Boot hanno il supporto per USB e permettono di fare l'avvio da dispositivi di memorizzazione di massa USB come le chiavette USB. Sfortunatamente i passi esatti per fare l'avvio variano leggermente da dispositivo a dispositivo. @@ -288,7 +288,7 @@ installation from a USB stick on such systems, but unfortunately not all platforms have adopted this new framework yet. --> -In u-boot v2014.10 sono stati introdotti una gestione comune della riga +In U-Boot v2014.10 sono stati introdotti una gestione comune della riga di comando e l'infrastruttura autoboot. Ciò permette di creare immagini d'avvio generiche che funzionano su qualsiasi sistema con tale framework. Il &d-i; può fare l'installazione a partire da una chiavetta USB su tali @@ -300,8 +300,8 @@ nuova infrastruttura. <!-- To build a bootable USB stick for installing &debian;, unpack the hd-media tarball (see <xref linkend="where-files"/>) onto a -USB stick formatted with a filesystem supported by the u-boot version -on your device. For modern u-boot versions, any of FAT16 / FAT32 / +USB stick formatted with a filesystem supported by the U-Boot version +on your device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. Then copy the ISO image file of the first &debian; installation CD or DVD onto the stick. --> @@ -309,31 +309,31 @@ first &debian; installation CD or DVD onto the stick. Per creare una chiavetta USB con la quale installare &debian; occorre prima scompattare l'archivio tar hd-media (consultare <xref linkend="where-files"/>) su una chiavetta USB formattata con uno dei -filesystem supportati dalla versione di u-boot del proprio dispositivo -(le versioni più recenti di u-boot suportano FAT16 / FAT32 / ext2 / +filesystem supportati dalla versione di U-Boot del proprio dispositivo +(le versioni più recenti di U-Boot suportano FAT16 / FAT32 / ext2 / ext3 / ext4), poi copiare il file dell'immagine ISO del primo CD o DVD d'installazione &debian; sulla chiavetta. </para><para> <!-- -The autoboot framework in modern u-boot versions works similar to the +The autoboot framework in modern U-Boot versions works similar to the boot ordering options in a PC BIOS, i.e. it checks a list of possible boot devices for a valid boot image and starts the first one it finds. If there is no operating system installed, plugging in the USB stick and powering up the system should result in starting the installer. -You can also initiate the USB-boot process any time from the u-boot +You can also initiate the USB-boot process any time from the U-Boot prompt by entering the <quote>run bootcmd_usb0</quote> command. --> -L'infrastruttura autoboot delle recenti versioni di u-boot funziona in +L'infrastruttura autoboot delle recenti versioni di U-Boot funziona in modo similare alla opzione sull'ordine di avvio del BIOS dei PC, cioè ricerca nell'elenco dei dispositivi da cui è possibile fare l'avvio il primo che contiene un'immagine avviabile e la fa partire. Se non è installato alcun sistema operativo, inserendo una chiavetta USB e l'accensione del sistema dovrebbe comportare l'avvio dell'installatore. È anche possibile iniziare il processo d'avvio da USB in qualsiasi -momento inserendo dal prompt di u-boot il comando +momento inserendo dal prompt di U-Boot il comando <quote>run bootcmd_usb0</quote>. @@ -342,7 +342,7 @@ momento inserendo dal prompt di u-boot il comando <!-- One problem that can come up when booting from a USB stick while using a serial console can be a console baudrate mismatch. If a console -variable is defined in u-boot, the &d-i; boot script automatically +variable is defined in U-Boot, the &d-i; boot script automatically passes it to the kernel to set the primary console device and, if applicable, the console baudrate. Unfortunately the handling of the console variable varies from platform to platform - on some platforms, @@ -350,8 +350,8 @@ the console variable includes the baudrate (as in <quote>console=ttyS0,115200</quote>), while on other platforms the console variable contains only the device (as in <quote>console=ttyS0</quote>). The latter case leads to a garbled -console output when the default baudrate differs between u-boot and -the kernel. Modern u-boot versions often use 115200 baud while the +console output when the default baudrate differs between U-Boot and +the kernel. Modern U-Boot versions often use 115200 baud while the kernel still defaults to the traditional 9600 baud. If this happens, you should manually set the console variable to contain the correct baudrate for your system and then start the installer with the @@ -360,7 +360,7 @@ baudrate for your system and then start the installer with the Un problema che può verificarsi durante l'avvio da una chiavetta USB quando è collegata una console seriale è un disallineamento della -velocità di comunicazione. Se in u-boot è definita la varibile console, +velocità di comunicazione. Se in U-Boot è definita la varibile console, lo script di avvio del &d-i; ne passa automaticamente il valore al kernel in modo da impostare il device della console primaria e, se possibile, la velocità di trasmissione. Sfortunatamente la gestione @@ -369,8 +369,8 @@ la varibile contiene anche la velocità (come in <quote>console=ttyS0,115200</quote>), invece su altre la varibile contiene solo il device (come in <quote>console=ttyS0</quote>). In quest'ultimo caso è possibile avere dell'output confuso sulla console -qual ora la velocità predefinita di u-boot sia diversa da quella del -kernel. Le versioni recenti di u-boot spesso utilizzano 115200 baud +qual ora la velocità predefinita di U-Boot sia diversa da quella del +kernel. Le versioni recenti di U-Boot spesso utilizzano 115200 baud mentre il kernel tutt'ora utilizza i tradizionali 9600 baud. In questo caso è necessario impostare manualmente la varibile console in modo che contenga anche la velocità di trasmissione adatta al sistema e avviare diff --git a/it/hardware/supported/arm.xml b/it/hardware/supported/arm.xml index 8ead68fed..558741fcd 100644 --- a/it/hardware/supported/arm.xml +++ b/it/hardware/supported/arm.xml @@ -448,16 +448,16 @@ in alcuni sistemi sunXi non è supportata. Using a local display is technically possible without native display drivers via the <quote>simplefb</quote> infrastructure in the mainline kernel, which relies on the -<quote>u-boot</quote> bootloader for initializing the display -hardware, but this is not supported by the u-boot version in +<quote>U-Boot</quote> bootloader for initializing the display +hardware, but this is not supported by the U-Boot version in &debian; 8. --> Tecnicamente è possibile usare un display locale senza il driver nativo tramite l'infrastruttura <quote>simplefb</quote> presente nel -kernel, la quale si appoggia al bootloader <quote>u-boot</quote> per +kernel, la quale si appoggia al bootloader <quote>U-Boot</quote> per l'inizializzazione dell'hardware del diplay; purtroppo tale operazione -non è supportata nella versione di u-boot presente in &debian; 8. +non è supportata nella versione di U-Boot presente in &debian; 8. </para> </listitem> diff --git a/it/using-d-i/modules/arm/flash-kernel-installer.xml b/it/using-d-i/modules/arm/flash-kernel-installer.xml index 818bf058a..90b550d44 100644 --- a/it/using-d-i/modules/arm/flash-kernel-installer.xml +++ b/it/using-d-i/modules/arm/flash-kernel-installer.xml @@ -48,14 +48,14 @@ può solo sovrascrive il contenuto della memoria flash! </para><para> <!-- -For ARM systems that use u-boot as their system firmware and boot the +For ARM systems that use U-Boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting without user interaction. --> -Su i sistemi ARM con u-boot come firmware di sistema è possibile avviare +Su i sistemi ARM con U-Boot come firmware di sistema è possibile avviare il kernel e il ramdisk iniziale da supporti esterni (come schedine MMC o SD, dispositivi di memorizzazione di massa USB oppure dischi IDE/SATA), flash-kernel crea gli script di avvio che permettono di avere l'avvio diff --git a/po/da/boot-installer.po b/po/da/boot-installer.po index 9a8eab0f7..bf6933fb4 100644 --- a/po/da/boot-installer.po +++ b/po/da/boot-installer.po @@ -82,10 +82,10 @@ msgstr "" #: boot-installer.xml:47 #, fuzzy, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. Older U-Boot versions can only boot files " #| "in uImage/uInitrd format, so these are often used on older armel systems. " -#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot " +#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot " #| "standard Linux kernels and ramdisk images, but the command syntax to do " #| "that is slightly different from that for booting uImages." msgid "" @@ -96,10 +96,10 @@ msgid "" "Linux kernels and ramdisk images, but the command syntax to do that is " "slightly different from that for booting uImages." msgstr "" -"uImage/uInitrd er aftryksformater designet for firmwaren u-boot, som bruges " -"på mange ARM-baserede systemer. Ældre versioner af u-boot kan kun opstarte " +"uImage/uInitrd er aftryksformater designet for firmwaren U-Boot, som bruges " +"på mange ARM-baserede systemer. Ældre versioner af U-Boot kan kun opstarte " "filer i uImage/uInitrd-formatet, så de bruges ofte på ældre armel-systemer. " -"Nyere versioner af u-boot kan - udover opstarte uImages/uInitrds - også " +"Nyere versioner af U-Boot kan - udover opstarte uImages/uInitrds - også " "opstarte standardkerner med Linux og ramdisk-aftryk, men kommandosyntaksen " "til dette er en smule anderledes end at starte fra uImages." @@ -189,15 +189,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" -msgstr "TFTP-opstart i u-boot" +msgstr "TFTP-opstart i U-Boot" #. Tag: para #: boot-installer.xml:109 #, fuzzy, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -206,7 +206,7 @@ msgid "" "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" -"Netværksopstart på systemer, der bruger firmwaren u-boot, består af tre " +"Netværksopstart på systemer, der bruger firmwaren U-Boot, består af tre " "trin: a) konfiguration af netværket, b) indlæsning af aftrykket (kerne/" "initiel ramdisk/dtb) i hukommelsen og c) faktisk kørsel af den tidligere " "indlæste kode." @@ -269,7 +269,7 @@ msgstr "" #: boot-installer.xml:132 #, fuzzy, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -290,7 +290,7 @@ msgid "" "name <quote>sun4i</quote> or the Allwinner A20, architecture name " "<quote>sun7i</quote>), you can e.g. use the follwing values:" msgstr "" -"På nogle systemer, prædefinerer u-boot et sæt af miljøparametre med egnede " +"På nogle systemer, prædefinerer U-Boot et sæt af miljøparametre med egnede " "indlæsningsadresser: kernel_addr_r, ramdisk_addr_r og fdt_addr_r. Du kan " "kontrollere om de er defineret ved at køre <informalexample><screen>\n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" @@ -391,7 +391,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, fuzzy, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -405,7 +405,7 @@ msgid "" "the ${fdt_addr_r} parameter." msgstr "" "Bemærk: Når der opstartes standardaftryk for Linux, så er det vigtigt at " -"indlæse det oprindelige ramdisk-aftryk efter kernen og dtb'en, da u-boot " +"indlæse det oprindelige ramdisk-aftryk efter kernen og dtb'en, da U-Boot " "angiver filstørrelsesvariablen til størrelsen på den sidst indlæste fil og " "kommandoen bootz kræver størrelsen af ramdisk-aftrykket for at fungere " "korrekt. I tilfælde hvor der opstartes en platformspecifik kerne, d.v.s. en " @@ -466,15 +466,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, fuzzy, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" -msgstr "Opstart fra et USB-hukommelsesdrev i u-boot" +msgstr "Opstart fra et USB-hukommelsesdrev i U-Boot" #. Tag: para #: boot-installer.xml:207 #, fuzzy, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -482,7 +482,7 @@ msgid "" "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" -"Mange moderne u-boot-versioner har USB-understøttelse og tillader opstart " +"Mange moderne U-Boot-versioner har USB-understøttelse og tillader opstart " "fra USB-lagerenheder såsom USB-drev. Desværre er de præcise trin krævet for " "dette forskellige fra enhed til enhed." @@ -508,8 +508,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -522,8 +522,8 @@ msgid "" msgstr "" "For at bygge et USB-drev, der kan startes op fra, til installation af " "&debian; udpakkes hd-media-tarball'en (se <xref linkend=\"where-files\"/>) " -"til et USB-drev formateret med et filsystem, der understøtter u-boot-" -"versionen på din enhed. For moderne u-boot-versioner, fungerer enhver FAT16/" +"til et USB-drev formateret med et filsystem, der understøtter U-Boot-" +"versionen på din enhed. For moderne U-Boot-versioner, fungerer enhver FAT16/" "FAT32/ext2/ext3/ext4 normalt. Kopier så ISO-aftryksfilen fra den første " "&debian;-installations-cd eller dvd til drevet." @@ -531,12 +531,12 @@ msgstr "" #: boot-installer.xml:233 #, fuzzy, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run bootcmd_usb0</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -547,7 +547,7 @@ msgid "" "the USB-boot process any time from the U-Boot prompt by entering the " "<quote>run bootcmd_usb0</quote> command." msgstr "" -"Autoboot-rammen i moderne u-boot-versioner fungerer på samme måde som " +"Autoboot-rammen i moderne U-Boot-versioner fungerer på samme måde som " "indstillingerne for opstartsrækkefølgen i en PC BIOS, dvs. den kontrollerer " "en liste over mulige opstartsenheder for et gyldigt opstartsaftryk og starer " "den første den finder. Hvis der ikke er et operativsystem installeret, vil " @@ -561,15 +561,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " @@ -592,7 +592,7 @@ msgid "" msgstr "" "Et problem som kan fremkomme, når der startes op fra et USB-drev, mens der " "anvendes en seriel konsol er en konsols baudhastighedsforskel. Hvis en " -"konsolvariabel er defineret i u-boot, sender &d-i;-opstartskriptet " +"konsolvariabel er defineret i U-Boot, sender &d-i;-opstartskriptet " "automatisk den til kernen for at sætte den primære konsolenhed og, hvis " "anvendelig, konsollens baudhastighed. Desværre varierer håndteringen af " "konsollens variabler fra platform til platform - på nogle platforme " @@ -600,7 +600,7 @@ msgstr "" "<quote>console=ttyS0,115200</quote>), mens på andre platforme indeholder " "konsolvariablen kun enheden (som i <quote>console=ttyS0</quote>). Det sidste " "tilfælde fører til et forvansket konsolresultat, når standardbauthastigheden " -"er forskellig mellem u-boot og kernen. Moderen u-boot-versioner bruger ofte " +"er forskellig mellem U-Boot og kernen. Moderen U-Boot-versioner bruger ofte " "115200 baud mens kernen stadig har en standard å de traditionelle 9600 baud. " "Hvis dette opstår, så skal du manuelt sætte konsolvariablen til at indeholde " "den korrekte baudhastighed for dit system og så starte " diff --git a/po/da/hardware.po b/po/da/hardware.po index f4c673dfe..422c6dd7c 100644 --- a/po/da/hardware.po +++ b/po/da/hardware.po @@ -891,7 +891,7 @@ msgstr "" #| msgid "" #| "Using a local display is technically possible without native display " #| "drivers via the <quote>simplefb</quote> infrastructure in the mainline " -#| "kernel, which relies on the <quote>u-boot</quote> bootloader for " +#| "kernel, which relies on the <quote>U-Boot</quote> bootloader for " #| "initializing the display hardware, but this is not supported by the u-" #| "boot version in &debian; 8." msgid "" @@ -902,8 +902,8 @@ msgid "" msgstr "" "Brug af en lokal skærm er teknisk muligt uden standarddrivere for skærmen " "via infrastrukturen <quote>simplefb</quote> i hovedlinjekernen, som afhænger " -"af opstartsindlæseren <quote>u-boot</quote> for initialisering af " -"skærmudstyret, men dette er ikke understøttet af u-boot-versionen i &debian; " +"af opstartsindlæseren <quote>U-Boot</quote> for initialisering af " +"skærmudstyret, men dette er ikke understøttet af U-Boot-versionen i &debian; " "8." #. Tag: term diff --git a/po/da/using-d-i.po b/po/da/using-d-i.po index a286b9247..d4b3c80b8 100644 --- a/po/da/using-d-i.po +++ b/po/da/using-d-i.po @@ -5135,12 +5135,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"For ARM-systemer som bruger u-boot som deres systemfirmware og starter " +"For ARM-systemer som bruger U-Boot som deres systemfirmware og starter " "kernen og den oprindelige ramdisk fra ekstern lagermedie (såsom MMC/SD-kort, " "USB-masselagerenheder eller IDE/SATA-harddiske), opretter flash-kernel et " "passende opstartsskript så der automatisk kan startes op uden " diff --git a/po/el/boot-installer.po b/po/el/boot-installer.po index 30f01fc79..a66b8e9c1 100644 --- a/po/el/boot-installer.po +++ b/po/el/boot-installer.po @@ -184,9 +184,9 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" -msgstr "Εκκίνηση με TFTP σε u-boot" +msgstr "Εκκίνηση με TFTP σε U-Boot" #. Tag: para #: boot-installer.xml:109 diff --git a/po/el/using-d-i.po b/po/el/using-d-i.po index 7160c44e6..42bfd1a7e 100644 --- a/po/el/using-d-i.po +++ b/po/el/using-d-i.po @@ -5444,7 +5444,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/es/using-d-i.po b/po/es/using-d-i.po index 3d53f7507..3664c23df 100644 --- a/po/es/using-d-i.po +++ b/po/es/using-d-i.po @@ -5355,7 +5355,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/fi/using-d-i.po b/po/fi/using-d-i.po index f141042fc..dfbefbca3 100644 --- a/po/fi/using-d-i.po +++ b/po/fi/using-d-i.po @@ -5178,7 +5178,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/fr/boot-installer.po b/po/fr/boot-installer.po index 0abe27953..166009a51 100644 --- a/po/fr/boot-installer.po +++ b/po/fr/boot-installer.po @@ -81,10 +81,10 @@ msgstr "" #: boot-installer.xml:47 #, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. Older U-Boot versions can only boot files " #| "in uImage/uInitrd format, so these are often used on older armel systems. " -#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot " +#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot " #| "standard Linux kernels and ramdisk images, but the command syntax to do " #| "that is slightly different from that for booting uImages." msgid "" @@ -199,7 +199,7 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" msgstr "Amorcer à partir de TFTP avec U-Boot" @@ -207,7 +207,7 @@ msgstr "Amorcer à partir de TFTP avec U-Boot" #: boot-installer.xml:109 #, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -278,7 +278,7 @@ msgstr "" #: boot-installer.xml:132 #, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -402,7 +402,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -495,7 +495,7 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" msgstr "Amorcer sur une clé USB avec U-Boot" @@ -503,7 +503,7 @@ msgstr "Amorcer sur une clé USB avec U-Boot" #: boot-installer.xml:207 #, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -539,8 +539,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -562,12 +562,12 @@ msgstr "" #: boot-installer.xml:233 #, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run bootcmd_usb0</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -593,15 +593,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " diff --git a/po/fr/hardware.po b/po/fr/hardware.po index 38d270840..017267d43 100644 --- a/po/fr/hardware.po +++ b/po/fr/hardware.po @@ -927,7 +927,7 @@ msgstr "" #| msgid "" #| "Using a local display is technically possible without native display " #| "drivers via the <quote>simplefb</quote> infrastructure in the mainline " -#| "kernel, which relies on the <quote>u-boot</quote> bootloader for " +#| "kernel, which relies on the <quote>U-Boot</quote> bootloader for " #| "initializing the display hardware, but this is not supported by the u-" #| "boot version in &debian; 8." msgid "" diff --git a/po/fr/preparing.po b/po/fr/preparing.po index 0ebb95de6..8ca0a6921 100644 --- a/po/fr/preparing.po +++ b/po/fr/preparing.po @@ -2679,7 +2679,7 @@ msgstr "" #. Tag: title #: preparing.xml:1706 #, no-c-format -#| msgid "Setting the ethernet MAC address in u-boot" +#| msgid "Setting the ethernet MAC address in U-Boot" msgid "Setting the ethernet MAC address in U-Boot" msgstr "Configurer l'adresse MAC Ethernet dans U-Boot" diff --git a/po/fr/using-d-i.po b/po/fr/using-d-i.po index 566f7b3da..8a0ca889a 100644 --- a/po/fr/using-d-i.po +++ b/po/fr/using-d-i.po @@ -5202,12 +5202,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"Pour les systèmes ARM qui utilisent u-boot comme microprogramme, et qui " +"Pour les systèmes ARM qui utilisent U-Boot comme microprogramme, et qui " "amorcent le noyau et la mémoire initiale depuis un périphérique de stockage " "externe (comme une carte MMC/SD, un périphérique de stockage de masse USB ou " "un disque dur IDE/SATA), flash-kernel génère un script d'amorçage approprié " diff --git a/po/hu/using-d-i.po b/po/hu/using-d-i.po index c84dfcfae..59d00077b 100644 --- a/po/hu/using-d-i.po +++ b/po/hu/using-d-i.po @@ -5064,7 +5064,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/ja/using-d-i.po b/po/ja/using-d-i.po index 28ceef337..7c374ab8a 100644 --- a/po/ja/using-d-i.po +++ b/po/ja/using-d-i.po @@ -5044,7 +5044,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po index c48a2cb87..5badb3c8d 100644 --- a/po/ko/boot-installer.po +++ b/po/ko/boot-installer.po @@ -85,10 +85,10 @@ msgstr "" #: boot-installer.xml:47 #, fuzzy, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. Older U-Boot versions can only boot files " #| "in uImage/uInitrd format, so these are often used on older armel systems. " -#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot " +#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot " #| "standard Linux kernels and ramdisk images, but the command syntax to do " #| "that is slightly different from that for booting uImages." msgid "" @@ -99,10 +99,10 @@ msgid "" "Linux kernels and ramdisk images, but the command syntax to do that is " "slightly different from that for booting uImages." msgstr "" -"uImage/uInitrd는 u-boot 펌웨어에서 사용하려고 만들어진 이미지 형식입니다. u-" -"boot는 여러 ARM 시스템에서 사용합니다. 예전 버전의 u-boot에서는 uImage/" +"uImage/uInitrd는 U-Boot 펌웨어에서 사용하려고 만들어진 이미지 형식입니다. u-" +"boot는 여러 ARM 시스템에서 사용합니다. 예전 버전의 U-Boot에서는 uImage/" "uInitrd 형식의 파일만 부팅할 수 있습니다. 즉 이 형식은 예전의 armel 시스템에" -"서 주로 사용합니다. 최근 버전의 u-boot에서는 uImage/uInitrd 부팅 말고 표준 리" +"서 주로 사용합니다. 최근 버전의 U-Boot에서는 uImage/uInitrd 부팅 말고 표준 리" "눅스 커널과 램디스크 이미지로 부팅할 수 있습니다. 하지만 uImage 부팅과는 명령" "어 문법이 약간 다릅니다." @@ -191,15 +191,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" -msgstr "u-boot에서 TFTP 부팅" +msgstr "U-Boot에서 TFTP 부팅" #. Tag: para #: boot-installer.xml:109 #, fuzzy, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -208,7 +208,7 @@ msgid "" "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" -"u-boot 펌웨어를 사용하는 시스템에서 네트워크 부팅은 3가지 단계로 이루어져 있" +"U-Boot 펌웨어를 사용하는 시스템에서 네트워크 부팅은 3가지 단계로 이루어져 있" "습니다: (1) 네트워크 설정, (2) 이미지(커널/최초 램디스크/DTB) 메모리에 읽어들" "이기, (3) 읽어들인 코드 실행." @@ -267,7 +267,7 @@ msgstr "" #: boot-installer.xml:132 #, fuzzy, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -288,7 +288,7 @@ msgid "" "name <quote>sun4i</quote> or the Allwinner A20, architecture name " "<quote>sun7i</quote>), you can e.g. use the follwing values:" msgstr "" -"일부 시스템에서는, u-boot에 적합한 로딩 주소가 환경 변수로 미리 정의되어 있습" +"일부 시스템에서는, U-Boot에 적합한 로딩 주소가 환경 변수로 미리 정의되어 있습" "니다: kernel_addr_r, ramdisk_addr_r 및 fdt_addr_r. 이 환경 변수가 정의되어 있" "는지 여부를 다음 명령으로 확인해 볼 수 있습니다 <informalexample><screen>\n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" @@ -388,7 +388,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, fuzzy, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -402,7 +402,7 @@ msgid "" "the ${fdt_addr_r} parameter." msgstr "" "표준 리눅스 이미지로 부팅할 때, 커널과 DTB를 읽어들이고 다음에 최초 램디스크 " -"이미지를 읽어들이는 게 중요합니다. u-boot에서는 파일 크기 변수를 마지막에 읽" +"이미지를 읽어들이는 게 중요합니다. U-Boot에서는 파일 크기 변수를 마지막에 읽" "어들인 파일의 크기로 설정하고, bootz 명령이 제대로 동작하려면 램디스크 이미지" "의 크기가 필요하기 떄문입니다. 플랫폼 전용 커널로 부팅하는 경우(예를 들어 디" "바이스 트리 없는 커널)에는 ${fdt_addr_r} 파라미터를 생략하면 됩니다." @@ -462,15 +462,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, fuzzy, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" -msgstr "u-boot 이용해 USB 메모리에서 부팅하기" +msgstr "U-Boot 이용해 USB 메모리에서 부팅하기" #. Tag: para #: boot-installer.xml:207 #, fuzzy, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -478,7 +478,7 @@ msgid "" "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" -"최근의 u-boot 버전에서는 USB를 지원하므로, USB 메모리와 같은 USB 대용량 저장" +"최근의 U-Boot 버전에서는 USB를 지원하므로, USB 메모리와 같은 USB 대용량 저장" "소 장치에서 부팅할 수 있습니다. 아쉽지만 부팅하는 정확한 단계는 하드웨어마다 " "조금씩 다를 수 있습니다." @@ -504,8 +504,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -518,8 +518,8 @@ msgid "" msgstr "" "&debian; 설치에 사용할 부팅 가능 USB 메모리를 만드려면, hd-media 묶음을 " "(<xref linkend=\"where-files\"/> 참고) USB 메모리에 풀어 놓습니다. USB 메모리" -"는 하드웨어의 u-boot 버전에서 지원하는 파일 시스템으로 포맷해야 합니다. 최근" -"의 u-boot 버전에서는 FAT16 / FAT32 / ext2 / ext3 / ext4 모두 동작합니다. 그리" +"는 하드웨어의 U-Boot 버전에서 지원하는 파일 시스템으로 포맷해야 합니다. 최근" +"의 U-Boot 버전에서는 FAT16 / FAT32 / ext2 / ext3 / ext4 모두 동작합니다. 그리" "고 첫번째 &debian; 설치 CD 또는 DVD의 ISO 이미지를 그 USB 메모리에 복사합니" "다." @@ -527,12 +527,12 @@ msgstr "" #: boot-installer.xml:233 #, fuzzy, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run usb_boot</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -543,10 +543,10 @@ msgid "" "the USB-boot process any time from the U-Boot prompt by entering the " "<quote>run bootcmd_usb0</quote> command." msgstr "" -"최근 u-boot 버전의 자동 부팅 프레임워크는 PC BIOS의 부팅 순서와 비슷하게 동작" +"최근 U-Boot 버전의 자동 부팅 프레임워크는 PC BIOS의 부팅 순서와 비슷하게 동작" "합니다. 즉 가능한 부팅 장치에서 부팅 이미지를 확인하고, 찾은 부팅 장치 중에" "서 첫 번째에서 부팅합니다. 운영 체제를 설치하지 않았으면, USB 메모리를 연결하" -"고 전원을 켜면 설치 프로그램을 시작하게 됩니다. u-boot 프롬프트에서 " +"고 전원을 켜면 설치 프로그램을 시작하게 됩니다. U-Boot 프롬프트에서 " "<quote>run usb_boot</quote> 명령을 입력하면 언제든지 USB 부팅을 할 수 있습니" "다." @@ -556,15 +556,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " @@ -586,12 +586,12 @@ msgid "" "start the installer with the <quote>run bootcmd_usb0</quote> command." msgstr "" "시리얼 콘솔을 사용할 때 USB 메모리에서 부팅할 경우 발생할 수 있는 한 가지 문" -"제는 보우레이트가 일치하지 않는 경우입니다. 콘솔 변수를 u-boot에서 지정한 경" +"제는 보우레이트가 일치하지 않는 경우입니다. 콘솔 변수를 U-Boot에서 지정한 경" "우, &d-i; 부팅 스크립트에서 자동으로 커널에 전달해서 사용하는 콘솔 장치와 보" "우레이트를 설정합니다. 아쉽지만 콘솔 변수 처리는 플랫폼마다 다릅니다. 일부 시" "스템에서는 콘솔 변수에서 보우레이트를 지정하고 (<quote>console=ttyS0,115200</" "quote>처럼), 어떤 플랫폼에서는 콘솔 변수에 시리얼 장치만 " -"(<quote>console=ttyS0</quote>처럼) 설정합니다. 후자의 경우 u-boot와 커널이 사" +"(<quote>console=ttyS0</quote>처럼) 설정합니다. 후자의 경우 U-Boot와 커널이 사" "용하는 기본 보우레이트가 다른 경우 콘솔 출력이 깨질 수 있습니다. 최근의 u-" "boot 버전에서는 115200 보우레이트를 사용하지만, 여전히 커널은 전통적인 9600 " "보우레이트를 사용합니다. 이런 상황이 벌어지는 경우, 콘솔 변수를 수동으로 설정" diff --git a/po/ko/preparing.po b/po/ko/preparing.po index 311b85478..2d221c8dd 100644 --- a/po/ko/preparing.po +++ b/po/ko/preparing.po @@ -2550,9 +2550,9 @@ msgstr "" #. Tag: title #: preparing.xml:1706 #, fuzzy, no-c-format -#| msgid "Setting the ethernet MAC address in u-boot" +#| msgid "Setting the ethernet MAC address in U-Boot" msgid "Setting the ethernet MAC address in U-Boot" -msgstr "u-boot에서 이더넷 MAC 주소 설정하기" +msgstr "U-Boot에서 이더넷 MAC 주소 설정하기" #. Tag: para #: preparing.xml:1707 @@ -2614,9 +2614,9 @@ msgstr "" #: preparing.xml:1736 #, fuzzy, no-c-format #| msgid "" -#| "On systems using u-boot as system firmware, the ethernet MAC address is " +#| "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 " +#| "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." @@ -2628,8 +2628,8 @@ msgid "" "ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</" "quote> makes the assignment permanent." msgstr "" -"u-boot를 시스템 펌웨어로 사용하는 시스템에서는, 이더넷 MAC 주소를 " -"<quote>ethaddr</quote> 환경 변수에 저장합니다. 이 값은 u-boot 명령 프롬프트에" +"U-Boot를 시스템 펌웨어로 사용하는 시스템에서는, 이더넷 MAC 주소를 " +"<quote>ethaddr</quote> 환경 변수에 저장합니다. 이 값은 U-Boot 명령 프롬프트에" "서 <quote>printenv ethaddr</quote> 명령으로 확인해 볼 수 있고, <quote>setenv " "ethaddr ca:ff:ee:12:34:56</quote> 명령과 같이 설정할 수 있습니다. 값을 설정하" "면 <quote>saveenv</quote> 명령으로 값을 저장합니다." @@ -2637,20 +2637,20 @@ msgstr "" #. Tag: title #: preparing.xml:1747 #, fuzzy, no-c-format -#| msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot" +#| msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" -msgstr "u-boot의 커널/최초 램디스크/디바이스 트리 재배치 문제" +msgstr "U-Boot의 커널/최초 램디스크/디바이스 트리 재배치 문제" #. Tag: para #: preparing.xml:1748 #, fuzzy, no-c-format #| msgid "" -#| "On some systems with older u-boot versions there can be problems with " +#| "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 " +#| "tree blob in memory during the boot process. In this case, U-Boot shows " #| "the message <quote>Starting kernel ...</quote>, but the system freezes " #| "afterwards without further output. These issues have been solved with " -#| "newer u-boot versions from v2014.07 onwards." +#| "newer U-Boot versions from v2014.07 onwards." 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-" @@ -2659,25 +2659,25 @@ msgid "" "afterwards without further output. These issues have been solved with newer " "U-Boot versions from v2014.07 onwards." msgstr "" -"예전 버전의 u-boot를 사용하는 일부 시스템에서는, 부팅 과정에서 메모리에 있는 " +"예전 버전의 U-Boot를 사용하는 일부 시스템에서는, 부팅 과정에서 메모리에 있는 " "리눅스 커널, 최초 램디스크, 디바이스 트리를 재배치할 때 문제가 있을 수도 있습" -"니다. 이 경우 u-boot에서 <quote>Starting kernel ...</quote> 메시지를 표시히지" -"만, 그 뒤에 출력이 없이 시스템이 멈춰 있습니다. 이 문제는 u-boot v2014.07 버" +"니다. 이 경우 U-Boot에서 <quote>Starting kernel ...</quote> 메시지를 표시히지" +"만, 그 뒤에 출력이 없이 시스템이 멈춰 있습니다. 이 문제는 U-Boot v2014.07 버" "전 이후로 해결되었습니다." #. Tag: para #: preparing.xml:1757 #, fuzzy, no-c-format #| msgid "" -#| "If the system has originally used a u-boot version older than v2014.07 " +#| "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 " +#| "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 " +#| "data. It is possible to manually set bootm_size to the new U-Boot's " #| "default value by running the command <quote>env default bootm_size; " -#| "saveenv</quote> at the u-boot prompt." +#| "saveenv</quote> at the U-Boot prompt." 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 " @@ -2689,13 +2689,13 @@ msgid "" "running the command <quote>env default bootm_size; saveenv</quote> at the U-" "Boot prompt." msgstr "" -"만약 시스템에서 v2014.07보다 오래 된 u-boot 버전을 사용하고 나중에 그 보다 나" -"중 버전으로 업그레이드했다면, u-boot 업그레이드 후에도 문제가 계속 발생할 수 " -"있습니다. u-boot를 업그레이드해도 현재 u-boot 환경 변수를 수정하지는 않고, 추" -"가 환경 변수를(bootm_size) 설정해야 합니다. u-boot는 환경 변수 데이터가 없이 " -"새로 설치할 경우에만 자동으로 이 환경 변수를 설정합니다. u-boot 프롬프트에서 " +"만약 시스템에서 v2014.07보다 오래 된 U-Boot 버전을 사용하고 나중에 그 보다 나" +"중 버전으로 업그레이드했다면, U-Boot 업그레이드 후에도 문제가 계속 발생할 수 " +"있습니다. U-Boot를 업그레이드해도 현재 U-Boot 환경 변수를 수정하지는 않고, 추" +"가 환경 변수를(bootm_size) 설정해야 합니다. U-Boot는 환경 변수 데이터가 없이 " +"새로 설치할 경우에만 자동으로 이 환경 변수를 설정합니다. U-Boot 프롬프트에서 " "<quote>env default bootm_size; saveenv</quote> 명령으로 bootm_size 환경 변수" -"를 u-boot의 기본값으로 수동 설정할 수도 있습니다." +"를 U-Boot의 기본값으로 수동 설정할 수도 있습니다." #. Tag: para #: preparing.xml:1768 @@ -2703,7 +2703,7 @@ msgstr "" #| msgid "" #| "Another possibility to circumvent relocation-related problems is to run " #| "the command <quote>setenv fdt_high ffffffff; setenv initrd_high " -#| "0xffffffff; saveenv</quote> at the u-boot prompt to completely disable " +#| "0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable " #| "the relocation of the initial ramdisk and the device-tree blob." msgid "" "Another possibility to circumvent relocation-related problems is to run the " @@ -2712,7 +2712,7 @@ msgid "" "the initial ramdisk and the device-tree blob." msgstr "" "재배치와 관련된 문제를 피해가는 한 가지 가능한 방법은 <quote>setenv fdt_high " -"ffffffff; setenv initrd_high 0xffffffff; saveenv</quote> 명령을 u-boot 프롬" +"ffffffff; setenv initrd_high 0xffffffff; saveenv</quote> 명령을 U-Boot 프롬" "프트에서 실행해서 최초 램디스크와 디바이스 트리 파일의 재배치를 완전히 막는 " "방법입니다." diff --git a/po/ko/using-d-i.po b/po/ko/using-d-i.po index 91fc1c0c7..e70127c52 100644 --- a/po/ko/using-d-i.po +++ b/po/ko/using-d-i.po @@ -4887,12 +4887,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"시스템 펌웨어로 u-boot를 사용해 커널과 최초 램디스크를 외부 저장 장치에서 " +"시스템 펌웨어로 U-Boot를 사용해 커널과 최초 램디스크를 외부 저장 장치에서 " "(MMC/SD 카드, USB 저장 장치, IDE/SATA 하드 디스크 등) 부팅할 수 있는 ARM 시스" "템의 경우, flash-kernel에서는 사용자가 입력하지 않아도 자동 부팅할 수 있도록 " "적절한 부팅 스크립트를 만듭니다." diff --git a/po/nl/using-d-i.po b/po/nl/using-d-i.po index 1ca81d172..493e91939 100644 --- a/po/nl/using-d-i.po +++ b/po/nl/using-d-i.po @@ -3766,7 +3766,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/nn/using-d-i.po b/po/nn/using-d-i.po index 1ca81d172..493e91939 100644 --- a/po/nn/using-d-i.po +++ b/po/nn/using-d-i.po @@ -3766,7 +3766,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 2e796ff93..47f0853c6 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -2494,7 +2494,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:3118 #, no-c-format -msgid "For ARM systems that use u-boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting without user interaction." +msgid "For ARM systems that use U-Boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting without user interaction." msgstr "" #. Tag: title diff --git a/po/pt/boot-installer.po b/po/pt/boot-installer.po index ffea16843..4a2016472 100644 --- a/po/pt/boot-installer.po +++ b/po/pt/boot-installer.po @@ -85,10 +85,10 @@ msgstr "" #: boot-installer.xml:47 #, fuzzy, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. Older U-Boot versions can only boot files " #| "in uImage/uInitrd format, so these are often used on older armel systems. " -#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot " +#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot " #| "standard Linux kernels and ramdisk images, but the command syntax to do " #| "that is slightly different from that for booting uImages." msgid "" @@ -99,10 +99,10 @@ msgid "" "Linux kernels and ramdisk images, but the command syntax to do that is " "slightly different from that for booting uImages." msgstr "" -"uImage/uInitrd são formatos de imagens desenhados para o firmware u-boot que " -"é utilizado em muitos sistemas ARM. As versões mais antigas de u-boot apenas " +"uImage/uInitrd são formatos de imagens desenhados para o firmware U-Boot que " +"é utilizado em muitos sistemas ARM. As versões mais antigas de U-Boot apenas " "podem arrancar com o formato uImage/uInitrd, por isso estes são vulgarmente " -"utilizados em sistemas armel antigos. As novas versões u-boot podem - além " +"utilizados em sistemas armel antigos. As novas versões U-Boot podem - além " "de arrancar uImages/uInitrds - também arrancar kernels Linux standard e " "imagens ramdisk, mas a sintaxe de comando para o fazer é ligeiramente " "diferente da para arrancar a partir de uImages." @@ -193,15 +193,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" -msgstr "Arranque por TFTP em u-boot" +msgstr "Arranque por TFTP em U-Boot" #. Tag: para #: boot-installer.xml:109 #, fuzzy, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -210,7 +210,7 @@ msgid "" "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" -"O arranque pela rede em sistemas que utilizam o firmware u-boot consiste em " +"O arranque pela rede em sistemas que utilizam o firmware U-Boot consiste em " "três passos: a) configurar a rede, b) carregar as imagens (kernel/ramdisk " "inicial/dtb) para a memória e c) efectivamente executar o código carregado." @@ -271,7 +271,7 @@ msgstr "" #: boot-installer.xml:132 #, fuzzy, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -292,7 +292,7 @@ msgid "" "name <quote>sun4i</quote> or the Allwinner A20, architecture name " "<quote>sun7i</quote>), you can e.g. use the follwing values:" msgstr "" -"Em alguns sistemas, u-boot pré-define um conjunto de variáveis de ambiente " +"Em alguns sistemas, U-Boot pré-define um conjunto de variáveis de ambiente " "com endereços de carregamento apropriados: kernel_addr_r, ramdisk_addr_r e " "fdt_addr_r. Pode verificar se estão definidos ao correr " "<informalexample><screen>\n" @@ -396,7 +396,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, fuzzy, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -410,7 +410,7 @@ msgid "" "the ${fdt_addr_r} parameter." msgstr "" "Nota: Quando arrancar imagens standard de linux, é importante carregar a " -"imagem ramdisk inicial após o kernel e o dtb já que u-boot define a variável " +"imagem ramdisk inicial após o kernel e o dtb já que U-Boot define a variável " "de tamanho de ficheiro ao tamanho do último ficheiro carregado e o comando " "bootz necessita o tamanho da imagem ramdisk para funcionar correctamente. Em " "caso de arrancar um kernel específico da plataforma, i.e. um kernel sem " @@ -471,15 +471,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, fuzzy, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" -msgstr "Arrancar a partir de uma 'pen' USB em u-boot" +msgstr "Arrancar a partir de uma 'pen' USB em U-Boot" #. Tag: para #: boot-installer.xml:207 #, fuzzy, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -487,7 +487,7 @@ msgid "" "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" -"Muitas versões modernas do u-boot suportam USB e permitem arrancar através " +"Muitas versões modernas do U-Boot suportam USB e permitem arrancar através " "de dispositivos de armazenamento USB tais como pens USB. Infelizmente os " "passos exactos necessários para o fazer poderão variar bastante de " "dispositivo para dispositivo." @@ -514,8 +514,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -528,8 +528,8 @@ msgid "" msgstr "" "Para compilar uma pen USB de arranque para instalar &debian;, desempacote o " "tarball hd-media (veja <xref linkend=\"where-files\"/>) numa pen USB " -"formatada com um sistema de ficheiros suportado pela versão do u-boot no seu " -"dispositivo. Para versões do u-boot modernas, qualquer dos FAT16 / FAT32 / " +"formatada com um sistema de ficheiros suportado pela versão do U-Boot no seu " +"dispositivo. Para versões do U-Boot modernas, qualquer dos FAT16 / FAT32 / " "ext2 / ext3 / ext4 normalmente funciona. Depois copie o ficheiro da imagem " "ISO do primeiro CD ou DVD &debian; de instalação para a pen." @@ -537,12 +537,12 @@ msgstr "" #: boot-installer.xml:233 #, fuzzy, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run bootcmd_usb0</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -553,13 +553,13 @@ msgid "" "the USB-boot process any time from the U-Boot prompt by entering the " "<quote>run bootcmd_usb0</quote> command." msgstr "" -"A framework autoboot nas versões modernas do u-boot funciona de forma " +"A framework autoboot nas versões modernas do U-Boot funciona de forma " "similar às opções de ordem de arranque numa BIOS de PC, i.e. verifica numa " "lista de dispositivos de arranque possíveis por uma imagem de arranque e " "inicia a primeira que encontrar. Se não houver um sistema operativo " "instalado, ligar a pen USB e ligar o sistema deve resultar no inicio do " "instalador. Pode também iniciar o processo USB-boot em qualquer altura a " -"partir da linha de comandos do u-boot ao introduzir o comando <quote>run " +"partir da linha de comandos do U-Boot ao introduzir o comando <quote>run " "bootcmd_usb0</quote>." #. Tag: para @@ -568,15 +568,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " @@ -599,15 +599,15 @@ msgid "" msgstr "" "Um problema que pode surgir ao arrancar a partir de uma pen USB enquanto " "utiliza uma consola série pode ser o baudrate da consola errado. Se a " -"variável console for definida no u-boot, o script de arranque do &d-i; passa-" +"variável console for definida no U-Boot, o script de arranque do &d-i; passa-" "a automaticamente ao kernel para definir a consola primária e, se aplicável, " "o baudrate da consola. Infelizmente a forma de lidar com a variável da " "consola varia de plataforma para plataforma - em algumas plataformas, a " "variável console inclui o baudrate (com em <quote>console=ttyS0,115200</" "quote>), enquanto que noutras plataformas a variável console contém apenas o " "dispositivo (como em <quote>console=ttyS0</quote>). O último caso leva a uma " -"saída da consola errada quando o baudrate predefinido difere entre o u-boot " -"e o kernel. As versões modernas do u-boot vulgarmente utilizam 115200 baud " +"saída da consola errada quando o baudrate predefinido difere entre o U-Boot " +"e o kernel. As versões modernas do U-Boot vulgarmente utilizam 115200 baud " "enquanto que o kernel ainda está predefinido para os tradicionais 9600 baud. " "Se isto acontecer, deve definir manualmente a variável console para conter o " "baudrate correcto para o seu sistema e depois iniciar o instalador com o " diff --git a/po/pt/hardware.po b/po/pt/hardware.po index e642e9a7c..181bc08a9 100644 --- a/po/pt/hardware.po +++ b/po/pt/hardware.po @@ -896,7 +896,7 @@ msgstr "" #| msgid "" #| "Using a local display is technically possible without native display " #| "drivers via the <quote>simplefb</quote> infrastructure in the mainline " -#| "kernel, which relies on the <quote>u-boot</quote> bootloader for " +#| "kernel, which relies on the <quote>U-Boot</quote> bootloader for " #| "initializing the display hardware, but this is not supported by the u-" #| "boot version in &debian; 8." msgid "" @@ -907,8 +907,8 @@ msgid "" msgstr "" "É tecnicamente possível utilizar um display local sem drivers de display " "nativos através da infraestrutura <quote>simplefb</quote> no kernel oficial, " -"a qual depende do gestor de arranque <quote>u-boot</quote> para inicializar " -"o hardware do display, mas isto não é suportado na versão do u-boot que está " +"a qual depende do gestor de arranque <quote>U-Boot</quote> para inicializar " +"o hardware do display, mas isto não é suportado na versão do U-Boot que está " "em &debian; 8." #. Tag: term diff --git a/po/pt/preparing.po b/po/pt/preparing.po index 6cb75c706..016c7f231 100644 --- a/po/pt/preparing.po +++ b/po/pt/preparing.po @@ -2678,9 +2678,9 @@ msgstr "" #. Tag: title #: preparing.xml:1706 #, fuzzy, no-c-format -#| msgid "Setting the ethernet MAC address in u-boot" +#| msgid "Setting the ethernet MAC address in U-Boot" msgid "Setting the ethernet MAC address in U-Boot" -msgstr "Definir o endereço MAC de ethernet em u-boot" +msgstr "Definir o endereço MAC de ethernet em U-Boot" #. Tag: para #: preparing.xml:1707 @@ -2747,9 +2747,9 @@ msgstr "" #: preparing.xml:1736 #, fuzzy, no-c-format #| msgid "" -#| "On systems using u-boot as system firmware, the ethernet MAC address is " +#| "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 " +#| "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." @@ -2761,9 +2761,9 @@ msgid "" "ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</" "quote> makes the assignment permanent." msgstr "" -"Em sistemas que utilizem u-boot como firmware de sistema, o endereço MAC é " +"Em sistemas que utilizem U-Boot como firmware de sistema, o endereço MAC é " "colocado na variável de ambiente <quote>ethaddr</quote>. Pode ser verificado " -"na linha de comandos do u-boot com o comando <quote>printenv ethaddr</quote> " +"na linha de comandos do U-Boot com o comando <quote>printenv ethaddr</quote> " "e pode ser definido com o comando <quote>setenv ethaddr ca:ff:ee:12:34:56</" "quote>. Após definir o valor, o comando <quote>saveenv</quote> torna a " "atribuição permanente." @@ -2771,20 +2771,20 @@ msgstr "" #. Tag: title #: preparing.xml:1747 #, fuzzy, no-c-format -#| msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot" +#| msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" -msgstr "Problemas de relocação do Kernel/Initrd/Device-tree no u-boot" +msgstr "Problemas de relocação do Kernel/Initrd/Device-tree no U-Boot" #. Tag: para #: preparing.xml:1748 #, fuzzy, no-c-format #| msgid "" -#| "On some systems with older u-boot versions there can be problems with " +#| "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 " +#| "tree blob in memory during the boot process. In this case, U-Boot shows " #| "the message <quote>Starting kernel ...</quote>, but the system freezes " #| "afterwards without further output. These issues have been solved with " -#| "newer u-boot versions from v2014.07 onwards." +#| "newer U-Boot versions from v2014.07 onwards." 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-" @@ -2793,26 +2793,26 @@ msgid "" "afterwards without further output. These issues have been solved with newer " "U-Boot versions from v2014.07 onwards." msgstr "" -"Em alguns sistemas com versões mais antigas do u-boot podem haver problemas " +"Em alguns sistemas com versões mais antigas do U-Boot podem haver problemas " "com a correcta relocação do kernel Linux, do ramdisk inicial e do blob de " -"device-tree em memória durante o processo de arranque. Neste caso, o u-boot " +"device-tree em memória durante o processo de arranque. Neste caso, o U-Boot " "mostra a mensagem <quote>Starting kernel ...</quote>, mas o sistema congela " "de seguida sem mais qualquer saída. Estes problemas foram resolvidos com " -"novas versões do u-boot a partir da v2014.07." +"novas versões do U-Boot a partir da v2014.07." #. Tag: para #: preparing.xml:1757 #, fuzzy, no-c-format #| msgid "" -#| "If the system has originally used a u-boot version older than v2014.07 " +#| "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 " +#| "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 " +#| "data. It is possible to manually set bootm_size to the new U-Boot's " #| "default value by running the command <quote>env default bootm_size; " -#| "saveenv</quote> at the u-boot prompt." +#| "saveenv</quote> at the U-Boot prompt." 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 " @@ -2824,14 +2824,14 @@ msgid "" "running the command <quote>env default bootm_size; saveenv</quote> at the U-" "Boot prompt." msgstr "" -"Se o sistema utilizou originalmente uma versão do u-boot anterior à v2014.7 " +"Se o sistema utilizou originalmente uma versão do U-Boot anterior à v2014.7 " "e foi posteriormente actualizado para uma versão mais recente, o problema " -"pode ainda assim ocorrer mesmo após actualizar o u-boot. A actualização do u-" +"pode ainda assim ocorrer mesmo após actualizar o U-Boot. A actualização do u-" "boot normalmente não altera as variáveis de ambiente existentes e a correção " "requer que seja definida uma variável de ambiente adicional (bootm_size), o " -"que o u-boot faz automaticamente apenas em novas instalações sem dados de " +"que o U-Boot faz automaticamente apenas em novas instalações sem dados de " "ambiente. É possível definir manualmente bootm_size para a nova predefinição " -"do u-boot ao correr na linha de comandos o comando <quote>env default " +"do U-Boot ao correr na linha de comandos o comando <quote>env default " "bootm_size; saveenv</quote>." #. Tag: para @@ -2840,7 +2840,7 @@ msgstr "" #| msgid "" #| "Another possibility to circumvent relocation-related problems is to run " #| "the command <quote>setenv fdt_high ffffffff; setenv initrd_high " -#| "0xffffffff; saveenv</quote> at the u-boot prompt to completely disable " +#| "0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable " #| "the relocation of the initial ramdisk and the device-tree blob." msgid "" "Another possibility to circumvent relocation-related problems is to run the " @@ -2849,7 +2849,7 @@ msgid "" "the initial ramdisk and the device-tree blob." msgstr "" "Outra possibilidade de contornar os problemas relacionados com a relocação é " -"correr o seguinte comando na linha de comandos do u-boot <quote>setenv " +"correr o seguinte comando na linha de comandos do U-Boot <quote>setenv " "fdt_high ffffffff; setenv iitrd_high 0xffffffff; saveenv</quote> para " "desabilitar completamente a relocação do ramdisk inicial e do blob device-" "tree." diff --git a/po/pt/using-d-i.po b/po/pt/using-d-i.po index 2df8e0d33..ee27d66a9 100644 --- a/po/pt/using-d-i.po +++ b/po/pt/using-d-i.po @@ -5185,12 +5185,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"Para sistemas ARM que utilizem u-boot como o seu firmware de sistema e " +"Para sistemas ARM que utilizem U-Boot como o seu firmware de sistema e " "arranquem o kernel e ramdisk inicial a partir de um meio externo (tal como " "cartões MMC/SD, dispositivos de armazenamento USB ou discos IDE/SATA), o " "flash-kernel gera um script de arranque apropriado para permitir o arranque " diff --git a/po/ro/using-d-i.po b/po/ro/using-d-i.po index 6e62ff311..afd9d3d05 100644 --- a/po/ro/using-d-i.po +++ b/po/ro/using-d-i.po @@ -4660,7 +4660,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/ru/boot-installer.po b/po/ru/boot-installer.po index 587fef873..51d987a8f 100644 --- a/po/ru/boot-installer.po +++ b/po/ru/boot-installer.po @@ -88,10 +88,10 @@ msgstr "" #: boot-installer.xml:47 #, fuzzy, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. Older U-Boot versions can only boot files " #| "in uImage/uInitrd format, so these are often used on older armel systems. " -#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot " +#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot " #| "standard Linux kernels and ramdisk images, but the command syntax to do " #| "that is slightly different from that for booting uImages." msgid "" @@ -102,10 +102,10 @@ msgid "" "Linux kernels and ramdisk images, but the command syntax to do that is " "slightly different from that for booting uImages." msgstr "" -"uImage/uInitrd — формат образов, разработанный для микропрограммы u-boot, " -"которая используется во многих системах за основе ARM. Старые версии u-boot " +"uImage/uInitrd — формат образов, разработанный для микропрограммы U-Boot, " +"которая используется во многих системах за основе ARM. Старые версии U-Boot " "позволяли только загружать файлы в формате uImage/uInitrd, поэтому они часто " -"используются в старых системах armel. Новые версии u-boot — помимо загрузки " +"используются в старых системах armel. Новые версии U-Boot — помимо загрузки " "uImage/uInitrd — также загружают стандартные ядра Linux и образы ramdisk, но " "синтаксис команды загрузки несколько отличается от работающего на загрузку " "uImage." @@ -199,15 +199,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" -msgstr "Загрузка по TFTP из u-boot" +msgstr "Загрузка по TFTP из U-Boot" #. Tag: para #: boot-installer.xml:109 #, fuzzy, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -216,7 +216,7 @@ msgid "" "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" -"Загрузка по сети в системах, использующих микропрограмму u-boot, состоит из " +"Загрузка по сети в системах, использующих микропрограмму U-Boot, состоит из " "трёх шагов: а) настройка сети, б) загрузка образов (ядро/начальный ramdisk/" "dtb) в память и в) исполнение ранее загруженного кода." @@ -278,7 +278,7 @@ msgstr "" #: boot-installer.xml:132 #, fuzzy, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -299,7 +299,7 @@ msgid "" "name <quote>sun4i</quote> or the Allwinner A20, architecture name " "<quote>sun7i</quote>), you can e.g. use the follwing values:" msgstr "" -"В некоторых системах в u-boot уже настроены переменные окружения нужными " +"В некоторых системах в U-Boot уже настроены переменные окружения нужными " "адресами загрузки: kernel_addr_r, ramdisk_addr_r и fdt_addr_r. Вы можете " "проверить их наличие выполнив <informalexample><screen>\n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" @@ -400,7 +400,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, fuzzy, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -414,7 +414,7 @@ msgid "" "the ${fdt_addr_r} parameter." msgstr "" "Замечание: При загрузке стандартных образов linux важно загрузить образ " -"начального ramdisk после ядра и dtb так как u-boot устанавливает переменную " +"начального ramdisk после ядра и dtb так как U-Boot устанавливает переменную " "filesize равной размеру последнего загруженного файла, а для правильной " "работы команды bootz требуется размер образа ramdisk. При загрузке " "специального ядра устройства, то есть ядра без дерева устройств, просто не " @@ -475,15 +475,15 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, fuzzy, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" -msgstr "Загрузка с карты памяти USB из u-boot" +msgstr "Загрузка с карты памяти USB из U-Boot" #. Tag: para #: boot-installer.xml:207 #, fuzzy, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -491,7 +491,7 @@ msgid "" "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" -"Многие современные версии u-boot поддерживают USB и позволяют выполнять " +"Многие современные версии U-Boot поддерживают USB и позволяют выполнять " "загрузку накопителей USB, например карт памяти USB (флешек). К сожалению, " "точный шаги для выполнения данной процедуры для разных устройств различаются." @@ -517,8 +517,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -531,8 +531,8 @@ msgid "" msgstr "" "Чтобы создать загрузочный носитель USB для установки &debian; распакуйте tar-" "архив hd-media (смотрите <xref linkend=\"where-files\"/>) на носитель USB с " -"файловой системой, поддерживаемой версией u-boot вашего устройства. " -"Современные версии u-boot, обычно, работают с FAT16 / FAT32 / ext2 / ext3 / " +"файловой системой, поддерживаемой версией U-Boot вашего устройства. " +"Современные версии U-Boot, обычно, работают с FAT16 / FAT32 / ext2 / ext3 / " "ext4. После этого скопируйте на носитель образ ISO первого установочного CD " "или DVD &debian;." @@ -540,12 +540,12 @@ msgstr "" #: boot-installer.xml:233 #, fuzzy, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run usb_boot</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -556,12 +556,12 @@ msgid "" "the USB-boot process any time from the U-Boot prompt by entering the " "<quote>run bootcmd_usb0</quote> command." msgstr "" -"Механизм autoboot в современных версиях u-boot работает также как BIOS ПК, " +"Механизм autoboot в современных версиях U-Boot работает также как BIOS ПК, " "т. е. по списку возможных загрузочных устройств ищется корректный " "загрузочный образ и запускается первый найденный. Если операционная система " "не установлена, то подключение носителя USB и включение питания должно " "привести к запуску программы установки. Также вы можете запустить процесс " -"загрузки с USB в любой момент из приглашения u-boot с помощью команды " +"загрузки с USB в любой момент из приглашения U-Boot с помощью команды " "<quote>run usb_boot</quote>." #. Tag: para @@ -570,15 +570,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " @@ -601,14 +601,14 @@ msgid "" msgstr "" "Единственная проблема, которая может возникнуть при загрузке с USB при " "использовании последовательной консоли — несовпадение скоростей передачи " -"консоли. Если переменная консоли определена в u-boot, то загрузочный " +"консоли. Если переменная консоли определена в U-Boot, то загрузочный " "сценарий &d-i; автоматически передаёт её ядру для настройки первичной " "консоли устройства и, если уместно, скорость консоли. К сожалению, на разных " "платформах используется разная переменная консоли — у некоторых она содержит " "скорость (<quote>console=ttyS0,115200</quote>), а у других имеется только " "устройство (<quote>console=ttyS0</quote>). В последнем случае из-за " -"несовпадения скоростей консоли по умолчанию у u-boot и ядра вывод данных " -"искажается. Современные версии u-boot часто используют скорость 115200 бод, " +"несовпадения скоростей консоли по умолчанию у U-Boot и ядра вывод данных " +"искажается. Современные версии U-Boot часто используют скорость 115200 бод, " "а ядро по-прежнему работает на традиционных 9600 бод. Если такое произошло, " "то вы должны задать переменную консоли вручную с правильной скоростью и " "затем запустить программу установки с помощью команды <quote>run usb_boot</" diff --git a/po/ru/preparing.po b/po/ru/preparing.po index 1d998cdf4..94b8aaeb5 100644 --- a/po/ru/preparing.po +++ b/po/ru/preparing.po @@ -2658,9 +2658,9 @@ msgstr "" #. Tag: title #: preparing.xml:1706 #, fuzzy, no-c-format -#| msgid "Setting the ethernet MAC address in u-boot" +#| msgid "Setting the ethernet MAC address in U-Boot" msgid "Setting the ethernet MAC address in U-Boot" -msgstr "Задание MAC-адреса ethernet в u-boot" +msgstr "Задание MAC-адреса ethernet в U-Boot" #. Tag: para #: preparing.xml:1707 @@ -2724,9 +2724,9 @@ msgstr "" #: preparing.xml:1736 #, fuzzy, no-c-format #| msgid "" -#| "On systems using u-boot as system firmware, the ethernet MAC address is " +#| "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 " +#| "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." @@ -2738,29 +2738,29 @@ msgid "" "ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</" "quote> makes the assignment permanent." msgstr "" -"В устройствах с u-boot в качестве системной микропрограммы, ethernet MAC-" +"В устройствах с U-Boot в качестве системной микропрограммы, ethernet MAC-" "адрес хранится в переменной окружения <quote>ethaddr</quote>. Его можно " -"увидеть из приглашения u-boot по команде <quote>printenv ethaddr</quote> и " +"увидеть из приглашения U-Boot по команде <quote>printenv ethaddr</quote> и " "изменить командой <quote>setenv ethaddr ca:ff:ee:12:34:56</quote>. После " "установки значения команда <quote>saveenv</quote> делает его постоянным." #. Tag: title #: preparing.xml:1747 #, fuzzy, no-c-format -#| msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot" +#| msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" -msgstr "Проблемы размещения ядра/Initrd/дерева-устройств в u-boot" +msgstr "Проблемы размещения ядра/Initrd/дерева-устройств в U-Boot" #. Tag: para #: preparing.xml:1748 #, fuzzy, no-c-format #| msgid "" -#| "On some systems with older u-boot versions there can be problems with " +#| "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 " +#| "tree blob in memory during the boot process. In this case, U-Boot shows " #| "the message <quote>Starting kernel ...</quote>, but the system freezes " #| "afterwards without further output. These issues have been solved with " -#| "newer u-boot versions from v2014.07 onwards." +#| "newer U-Boot versions from v2014.07 onwards." 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-" @@ -2769,25 +2769,25 @@ msgid "" "afterwards without further output. These issues have been solved with newer " "U-Boot versions from v2014.07 onwards." msgstr "" -"В процессе загрузки в некоторых устройствах со старыми версиями u-boot могут " +"В процессе загрузки в некоторых устройствах со старыми версиями U-Boot могут " "быть проблемы с правильным размещением в памяти ядра Linux, начального " -"ramdisk и файла дерева устройств. В этот случае u-boot выводит сообщение " +"ramdisk и файла дерева устройств. В этот случае U-Boot выводит сообщение " "<quote>Starting kernel ...</quote>, и система повисает ничего больше не " -"выводя. Эти проблемы были решены в новых версиях u-boot, начиная с v2014.07." +"выводя. Эти проблемы были решены в новых версиях U-Boot, начиная с v2014.07." #. Tag: para #: preparing.xml:1757 #, fuzzy, no-c-format #| msgid "" -#| "If the system has originally used a u-boot version older than v2014.07 " +#| "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 " +#| "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 " +#| "data. It is possible to manually set bootm_size to the new U-Boot's " #| "default value by running the command <quote>env default bootm_size; " -#| "saveenv</quote> at the u-boot prompt." +#| "saveenv</quote> at the U-Boot prompt." 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 " @@ -2799,14 +2799,14 @@ msgid "" "running the command <quote>env default bootm_size; saveenv</quote> at the U-" "Boot prompt." msgstr "" -"Если в системе сначала использовалась версия u-boot старее v2014.07 и позже " +"Если в системе сначала использовалась версия U-Boot старее v2014.07 и позже " "она была обновлена на новую, то проблема может остаться. При обновлении u-" -"boot, обычно, не изменяются существующие переменные окружения u-boot и для " +"boot, обычно, не изменяются существующие переменные окружения U-Boot и для " "исправления требуется установка дополнительной переменной окружения " -"(bootm_size), что делается u-boot автоматически только при установке с нуля, " +"(bootm_size), что делается U-Boot автоматически только при установке с нуля, " "при отсутствии данных окружения. Возможно вручную указать bootm_size со " -"значением по умолчанию нового u-boot командой <quote>env default bootm_size; " -"saveenv</quote> из приглашения u-boot." +"значением по умолчанию нового U-Boot командой <quote>env default bootm_size; " +"saveenv</quote> из приглашения U-Boot." #. Tag: para #: preparing.xml:1768 @@ -2814,7 +2814,7 @@ msgstr "" #| msgid "" #| "Another possibility to circumvent relocation-related problems is to run " #| "the command <quote>setenv fdt_high ffffffff; setenv initrd_high " -#| "0xffffffff; saveenv</quote> at the u-boot prompt to completely disable " +#| "0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable " #| "the relocation of the initial ramdisk and the device-tree blob." msgid "" "Another possibility to circumvent relocation-related problems is to run the " @@ -2824,7 +2824,7 @@ msgid "" msgstr "" "Ещё один способ обхода проблем размещения: выполнить команду <quote>setenv " "fdt_high ffffffff; setenv initrd_high 0xffffffff; saveenv</quote> в " -"приглашении u-boot, полностью выключающую размещение начального ramdisk и " +"приглашении U-Boot, полностью выключающую размещение начального ramdisk и " "файла дерева устройств." #. Tag: title diff --git a/po/ru/using-d-i.po b/po/ru/using-d-i.po index 3a037070c..d542aa23a 100644 --- a/po/ru/using-d-i.po +++ b/po/ru/using-d-i.po @@ -5121,12 +5121,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"Для систем ARM, использующих u-boot в качестве системной микропрограммы и " +"Для систем ARM, использующих U-Boot в качестве системной микропрограммы и " "загружающих ядро и начальный ramdisk с внешнего носителя информации " "(например карты MMC/SD, USB или жёсткие диски IDE/SATA), flash-kernel " "генерирует соответствующий сценарий загрузки, который позволяет выполнить " diff --git a/po/sv/using-d-i.po b/po/sv/using-d-i.po index 1860057d4..ad7f562fc 100644 --- a/po/sv/using-d-i.po +++ b/po/sv/using-d-i.po @@ -5199,7 +5199,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/tl/using-d-i.po b/po/tl/using-d-i.po index 1ca81d172..493e91939 100644 --- a/po/tl/using-d-i.po +++ b/po/tl/using-d-i.po @@ -3766,7 +3766,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/vi/using-d-i.po b/po/vi/using-d-i.po index 2dcbc218d..fc42a18af 100644 --- a/po/vi/using-d-i.po +++ b/po/vi/using-d-i.po @@ -5204,7 +5204,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/zh_CN/using-d-i.po b/po/zh_CN/using-d-i.po index 6b1c64ada..8f6e6a8b5 100644 --- a/po/zh_CN/using-d-i.po +++ b/po/zh_CN/using-d-i.po @@ -4709,7 +4709,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." diff --git a/po/zh_TW/using-d-i.po b/po/zh_TW/using-d-i.po index 0112cac37..ae4368ae5 100644 --- a/po/zh_TW/using-d-i.po +++ b/po/zh_TW/using-d-i.po @@ -4309,7 +4309,7 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." |