# debian-installer po translation to Spanish # Copyright (C) 2004-2012 Software in the Public Interest # This file is distributed under the same license as the debian-installer # package. # # Changes: # - Initial translation # Rudy Godoy, 2004 # Javier Fernández-Sanguino, 2007 # Rubén Porras Campo, 2004 # Steve Langasek # # - Updates # Igor Támara, 2007 # Francisco García, 2007 # Carlos Galisteo, 2007 # Omar Campagne, 2010, 2012 # Camaleón , 2011 # Javier Fernández-Sanguino, 2013 # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guía de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # # Javier Fernández-Sanguino , 2010. msgid "" msgstr "" "Project-Id-Version: debian-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2016-12-18 14:58+0000\n" "PO-Revision-Date: 2013-04-28 22:38+0200\n" "Last-Translator: Javier Fernández-Sanguino \n" "Language-Team: Debian l10n Spanish \n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Virtaal 0.7.1\n" #. Tag: title #: hardware.xml:5 #, no-c-format msgid "System Requirements" msgstr "Requisitos del sistema" #. Tag: para #: hardware.xml:7 #, no-c-format msgid "" "This section contains information about what hardware you need to get " "started with &debian;. You will also find links to further information about " "hardware supported by GNU and &arch-kernel;." msgstr "" "Esta sección contiene información sobre el hardware necesario para empezar " "con &debian;. También encontrará enlaces a más información sobre el hardware " "compatible con GNU y &arch-kernel;." #. Tag: title #: hardware.xml:20 #, no-c-format msgid "Supported Hardware" msgstr "Hardware compatible" #. Tag: para #: hardware.xml:21 #, no-c-format msgid "" "&debian; does not impose hardware requirements beyond the requirements of " "the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any " "architecture or platform to which the Linux or kFreeBSD kernel, libc, " "gcc, etc. have been ported, and for which a &debian; port " "exists, can run &debian;. Please refer to the Ports pages at for more details on &arch-title; architecture " "systems which have been tested with &debian-gnu;." msgstr "" "&debian; no impone requisitos de hardware más allá de los que establecen el " "núcleo Linux o kFreeBSD y el conjunto de herramientas GNU. En cualquier " "caso, cualquier arquitectura o plataforma a la que se haya adaptado el " "núcleo Linux o kFreeBSD, libc, gcc, etc., y para los que " "exista una adaptación de &debian;, puede ejecutar &debian;. Por favor, " "diríjase a las páginas de adaptaciones en para más información sobre sistemas de arquitectura &arch-title; " "probados con &debian-gnu;." #. Tag: para #: hardware.xml:32 #, no-c-format msgid "" "Rather than attempting to describe all the different hardware configurations " "which are supported for &arch-title;, this section contains general " "information and pointers to where additional information can be found." msgstr "" "En lugar de intentar describir las diferentes configuraciones de hardware " "compatibles con &arch-title;, esta sección contiene información general y " "referencias adicionales donde puede encontrar más información." #. Tag: title #: hardware.xml:41 #, no-c-format msgid "Supported Architectures" msgstr "Arquitecturas compatibles" #. Tag: para #: hardware.xml:42 #, fuzzy, no-c-format #| msgid "" #| "&debian; GNU/Linux &release; supports eleven major architectures and " #| "several variations of each architecture known as flavors." msgid "" "&debian; GNU/Linux &release; supports ten major architectures and several " "variations of each architecture known as flavors." msgstr "" "&debian; GNU/Linux &release; permite el uso de once arquitecturas " "principales y algunas variaciones de cada arquitectura conocidas como " "sabores." #. Tag: entry #: hardware.xml:53 #, no-c-format msgid "Architecture" msgstr "Arquitectura" #. Tag: entry #: hardware.xml:53 #, no-c-format msgid "&debian; Designation" msgstr "Designación de &debian;" #. Tag: entry #: hardware.xml:54 #, no-c-format msgid "Subarchitecture" msgstr "Subarquitectura" #. Tag: entry #: hardware.xml:54 #, no-c-format msgid "Flavor" msgstr "Sabor" #. Tag: entry #: hardware.xml:60 #, no-c-format msgid "Intel x86-based" msgstr "Basada en Intel x86" #. Tag: entry #: hardware.xml:61 #, no-c-format msgid "i386" msgstr "i386" #. Tag: entry #: hardware.xml:67 #, no-c-format msgid "AMD64 & Intel 64" msgstr "AMD64 e Intel 64" #. Tag: entry #: hardware.xml:68 #, no-c-format msgid "amd64" msgstr "amd64" #. Tag: entry #: hardware.xml:74 #, no-c-format msgid "ARM" msgstr "ARM" #. Tag: entry #: hardware.xml:75 #, no-c-format msgid "armel" msgstr "armel" #. Tag: entry #: hardware.xml:76 #, fuzzy, no-c-format #| msgid "Marvell Kirkwood" msgid "Marvell Kirkwood and Orion" msgstr "Marvell Kirkwood" #. Tag: entry #: hardware.xml:77 #, fuzzy, no-c-format #| msgid "Marvell Orion" msgid "marvell" msgstr "Marvell Orion" #. Tag: entry #: hardware.xml:79 #, no-c-format msgid "Versatile" msgstr "Versatile" #. Tag: entry #: hardware.xml:80 #, no-c-format msgid "versatile" msgstr "versatile" #. Tag: entry #: hardware.xml:84 #, no-c-format msgid "ARM with hardware FPU" msgstr "ARM con hardware FPU" #. Tag: entry #: hardware.xml:85 #, no-c-format msgid "armhf" msgstr "armhf" #. Tag: entry #: hardware.xml:86 #, no-c-format msgid "multiplatform" msgstr "" #. Tag: entry #: hardware.xml:87 #, no-c-format msgid "armmp" msgstr "" #. Tag: entry #: hardware.xml:89 #, no-c-format msgid "multiplatform for LPAE-capable systems" msgstr "" #. Tag: entry #: hardware.xml:90 #, no-c-format msgid "armmp-lpae" msgstr "" #. Tag: entry #: hardware.xml:94 #, no-c-format msgid "64bit ARM" msgstr "" #. Tag: entry #: hardware.xml:95 #, no-c-format msgid "arm64" msgstr "" #. Tag: entry #: hardware.xml:101 #, no-c-format msgid "MIPS (big endian)" msgstr "MIPS (big endian)" #. Tag: entry #: hardware.xml:102 #, no-c-format msgid "mips" msgstr "mips" #. Tag: entry #: hardware.xml:111 hardware.xml:124 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "MIPS Malta (32 bit)" #. Tag: entry #: hardware.xml:112 hardware.xml:125 #, no-c-format msgid "4kc-malta" msgstr "4kc-malta" #. Tag: entry #: hardware.xml:114 hardware.xml:127 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "MIPS Malta (64 bit)" #. Tag: entry #: hardware.xml:115 hardware.xml:128 #, no-c-format msgid "5kc-malta" msgstr "5kc-malta" #. Tag: entry #: hardware.xml:117 hardware.xml:130 #, no-c-format msgid "Cavium Octeon" msgstr "" #. Tag: entry #: hardware.xml:118 hardware.xml:131 #, no-c-format msgid "octeon" msgstr "" #. Tag: entry #: hardware.xml:122 #, no-c-format msgid "MIPS (little endian)" msgstr "MIPS (little endian)" #. Tag: entry #: hardware.xml:123 #, no-c-format msgid "mipsel" msgstr "mipsel" #. Tag: entry #: hardware.xml:133 #, no-c-format msgid "Loongson 3A" msgstr "" #. Tag: entry #: hardware.xml:134 #, no-c-format msgid "loongson-3" msgstr "" #. Tag: entry #: hardware.xml:140 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "IBM/Motorola PowerPC" #. Tag: entry #: hardware.xml:141 #, fuzzy, no-c-format #| msgid "powerpc" msgid "powerpc" msgstr "powerpc" #. Tag: entry #: hardware.xml:154 #, no-c-format msgid "Power Systems" msgstr "Power Systems" #. Tag: entry #: hardware.xml:155 #, no-c-format msgid "ppc64el" msgstr "ppc64el" #. Tag: entry #: hardware.xml:156 #, no-c-format msgid "IBM POWER8 or newer machines" msgstr "" #. Tag: entry #: hardware.xml:181 #, no-c-format msgid "64bit IBM S/390" msgstr "IBM S/390 64bit" #. Tag: entry #: hardware.xml:182 #, no-c-format msgid "s390x" msgstr "s390x" #. Tag: entry #: hardware.xml:183 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "IPL del lector VM y DASD" #. Tag: entry #: hardware.xml:184 #, no-c-format msgid "generic" msgstr "genérico" #. Tag: para #: hardware.xml:191 #, no-c-format msgid "" "This document covers installation for the &arch-title; " "architecture using the &arch-kernel; kernel. If you are " "looking for information on any of the other &debian;-supported architectures " "take a look at the &debian;-" "Ports pages." msgstr "" "Este documento cubre la instalación para la arquitectura &arch-" "title; usando el núcleo &arch-kernel;. Si " "busca información sobre cualquiera de las otras arquitecturas compatibles " "con &debian; consulte las páginas de las adaptaciones de &debian;." #. Tag: para #: hardware.xml:201 #, no-c-format msgid "" "This is the first official release of &debian-gnu; for the &arch-title; " "architecture. We feel that it has proven itself sufficiently to be released. " "However, because it has not had the exposure (and hence testing by users) " "that some other architectures have had, you may encounter a few bugs. Use " "our Bug Tracking System to report any " "problems; make sure to mention the fact that the bug is on the &arch-title; " "platform using the &arch-kernel; kernel. It can be " "necessary to use the debian-&arch-" "listname; mailing list as well." msgstr "" "Esta es la primera versión oficial de &debian-gnu; para la arquitectura " "&arch-title;. Consideramos que se ha probado ésta lo suficientemente como " "para ser publicada. No obstante, podría encontrar algunos fallos dado que " "ésta no ha tenido la exposición (y por tanto pruebas por usuarios) que han " "tenido otras arquitecturas. Utilice nuestro sistema " "de seguimiento de fallos para informar cualquier problema; asegúrese " "de indicar que el problema se encuentra en la plataforma &arch-title; usando " "el núcleo &arch-kernel;. También, podría ser necesario " "utilizar la lista de correo de debian-" "&arch-listname;." #. Tag: title #: hardware.xml:223 #, no-c-format msgid "CPU Support" msgstr "Compatibilidad de CPU" #. Tag: para #: hardware.xml:224 #, no-c-format msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" "Se permiten tanto los procesadores AMD64 como los procesadores Intel 64." #. Tag: title #: hardware.xml:248 #, no-c-format msgid "Three different ARM ports" msgstr "" #. Tag: para #: hardware.xml:250 #, no-c-format msgid "" "The ARM architecture has evolved over time and modern ARM processors provide " "features which are not available in older models. &debian; therefore " "provides three ARM ports to give the best support for a very wide range of " "different machines:" msgstr "" #. Tag: para #: hardware.xml:256 #, no-c-format msgid "" "&debian;/armel targets older 32-bit ARM processors without support for a " "hardware floating point unit (FPU)," msgstr "" #. Tag: para #: hardware.xml:260 #, no-c-format msgid "" "&debian;/armhf works only on newer 32-bit ARM processors which implement at " "least the ARMv7 architecture with version 3 of the ARM vector floating point " "specification (VFPv3). It makes use of the extended features and performance " "enhancements available on these models." msgstr "" #. Tag: para #: hardware.xml:267 #, no-c-format msgid "" "&debian;/arm64 works on 64-bit ARM processors which implement at least the " "ARMv8 architecture." msgstr "" #. Tag: para #: hardware.xml:274 #, fuzzy, no-c-format #| msgid "" #| "Most ARM CPUs may be run in either endian mode (big or little). However, " #| "the majority of current system implementation uses little-endian mode. " #| "&debian; currently only supports little-endian ARM systems." msgid "" "Technically, all currently available ARM CPUs can be run in either endian " "mode (big or little), but in practice the vast majority use little-endian " "mode. All of &debian;/arm64, &debian;/armhf and &debian;/armel support only " "little-endian systems." msgstr "" "Muchas CPUs ARM también pueden funcionar en cualquier modo endian «little-" "endian» o «big-endian»). Sin embargo, la mayoría de las implementaciones de " "sistemas actuales usan el modo «little-endian». &debian; sólo permite " "actualmente sistemas ARM «little-endian»." #. Tag: title #: hardware.xml:283 #, no-c-format msgid "Variations in ARM CPU designs and support complexity" msgstr "" #. Tag: para #: hardware.xml:285 #, no-c-format msgid "" "ARM systems are much more heterogeneous than those based on the i386/amd64-" "based PC architecture, so the support situation can be much more complicated." msgstr "" #. Tag: para #: hardware.xml:291 #, no-c-format msgid "" "The ARM architecture is used mainly in so-called system-on-chip (SoC) designs. These SoCs are designed by many different companies " "with vastly varying hardware components even for the very basic " "functionality required to bring the system up. System firmware interfaces " "have been increasingly standardised over time, but especially on older " "hardware firmware/boot interfaces vary a great deal, so on these systems the " "Linux kernel has to take care of many system-specific low-level issues which " "would be handled by the mainboard's BIOS in the PC world." msgstr "" #. Tag: para #: hardware.xml:303 #, no-c-format msgid "" "At the beginning of the ARM support in the Linux kernel, the hardware " "variety resulted in the requirement of having a separate kernel for each ARM " "system in contrast to the one-fits-all kernel for PC systems. " "As this approach does not scale to a large number of different systems, work " "was done to allow booting with a single ARM kernel that can run on different " "ARM systems. Support for newer ARM systems is now implemented in a way that " "allows the use of such a multiplatform kernel, but for several older systems " "a separate specific kernel is still required. Because of this, the standard " "&debian; distribution only supports installation on a selected number of " "such older ARM systems, alongside the newer systems which are supported by " "the ARM multiplatform kernels (called armmp) in &debian;/" "armhf." msgstr "" #. Tag: para #: hardware.xml:319 #, no-c-format msgid "" "The ARM architecture is used mainly in so-called system-on-chip (SoC) designs. These SoCs are designed by many different companies, " "often with vastly varying hardware components even for the very basic " "functionality required to bring the system up. Older versions of the ARM " "architecture have seen massive differences from one SoC to the next, but " "ARMv8 (arm64) is much more standardised and so is easier for the Linux " "kernel and other software to support." msgstr "" #. Tag: para #: hardware.xml:330 #, no-c-format msgid "" "Server versions of ARMv8 hardware are typically configured using the Unified " "Extensible Firmware Interface (UEFI) and Advanced Configuration and Power " "Interface (ACPI) standards. These two provide common, device-independent " "ways to boot and configure computer hardware. They are also common in the " "x86 PC world." msgstr "" #. Tag: title #: hardware.xml:340 #, no-c-format msgid "Platforms supported by Debian/arm64" msgstr "" #. Tag: para #: hardware.xml:342 #, no-c-format msgid "" "Arm64/AArch64/ARMv8 hardware became available quite late in the &debian; " "&releasename-cap; release cycle so not many platforms had support merged in " "the mainline kernel version by the time of this release; this is the main " "requirement to have &d-i; working on them. The following platforms are known " "to be supported by &debian;/arm64 in this release. There is only one kernel " "image, which supports all the listed platforms." msgstr "" #. Tag: term #: hardware.xml:354 #, no-c-format msgid "Applied Micro (APM) Mustang/X-Gene" msgstr "" #. Tag: para #: hardware.xml:356 #, no-c-format msgid "" "The APM Mustang was the first Linux-capable ARMv8 system available. It uses " "the X-gene SoC, which has since also been used in other machines. It is an 8-" "core CPU, with ethernet, USB and serial. A common form-factor looks just " "like a desktop PC box, but many other versions are expected in the future. " "Most of the hardware is supported in the mainline kernel, but at this point " "USB support is lacking in the &releasename-cap; kernel." msgstr "" #. Tag: term #: hardware.xml:370 #, no-c-format msgid "ARM Juno Development Platform" msgstr "" #. Tag: para #: hardware.xml:372 #, no-c-format msgid "" "Juno is a capable development board with a 6-core (2xA57, 4xA53) ARMv8-A " "800Mhz CPU, Mali (T624) graphics, 8GB DDR3 RAM, Ethernet, USB, Serial. It " "was designed for system bring-up and power testing so is neither small nor " "cheap, but was one of the first boards available. All the on-board hardware " "is supported in the mainline kernel and in &releasename-cap;." msgstr "" #. Tag: para #: hardware.xml:386 #, no-c-format msgid "" "When using &d-i; on non-UEFI systems, you may have to manually make the " "system bootable at the end of the installation, e.g. by running the required " "commands in a shell started from within &d-i;. flash-kernel knows how to set " "up an X-Gene system booting with U-Boot." msgstr "" #. Tag: title #: hardware.xml:394 #, fuzzy, no-c-format #| msgid "The supported platforms are:" msgid "Other platforms" msgstr "Las plataformas compatibles son:" #. Tag: para #: hardware.xml:395 #, no-c-format msgid "" "The multiplatform support in the arm64 Linux kernel may also allow running " "&d-i; on arm64 systems not explicitly listed above. So long as the kernel " "used by &d-i; has support for the target system's components, and a device-" "tree file for that target is available, a new target system may work just " "fine. In these cases, the installer can usually provide a working " "installation, and so long as UEFI is in use, it should be able to make the " "system bootable as well. If UEFI is not used you may also need to perform " "some manual configuration steps to make the system bootable." msgstr "" #. Tag: title #: hardware.xml:411 #, no-c-format msgid "Platforms supported by Debian/armhf" msgstr "" #. Tag: para #: hardware.xml:413 #, no-c-format msgid "" "The following systems are known to work with &debian;/armhf using the " "multiplatform (armmp) kernel:" msgstr "" #. Tag: term #: hardware.xml:420 #, no-c-format msgid "Freescale MX53 Quick Start Board (MX53 LOCO Board)" msgstr "" #. Tag: para #: hardware.xml:422 #, no-c-format msgid "The IMX53QSB is a development board based on the i.MX53 SoC." msgstr "" #. Tag: term #: hardware.xml:429 #, fuzzy, no-c-format #| msgid "versatile" msgid "Versatile Express" msgstr "versatile" #. Tag: para #: hardware.xml:431 #, no-c-format msgid "" "The Versatile Express is a development board series from ARM consisting of a " "baseboard which can be equipped with various CPU daughter boards." msgstr "" #. Tag: term #: hardware.xml:440 #, no-c-format msgid "Certain Allwinner sunXi-based development boards and embedded systems" msgstr "" #. Tag: para #: hardware.xml:443 #, no-c-format msgid "" "The armmp kernel supports several development boards and embedded systems " "based on the Allwinner A10 (architecture codename sun4i), " "A10s/A13 (architecture codename sun5i), A20 (architecture " "codename sun7i), A31/A31s (architecture codename " "sun6i) and A23/A33 (part of the sun8i family) " "SoCs. Full installer support (including provision of ready-made SD card " "images with the installer) is currently available for the following sunXi-" "based systems:" msgstr "" #. Tag: para #: hardware.xml:457 #, no-c-format msgid "Cubietech Cubieboard 1 + 2 / Cubietruck" msgstr "" #. Tag: para #: hardware.xml:460 #, no-c-format msgid "LeMaker Banana Pi and Banana Pro" msgstr "" #. Tag: para #: hardware.xml:463 #, no-c-format msgid "LinkSprite pcDuino and pcDuino3" msgstr "" #. Tag: para #: hardware.xml:466 #, no-c-format msgid "" "Olimex A10-Olinuxino-LIME / A20-Olinuxino-LIME / A20-Olinuxino-LIME2 / A20-" "Olinuxino Micro / A20-SOM-EVB" msgstr "" #. Tag: para #: hardware.xml:470 #, no-c-format msgid "Xunlong OrangePi Plus" msgstr "" #. Tag: para #: hardware.xml:476 #, no-c-format msgid "" "System support for Allwinner sunXi-based devices is limited to drivers and " "device-tree information available in the mainline Linux kernel. Vendor-" "specific kernel trees (such as the Allwinner SDK kernels) and the android-" "derived linux-sunxi.org kernel 3.4 series are not supported by &debian;." msgstr "" #. Tag: para #: hardware.xml:484 #, no-c-format msgid "" "The mainline Linux kernel generally supports serial console, ethernet, SATA, " "USB and MMC/SD-cards on Allwinner A10, A10s/A13, A20, A23/A33 and A31/A31s " "SoCs. The level of support for local display (HDMI/VGA/LCD) and audio " "hardware varies between individual systems. For most systems, the kernel " "doesn't have native graphics drivers but instead uses the simplefb infrastructure in which the bootloader initializes the display and " "the kernel just re-uses the pre-initialized framebuffer. This generally " "works reasonably well, although it results in certain limitations (the " "display resolution cannot be changed on the fly and display powermanagement " "is not possible)." msgstr "" #. Tag: para #: hardware.xml:499 #, no-c-format msgid "" "Onboard flash memory intended to be used as a mass storage device generally " "exists in two basic variants on sunXi-based systems: raw NAND flash and eMMC " "flash. Most older sunXi-based boards with onboard flash storage use raw NAND " "flash for which support is not generally available in the mainline kernel " "and therefore also not in Debian. A number of newer systems use eMMC flash " "instead of raw NAND flash. An eMMC flash chip basically appears as a fast, " "non-removable SD card and is supported in the same way as a regular SD card." msgstr "" #. Tag: para #: hardware.xml:512 #, no-c-format msgid "" "The installer includes basic support for a number of sunXi-based systems not " "listed above, but it is largely untested on those systems as the &debian; " "project doesn't have access to the corresponding hardware. No pre-built SD " "card images with the installer are provided for those systems. Development " "boards with such limited support include:" msgstr "" #. Tag: para #: hardware.xml:521 #, no-c-format msgid "Olimex A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro" msgstr "" #. Tag: para #: hardware.xml:525 #, no-c-format msgid "Sinovoip BPI-M2 (A31s-based)" msgstr "" #. Tag: para #: hardware.xml:528 #, no-c-format msgid "Xunlong Orange Pi (A20-based) / Orange Pi Mini (A20-based)" msgstr "" #. Tag: para #: hardware.xml:533 #, no-c-format msgid "" "In addition to the SoCs and systems listed above, the installer has very " "limited support for the Allwinner H3 SoC and a number of boards based on it. " "Mainline kernel support for the H3 is still largely work in progress at the " "time of the Debian 9 release freeze, so the installer only supports serial " "console, MMC/SD and the USB host controller on H3-based systems. There is no " "driver for the on-board ethernet port of the H3 yet, so networking is only " "possible with a USB ethernet adaptor or a USB wifi dongle. Systems based on " "the H3 for which such very basic installer support is available include:" msgstr "" #. Tag: para #: hardware.xml:546 #, no-c-format msgid "FriendlyARM NanoPi NEO" msgstr "" #. Tag: para #: hardware.xml:549 #, no-c-format msgid "" "Xunlong Orange Pi Lite / Orange Pi One / Orange Pi PC / Orange Pi PC Plus / " "Orange Pi Plus / Orange Pi Plus 2E / Orange Pi 2" msgstr "" #. Tag: term #: hardware.xml:560 #, no-c-format msgid "NVIDIA Jetson TK1" msgstr "" #. Tag: para #: hardware.xml:562 #, no-c-format msgid "" "The NVIDIA Jetson TK1 is a developer board based on the Tegra K1 chip (also " "known as Tegra 124). The Tegra K1 features a quad-core 32-bit ARM Cortex-A15 " "CPU and Kepler GPU (GK20A) with 192 CUDA cores. Other systems based on the " "Tegra 124 may work, too." msgstr "" #. Tag: term #: hardware.xml:573 #, no-c-format msgid "Seagate Personal Cloud and Seagate NAS" msgstr "" #. Tag: para #: hardware.xml:575 #, no-c-format msgid "" "The Seagate Personal Cloud and Seagate NAS are NAS devices based on " "Marvell's Armada 370 platform. Debian supports the Personal Cloud (SRN21C), " "Personal Cloud 2-Bay (SRN22C), Seagate NAS 2-Bay (SRPD20) and Seagate NAS 4-" "Bay (SRPD40)." msgstr "" #. Tag: term #: hardware.xml:585 #, no-c-format msgid "SolidRun Cubox-i2eX / Cubox-i4Pro" msgstr "" #. Tag: para #: hardware.xml:587 #, no-c-format msgid "" "The Cubox-i series is a set of small, cubical-shaped systems based on the " "Freescale i.MX6 SoC family. System support for the Cubox-i series is limited " "to drivers and device-tree information available in the mainline Linux " "kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by " "&debian;. Available drivers in the mainline kernel include serial console, " "ethernet, USB, MMC/SD-card and display support over HDMI (console and X11). " "In addition to that, the eSATA port on the Cubox-i4Pro is supported." msgstr "" #. Tag: term #: hardware.xml:602 #, no-c-format msgid "Wandboard Quad" msgstr "" #. Tag: para #: hardware.xml:604 #, no-c-format msgid "" "The Wandboard Quad is a development board based on the Freescale i.MX6 Quad " "SoC. System support for it is limited to drivers and device-tree information " "available in the mainline Linux kernel; the wandboard-specific 3.0 and 3.10 " "kernel series from wandboard.org are not supported by &debian;. The mainline " "kernel includes driver support for serial console, display via HDMI (console " "and X11), ethernet, USB, MMC/SD and SATA. Support for the onboard audio " "options (analog, S/PDIF, HDMI-Audio) and for the onboard WLAN/Bluetooth " "module is not available in &debian; 8." msgstr "" #. Tag: para #: hardware.xml:622 #, no-c-format msgid "" "Generally, the ARM multiplatform support in the Linux kernel allows running " "&d-i; on armhf systems not explicitly listed above, as long as the kernel " "used by &d-i; has support for the target system's components and a device-" "tree file for the target is available. In these cases, the installer can " "usually provide a working installation, but it may not be able to " "automatically make the system bootable. Doing that in many cases requires " "device-specific information." msgstr "" #. Tag: para #: hardware.xml:634 #, no-c-format msgid "" "When using &d-i; on such systems, you may have to manually make the system " "bootable at the end of the installation, e.g. by running the required " "commands in a shell started from within &d-i;." msgstr "" #. Tag: title #: hardware.xml:643 #, no-c-format msgid "Platforms no longer supported by Debian/armhf" msgstr "" #. Tag: term #: hardware.xml:647 #, no-c-format msgid "EfikaMX" msgstr "" #. Tag: para #: hardware.xml:648 #, no-c-format msgid "" "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) was " "supported in &debian; 7 with a platform-specific kernel, but is no longer " "supported from &debian; 8 onwards. The code required to build the formerly " "used platform-specific kernel has been removed from the upstream Linux " "kernel source in 2012, so &debian; cannot provide newer builds. Using the " "armmp multiplatform kernel on the EfikaMX platform would require device-tree " "support for it, which is currently not available." msgstr "" #. Tag: title #: hardware.xml:666 #, no-c-format msgid "Platforms supported by Debian/armel" msgstr "" #. Tag: para #: hardware.xml:668 #, no-c-format msgid "" "The following platforms are supported by &debian;/armel; they require " "platform-specific kernels." msgstr "" #. Tag: term #: hardware.xml:676 #, no-c-format msgid "Kirkwood" msgstr "Kirkwood" #. Tag: para #: hardware.xml:677 #, no-c-format msgid "" "Kirkwood is a system-on-chip (SoC) from Marvell that integrates an ARM CPU, " "Ethernet, SATA, USB, and other functionality in one chip. &debian; currently " "supports the following Kirkwood based devices:" msgstr "" #. Tag: ulink #: hardware.xml:685 #, no-c-format msgid "" "Plug computers (SheevaPlug, GuruPlug, DreamPlug and Seagate FreeAgent " "DockStar)" msgstr "" #. Tag: para #: hardware.xml:688 #, no-c-format msgid "" "QNAP Turbo Station " "(all TS-11x/TS-12x, HS-210, TS-21x/TS-22x and TS-41x/TS-42x models)" msgstr "" #. Tag: para #: hardware.xml:692 #, no-c-format msgid "" "LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 " "Network v2, 2Big Network v2 and 5Big Network v2)" msgstr "" #. Tag: para #: hardware.xml:696 #, no-c-format msgid "OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate)" msgstr "" #. Tag: term #: hardware.xml:705 hardware.xml:750 #, no-c-format msgid "Orion5x" msgstr "Orion5x" #. Tag: para #: hardware.xml:706 #, fuzzy, no-c-format #| msgid "" #| "Orion is a system on a chip (SoC) from Marvell that integrates an ARM " #| "CPU, Ethernet, SATA, USB, and other functionality in one chip. There are " #| "many Network Attached Storage (NAS) devices on the market that are based " #| "on an Orion chip. We currently support the following Orion based devices: " #| "Buffalo Kurobox, " #| "D-Link DNS-323 and HP mv2120." msgid "" "Orion is a system-on-chip (SoC) from Marvell that integrates an ARM CPU, " "Ethernet, SATA, USB, and other functionality in one chip. There are many " "Network Attached Storage (NAS) devices on the market that are based on an " "Orion chip. &debian; currently supports the following Orion based devices: " "Buffalo Kurobox, HP mv2120 and QNAP TS-109, TS-209, TS-409 and TS-409U and variants." msgstr "" "Orion es un sistema en un chip (SoC) de Marvell que integra una CPU ARM, " "Ethernet, SATA, USB y otras funcionalidades en un chip. Hay muchos " "dispositivos de almacenamiento con conexión a la red (NAS) en el mercado que " "están basados en el chip Orion. Actualmente, hay compatibilidad con los " "siguientes dispositivos basados en Orion: Buffalo Kurobox, D-Link DNS-323 y HP " "mv2120." #. Tag: term #: hardware.xml:721 #, no-c-format msgid "Versatile" msgstr "Versatile" #. Tag: para #: hardware.xml:722 #, fuzzy, no-c-format #| msgid "" #| "The Versatile platform is emulated by QEMU and is therefore a nice way to " #| "test and run &debian; on ARM if you don't have the hardware." msgid "" "The Versatile platform is emulated by QEMU and is therefore a nice way to " "test and run &debian; on ARM if you don't have real hardware." msgstr "" "La plataforma Versatile se emula con QEMU y por lo tanto es una buena forma " "de probar y ejecutar &debian; en ARM si no tiene el hardware." #. Tag: title #: hardware.xml:735 #, no-c-format msgid "Platforms and devices no longer supported by Debian/armel" msgstr "" #. Tag: term #: hardware.xml:739 #, no-c-format msgid "IXP4xx" msgstr "IXP4xx" #. Tag: para #: hardware.xml:740 #, no-c-format msgid "" "Support for the Intel IXP4xx platform has been dropped in &debian; 9. The " "Linksys NSLU2 device is based on IXP4xx and is therefore no longer supported." msgstr "" #. Tag: para #: hardware.xml:751 #, no-c-format msgid "" "Support for the D-Link DNS-323 and Conceptronic CH3SNAS devices has been " "dropped from the Orion5x platform in &debian; 9. The Linux kernel no longer " "fits into the flash on these devices. Other Orion devices, such as Buffalo " "Kurobox and HP mv2120, are still supported." msgstr "" #. Tag: title #: hardware.xml:770 hardware.xml:820 hardware.xml:878 hardware.xml:908 #: hardware.xml:938 hardware.xml:1381 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "Compatibilidad de CPU, placas base y vídeo" #. Tag: para #: hardware.xml:771 #, no-c-format msgid "" "Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. " "This section merely outlines the basics." msgstr "" "Puede encontrar información completa sobre los periféricos compatibles en el " "CÓMO de compatibilidad hardware de " "Linux. Esta sección sólo trata algunos aspectos básicos." #. Tag: title #: hardware.xml:779 hardware.xml:855 #, no-c-format msgid "CPU" msgstr "CPU" #. Tag: para #: hardware.xml:780 #, fuzzy, no-c-format #| msgid "" #| "Nearly all x86-based (IA-32) processors still in use in personal " #| "computers are supported, including all varieties of Intel's \"Pentium\" " #| "series. This also includes 32-bit AMD and VIA (former Cyrix) processors, " #| "and processors like the Athlon XP and Intel P4 Xeon." msgid "" "Nearly all x86-based (IA-32) processors still in use in personal computers " "are supported. This also includes 32-bit AMD and VIA (former Cyrix) " "processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" "Prácticamente todos los procesadores basados en x86 (IA-32) utilizados en " "ordenadores personales son compatibles, incluyendo todas las variedades de " "la serie «Pentium» de Intel. Esto también incluye los procesadores AMD y VIA " "(anteriormente Cyrix). También se pueden usar procesadores nuevos como " "Athlon XP e Intel P4 Xeon." #. Tag: para #: hardware.xml:787 #, no-c-format msgid "" "However, &debian; GNU/Linux &releasename; will not run " "on 586 (Pentium) or earlier processors." msgstr "" #. Tag: para #: hardware.xml:793 #, no-c-format msgid "" "If your system has a 64-bit processor from the AMD64 or Intel 64 families, " "you will probably want to use the installer for the amd64 architecture " "instead of the installer for the (32-bit) i386 architecture." msgstr "" "Si su sistema tiene un procesador de 64 bits de las familias de AMD64 o " "Intel 64 es posible que quiera utilizar el instalador para la arquitectura " "amd64 en lugar del instalador para la arquitectura i386 (de 32 bits)." #. Tag: title #: hardware.xml:802 #, no-c-format msgid "I/O Bus" msgstr "Bus de E/S" #. Tag: para #: hardware.xml:803 #, fuzzy, no-c-format #| msgid "" #| "The system bus is the part of the motherboard which allows the CPU to " #| "communicate with peripherals such as storage devices. Your computer must " #| "use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes " #| "called the VL bus). Essentially all personal computers sold in recent " #| "years use one of these." msgid "" "The system bus is the part of the motherboard which allows the CPU to " "communicate with peripherals such as storage devices. Your computer must use " "the PCI, PCIe, or PCI-X bus. Essentially all personal computers sold in " "recent years use one of these." msgstr "" "El bus del sistema es la parte de la placa base que permite comunicar la CPU " "con los periféricos (tales como los dispositivos de almacenamiento). Su " "ordenador debe usar ISA, EISA, PCI, PCIe, PCI-X, o VESA Local Bus (VLB, a " "veces llamado el bus VL). Todos los ordenadores personales vendidos en los " "últimos años utilizan uno de éstos." #. Tag: para #: hardware.xml:821 #, fuzzy, no-c-format #| msgid "" #| "&debian; on &arch-title; supports the following platforms: " #| " SGI IP22: this platform includes the SGI machines Indy, " #| "Indigo 2 and Challenge S. Since these machines are very similar, whenever " #| "this document refers to the SGI Indy, the Indigo 2 and Challenge S are " #| "meant as well. SGI IP32: this " #| "platform is generally known as SGI O2. " #| " MIPS Malta: this platform is emulated by QEMU and is " #| "therefore a nice way to test and run &debian; on MIPS if you don't have " #| "the hardware. Complete information " #| "regarding supported mips/mipsel machines can be found at the Linux-MIPS homepage. In the following, only " #| "the systems supported by the &debian; installer will be covered. If you " #| "are looking for support for other subarchitectures, please contact the " #| " debian-&arch-listname; mailing list." msgid "" "&debian; on &arch-title; supports the following platforms: " " SGI IP22: this platform includes the SGI machines Indy, " "Indigo 2 and Challenge S. Since these machines are very similar, whenever " "this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant " "as well. SGI IP32: this platform is " "generally known as SGI O2. MIPS Malta: " "this platform is emulated by QEMU and is therefore a nice way to test and " "run &debian; on MIPS if you don't have the hardware. Complete information regarding supported mips/mipsel/mips64el " "machines can be found at the Linux-MIPS " "homepage. In the following, only the systems supported by the " "&debian; installer will be covered. If you are looking for support for other " "subarchitectures, please contact the " "debian-&arch-listname; mailing list." msgstr "" "&debian; para &arch-title; es compatible con las siguientes " "subarquitecturas: SGI IP22: esta plataforma " "incluye a las máquinas SGI Indy, Indigo 2 y Challenge S. Estas máquinas son " "muy similares, cuando este documento hable de la máquina SGI Indy, se " "refiere también a la Indigo 2 y Challenge S. " " SGI IP32: a esta plataforma se la conoce generalmente como " "SGI O2. MIPS Malta: QEMU emula esta " "plataforma y es una buena forma de ejecutar y probar &debian; sobre MIPS si " "no dispone del hardware. Puede encontrar " "información detallada respecto al uso de máquinas mips/mipsel en la página principal de Linux MIPS. En lo que " "sigue, sólo se cubrirán los sistemas compatibles con el instalador de " "&debian;. Si está buscando otras subarquitecturas, por favor, contacte con " "la lista de correo debian-&arch-listname;" "." #. Tag: para #: hardware.xml:856 #, no-c-format msgid "" "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and " "R5000 processors are supported by the &debian; installation system on big " "endian MIPS. On SGI IP32, currently only systems based on the R5000 are " "supported." msgstr "" "Las máquinas SGI IP22, SGI Indy, Indigo 2 y Challenge S con los procesadores " "R4000, R4400, R4600 y R5000 se pueden usar con el sistema de instalación de " "&debian; en MIPS «big endian». En el caso de la máquina SGI IP32 sólo se " "permiten los sistemas basados en el procesador R5000." #. Tag: para #: hardware.xml:862 #, fuzzy, no-c-format #| msgid "" #| "Some MIPS machines can be operated in both big and little endian mode. " #| "For little endian MIPS, please read the documentation for the mipsel " #| "architecture." msgid "" "Some MIPS machines can be operated in both big and little endian mode. For " "little endian MIPS, please read the documentation for the mipsel and " "mips64el architectures." msgstr "" "Algunas máquinas MIPS pueden operar tanto en modo «big endian» como en modo " "«little endian». Para más información sobre los MIPS «little endian» " "consulte la documentación de la arquitectura mipsel." #. Tag: para #: hardware.xml:879 hardware.xml:909 #, fuzzy, no-c-format #| msgid "" #| "&debian; on &arch-title; supports the following platforms: " #| " Cobalt Microserver: only MIPS based Cobalt machines are " #| "covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the " #| "Gateway Microserver. MIPS Malta: this " #| "platform is emulated by QEMU and is therefore a nice way to test and run " #| "&debian; on MIPS if you don't have the hardware. Complete information regarding supported mips/mipsel " #| "machines can be found at the Linux-MIPS " #| "homepage. In the following, only the systems supported by the " #| "&debian; installer will be covered. If you are looking for support for " #| "other subarchitectures, please contact the debian-&arch-listname; mailing list." msgid "" "&debian; on &arch-title; supports the following platforms: " " MIPS Malta: this platform is emulated by QEMU and is " "therefore a nice way to test and run &debian; on MIPS if you don't have the " "hardware. Complete information regarding " "supported mips/mipsel/mips64el machines can be found at the Linux-MIPS homepage. In the following, only the " "systems supported by the &debian; installer will be covered. If you are " "looking for support for other subarchitectures, please contact the debian-&arch-listname; mailing list." msgstr "" "&debian; para &arch-title; es compatible con las siguientes " "subarquitecturas: Cobalt Microserver: Sólo " "se cubren aquí los sistemas basados en MIPS. Esto incluye los sistemas " "Cobalt RaQ, Qube2, RaQ2, y el «Gateway Microserver». " " MIPS Malta: QEMU emula esta plataforma y es una buena forma " "de ejecutar y probar &debian; sobre MIPS si no dispone del hardware. Puede encontrar información detallada " "respecto al uso de máquinas mips/mipsel en la página principal de Linux MIPS. En lo que sigue, sólo se cubrirán " "los sistemas compatibles con el instalador de &debian;. Si está buscando " "otras subarquitecturas, por favor, contacte con la lista de correo debian-&arch-listname;." #. Tag: para #: hardware.xml:939 #, no-c-format msgid "" "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and " "PreP subarchitectures are supported." msgstr "" "&debian-gnu; &release; sólo es compatible con las subarquitecturas PMac " "(Power-Macintosh o PowerMac) y PreP." #. Tag: title #: hardware.xml:960 #, no-c-format msgid "Kernel Flavours" msgstr "Tipos de núcleo" #. Tag: para #: hardware.xml:962 #, no-c-format msgid "" "There are two flavours of the powerpc kernel in &debian;, based on the CPU " "type:" msgstr "" "Hay dos tipos distintos de núcleo de powerpc en &debian;, en función del " "tipo de CPU. Son:" #. Tag: term #: hardware.xml:969 #, no-c-format msgid "powerpc" msgstr "powerpc" #. Tag: para #: hardware.xml:970 #, fuzzy, no-c-format #| msgid "" #| "Most systems use this kernel flavour, which supports the PowerPC 601, " #| "603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up " #| "to and including the one marketed as G4 use one of these processors." msgid "" "This kernel flavour supports the PowerPC 601, 603, 604, 740, 750, and 7400 " "processors. All Apple PowerMac machines up to and including the one marketed " "as G4 use one of these processors." msgstr "" "La mayoría de los sistemas utilizan este núcleo, que permite el uso de " "procesadores PowerPC 601, 603, 604, 740, 750, y 7400. Todos los sistemas " "PowerMac hasta el G4 inclusive utilizan alguno de estos procesadores." #. Tag: term #: hardware.xml:980 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para #: hardware.xml:981 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term #: hardware.xml:989 #, no-c-format msgid "power64" msgstr "power64" #. Tag: para #: hardware.xml:990 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" "La variante del núcleo de power64 permite el uso de las siguientes CPUs:" #. Tag: para #: hardware.xml:994 #, no-c-format msgid "" "The POWER3 processor is used in older IBM 64-bit server systems: known " "models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " "and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" "Los sistemas IBM de 64 bits antiguos usan el procesador POWER3. Algunos de " "estos sistemas son: el sistema IntelliStation POWER Modelo 265, el pSeries " "610 y 640, y el RS/6000 7044-170, 7044-260, y 7044-270." #. Tag: para #: hardware.xml:1000 #, no-c-format msgid "" "The POWER4 processor is used in more recent IBM 64-bit server systems: known " "models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" "Los sistemas de IBM de 64 bits más recientes utilizan el procesador POWER4. " "Algunos de los modelos más conocidos incluyen los pSeries 615, 630, 650, " "655, 670, y 690." #. Tag: para #: hardware.xml:1005 #, fuzzy, no-c-format #| msgid "" #| "Systems using the Apple G5 (PPC970FX processor) are also based on the " #| "POWER4 architecture, and use this kernel flavour." msgid "" "Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM " "Intellistation POWER 185) are also based on the POWER4 architecture, and use " "this kernel flavour." msgstr "" "Los sistemas basados en el Apple G5 (procesador PPC970FX) también están " "basado en la arquitectura POWER4 y utiliza el mismo tipo de núcleo." #. Tag: para #: hardware.xml:1011 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title #: hardware.xml:1044 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "Subarquitectura Power Macintosh (pmac)" #. Tag: para #: hardware.xml:1046 #, no-c-format msgid "" "Apple (and briefly a few other manufacturers — Power Computing, for " "example) made a series of Macintosh computers based on the PowerPC " "processor. For purposes of architecture support, they are categorized as " "NuBus (not supported by &debian;), OldWorld, and NewWorld." msgstr "" "Apple (y algunos otros fabricantes como por ejemplo Power Computing) produjo " "diversas series de ordenadores Macintosh basados en el procesador PowerPC. A " "efectos de compatibilidad de arquitectura, éstos se categorizan como NuBus " "(no compatible con &debian;), OldWorld PCI y NewWorld." #. Tag: para #: hardware.xml:1053 #, no-c-format msgid "" "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " "bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld " "machines. Those pre-iMac PowerPC models from Apple use a four digit naming " "scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" "Los sistemas OldWorld son en su mayoría máquinas Power Macintosh con una " "unidad de disquete y un bus PCI. Muchas de las Power Macintosh basadas en " "603, 603e, 604 y 604e son máquinas OldWorld. Los modelos de Apple previos al " "PowerPC iMac utilizan un esquema de numeración de cuatro dígitos, excepto " "los sistemas G3 de color beige que también son OldWorld." #. Tag: para #: hardware.xml:1061 #, no-c-format msgid "" "The so called NewWorld PowerMacs are any PowerMacs in translucent colored " "plastic cases and later models. That includes all iMacs, iBooks, G4 systems, " "blue colored G3 systems, and most PowerBooks manufactured in and after 1999. " "The NewWorld PowerMacs are also known for using the ROM in RAM system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" "Los también llamados PowerMac NewWorld son en realidad un PowerMac en cajas " "plásticas de color traslúcido y cualquier modelo posterior. Esto incluye " "todas los iMacs, iBooks, sistemas G4, sistemas G3 de color azul y la mayoría " "de los PowerBooks producidos desde el año 1999 inclusive. Los sistemas " "PowerMac NewWorld también utilizan el sistema ROM en RAM para " "MacOS, y fueron producidos desde mediados de 1998 en adelante." #. Tag: para #: hardware.xml:1069 #, no-c-format msgid "" "Specifications for Apple hardware are available at AppleSpec, and, for older " "hardware, AppleSpec Legacy." msgstr "" "Las especificaciones del hardware de Apple están disponibles en AppleSpec, y, " "para hardware antiguo, en AppleSpec Legacy." #. Tag: entry #: hardware.xml:1085 hardware.xml:1220 hardware.xml:1264 hardware.xml:1297 #, no-c-format msgid "Model Name/Number" msgstr "Nombre/número de modelo" #. Tag: entry #: hardware.xml:1086 #, no-c-format msgid "Generation" msgstr "Generación" #. Tag: entry #: hardware.xml:1092 #, no-c-format msgid "Apple" msgstr "Apple" #. Tag: entry #: hardware.xml:1093 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "iMac Bondi Blue, 5 Flavors, Slot Loading" #. Tag: entry #: hardware.xml:1094 hardware.xml:1097 hardware.xml:1100 hardware.xml:1103 #: hardware.xml:1106 hardware.xml:1109 hardware.xml:1112 hardware.xml:1115 #: hardware.xml:1118 hardware.xml:1121 hardware.xml:1124 hardware.xml:1127 #: hardware.xml:1130 hardware.xml:1133 hardware.xml:1136 hardware.xml:1139 #, no-c-format msgid "NewWorld" msgstr "NewWorld" #. Tag: entry #: hardware.xml:1096 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "iMac Summer 2000, principios de 2001" #. Tag: entry #: hardware.xml:1099 #, no-c-format msgid "iMac G5" msgstr "iMac G5" #. Tag: entry #: hardware.xml:1102 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "iBook, iBook SE, iBook Dual USB" #. Tag: entry #: hardware.xml:1105 #, no-c-format msgid "iBook2" msgstr "iBook2" #. Tag: entry #: hardware.xml:1108 #, no-c-format msgid "iBook G4" msgstr "iBook G4" #. Tag: entry #: hardware.xml:1111 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "Power Macintosh Azul y Blanco (B&W) G3" #. Tag: entry #: hardware.xml:1114 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "Power Macintosh G4 PCI, AGP, Cube" #. Tag: entry #: hardware.xml:1117 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "Power Macintosh G4 Gigabit Ethernet" #. Tag: entry #: hardware.xml:1120 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "Power Macintosh G4 Digital Audio, Quicksilver" #. Tag: entry #: hardware.xml:1123 #, no-c-format msgid "Power Macintosh G5" msgstr "Power Macintosh G5" #. Tag: entry #: hardware.xml:1126 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "PowerBook G3 FireWire Pismo (2000)" #. Tag: entry #: hardware.xml:1129 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "PowerBook G3 Lombard (1999)" #. Tag: entry #: hardware.xml:1132 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "PowerBook G4 Titanium" #. Tag: entry #: hardware.xml:1135 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "PowerBook G4 Aluminum" #. Tag: entry #: hardware.xml:1138 #, no-c-format msgid "Xserve G5" msgstr "Xserve G5" #. Tag: entry #: hardware.xml:1141 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "Performa 4400, 54xx, 5500" #. Tag: entry #: hardware.xml:1142 hardware.xml:1145 hardware.xml:1148 hardware.xml:1151 #: hardware.xml:1154 hardware.xml:1157 hardware.xml:1160 hardware.xml:1163 #: hardware.xml:1166 hardware.xml:1169 hardware.xml:1172 hardware.xml:1175 #: hardware.xml:1181 hardware.xml:1184 hardware.xml:1190 hardware.xml:1196 #: hardware.xml:1202 #, no-c-format msgid "OldWorld" msgstr "OldWorld" #. Tag: entry #: hardware.xml:1144 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "Performa 6360, 6400, 6500" #. Tag: entry #: hardware.xml:1147 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "Power Macintosh 4400, 5400" #. Tag: entry #: hardware.xml:1150 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "Power Macintosh 7200, 7300, 7500, 7600" #. Tag: entry #: hardware.xml:1153 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "Power Macintosh 8200, 8500, 8600" #. Tag: entry #: hardware.xml:1156 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "Power Macintosh 9500, 9600" #. Tag: entry #: hardware.xml:1159 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "Power Macintosh (Beige) G3 Minitower" #. Tag: entry #: hardware.xml:1162 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "Power Macintosh (Beige) Desktop, All-in-One" #. Tag: entry #: hardware.xml:1165 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "PowerBook 2400, 3400, 3500" #. Tag: entry #: hardware.xml:1168 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "PowerBook G3 Wallstreet (1998)" #. Tag: entry #: hardware.xml:1171 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "Twentieth Anniversary Macintosh" #. Tag: entry #: hardware.xml:1174 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "Workgroup Server 7250, 7350, 8550, 9650, G3" #. Tag: entry #: hardware.xml:1179 #, no-c-format msgid "Power Computing" msgstr "Power Computing" #. Tag: entry #: hardware.xml:1180 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "PowerBase, PowerTower / Pro, PowerWave" #. Tag: entry #: hardware.xml:1183 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "PowerCenter / Pro, PowerCurve" #. Tag: entry #: hardware.xml:1188 #, no-c-format msgid "UMAX" msgstr "UMAX" #. Tag: entry #: hardware.xml:1189 #, no-c-format msgid "C500, C600, J700, S900" msgstr "C500, C600, J700, S900" #. Tag: entry #: hardware.xml:1194 #, no-c-format msgid "APS" msgstr "APS" #. Tag: entry #: hardware.xml:1195 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "APS Tech M*Power 604e/2000" #. Tag: entry #: hardware.xml:1200 hardware.xml:1226 #, no-c-format msgid "Motorola" msgstr "Motorola" #. Tag: entry #: hardware.xml:1201 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "Starmax 3000, 4000, 5000, 5500" #. Tag: title #: hardware.xml:1210 #, no-c-format msgid "PReP subarchitecture" msgstr "Subarquitectura PReP" #. Tag: entry #: hardware.xml:1227 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "Firepower, PowerStack Series E, PowerStack II" #. Tag: entry #: hardware.xml:1229 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "MPC 7xx, 8xx" #. Tag: entry #: hardware.xml:1231 #, no-c-format msgid "MTX, MTX+" msgstr "MTX, MTX+" #. Tag: entry #: hardware.xml:1233 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" #. Tag: entry #: hardware.xml:1235 #, no-c-format msgid "MCP(N)750" msgstr "MCP(N)750" #. Tag: entry #: hardware.xml:1239 hardware.xml:1270 #, no-c-format msgid "IBM RS/6000" msgstr "IBM RS/6000" #. Tag: entry #: hardware.xml:1240 #, no-c-format msgid "40P, 43P" msgstr "40P, 43P" #. Tag: entry #: hardware.xml:1242 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "Power 830/850/860 (6070, 6050)" #. Tag: entry #: hardware.xml:1244 #, no-c-format msgid "6030, 7025, 7043" msgstr "6030, 7025, 7043" #. Tag: entry #: hardware.xml:1246 #, no-c-format msgid "p640" msgstr "p640" #. Tag: title #: hardware.xml:1254 #, fuzzy, no-c-format #| msgid "PReP subarchitecture" msgid "CHRP subarchitecture" msgstr "Subarquitectura PReP" #. Tag: entry #: hardware.xml:1271 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "B50, 43P-150, 44P" #. Tag: entry #: hardware.xml:1274 #, no-c-format msgid "Genesi" msgstr "Genesi" #. Tag: entry #: hardware.xml:1275 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "Pegasos I, Pegasos II" #. Tag: entry #: hardware.xml:1278 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry #: hardware.xml:1279 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title #: hardware.xml:1287 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "Subarquitectura APUS (no es compatible)" #. Tag: entry #: hardware.xml:1303 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "Amiga Power-UP Systems (APUS)" #. Tag: entry #: hardware.xml:1304 #, no-c-format msgid "A1200, A3000, A4000" msgstr "A1200, A3000, A4000" #. Tag: title #: hardware.xml:1312 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "Subarquitectura Nubus PowerMac (no es compatible)" #. Tag: para #: hardware.xml:1314 #, no-c-format msgid "" "NuBus systems are not currently supported by &debian;/powerpc. The " "monolithic Linux/PPC kernel architecture does not have support for these " "machines; instead, one must use the MkLinux Mach microkernel, which &debian; " "does not yet support. These include the following: " " Power Macintosh 6100, 7100, 8100 " " Performa 5200, 6200, 6300 " " Powerbook 1400, 2300, and 5300 " " Workgroup Server 6150, 8150, 9150 A linux kernel for these machines and limited support is " "available at ." msgstr "" "En la actualidad, los sistemas NuBus no son compatibles con &debian;/" "powerpc. La arquitectura monolítica del núcleo Linux/PPC no tiene permite el " "uso de estas máquinas; puede usar en su lugar el micronúcleo MkLinux Mach, " "aún no compatible con &debian;. Entre estos sistemas se incluyen los " "siguientes: Power Macintosh 6100, 7100, 8100 " " Performa 5200, 6200, 6300 Powerbook 1400, 2300 y 5300 " " Workgroup Server 6150, 8150, 9150 Existe un núcleo Linux para estas máquinas con compatibilidad " "limitada en ." #. Tag: title #: hardware.xml:1351 #, no-c-format msgid "Non-PowerPC Macs" msgstr "Macs que no son PowerPC" #. Tag: para #: hardware.xml:1353 #, no-c-format msgid "" "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models " "start with Mac II series, go on to the LC " "family, then the Centris series, and culminate in the Quadras and Performas. " "These models usually have a Roman numeral or 3-digit model number such as " "Mac IIcx, LCIII or Quadra 950." msgstr "" "Los ordenadores Macintosh que usan la serie de procesadores 680x0 " "no están dentro de la familia PowerPC, sino que son " "máquinas m68k. Estos modelos empiezan con la serie Mac II, " "continua con la familia LC, después le siguió la serie " "Centries y la familia terminó con los equipos Quadras y Performas. Estos " "modelos generalmente tenía un número romano o un número de modelo de tres " "digitos como Mac IIcx, LCIII o Quadra 950." #. Tag: para #: hardware.xml:1362 #, no-c-format msgid "" "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, " "IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, " "580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra " "(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the " "Performa 200-640CD." msgstr "" "Este rango de modelos comenzó con el Mac II (Mac II, IIx, IIcx, IIci, IIsi, " "IIvi, IIvx, IIfx), después siguió el LC (LC, LCII, III, III+, 475, 520, 550, " "575, 580, 630), después el Mac TV, el Centris (610, 650, 660AV), el Quadra " "(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), y finalmente el " "Performa 200-640CD." #. Tag: para #: hardware.xml:1370 #, no-c-format msgid "" "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs " "and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, " "please see the section above)." msgstr "" "En los equipos portátiles la serie empezó con el Mac Portable, seguido por " "el PowerBook 100-190cs y el PowerBook Duo 210-550c (excepto el PowerBook 500 " "que es un Nubus, consulte la sección anterior)." #. Tag: title #: hardware.xml:1384 #, fuzzy, no-c-format #| msgid "CPU/Machine types" msgid "Machines" msgstr "Tipos de CPU/Máquina" #. Tag: para #: hardware.xml:1387 #, no-c-format msgid "S822L" msgstr "" #. Tag: para #: hardware.xml:1392 #, no-c-format msgid "S821L" msgstr "" #. Tag: para #: hardware.xml:1397 #, no-c-format msgid "S822" msgstr "" #. Tag: para #: hardware.xml:1402 #, no-c-format msgid "S821" msgstr "" #. Tag: para #: hardware.xml:1407 #, no-c-format msgid "TYAN GN70-BP010" msgstr "" #. Tag: title #: hardware.xml:1422 #, no-c-format msgid "zSeries and System z machine types" msgstr "Tipos de máquinas zSeries y System z" #. Tag: para #: hardware.xml:1423 #, fuzzy, no-c-format #| msgid "" #| "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. " #| "Your machine needs to support the z/Architecture, 64-bit support is " #| "mandatory. The userland of the s390 port is still compiled for ESA/390, " #| "though. All zSeries and System z hardware is fully supported. &arch-" #| "title; support software is included from the kernel 3.1 development " #| "stream. The most current information about IBM's Linux support can be " #| "found at the Linux on System z page on developerWorks." msgid "" "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. " "Your machine needs to support the z/Architecture, 64-bit support is " "mandatory. The userland of the s390 port is still compiled for ESA/390, " "though. All zSeries and System z hardware is fully supported. &arch-title; " "support software is included from the kernel 4.3 development stream. The " "most current information about IBM's Linux support can be found at the " " Linux on System z page on developerWorks." msgstr "" "A partir de &debian; Squeeze, se ha eliminado la posibilidad de arranque en " "modo ESA/390. El sistema requiere la compatibilidad la arquitectura z/" "Architecture, y la compatibilidad con 64-bit es obligatoria. Aún así, el " "espacio de usuario («userland») de la adaptación de s390 se sigue compilando " "para ESA/390. Todo el hardware de las series zSeries y System z es " "totalmente compatible. El software de compatibilidad de &arch-title; está " "incluido a partir de la rama de desarrollo de la versión 3.1 del núcleo. La " "información más actualizada de la compatibilidad de Linux con IBM se puede " "consultar en la página Linux on System z en developerWorks." #. Tag: title #: hardware.xml:1440 #, no-c-format msgid "PAV and HyperPAV" msgstr "PAV e HyperPAV" #. Tag: para #: hardware.xml:1441 #, no-c-format msgid "" "PAV and HyperPAV are supported transparently, multipathing is not needed to " "take advantage of these storage system features. Be sure to configure the " "devices during DASD device selection. The alias devices will not be offered " "neither for formatting, partitioning nor direct use." msgstr "" "PAV e HyperPAV son plenamente compatibles, y multipathing no es necesario " "para aprovechar las funcionalidades de estos sistemas de almacenamiento. " "Asegúrese de configurar los dispositivos durante la selección de dispositivo " "DASD. Los alias de dispositivo no se ofrecerán para el formateo, el " "particionado, ni el uso directo." #. Tag: title #: hardware.xml:1457 #, no-c-format msgid "CPU and Main Boards Support" msgstr "Compatibilidad de CPU, placas base y vídeo" #. Tag: para #: hardware.xml:1458 #, no-c-format msgid "" "Sparc-based hardware is divided into a number of different subarchitectures, " "identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u " "or sun4v. The following list describes what machines they include and what " "level of support may be expected for each of them." msgstr "" "Los equipos basados en Sparc se dividen en un conjunto de distintas " "subarquitecturas identificadas por alguno de los nombres siguientes: sun4, " "sun4c, sun4d, sun4m, sun4u o sun4v. A continuación se proporciona una lista " "que describe los distintos equipos y el nivel de compatibilidad que se puede " "esperar de cada uno." #. Tag: term #: hardware.xml:1469 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "sun4, sun4c, sun4d, sun4m" #. Tag: para #: hardware.xml:1471 #, no-c-format msgid "" "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a " "complete list of machines belonging to these subarchitectures, please " "consult the Wikipedia SPARCstation page." msgstr "" "No es compatible ninguna de estas subarquitecturas de 32 bits. Si quiere una " "lista completa de las máquinas que pertenecen a estas subarquitecturas puede " "consultar la página " "de SPARCstation en la Wikipedia." #. Tag: para #: hardware.xml:1478 #, no-c-format msgid "" "The last &debian; release to support sparc32 was Etch, but even then only " "for sun4m systems. Support for the other 32-bits subarchitectures had " "already been discontinued after earlier releases." msgstr "" "La última versión de &debian; compatible con la arquitectura sparc32 fue " "Etch, y sólo en sistemas sun4m. El uso de otras subarquitecturas de 32-bits " "ya se había dejado de ofrecer en versiones anteriores." #. Tag: term #: hardware.xml:1488 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para #: hardware.xml:1490 #, no-c-format msgid "" "This subarchitecture includes all 64-bit machines (sparc64) based on the " "UltraSparc processor and its clones. Most of the machines are well " "supported, even though for some you may experience problems booting from CD " "due to firmware or bootloader bugs (this problem may be worked around by " "using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP " "configurations respectively." msgstr "" "Esta subarquitectura incluye todos los equipos de 64 bits (sparc64) basados " "en el procesador UltraSparc y sus clones. Existe una alta compatibilidad con " "la mayoría de estos equipos, aunque puede que tenga algunos problemas con el " "arranque de CD debido a erratas en el firmware o en el cargador de arranque " "(puede evitar estos problemas si utiliza el arranque vía red). Utilice el " "núcleo sparc64 o sparc64-smp en configuraciones UP y SMP respectivamente." #. Tag: term #: hardware.xml:1503 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para #: hardware.xml:1505 #, no-c-format msgid "" "This is the newest addition to the Sparc family, which includes machines " "based on the Niagara multi-core CPUs. At the moment such CPUs are only " "available in T1000 and T2000 servers by Sun, and are well supported. Use the " "sparc64-smp kernel." msgstr "" "Esta es el miembro más nuevo de la familia Sparc e incluye a los equipos " "basados en las CPUs multi-core Niagara. De momento estas CPUs sólo están " "disponibles en los servidores T1000 y T2000 de Sun, con una alta " "compatibilidad. Utilice el núcleo sparc64-smp." #. Tag: para #: hardware.xml:1516 #, no-c-format msgid "" "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are " "not supported due to lack of support in the Linux kernel." msgstr "" "Tenga en cuenta que las CPUs SPARC64 de Fujitsu utilizadas en la familia de " "servidores PRIMEPOWER no son compatibles porque no existe compatibilidad con " "éstas en el núcleo de Linux." #. Tag: title #: hardware.xml:1525 #, no-c-format msgid "Laptops" msgstr "Ordenadores portátiles" #. Tag: para #: hardware.xml:1526 #, no-c-format msgid "" "From a technical point of view, laptops are normal PCs, so all information " "regarding PC systems applies to laptops as well. Installations on laptops " "nowadays usually work out of the box, including things like automatically " "suspending the system on closing the lid and laptop specfic hardware buttons " "like those for disabling the wifi interfaces (airplane mode). " "Nonetheless sometimes the hardware vendors use specialized or proprietary " "hardware for some laptop-specific functions which might not be supported. To " "see if your particular laptop works well with GNU/Linux, see for example the " "Linux Laptop pages." msgstr "" "Desde un punto de vista técnico, los ordenadores portátiles son PC normales, " "y por ello toda la información relativa a sistemas PC también se aplica a " "los portátiles. Actualmente, las instalaciones en portátil funcionan " "habitualmente sin configuraciones especiales, incluyendo la suspensión del " "sistema al cerrar el portátil, y botones específicos a portátiles como la " "desactivación de interfaz wifi (modo avión). Por otra parte, " "a veces los proveedores de hardware utilizan hardware especializado o " "propietario para algunas funciones específicas de portátil que no es " "compatible. Para ver si su ordenador portátil funciona bien con GNU/Linux, " "consulte las páginas de portátiles en Linux" #. Tag: title #: hardware.xml:1543 hardware.xml:1563 hardware.xml:1585 hardware.xml:1608 #, no-c-format msgid "Multiple Processors" msgstr "Múltiples procesadores" #. Tag: para #: hardware.xml:1544 #, fuzzy, no-c-format #| msgid "" #| "Multiprocessor support — also called symmetric " #| "multiprocessing or SMP — is available for this " #| "architecture. Having multiple processors in a computer was originally " #| "only an issue for high-end server systems but has become quite common in " #| "recent years even for rather low-end desktop computers and laptops with " #| "the introduction of so called multi-core processors. These " #| "contain two or more processor units, called cores, in one " #| "physical chip." msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. Having multiple " "processors in a computer was originally only an issue for high-end server " "systems but has become common in recent years nearly everywhere with the " "introduction of so called multi-core processors. These " "contain two or more processor units, called cores, in one " "physical chip." msgstr "" "Se permite el uso de múltiples procesadores (también llamado multi-" "procesamiento simétrico o SMP) con esta arquitectura. Originalmente, " "tener un sistema con varios procesadores era solo un problema para los " "sistemas de servidor más avanzados, aunque se ha extendido en los últimos " "años incluso en ordenadores y portátiles de rango bajo con la introducción " "de los denominados procesadores multi-core. Contienen dos o " "más unidades de procesamiento, denominados core, en un único " "procesador físico." #. Tag: para #: hardware.xml:1554 #, no-c-format msgid "" "The standard &debian; &release; kernel image has been compiled with SMP " "support. It is also usable on non-SMP systems without problems." msgstr "" "La imagen de núcleo estándar de &debian; &release; se ha compilado con " "compatibilidad con SMP. También se puede utilizar sin problemas en sistemas " "distintos a SMP." #. Tag: para #: hardware.xml:1565 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. The standard " "&debian; &release; kernel image has been compiled with SMP-" "alternatives support. This means that the kernel will detect the " "number of processors (or processor cores) and will automatically deactivate " "SMP on uniprocessor systems." msgstr "" "Se permite el uso de múltiples procesadores (también llamado multi-" "procesamiento simétrico o SMP) con esta arquitectura. La imagen " "estándar del núcleo de &debian; &release; ha sido compilada con " "compatibilidad con SMP-alternatives. Esto implica que " "el núcleo detectará el número de procesadores (o núcleos de procesador) y " "desactivará SMP de forma automática para sistemas de un solo procesador." #. Tag: para #: hardware.xml:1574 #, fuzzy, no-c-format #| msgid "" #| "Having multiple processors in a computer was originally only an issue for " #| "high-end server systems but has become quite common in recent years even " #| "for rather low-end desktop computers and laptops with the introduction of " #| "so called multi-core processors. These contain two or more " #| "processor units, called cores, in one physical chip." msgid "" "Having multiple processors in a computer was originally only an issue for " "high-end server systems but has become common in recent years nearly " "everywhere with the introduction of so called multi-core " "processors. These contain two or more processor units, called cores, in one physical chip." msgstr "" "Originalmente, tener un sistema con varios procesadores era solo un problema " "para los sistemas de servidor más avanzados, aunque se ha extendido en los " "últimos años incluso en ordenadores y portátiles de rango bajo con la " "introducción de los denominados procesadores multi-core. " "Contienen dos o más unidades de procesamiento, denominados core, en un único procesador físico." #. Tag: para #: hardware.xml:1586 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. However, the " "standard &debian; &release; kernel image does not support SMP. This should " "not prevent installation, since the standard, non-SMP kernel should boot on " "SMP systems; the kernel will simply use only the first CPU." msgstr "" "Se permite el uso de múltiples procesadores (también llamado multi-" "procesamiento simétrico o SMP) con esta arquitectura. Sin embargo, " "la imagen estándar del núcleo de &debian; &release; no permite SMP. Esto no " "debería impedir la instalación, ya que el núcleo estándar, sin SMP, debería " "arrancar en sistemas SMP. El núcleo simplemente utilizará el primer " "procesador." #. Tag: para #: hardware.xml:1595 #, no-c-format msgid "" "In order to take advantage of multiple processors, you'll have to replace " "the standard &debian; kernel. You can find a " "discussion of how to do this in . At this " "time (kernel version &kernelversion;) the way you enable SMP is to select " "&smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "" "Tendrá que sustituir el núcleo estándar de &debian; si quiere aprovechar el " "uso de múltiples procesadores. Puede encontrar " "una discusión acerca de cómo hacer esto en . En este momento (versión del núcleo &kernelversion;) puede habilitar SMP " "seleccionando &smp-config-option; en la sección &smp-" "config-section; de la configuración del núcleo." #. Tag: para #: hardware.xml:1609 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture, and is supported " "by a precompiled &debian; kernel image. Depending on your install media, " "this SMP-capable kernel may or may not be installed by default. This should " "not prevent installation, since the standard, non-SMP kernel should boot on " "SMP systems; the kernel will simply use the first CPU." msgstr "" "La posibilidad de usar múltiples procesadores (también llamado " "multiprocesamiento simétrico o SMP) está disponible para ésta " "arquitectura, y está incluido en una imagen pre-compilada del núcleo de " "&debian;. Dependiendo de su medio de instalación, este núcleo con capacidad " "de usar SMP podría o no instalarse como el núcleo predeterminado. Esto no " "debería entorpecer la instalación, debido a que el núcleo estándar, sin SMP, " "debería arrancar en sistemas SMP. En este caso, el núcleo simplemente " "utilizará el primer procesador." #. Tag: para #: hardware.xml:1619 #, no-c-format msgid "" "In order to take advantage of multiple processors, you should check to see " "if a kernel package that supports SMP is installed, and if not, choose an " "appropriate kernel package." msgstr "" "Si desea hacer uso de múltiples procesadores deberá verificar que el paquete " "del núcleo que permite SMP esté instalado; si no lo está, seleccione un " "núcleo apropiado." #. Tag: para #: hardware.xml:1625 #, no-c-format msgid "" "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in . At this time (kernel version &kernelversion;) the way " "you enable SMP is to select &smp-config-option; in the " "&smp-config-section; section of the kernel config." msgstr "" "También puede construir su propio núcleo personalizado incluyendo " "compatibilidad con SMP. Puede encontrar una " "discusión sobre cómo hacerlo en . En este " "momentos (versión del núcleo &kernelversion;) la forma de habilitar SMP es " "elegir la opción &smp-config-option; en la sección " "&smp-config-section; de la configuración del núcleo." #. Tag: title #: hardware.xml:1636 #, fuzzy, no-c-format #| msgid "Graphics Card Support" msgid "Graphics Hardware Support" msgstr "Compatibilidad de tarjeta gráfica" #. Tag: para #: hardware.xml:1637 #, fuzzy, no-c-format #| msgid "" #| "&debian;'s support for graphical interfaces is determined by the " #| "underlying support found in X.Org's X11 system. On modern PCs, having a " #| "graphical display usually works out of the box. Whether advanced graphics " #| "card features such as 3D-hardware acceleration or hardware-accelerated " #| "video are available, depends on the actual graphics hardware used in the " #| "system and in some cases on the installation of additional " #| "firmware images (see ). In very few cases there have been reports about hardware on which " #| "installation of additional graphics card firmware was required even for " #| "basic graphics support, but these have been rare exceptions." msgid "" "&debian;'s support for graphical interfaces is determined by the underlying " "support found in X.Org's X11 system, and the kernel. Basic framebuffer " "graphics is provided by the kernel, whilst desktop environments use X11. " "Whether advanced graphics card features such as 3D-hardware acceleration or " "hardware-accelerated video are available, depends on the actual graphics " "hardware used in the system and in some cases on the installation of " "additional firmware images (see )." msgstr "" "La compatibilidad de &debian; con interfaces gráficas está determinada por " "la compatibilidad subyacente encontrada en el sistema X11 de X.Org. En " "sistemas PC modernos, habitualmente la interfaz gráfica funcionará desde el " "primer momento sin una configuración posterior. La disponibilidad de " "funciones avanzadas de tarjeta gráfica como la aceleración de hardware 3D o " "vídeo acelerado por hardware depende del hardware de gráficos utilizado en " "el sistema, y en algunos casos de la instalación de imágenes de " "firmware adicionales (consulte ). Se han dado algunos casos de hardware donde la instalación de " "firmware adicional de tarjeta gráfica era necesario incluso para la " "compatibilidad básica de gráficos, pero son situaciones excepcionales." #. Tag: para #: hardware.xml:1649 #, no-c-format msgid "" "On modern PCs, having a graphical display usually works out of the box. In " "very few cases there have been reports about hardware on which installation " "of additional graphics card firmware was required even for basic graphics " "support, but these have been rare exceptions. For quite a lot of hardware, " "3D acceleration also works well out of the box, but there is still some " "hardware that needs binary blobs to work well." msgstr "" #. Tag: para #: hardware.xml:1660 #, no-c-format msgid "" "Nearly all ARM machines have the graphics hardware built-in, rather than " "being on a plug-in card. Some machines do have expansion slots which will " "take graphics cards, but that is a rarity. Hardware designed to be headless " "with no graphics at all is quite common. Whilst basic framebuffer video " "provided by the kernel should work on all devices that have graphics, fast " "3D graphics invariably needs binary drivers to work. The situation is " "changing quickly but at the time of the &releasename; release free drivers " "for nouveau (Nvidia Tegra K1 SoC) and freedreno (Qualcomm Snapdragon SoCs) " "are available in the release. Other hardware needs non-free drivers from 3rd " "parties." msgstr "" #. Tag: para #: hardware.xml:1674 #, fuzzy, no-c-format #| msgid "" #| "Details on supported graphics cards and pointing devices can be found at " #| ". &debian; &release; ships with X.Org " #| "version &x11ver;." msgid "" "Details on supported graphics hardware and pointing devices can be found at " ". &debian; &release; ships with X.Org " "version &x11ver;." msgstr "" "Para más detalles sobre tarjetas de vídeo y dispositivos de señalamiento " "compatibles en . &debian; &release; " "incluye X.Org versión &x11ver;." #. Tag: para #: hardware.xml:1679 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "" "Sólo se permite el uso del sistema de ventanas X de X.Org en la SGI Indy y " "en la O2." #. Tag: para #: hardware.xml:1684 #, no-c-format msgid "" "Most graphics options commonly found on Sparc-based machines are supported. " "X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, " "sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), " "PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards " "(glint driver). To use an Elite3D card with X.org you additionally need to " "install the afbinit package, and read the " "documentation included with it on how to activate the card." msgstr "" "Se permite el uso de la mayoría de las opciones gráficas que se encuentran " "habitualmente en equipos basados en procesadores Sparc. Existen " "controladores de gráficos X.org para el framebufer de sunbw2, suncg14, " "suncg3, suncg6, sunleo y suntcx, las tarjetas Creator3D y " "Elite3D(controlador sunffb), las tarjetas basadas en ATI PGX24/" "PGX64(controlador ati), y las tarjetas basadas en PermediaII(controlador " "glint). Si desea utilizar una tarjeta Elite3D con X.org tiene que instalar " "además el paquete afbinit y leer la documentación que " "se incluye en él para saber cómo activar la tarjeta." #. Tag: para #: hardware.xml:1694 #, no-c-format msgid "" "It is not uncommon for a Sparc machine to have two graphics cards in a " "default configuration. In such a case there is a possibility that the Linux " "kernel will not direct its output to the card initially used by the " "firmware. The lack of output on the graphical console may then be mistaken " "for a hang (usually the last message seen on console is 'Booting Linux...'). " "One possible solution is to physically remove one of the video cards; " "another option is to disable one of the cards using a kernel boot parameter. " "Also, if graphical output is not required or desired, serial console may be " "used as an alternative. On some systems use of serial console can be " "activated automatically by disconnecting the keyboard before booting the " "system." msgstr "" "No es raro tener dos tarjetas gráficas con la configuración de fábrica de " "sistemas Sparc. Existe la posibilidad en este caso de que el núcleo de Linux " "no envíe la salida a la tarjeta utilizada inicialmente por el firmware. A " "veces se confunde la falta de salida en la consola gráfica con un fallo del " "sistema (generalmente el último mensaje que se ve en la consola es «Booting " "Linux...»). Una solución posible a este problema es quitar físicamente una " "de las tarjetas de vídeo, otra opción es deshabilitar una de las tarjetas " "utilizando un parámetro de arranque del núcleo. También puede utilizar la " "consola serial como una alternativa si no necesita (o no desea) la salida " "gráfica. En algunos sistemas puede activar automáticamente el uso de la " "consola serial desconectando el teclado antes de arrancar el sistema." #. Tag: title #: hardware.xml:1716 #, no-c-format msgid "Network Connectivity Hardware" msgstr "Hardware de conectividad de red" #. Tag: para #: hardware.xml:1717 #, no-c-format msgid "" "Almost any network interface card (NIC) supported by the &arch-kernel; " "kernel should also be supported by the installation system; drivers should " "normally be loaded automatically. This includes most " "PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops. " "Many older ISA cards are supported as well." msgstr "" "Casi cualquier tarjeta de interfaz de red (también llamadas «network " "interface card» o NIC, n. del t.) compatible con el núcleo de &arch-kernel; " "es también compatible con el sistema de instalación. Por regla general, los " "controladores modulares se cargarán automáticamente. Esto incluye la mayoría de las tarjetas PCI/PCI-Express y tarjetas " "PCMCIA/Express en portátiles. También son " "compatibles muchas tarjetas ISA antiguas." #. Tag: para #: hardware.xml:1727 #, no-c-format msgid "" "This includes a lot of generic PCI cards (for systems that have PCI) and the " "following NICs from Sun:" msgstr "" "Esta lista incluye muchas de las tarjetas PCI genéricas (en aquellos " "sistemas que tienen PCI) y las siguientes NICs de Sun:" #. Tag: para #: hardware.xml:1733 #, no-c-format msgid "Sun LANCE" msgstr "Sun LANCE" #. Tag: para #: hardware.xml:1738 #, no-c-format msgid "Sun Happy Meal" msgstr "Sun Happy Meal" #. Tag: para #: hardware.xml:1743 #, no-c-format msgid "Sun BigMAC" msgstr "Sun BigMAC" #. Tag: para #: hardware.xml:1748 #, no-c-format msgid "Sun QuadEthernet" msgstr "Sun QuadEthernet" #. Tag: para #: hardware.xml:1753 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "MyriCOM Gigabit Ethernet" #. Tag: para #: hardware.xml:1760 #, no-c-format msgid "The list of supported network devices is:" msgstr "La lista de dispositivos de red compatibles es:" #. Tag: para #: hardware.xml:1765 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "Conexión canal a canal (CTC) y ESCON (real o emulado)" #. Tag: para #: hardware.xml:1770 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "OSA-2 Token Ring/Ethernet y OSA-Express Fast Ethernet (non-QDIO)" #. Tag: para #: hardware.xml:1775 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "OSA-Express en modo QDIO, HiperSockets y Guest-LANs" #. Tag: para #: hardware.xml:1784 #, no-c-format msgid "" "On &arch-title;, most built-in Ethernet devices are supported and modules " "for additional PCI and USB devices are provided." msgstr "" "Para &arch-title;, la mayoría de dispositivos incorporados Ethernet son " "compatibles, y se proporcionan módulos para dispositivos adicionales PCI e " "USB." #. Tag: para #: hardware.xml:1789 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "Se permite el uso de RDSI, pero no durante la instalación." #. Tag: title #: hardware.xml:1796 #, no-c-format msgid "Wireless Network Cards" msgstr "Tarjetas de red inalámbrica" #. Tag: para #: hardware.xml:1797 #, no-c-format msgid "" "Wireless networking is in general supported as well and a growing number of " "wireless adapters are supported by the official &arch-kernel; kernel, " "although many of them do require firmware to be loaded." msgstr "" "En la mayoría de los casos, las tarjetas de red inalámbrica son compatibles. " "El núcleo oficial de &arch-kernel; permite un número creciente de " "adaptadores inalámbricos, aunque muchos necesitan que se cargue primero su " "firmware." #. Tag: para #: hardware.xml:1804 #, no-c-format msgid "" "If firmware is needed, the installer will prompt you to load firmware. See " " for detailed information on how to load " "firmware during the installation." msgstr "" "Si el firmware es necesario, el instalador le pedirá que lo cargue. Consulte " " para una información detallada de cómo " "cargar firmware durante la instalación." #. Tag: para #: hardware.xml:1809 #, no-c-format msgid "" "Wireless NICs that are not supported by the official &arch-kernel; kernel " "can generally be made to work under &debian-gnu;, but are not supported " "during the installation." msgstr "" "Aunque puede hacer funcionar en &debian-gnu; muchos adaptadores de red " "inalámbricos que no son compatibles con el núcleo oficial de &arch-kernel;, " "no estarán disponibles durante el proceso de instalación." #. Tag: para #: hardware.xml:1814 #, no-c-format msgid "" "If there is a problem with wireless and there is no other NIC you can use " "during the installation, it is still possible to install &debian-gnu; using " "a full CD-ROM or DVD image. Select the option to not configure a network and " "install using only the packages available from the CD/DVD. You can then " "install the driver and firmware you need after the installation is completed " "(after the reboot) and configure your network manually." msgstr "" "En cualquier caso, puede instalar &debian-gnu; utilizando una imagen " "completa de CD-ROM o DVD si no puede utilizar ninguna otra tarjeta de red. " "Rechace la opción de configurar la red e instale el sistema sólo con los " "paquetes disponibles en el CD/DVD. Una vez haya hecho esto podrá instalar el " "controlador y el firmware que necesite después de terminar la instalación " "(después del reinicio del sistema) y configurar la red manualmente." #. Tag: para #: hardware.xml:1824 #, no-c-format msgid "" "In some cases the driver you need may not be available as a &debian; " "package. You will then have to look if there is source code available in the " "internet and compile the driver yourself. How to do this is outside the " "scope of this manual. If no Linux driver is available, " "your last resort is to use the ndiswrapper package, " "which allows you to use a Windows driver." msgstr "" "En algunos casos el controlador que necesita puede no estar disponible como " "paquete &debian;. Deberá comprobar si existe código fuente disponible en " "Internet y compilar el controlador usted mismo. Cómo hacer esto está fuera " "del ámbito de este manual. Si no hay ningún controlador " "de Linux disponible puede utilizar como último recurso el paquete " "ndiswrapper que le permite utilizar un controlador de " "Windows." #. Tag: title #: hardware.xml:1838 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "Problemas conocidos con &arch-title;" #. Tag: para #: hardware.xml:1839 #, no-c-format msgid "" "There are a couple of issues with specific network cards that are worth " "mentioning here." msgstr "" "Existen algunos problemas conocidos con tarjetas de red específicas que " "merece la pena tratar aquí." #. Tag: title #: hardware.xml:1846 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "Conflicto entre los controladores tulip y dfme" #. Tag: para #: hardware.xml:1848 #, no-c-format msgid "" "There are various PCI network cards that have the same PCI identification, " "but are supported by related, but different drivers. Some cards work with " "the tulip driver, others with the dfme " "driver. Because they have the same identification, the kernel cannot " "distinguish between them and it is not certain which driver will be loaded. " "If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" "Existen algunas tarjetas PCI que tienen la misma identificación PCI pero " "compatibles mediante controladores relacionados, pero distintos. Algunas " "tarjetas funcionan con el controlador tulip y otras con " "el controlador dfme. El núcleo no puede distinguir entre " "ellas ya que tienen la misma identificación, con lo que no está seguro de " "qué controlador se debe cargar. Si se instala el controlador incorrecto " "puede que no funcione la tarjeta de red o que funcione mal." #. Tag: para #: hardware.xml:1858 #, no-c-format msgid "" "This is a common problem on Netra systems with a Davicom (DEC-Tulip " "compatible) NIC. In that case the tulip driver is " "probably the correct one. You can prevent this issue by blacklisting the " "wrong driver module as described in ." msgstr "" "Este es un problema habitual en sistemas Netra con tarjetas Davicom " "(compatible DEC-Tulip). En estos equipos el controlador tulip es seguramente el que deba utilizar. Puede prevenir este problema " "poniendo el módulo del controlador incorrecto en una lista negra, como se " "describe en ." #. Tag: para #: hardware.xml:1866 #, no-c-format msgid "" "An alternative solution during the installation is to switch to a shell and " "unload the wrong driver module using modprobe -r " "module (or both, if they are both " "loaded). After that you can load the correct module using " "modprobe module. Note that " "the wrong module may then still be loaded when the system is rebooted." msgstr "" "Una solución alternativa durante la instalación es cambiar a un intérprete " "de órdenes, quitar el módulo del controlador incorrecto utilizando " "modprobe -r modulo (o " "quitar ambos, si están los dos). Y después cargar el módulo correcto con " "modprobe modulo." #. Tag: title #: hardware.xml:1879 #, no-c-format msgid "Sun B100 blade" msgstr "Sun B100 blade" #. Tag: para #: hardware.xml:1881 #, no-c-format msgid "" "The cassini network driver does not work with Sun B100 " "blade systems." msgstr "" "El controlador de red cassini no funciona en sistemas " "blade Sun B100." #. Tag: title #: hardware.xml:1896 #, no-c-format msgid "Braille Displays" msgstr "Dispositivos Braille" #. Tag: para #: hardware.xml:1897 #, no-c-format msgid "" "Support for braille displays is determined by the underlying support found " "in brltty. Most displays work under " "brltty, connected via either a serial port, USB or " "bluetooth. Details on supported braille devices can be found on the brltty website. &debian-" "gnu; &release; ships with brltty version &brlttyver;." msgstr "" "La compatibilidad de brltty determina el uso de " "dispositivos braille. La mayoría de dispositivos funcionan con " "brltty, vía un puerto serial, USB o bluetooth. Puede " "encontrar los detalles de los dispositivos braille en el sitio web de brltty. &debian-gnu; " "&release; ofrece la versión &brlttyver; de brltty." #. Tag: title #: hardware.xml:1911 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "Dispositivos de Síntesis de voz" #. Tag: para #: hardware.xml:1912 #, no-c-format msgid "" "Support for hardware speech synthesis devices is determined by the " "underlying support found in speakup. " "speakup only supports integrated boards and external " "devices connected to a serial port (no USB, serial-to-USB or PCI adapters " "are supported). Details on supported hardware speech synthesis devices can " "be found on the speakup " "website. &debian-gnu; &release; ships with speakup version &speakupver;." msgstr "" "La compatibilidad que ofrece speakup determina la " "compatibilidad con dispositivos de síntesis de voz. speakup acepta únicamente tarjetas integradas y dispositivos externos " "conectados a un puerto serial (no hay compatibilidad con USB, adaptadores " "serial-a-USB o PCI). Puede encontrar los detalles de los dispositivos " "compatibles en el sitio web de " "speakup. &debian-gnu; &release; ofrece la " "versión &speakupver; de speakup." #. Tag: title #: hardware.xml:1932 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "Periféricos y otro hardware" #. Tag: para #: hardware.xml:1933 #, fuzzy, no-c-format #| msgid "" #| "&arch-kernel; supports a large variety of hardware devices such as mice, " #| "printers, scanners, PCMCIA and USB devices. However, most of these " #| "devices are not required while installing the system." msgid "" "&arch-kernel; supports a large variety of hardware devices such as mice, " "printers, scanners, PCMCIA/CardBus/ExpressCard and USB devices. However, " "most of these devices are not required while installing the system." msgstr "" "&arch-kernel; es compatible con una amplia variedad de dispositivos de " "hardware como pueden ser: ratones, impresoras, escáneres y dispositivos " "PCMCIA y USB. Sin embargo, muchos de éstos no son necesarios durante la " "instalación del sistema." #. Tag: para #: hardware.xml:1939 #, no-c-format msgid "" "USB hardware generally works fine. On some very old PC systems some USB " "keyboards may require additional configuration (see ). On modern PCs, USB keyboards and mice work without requiring " "any specific configuration." msgstr "" "Habitualmente, el hardware USB funciona correctamente. En algunos sistemas " "PC muy antiguos, puede que sea necesaria una configuración adicional para " "algunos teclados USB (consulte ). En " "sistemas PC modernos, los teclados y ratones USB funcionan sin necesitar una " "configuración específica." #. Tag: para #: hardware.xml:1948 #, no-c-format msgid "" "Package installations from XPRAM and tape are not supported by this system. " "All packages that you want to install need to be available on a DASD or over " "the network using NFS, HTTP or FTP." msgstr "" "Este sistema no permite la instalación de paquetes desde XPRAM y cinta. " "Todos los paquetes que desee instalar necesitan estar disponibles en un DASD " "o a través de la red usando NFS, HTTP o FTP." #. Tag: title #: hardware.xml:1961 #, no-c-format msgid "Devices Requiring Firmware" msgstr "Dispositivos que requieren Firmware" #. Tag: para #: hardware.xml:1962 #, no-c-format msgid "" "Besides the availability of a device driver, some hardware also requires so-" "called firmware or microcode " "to be loaded into the device before it can become operational. This is most " "common for network interface cards (especially wireless NICs), but for " "example some USB devices and even some hard disk controllers also require " "firmware. With many graphics cards, basic functionality is available without " "additional firmware, but the use of advanced features requires an " "appropriate firmware file to be installed in the system." msgstr "" "Además de la disponibilidad de un controlador para un dispositivo, algunos " "dispositivos de hardware también requieren algo llamado firmware o microcode, que se debe cargar en el " "dispositivo antes de ser funcional. Esto es muy común para tarjetas de " "interfaz red (especialmente NIC inalámbricas), aunque algunos dispositivos " "USB e incluso ciertos controladores de discos duros también requieren " "firmware. Para muchas tarjetas gráficas, la funcionalidad básica está " "disponible sin hardware adicional, pero el uso de funciones avanzadas " "requiere la instalación de un fichero de firmware adicional en el sistema." #. Tag: para #: hardware.xml:1973 #, no-c-format msgid "" "On many older devices which require firmware to work, the firmware file was " "permanently placed in an EEPROM/Flash chip on the device itself by the " "manufacturer. Nowadays most new devices do not have the firmware embedded " "this way anymore, so the firmware file must be uploaded into the device by " "the host operating system every time the system boots." msgstr "" "En muchos dispositivos antiguos que requieren firmware para su " "funcionamiento, los ficheros de firmware se almacenaban por el fabricante de " "forma permanente en un procesador EEPROM/Flash en el mismo dispositivo. " "Actualmente, la mayoría de dispositivos no integran el firmware de esta " "forma, y por ello el fichero de firmware si debe cargar en el dispositivo " "por el sistema operativo anfitrión durante cada arranque del sistema." #. Tag: para #: hardware.xml:1981 #, no-c-format msgid "" "In most cases firmware is non-free according to the criteria used by the " "&debian-gnu; project and thus cannot be included in the main distribution or " "in the installation system. If the device driver itself is included in the " "distribution and if &debian-gnu; legally can distribute the firmware, it " "will often be available as a separate package from the non-free section of " "the archive." msgstr "" "En la mayoría de los casos el firmware es no-libre de acuerdo con los " "criterios usados por el proyecto &debian-gnu; y por lo tanto no puede " "incluirse en la distribución principal o en el sistema de instalación. Si el " "controlador del dispositivo está incluido en la distribución y si &debian-" "gnu; legalmente puede distribuir el firmware, es usual que esté disponible " "como un paquete separado en la sección non-free del archivo de &debian-gnu;." #. Tag: para #: hardware.xml:1990 #, no-c-format msgid "" "However, this does not mean that such hardware cannot be used during an " "installation. Starting with &debian-gnu; 5.0, &d-i; supports loading " "firmware files or packages containing firmware from a removable medium, such " "as a USB stick. See for detailed " "information on how to load firmware files or packages during the " "installation." msgstr "" "Aunque esto no quiere decir que tal hardware no pueda usarse durante una " "instalación. Desde &debian-gnu; 5.0, el &d-i; permite la carga de ficheros " "de firmware o paquetes que contienen el firmware de un medio extraíble, como " "una memoria USB. Consulte para obtener " "información detallada de cómo cargar los ficheros de firmware o paquetes " "durante la instalación." #. Tag: para #: hardware.xml:1999 #, no-c-format msgid "" "If the &d-i; prompts for a firmware file and you do not have this firmware " "file available or do not want to install a non-free firmware file on your " "system, you can try to proceed without loading the firmware. There are " "several cases where a driver prompts for additional firmware because it may " "be needed under certain circumstances, but the device does work without it " "on most systems (this e.g. happens with certain network cards using the tg3 " "driver)." msgstr "" "Si &d-i; solicita un fichero de firmware, y no dispone de ese fichero o no " "desea instalar un fichero de firmware no libre en su sistema, puede intentar " "continuar sin cargar el firmware. Hay varios casos en los que el controlador " "solicita firmware adicional por ser necesario bajo determinadas " "circunstancias, pero el dispositivo puede funcionar sin él en la mayoría de " "sistemas (por ejemplo, ocurre con algunas tarjetas de red que utilizan el " "controlador tg3)." #. Tag: title #: hardware.xml:2016 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "Adquisición de hardware específico para GNU/&arch-kernel;" #. Tag: para #: hardware.xml:2018 #, no-c-format msgid "" "There are several vendors, who ship systems with &debian; or other " "distributions of GNU/Linux pre-installed. You might pay more for the privilege, but it does buy a level of " "peace of mind, since you can be sure that the hardware is well-supported by " "GNU/Linux." msgstr "" "Existen algunos fabricantes que entregan sus sistemas con &debian; u otra " "distribución de GNU/Linux preinstalada. Quizás tenga que pagar más por este privilegio, pero esto le " "garantiza una cierta tranquilidad de espíritu puesto que puede estar seguro " "de que su hardware es totalmente compatible con GNU/Linux." #. Tag: para #: hardware.xml:2026 #, no-c-format msgid "" "If you do have to buy a machine with Windows bundled, carefully read the " "software license that comes with Windows; you may be able to reject the " "license and obtain a rebate from your vendor. Searching the Internet for " "windows refund may get you some useful information to help " "with that." msgstr "" "Consulte detenidamente la licencia de software que viene con Windows si " "tiene que comprar un equipo que provea este sistema operativo preinstalado. " "Puede que tenga la posibilidad de rechazar la licencia y obtener un " "descuento de su vendedor. Encontrará información útil sobre esto si busca " "información en Internet acerca de windows refund " "(reembolso windows, n. del t.)." #. Tag: para #: hardware.xml:2034 #, no-c-format msgid "" "Whether or not you are purchasing a system with &arch-kernel; bundled, or " "even a used system, it is still important to check that your hardware is " "supported by the &arch-kernel; kernel. Check if your hardware is listed in " "the references found above. Let your salesperson (if any) know that you're " "shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware " "vendors." msgstr "" "Es importante que compruebe que su hardware es compatible con el núcleo " "&arch-kernel;, ya sea si está adquiriendo un sistema con &arch-kernel; " "preinstalado o no, o incluso un sistema usado. Compruebe si su hardware está " "listado en las referencias citadas anteriormente. Haga saber a su vendedor " "(si lo hay) que está comprando un equipo para instalar &arch-kernel;. Apoye " "a los fabricantes de hardware que ofrecen compatibilidad con &arch-kernel;." #. Tag: title #: hardware.xml:2045 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "Evite hardware cerrado o privativo" #. Tag: para #: hardware.xml:2046 #, no-c-format msgid "" "Some hardware manufacturers simply won't tell us how to write drivers for " "their hardware. Others won't allow us access to the documentation without a " "non-disclosure agreement that would prevent us from releasing the driver's " "source code, which is one of the central elements of free software. Since we " "haven't been granted access to usable documentation on these devices, they " "simply won't work under &arch-kernel;." msgstr "" "Algunos fabricantes de hardware simplemente no nos dirán cómo escribir " "controladores para su hardware, o no nos permiten acceder a la documentación " "sin un acuerdo de no divulgación que nos impediría publicar el código fuente " "del controlador, uno de los elementos esenciales del software libre. Debido " "a que no se nos ha ofrecido el acceso a documentación útil sobre estos " "dispositivos, sencillamente no funcionan con &arch-kernel;." #. Tag: para #: hardware.xml:2056 #, no-c-format msgid "" "In many cases there are standards (or at least some de-facto standards) " "describing how an operating system and its device drivers communicate with a " "certain class of devices. All devices which comply to such a (de-" "facto-)standard can be used with a single generic device driver and no " "device-specific drivers are required. With some kinds of hardware (e.g. USB " "Human Interface Devices, i.e. keyboards, mice, etc., and USB " "mass storage devices like USB flash disks and memory card readers) this " "works very well and practically every device sold in the market is standards-" "compliant." msgstr "" "En muchas situaciones hay estándares (o al menos estándares de hecho) que " "describen la forma en que un sistema operativo y los controladores de sus " "dispositivos se comunican con un cierto tipo de dispositivos. Todos los " "dispositivos que cumplen tal estándar (de hecho) se pueden utilizar con un " "único controlador genérico de dispositivo, y no se requiere ningún " "controlador específico de dispositivo. Esto funciona muy bien para algunos " "tipos de hardware (como por ejemplo dispositivos de interfaz humana " "(HID) USB como teclados, ratón y otros, y dispositivos de " "almacenamiento USB como discos flash USB y lectores de tarjeta de memoria) y " "prácticamente todos los dispositivos vendidos en el mercado cumple con " "estándares." #. Tag: para #: hardware.xml:2068 #, no-c-format msgid "" "In other fields, among them e.g. printers, this is unfortunately not the " "case. While there are many printers which can be addressed via a small set " "of (de-facto-)standard control languages and therefore can be made to work " "without problems in any operating system, there are quite a few models which " "only understand proprietary control commands for which no usable " "documentation is available and therefore either cannot be used at all on " "free operating systems or can only be used with a vendor-supplied closed-" "source driver." msgstr "" "Desafortunadamente, en otros campos, entre ellos el de las impresoras, este " "no es el caso. Aunque hay muchas impresoras que pueden funcionar con un " "pequeño conjunto de lenguaje de control estándar (de hecho) sin problemas en " "cualquier sistema operativo, hay varios modelos que solo aceptan órdenes de " "control privativos que no se detallan en ninguna documentación, y por ello " "no se pueden utilizar en sistemas operativos libres, o solo se pueden " "utilizar con un controlador de código propietario proporcionado por el " "proveedor." #. Tag: para #: hardware.xml:2079 #, no-c-format msgid "" "Even if there is a vendor-provided closed-source driver for such hardware " "when purchasing the device, the practical lifespan of the device is limited " "by driver availability. Nowadays product cycles have become short and it is " "not uncommon that a short time after a consumer device has ceased " "production, no driver updates get made available any more by the " "manufacturer. If the old closed-source driver does not work anymore after a " "system update, an otherwise perfectly working device becomes unusable due to " "lacking driver support and there is nothing that can be done in this case. " "You should therefore avoid buying closed hardware in the first place, " "regardless of the operating system you want to use it with." msgstr "" "Incluso si hay un controlador de código propietario proporcionado por el " "fabricante para un dispositivo de hardware al comprar el producto, la vida " "útil del dispositivo está limitado a la disponibilidad del controlador. " "Actualmente, los ciclos de un producto son más cortos, y no es extraño que " "tras un breve período después de finalizar la producción del dispositivo, el " "fabricante no ofrezca más actualizaciones del controlador. Si el antiguo " "controlador de código propietario no funciona después de una actualización " "del sistema, un dispositivo funcionalmente perfecto se vuelve inútil por la " "falta un controlador, y en este caso nada se puede hacer. Por ello, debe " "evitar comprar hardware propietario en primer lugar, sin importar el sistema " "operativo con el que lo vaya a utilizar." #. Tag: para #: hardware.xml:2092 #, no-c-format msgid "" "You can help improve this situation by encouraging manufacturers of closed " "hardware to release the documentation and other resources necessary for us " "to provide free drivers for their hardware." msgstr "" "Puede ayudar a mejorar esta situación animando a fabricantes de hardware " "propietario para publiquen la documentación y otros recursos necesarios para " "que podamos proporcionar controladores libres para su hardware." #. Tag: title #: hardware.xml:2107 #, no-c-format msgid "Installation Media" msgstr "Medios de instalación" #. Tag: para #: hardware.xml:2109 #, no-c-format msgid "" "This section will help you determine which different media types you can use " "to install &debian;. There is a whole chapter devoted to media, , which lists the advantages and disadvantages " "of each media type. You may want to refer back to this page once you reach " "that section." msgstr "" "Esta sección le ayudará a determinar los diferentes tipos de medio que puede " "usar para instalar &debian;. Existe un capítulo entero dedicado a este " "asunto, el , que lista las ventajas y " "desventajas de cada tipo de medio. Puede que desee regresar a esta página " "una vez que consulte esa sección." #. Tag: title #: hardware.xml:2119 #, no-c-format msgid "Floppies" msgstr "Disquetes" #. Tag: para #: hardware.xml:2120 #, no-c-format msgid "" "In some cases, you'll have to do your first boot from floppy disks. " "Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch " "floppy drive." msgstr "" "Tendrá que hacer el primer arranque desde disquetes en algunos casos. " "Generalmente, todo lo que necesita es una unidad de disquetes de alta " "densidad (1440 kilobytes) de 3.5 pulgadas." #. Tag: para #: hardware.xml:2126 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "El uso de disquetes en CHRP es inservible en la actualidad." #. Tag: title #: hardware.xml:2133 #, no-c-format msgid "CD-ROM/DVD-ROM/BD-ROM" msgstr "CD-ROM/DVD-ROM/BD-ROM" #. Tag: para #: hardware.xml:2135 #, fuzzy, no-c-format #| msgid "" #| "Whenever you see CD-ROM in this manual, it applies to both " #| "CD-ROMs and DVD-ROMs, because both technologies are really the same from " #| "the operating system's point of view." msgid "" "Whenever you see CD-ROM in this manual, it applies to all of " "CD-ROMs, DVD-ROMs and BD-ROMs, because all these technologies are really the " "same from the operating system's point of view." msgstr "" "Donde quiera que vea CD-ROM en este manual, interprete esto " "como CD-ROM o DVD-ROM ya que ambas tecnologías son " "equivalentes desde el punto de vista del sistema operativo." #. Tag: para #: hardware.xml:2141 #, no-c-format msgid "CD-ROM based installation is supported for most architectures." msgstr "" "La instalación mediante CD-ROM es compatible con la mayoría de arquitecturas." #. Tag: para #: hardware.xml:2145 #, fuzzy, no-c-format #| msgid "" #| "USB CD-ROM drives are also supported, as are FireWire devices that are " #| "supported by the ohci1394 and sbp2 drivers." msgid "" "On PCs SATA, IDE/ATAPI, USB and SCSI CD-ROMs are supported, as are FireWire " "devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" "También son compatibles las unidades de CD-ROM USB, así como los " "dispositivos FireWire que aceptados por los controladores ohci1394 y sbp2." #. Tag: para #: hardware.xml:2160 #, no-c-format msgid "" "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of " "working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM " "drives sold on the PC market do not have this capability. If your CD-ROM " "drive has a jumper labeled Unix/PC or 512/2048, place it in the Unix or 512 position. " "To start the install, simply choose the System installation " "entry in the firmware." msgstr "" "En el caso de máquinas SGI, es necesario un CD-ROM SCSI capaz de trabajar " "con un tamaño de bloque lógicos de 512 bytes para arrancar desde CD-ROM. " "Muchas de las unidades de CD-ROM SCSI vendidas para el mercado de PCs no " "tienen esta capacidad. Si su CD-ROM tiene un puente etiquetado Unix/" "PC o 512/2048, colóquelo en la posición Unix ó 512. Elija la opción System installation en el firmware para iniciar la instalación." #. Tag: title #: hardware.xml:2174 #, no-c-format msgid "USB Memory Stick" msgstr "Dispositivo de memoria USB" #. Tag: para #: hardware.xml:2176 #, no-c-format msgid "" "USB flash disks a.k.a. USB memory sticks have become a commonly used and " "cheap storage device. Most modern computer systems also allow booting the &d-" "i; from such a stick. Many modern computer systems, in particular netbooks " "and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting " "from USB media is the standard way of installing a new operating system on " "them." msgstr "" "Los discos de flash USB o dispositivos de memoria USB se han convertido en " "un dispositivo de almacenamiento extendido y barato. La mayoría de sistemas " "informáticos modernos permiten el arranque de &d-i; desde tales " "dispositivos. Muchos sistemas informáticos modernos, en particular netbooks " "y portátiles delgados, ya no incorporan un dispositivo CD/DVD-ROM, y el " "arranque desde un dispositivo USB es el modo estándar de instalación de un " "nuevo sistema operativo." #. Tag: title #: hardware.xml:2188 #, no-c-format msgid "Network" msgstr "Red" #. Tag: para #: hardware.xml:2190 #, no-c-format msgid "" "The network can be used during the installation to retrieve files needed for " "the installation. Whether the network is used or not depends on the " "installation method you choose and your answers to certain questions that " "will be asked during the installation. The installation system supports most " "types of network connections (including PPPoE, but not ISDN or PPP), via " "either HTTP or FTP. After the installation is completed, you can also " "configure your system to use ISDN and PPP." msgstr "" "Puede utilizarse la red durante la instalación para recuperar los ficheros " "para la instalación. El que se utilice la red o no depende del mecanismo de " "instalación que escoja y de sus respuestas a algunas preguntas que se le " "realizarán durante la instalación. Este sistema de instalación puede " "utilizar la mayor parte de las conexiones de red (incluyendo PPPoE, pero no " "RDSI ó PPP) a través tanto de HTTP como FTP. Una vez haya terminado la " "instalación podrá configurar su sistema para que utilice RDSI y PPP." #. Tag: para #: hardware.xml:2200 #, fuzzy, no-c-format #| msgid "" #| "You can also boot the installation system over the " #| "network without needing any local media like CDs/DVDs or USB sticks. If " #| "you already have a netboot-infrastructure available (i.e. you are already " #| "running DHCP and TFTP services in your network), this allows an easy and " #| "fast deployment of a large number of machines. Setting up the necessary " #| "infrastructure requires a certain level of technical experience, so this " #| "is not recommended for novice users. This is " #| "the preferred installation technique for &arch-title;." msgid "" "You can also boot the installation system over the " "network without needing any local media like CDs/DVDs or USB sticks. If you " "already have a netboot-infrastructure available (i.e. you are already " "running DHCP and TFTP services in your network), this allows an easy and " "fast deployment of a large number of machines. Setting up the necessary " "infrastructure requires a certain level of technical experience, so this is " "not recommended for novice users. This " "is the preferred installation technique for &arch-title;." msgstr "" "También puede arrancar el sistema de instalación a " "través de la red sin necesidad de un medio local como CD/DVD o dispositivos " "USB. Si ya dispone de una infraestructura netboot (esto es, ejecuta " "servicios DHCP y TFTP en su red), puede realizar una instalación sencilla y " "rápido en varias máquinas. La configuración de la infraestructura necesaria " "requiere un cierto nivel de conocimientos técnicos, y no se recomienda para " "usuarios inexpertos. Esta es la técnica de " "instalación preferida para &arch-title;." #. Tag: para #: hardware.xml:2213 #, no-c-format msgid "" "Diskless installation, using network booting from a local area network and " "NFS-mounting of all local filesystems, is another option." msgstr "" "Otra opción es la instalación sin disco, basada en el arranque a través de " "red desde una red de área local y en el montaje a través de NFS de todos los " "sistemas de ficheros locales." #. Tag: title #: hardware.xml:2222 #, no-c-format msgid "Hard Disk" msgstr "Disco duro" #. Tag: para #: hardware.xml:2224 #, no-c-format msgid "" "Booting the installation system directly from a hard disk is another option " "for many architectures. This will require some other operating system to " "load the installer onto the hard disk. This method is only recommended for " "special cases when no other installation method is available." msgstr "" "El arranque del sistema de instalación desde el disco duro es otra opción " "para muchas arquitecturas. Para esto necesitará tener algún otro sistema " "operativo instalado para cargar el instalador en el disco duro. Este método " "se recomienda solo para casos especiales cuando no se dispone de ningún otro " "método de instalación." #. Tag: para #: hardware.xml:2231 #, no-c-format msgid "" "Although the &arch-title; does not allow booting from SunOS (Solaris), you " "can install from a SunOS partition (UFS slices)." msgstr "" "Aunque no es posible arrancar desde SunOS (Solaris) en &arch-title;, puede " "instalar desde una partición SunOS (particiones UFS)." #. Tag: title #: hardware.xml:2240 #, no-c-format msgid "Un*x or GNU system" msgstr "Sistema Un*x o GNU" #. Tag: para #: hardware.xml:2242 #, no-c-format msgid "" "If you are running another Unix-like system, you could use it to install " "&debian-gnu; without using the &d-i; described in the rest of this manual. " "This kind of install may be useful for users with otherwise unsupported " "hardware or on hosts which can't afford downtime. If you are interested in " "this technique, skip to the . This " "installation method is only recommended for advanced users when no other " "installation method is available." msgstr "" "Puede utilizar otro sistema operativo tipo Unix para instalar &debian-gnu; " "sin necesidad de usar el &d-i; que se describe en el resto de este manual. " "Este tipo de instalación puede ser útil para usuarios con hardware no " "compatible o en máquinas que no pueden dejar de dar servicio en ningún " "momento. Si está interesado en este método, pase a la . Esta forma de instalación solo se recomienda para usuarios " "avanzados cuando no se dispone de ningún otro método de instalación." #. Tag: title #: hardware.xml:2255 #, no-c-format msgid "Supported Storage Systems" msgstr "Sistemas de almacenamiento aceptados" #. Tag: para #: hardware.xml:2257 #, no-c-format msgid "" "The &debian; installer contains a kernel which is built to maximize the " "number of systems it runs on." msgstr "" "El instalador de &debian; incorpora un núcleo construido para maximizar el " "número de sistemas en los que puede funcionar." #. Tag: para #: hardware.xml:2261 #, no-c-format msgid "" "Generally, the &debian; installation system includes support for IDE (also " "known as PATA) drives, SATA and SCSI controllers and drives, USB, and " "FireWire. The supported file systems include FAT, Win-32 FAT extensions " "(VFAT) and NTFS." msgstr "" "Habitualmente, el sistema de instalación de &debian; permite el uso de " "unidades IDE (también llamadas PATA), controladores y unidades SATA y SCSI, " "USB y FireWire. Los sistemas de ficheros permitidos incluyen FAT, " "extensiones FAT Win-32 (VFAT) y NTFS." #. Tag: para #: hardware.xml:2278 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system. The following SCSI drivers are supported in the default kernel: " " Sparc ESP " " PTI Qlogic,ISP Adaptec " "AIC7xxx NCR and Symbios 53C8XX IDE systems (such as the UltraSPARC 5) are also " "supported. See Linux for SPARC " "Processors FAQ for more information on SPARC hardware supported by " "the Linux kernel." msgstr "" "El sistema de arranque también permite el uso de cualquier sistema de " "almacenamiento compatible con el núcleo Linux. El núcleo predeterminado es " "compatible con los siguientes controladores SCSI: " " Sparc ESP PTI Qlogic," "ISP Adaptec AIC7xxx " " NCR y Symbios 53C8XX " "También son compatibles los sistemas IDE (como el UltraSPARC 5). Consulte " "las PUF de Linux para procesadores " "SPARC para más información de la compatibilidad de hardware SPARC en " "el núcleo Linux." #. Tag: para #: hardware.xml:2311 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system. Note that the current Linux kernel does not support floppies on " "CHRP systems at all." msgstr "" "El sistema de arranque permite el uso de cualquier sistema de almacenamiento " "compatible con el núcleo Linux. Tenga en cuenta que el núcleo Linux actual " "no permite el uso de disquetes en sistemas CHRP." #. Tag: para #: hardware.xml:2317 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system. Note that the current Linux kernel does not support the floppy " "drive." msgstr "" "El sistema de arranque permite el uso de cualquier sistema de almacenamiento " "compatible con el núcleo Linux. Tenga en cuenta que el núcleo Linux actual " "no tiene permite el uso de unidades de disquete." #. Tag: para #: hardware.xml:2323 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system." msgstr "" "El sistema de arranque es compatible con cualquier sistema de almacenamiento " "compatible con el núcleo Linux." #. Tag: para #: hardware.xml:2328 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " "boot system. This means that FBA and ECKD DASDs are supported with the old " "Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" "El sistema de arranque permite cualquier sistema de almacenamiento " "compatible con el núcleo Linux. Esto significa que los DADs FBA y ECKD son " "compatibles con el anterior esquema de discos de Linux (ldl) y con el nuevo " "esquema común de discos para S/390 (cdl)." #. Tag: title #: hardware.xml:2345 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "Requisitos de memoria y espacio en disco" #. Tag: para #: hardware.xml:2347 #, no-c-format msgid "" "You must have at least &minimum-memory; of memory and &minimum-fs-size; of " "hard disk space to perform a normal installation. Note that these are fairly " "minimal numbers. For more realistic figures, see ." msgstr "" "Debe tener al menos &minimum-memory; de memoria y &minimum-fs-size; espacio " "de disco duro para realizar una instalación normal. Tenga en cuenta que " "éstos son los mínimos absolutos. Si desea valores más reales consulte . Para un sistema mínimo basado en " "consola (todos los paquetes estándar), se requiere 250 MB. Si quiere " "instalar una cantidad razonable de software, incluyendo el sistema de " "ventanas X, y algunos programas y bibliotecas de desarrollo, necesitará al " "menos 400 MB. Para una instalación más o menos completa de un sistema de " "escritorio, necesitará unos cuantos gigabytes." #. Tag: para #: hardware.xml:2354 #, fuzzy, no-c-format #| msgid "" #| "Installation on systems with less memory " #| " Installation images that support the graphical installer require " #| "more memory than images that support only the textual installer and " #| "should not be used on systems with less than &minimum-memory; of memory. " #| "If there is a choice between booting the regular and the graphical " #| "installer, the former should be selected. or disk " #| "space available may be possible but is only advised for experienced users." msgid "" "Installation on systems with less memory " "Installation images that support the graphical installer require more memory " "than images that support only the textual installer and should not be used " "on systems with less than &minimum-memory; of memory. If there is a choice " "between booting the text-based and the graphical installer, the former " "should be selected on such systems. or disk space " "available may be possible but is only advised for experienced users." msgstr "" "Puede ser posible la instalación en sistemas con menos memoria Las imágenes de instalación que tienen que " "incluyen el instalador gráfico necesitan más memoria que las imágenes que " "sólo incluyen el instalador de texto y no deberían utilizarse en sistemas " "cuya memoria sea inferior a &minimum-memory;. Si se le presenta la opción " "entre arrancar el instalador normal o el instalador gráfico debería utilizar " "la primera opción si su sistema no tiene mucha memoria. " "o con menos disco duro, pero sólo es aconsejable realizarla si es vd. un " "usuario experimentado." #~ msgid "kirkwood" #~ msgstr "kirkwood" #~ msgid "orion5x" #~ msgstr "orion5x" #~ msgid "SGI IP22 (Indy/Indigo 2)" #~ msgstr "SGI IP22 (Indy/Indigo 2)" #~ msgid "r4k-ip22" #~ msgstr "r4k-ip22" #~ msgid "SGI IP32 (O2)" #~ msgstr "SGI IP32 (O2)" #~ msgid "r5k-ip32" #~ msgstr "r5k-ip32" #~ msgid "PowerMac" #~ msgstr "PowerMac" #~ msgid "pmac" #~ msgstr "pmac" #~ msgid "PReP" #~ msgstr "PReP" #~ msgid "prep" #~ msgstr "prep" #~ msgid "Intel IXP4xx" #~ msgstr "Intel IXP4xx" #~ msgid "ixp4xx" #~ msgstr "ixp4xx" #, fuzzy #~| msgid "" #~| "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM " #~| "CPU, Ethernet, SATA, USB, and other functionality in one chip. We " #~| "currently support the following Kirkwood based devices: OpenRD (OpenRD-" #~| "Base, OpenRD-Client and OpenRD-Ultimate), plug computers (SheevaPlug, GuruPlug and DreamPlug), QNAP Turbo " #~| "Station (all TS-11x, TS-21x and TS-41x models), and LaCie NASes " #~| "(Network Space v2, Network Space Max v2, Internet Space v2, d2 Network " #~| "v2, 2Big Network v2 and 5Big Network v2)." #~ msgid "" #~ "Kirkwood is a system-on-chip (SoC) from Marvell that integrates an ARM " #~ "CPU, Ethernet, SATA, USB, and other functionality in one chip. &debian; " #~ "currently supports the following Kirkwood based devices: OpenRD (OpenRD-" #~ "Base, OpenRD-Client and OpenRD-Ultimate), plug computers (SheevaPlug, GuruPlug and DreamPlug), QNAP Turbo Station (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network " #~ "Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big " #~ "Network v2 and 5Big Network v2)." #~ msgstr "" #~ "Kirkwood es un sistema en un chip («system on a chip», SoC) de Marvell " #~ "que integra un procesador ARM, Ethernet, SATA, USB y otras " #~ "funcionalidades en un solo chip. Actualmente, &debian; es compatible con " #~ "los siguientes dispositivos basados en Kirkwood: OpenRD (OpenRD-Base, " #~ "OpenRD-Client y OpenRD-Ultimate), PC de enchufe (SheevaPlug, GuruPlug y DreamPlug), QNAP Turbo Station (todos los " #~ "modelos TS-11x, TS-21x y TS-41x) y LaCie NASes (Network Space v2, Network " #~ "Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 y 5Big " #~ "Network v2)." #~ msgid "IOP32x" #~ msgstr "IOP32x" #~ msgid "" #~ "The 586 flavour of the &debian; kernel image packages for &arch-title; is " #~ "not compiled with SMP support." #~ msgstr "" #~ "Los paquetes con la versión 586 del la imagen del núcleo de &debian; en " #~ "&arch-title; no están compilados con compatibilidad con SMP." #~ msgid "&debian; GNU/kFreeBSD &release; supports two architectures." #~ msgstr "" #~ "&debian; GNU/kFreeBSD &release; es compatible con dos arquitecturas:" #~ msgid "kfreebsd-i386" #~ msgstr "kfreebsd-i386" #~ msgid "kfreebsd-amd64" #~ msgstr "kfreebsd-amd64" #, fuzzy #~| msgid "MIPS (little endian)" #~ msgid "IBM PowerPC (little endian)" #~ msgstr "MIPS (little endian)" #~ msgid "" #~ "The &arch-title; architecture only supports Intel Itanium processors and " #~ "not the much more common 64-bit processors from the Intel 64 family " #~ "(including e.g. the Pentium D and the Core2 Duo). Those systems " #~ "are supported by the amd64 architecture or, if you " #~ "prefer a 32-bit userland, the i386 architecture." #~ msgstr "" #~ "La arquitectura &arch-title; sólo es compatible con procesadores Intel " #~ "Itanium processors, y no con los procesadores más comunes de 64 bits de " #~ "la familia Intel 64 (incluyendo por ejemplo el Pentium D y " #~ "Core2 Duo). Estos sistemas son compatibles con la arquitectura " #~ "amd64, o, si prefiere un espacio de usuario de 32 " #~ "bit, la arquitectura i386." #~ msgid "" #~ "There are two major support &architecture; flavors: " #~ "PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at " #~ "32-bit processors whereas the 2.0 architecture is targeted to the 64-bit " #~ "processors. Some systems are able to run either kernel. In both cases, " #~ "the userland is 32-bit. There is the possibility of a 64-bit userland in " #~ "the future." #~ msgstr "" #~ "Son compatibles dos variantes principales de &architecture;: PA-RISC 1.1 y PA-RISC 2.0. La arquitectura PA-RISC 1.1 está " #~ "dirigida a procesadores de 32 bits mientras que la arquitectura 2.0 está " #~ "dirigida a procesadores de 64 bits. Algunos sistemas tienen la capacidad " #~ "de ejecutar ambas versiones del núcleo indistintamente. El entorno de " #~ "usuario es de 32 bits en ambos casos. En el futuro será posible tener un " #~ "entorno de usuario de 64 bits." #~ msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported." #~ msgstr "" #~ "En sistemas PC SATA, se permiten dispositivos CD-ROM IDE/ATAPI y SCSI." #~ msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." #~ msgstr "Las máquinas ARM permiten el uso de CD-ROMs IDE/ATAPI." #~ msgid "" #~ "However, &debian; GNU/Linux &releasename; will not " #~ "run on 386 or earlier processors. Despite the architecture name \"i386\", " #~ "support for actual 80386 processors (and their clones) was dropped with " #~ "the Sarge (r3.1) release of &debian; We have long tried " #~ "to avoid this, but in the end it was necessary due a unfortunate series " #~ "of issues with the compiler and the kernel, starting with an bug in the C+" #~ "+ ABI provided by GCC. You should still be able to run &debian; GNU/Linux " #~ "on actual 80386 processors if you compile your own kernel and compile all " #~ "packages from source, but that is beyond the scope of this manual. . (No version of Linux has ever supported the 286 or " #~ "earlier chips in the series.) All i486 and later processors are still " #~ "supported Many &debian; packages will actually run " #~ "slightly faster on modern computers as a positive side effect of dropping " #~ "support for these old chips. The i486, introduced in 1989, has three " #~ "opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, " #~ "did not have. Previously, these could not be easily used by most &debian; " #~ "packages; now they can. ." #~ msgstr "" #~ "Sin embargo, &debian; GNU/Linux &releasename; no " #~ "funcionará en procesadores 386 o anteriores. Aunque la arquitectura se " #~ "llame «i386», la compatibilidad con los procesadores 80386 (y sus clones) " #~ "dejó de existir con la versión Sarge (r3.1) de &debian; " #~ "Hemos intentado evitarlo durante mucho tiempo pero al final ha sido " #~ "necesario hacerlo debido a una serie de problemas desafortunados con el " #~ "compilador y el núcleo, empezando con un error en el ABI de C++ de GCC. " #~ "Aún puede ejecutar &debian; GNU/Linux en procesadores 80386 si compila su " #~ "propio núcleo y recompila todos los paquetes fuente, pero esto está fuera " #~ "del ámbito de este manual. . (Ninguna versión de Linux " #~ "ha permitido el uso de sistemas 286 o procesadores anteriores en la " #~ "serie). Aún se permiten todos los procesadores i486 y posteriores." #~ " Muchos paquetes &debian;, de hecho, se ejecutarán más " #~ "rápido en sistemas más modernos como resultado (positivo) de haber " #~ "descartado la compatibilidad con estos procesadores antiguos. El " #~ "procesador i486, que apareció en 1989, tiene tres códigos de operación " #~ "(también llamados «opcodes», son bswap, cmpxchg, y xadd) que el i386, " #~ "introducido en 1986, no tenía. Antes estos códigos no podían utilizarse " #~ "fácilmente dentro de los paquetes &debian;, y ahora es posible. ." #~ msgid "iop32x" #~ msgstr "iop32x" #~ msgid "Freescale" #~ msgstr "Freescale" #~ msgid "mx5" #~ msgstr "mx5" #~ msgid "Intel IA-64" #~ msgstr "Intel IA-64" #~ msgid "ia64" #~ msgstr "ia64" #~ msgid "Sun SPARC" #~ msgstr "Sun SPARC" #~ msgid "sparc" #~ msgstr "sparc" #~ msgid "sun4u" #~ msgstr "sun4u" #~ msgid "sparc64" #~ msgstr "sparc64" #~ msgid "sun4v" #~ msgstr "sun4v" #~ msgid "IBM S/390" #~ msgstr "IBM S/390" #~ msgid "s390" #~ msgstr "s390" #~ msgid "" #~ "Each distinct ARM architecture requires its own kernel. Because of this " #~ "the standard &debian; distribution only supports installation on a number " #~ "of the most common platforms. The &debian; userland however may be used " #~ "by any ARM CPU." #~ msgstr "" #~ "Cada arquitectura de ARM diferente requiere su propio núcleo. Esto es " #~ "debido a que la distribución estándar de &debian; solamente permite la " #~ "instalación en las plataformas más comunes. El espacio de usuario de " #~ "&debian; puede utilizarse, sin embargo, en cualquier " #~ "CPU ARM incluyendo «xscale»." #~ msgid "" #~ "Intel's I/O Processor (IOP) line is found in a number of products related " #~ "to data storage and processing. &debian; currently supports the IOP32x " #~ "platform, featuring the IOP 80219 and 32x chips commonly found in Network " #~ "Attached Storage (NAS) devices. &debian; explicitly supports two such " #~ "devices: the GLAN Tank " #~ "from IO-Data and the Thecus N2100." #~ msgstr "" #~ "La línea de procesadores de Intel de Entrada/Salida («Intel's I/O " #~ "Processor» o IOP) se puede encontrar en un conjunto de productos " #~ "dedicados al almacenamiento y procesado de datos. Actualmente, &debian; " #~ "permite usar la plataforma IOP32x, que incluye los chips IOP 80219 y 32x " #~ "que se encuentran habitualmente en dispositivos de almacenamiento en red " #~ "(«Network Attached Storage», NAS). &debian; es compatible de forma " #~ "explícita con dos de estos dispositivos: el equipo GLAN Tank de IO-Data y el Thecus N2100." #~ msgid "sun4u" #~ msgstr "sun4u" #~ msgid "sun4v" #~ msgstr "sun4v" #~ msgid "Cobalt" #~ msgstr "Cobalt" #~ msgid "cobalt" #~ msgstr "cobalt" #~ msgid "" #~ "All MIPS based Cobalt machines are supported with the exception of the " #~ "Qube 2700 (Qube 1)." #~ msgstr "" #~ "Todas las máquinas Cobalt MIPS son compatibles con la excepción de Qube " #~ "2700 (Qube 1)." #~ msgid "Supported console options" #~ msgstr "Opciones de consola permitidos" #~ msgid "Cobalt machines use 115200 bps." #~ msgstr "Las máquinas Cobalt usan 115200 bps." #~ msgid "" #~ "The Cobalt RaQ has no support for additional devices but the Qube has one " #~ "PCI slot." #~ msgstr "" #~ "El sistema Cobalt RaQ no tiene compatibilidad para dispositivos " #~ "adicionales, pero el Qube tiene un slot PCI." #~ msgid "IPL from tape" #~ msgstr "IPL de cinta" #~ msgid "tape" #~ msgstr "cinta" #~ msgid "CHRP subarchitecture (unsupported)" #~ msgstr "Subarquitectura CHRP (no es compatible)" #~ msgid "HP PA-RISC" #~ msgstr "HP PA-RISC" #~ msgid "hppa" #~ msgstr "hppa" #~ msgid "PA-RISC 1.1" #~ msgstr "PA-RISC 1.1" #~ msgid "PA-RISC 2.0" #~ msgstr "PA-RISC 2.0" #~ msgid "64" #~ msgstr "64" #~ msgid "" #~ "In order to optimize the kernel for single CPU systems, you'll have to " #~ "replace the standard &debian; kernel. You can " #~ "find a discussion of how to do this in . " #~ "At this time (kernel version &kernelversion;) the way you disable SMP is " #~ "to deselect &smp-config-option; in the &smp-config-" #~ "section; section of the kernel config." #~ msgstr "" #~ "Para optimizar el núcleo para sistemas de un sólo procesador, tendrá que " #~ "reemplazar el núcleo estándar de &debian;. Puede encontrar una discusión acerca de cómo hacer esto en . En este momento (versión del núcleo " #~ "&kernelversion;) la forma de deshabilitar SMP es deseleccionando " #~ "&smp-config-option; en la sección &smp-config-" #~ "section; de la configuración del núcleo." #~ msgid "" #~ "You should be using a VGA-compatible display interface for the console " #~ "terminal. Nearly every modern display card is compatible with VGA. " #~ "Ancient standards such CGA, MDA, or HGA should also work, assuming you do " #~ "not require X11 support. Note that X11 is not used during the " #~ "installation process described in this document unless the graphical " #~ "installer was explicitly selected." #~ msgstr "" #~ "Debería utilizar una interfaz de visualización compatible con VGA para la " #~ "terminal de consola. Prácticamente cualquier tarjeta de vídeo moderna es " #~ "compatible con VGA. Los estándares viejos como CGA, MDA o HGA también " #~ "deberían funcionar, asumiendo que no necesite usar X11. Tenga en cuenta " #~ "que no se usa X11 durante el proceso de instalación descrito en este " #~ "documento a menos que se seleccione el instalador gráfico." #~ msgid "" #~ "Again, see the Linux Hardware " #~ "Compatibility HOWTO to determine whether your specific hardware " #~ "is supported by Linux." #~ msgstr "" #~ "Consulte el CÓMO de compatibilidad " #~ "hardware de Linux para determinar si Linux ofrece compatibilidad " #~ "con su hardware específico." #~ msgid "" #~ "Since we haven't been granted access to the documentation on these " #~ "devices, they simply won't work under &arch-kernel;. You can help by " #~ "asking the manufacturers of such hardware to release the documentation. " #~ "If enough people ask, they will realize that the free software community " #~ "is an important market." #~ msgstr "" #~ "Estos dispositivos sencillamente no funcionarán bajo &arch-kernel; puesto " #~ "que no hemos tenido acceso a su documentación. Puede ayudar a cambiar " #~ "esta situación reclamando a los fabricantes de este hardware que " #~ "publiquen la documentación. Si un número importante de personas lo hacen, " #~ "se darán cuenta que la comunidad de software libre es un mercado " #~ "importante." #~ msgid "Windows-specific Hardware" #~ msgstr "Hardware específico para Windows" #~ msgid "" #~ "A disturbing trend is the proliferation of Windows-specific modems and " #~ "printers. In some cases these are specially designed to be operated by " #~ "the Microsoft Windows operating system and bear the legend " #~ "WinModem or Made especially for Windows-based " #~ "computers. This is generally done by removing the embedded " #~ "processors of the hardware and shifting the work they do over to a " #~ "Windows driver that is run by your computer's main CPU. This strategy " #~ "makes the hardware less expensive, but the savings are often " #~ "not passed on to the user and this hardware may even " #~ "be more expensive than equivalent devices that retain their embedded " #~ "intelligence." #~ msgstr "" #~ "Una tendencia preocupante es la proliferación de módems e impresoras " #~ "específicas para Windows. En algunos casos están diseñadas especialmente " #~ "para funcionar en el sistema operativo Microsoft Windows y muestran la " #~ "leyenda WinModem o Made especially for Windows-" #~ "based computers (Hecho especialmente para ordenadores " #~ "basados en Windows, n. del t.). Esto se hace habitualmente " #~ "eliminando los procesadores integrados del hardware y desplazando el " #~ "trabajo que éstos efectúan por un controlador en Windows que se ejecuta " #~ "sobre el procesador principal de su equipo. Esta estrategia abarata el " #~ "precio del hardware, pero el ahorro no repercute " #~ "generalmente en el usuario y este hardware puede ser incluso más caro que " #~ "los dispositivos equivalentes que mantienen su inteligencia integrada." #~ msgid "" #~ "You should avoid Windows-specific hardware for two reasons. The first is " #~ "that the manufacturers do not generally make the resources available to " #~ "write a &arch-kernel; driver. Generally, the hardware and software " #~ "interface to the device is proprietary, and documentation is not " #~ "available without a non-disclosure agreement, if it is available at all. " #~ "This precludes it being used for free software, since free software " #~ "writers disclose the source code of their programs. The second reason is " #~ "that when devices like these have had their embedded processors removed, " #~ "the operating system must perform the work of the embedded processors, " #~ "often at real-time priority, and thus the CPU is not " #~ "available to run your programs while it is driving these devices. Since " #~ "the typical Windows user does not multi-process as intensively as a &arch-" #~ "kernel; user, the manufacturers hope that the Windows user simply won't " #~ "notice the burden this hardware places on their CPU. However, any multi-" #~ "processing operating system, even Windows 2000 or XP, suffers from " #~ "degraded performance when peripheral manufacturers skimp on the embedded " #~ "processing power of their hardware." #~ msgstr "" #~ "Debería evitar el hardware específico para Windows por dos razones. La " #~ "primera es que los fabricantes no ofrecen recursos para que sea posible " #~ "escribir un controlador para &arch-kernel;. La interfaz de hardware y " #~ "software al dispositivo es habitualmente privativa, y la documentación no " #~ "está disponible sin un acuerdo de no divulgación, si es que está " #~ "disponible. Esto excluye su uso para el software libre, puesto que los " #~ "desarrolladores de software libre publican el código fuente de sus " #~ "programas. La segunda razón es que cuando se han eliminado los " #~ "procesadores integrados a dispositivos como éstos, el sistema operativo " #~ "debe efectuar el trabajo de éstos, con prioridad de tiempo " #~ "real, la CPU no estará entonces disponible para ejecutar sus " #~ "programas mientras controla dichos dispositivos. Puesto que el usuario " #~ "típico de Windows no multiprocesa tan intensamente como el de &arch-" #~ "kernel;, los fabricantes esperan que el usuario de Windows simplemente no " #~ "note la carga que este hardware impone a su CPU. No obstante, cualquier " #~ "sistema operativo multiproceso, incluso Windows 2000 o XP se degrada " #~ "cuando los fabricantes de periféricos escatiman en la capacidad de " #~ "procesamiento integrada en su hardware." #~ msgid "" #~ "You can help improve this situation by encouraging these manufacturers to " #~ "release the documentation and other resources necessary for us to program " #~ "their hardware, but the best strategy is simply to avoid this sort of " #~ "hardware until it is listed as working in the " #~ "Linux Hardware Compatibility HOWTO." #~ msgstr "" #~ "Puede ayudar a cambiar esta situación reclamando a los fabricantes de " #~ "este hardware a que publiquen la documentación así como otros recursos " #~ "necesarios para programar su hardware, pero la mejor estrategia es " #~ "simplemente evitar este tipo de hardware hasta " #~ "que se liste como compatible en el COMO de compatibilidad hardware de Linux." #~ msgid "" #~ "CD-ROM based installation is supported for some architectures. On " #~ "machines which support bootable CD-ROMs, you should be able to do a " #~ "completely floppy-less tape-less installation. Even if your system doesn't " #~ "support booting from a CD-ROM, you can use the CD-ROM in conjunction with " #~ "the other techniques to install your system, once you've booted up by " #~ "other means; see ." #~ msgstr "" #~ "Algunas arquitecturas permiten la instalación basada en CD-ROM. En " #~ "máquinas que permiten CD-ROMs arrancables, debería ser capaz de efectuar " #~ "una instalación totalmente sin disquetes sin cintas. Puede usar el CD-ROM " #~ "en conjunto con otras técnicas para instalar su sistema, una vez haya " #~ "arrancado a través de otros mecanismos incluso si su sistema no permite " #~ "el arranque desde CD-ROM, consulte el ." #~ msgid "" #~ "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The Linux CD-ROM HOWTO contains in-depth information on " #~ "using CD-ROMs with Linux." #~ msgstr "" #~ "Se aceptan tanto CD-ROMs SCSI, SATA e IDE/ATAPI. El CÓMO de Linux CD-ROM contiene información detallada " #~ "sobre el uso de CD-ROMs con Linux." #~ msgid "" #~ "Many &debian; boxes need their floppy and/or CD-ROM drives only for " #~ "setting up the system and for rescue purposes. If you operate some " #~ "servers, you will probably already have thought about omitting those " #~ "drives and using an USB memory stick for installing and (when necessary) " #~ "for recovering the system. This is also useful for small systems which " #~ "have no room for unnecessary drives." #~ msgstr "" #~ "Muchas máquinas &debian; sólo necesitan una unidad de disquetes y/o CD-" #~ "ROM para instalar el sistema o para propósitos de recuperación del " #~ "sistema. Si gestiona servidores, puede que haya pensado en omitir estas " #~ "unidades y usar un dispositivo de memoria USB para instalar y (cuando sea " #~ "necesario) recuperar el sistema. También es útil en el caso de sistemas " #~ "pequeños que no tienen espacio para unidades innecesarias." #~ msgid "" #~ "You can also boot the installation system over the " #~ "network. This is the preferred installation " #~ "technique for &arch-title;." #~ msgstr "" #~ "También puede arrancar el sistema de instalación a " #~ "través de la red. Este es el método de instalación " #~ "preferido para &arch-title;." #~ msgid "" #~ "The &debian; boot disks contain a kernel which is built to maximize the " #~ "number of systems it runs on. Unfortunately, this makes for a larger " #~ "kernel, which includes many drivers that won't be used for your " #~ "machine (see " #~ "to learn how to build your own kernel). Support for the widest " #~ "possible range of devices is desirable in general, to ensure that " #~ "&debian; can be installed on the widest array of hardware." #~ msgstr "" #~ "Los discos de inicio de &debian; contienen un núcleo construido para " #~ "maximizar el número de sistemas donde se puede ejecutar. " #~ "Desafortunadamente, esto lo convierte en un núcleo más grande, que " #~ "incluye muchos controladores que no se usarán en su máquina (consulte la para " #~ "aprender cómo construir su propio núcleo). Para poder asegurar " #~ "que &debian; se pueda instalar en la mayor cantidad de hardware posible, " #~ "se incluye la compatibilidad con el rango más amplio de dispositivos " #~ "posibles." #~ msgid "" #~ "Disk interfaces that emulate the AT hard disk interface " #~ "— often called MFM, RLL, IDE, or PATA — are supported. SATA " #~ "and SCSI disk controllers from many different manufacturers are " #~ "supported. See the Linux Hardware " #~ "Compatibility HOWTO for more details." #~ msgstr "" #~ "Hay compatibilidad con las interfaces de disco que emulan la interfaz de " #~ "disco duro AT, con frecuencia llamadas MFM, RLL, IDE o " #~ "PATA. Los controladoras SATA y SCSI de muchos fabricantes también son " #~ "compatibles. Consulte el CÓMO de " #~ "compatibilidad de hardware de Linux para más información."