diff options
415 files changed, 999 insertions, 977 deletions
diff --git a/build/arch-options/alpha b/build/arch-options/alpha index 760ec38e5..51c5a3fbf 100644 --- a/build/arch-options/alpha +++ b/build/arch-options/alpha @@ -2,7 +2,7 @@ # the 'alpha' architecture # It is sourced by the build scripts -archspec="alpha;not-i386;not-s390;not-m68k;not-powerpc" +archspec="alpha;not-x86;not-s390;not-m68k;not-powerpc" kernelversion="2.6.16" arch_listname="alpha" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/amd64 b/build/arch-options/amd64 new file mode 100644 index 000000000..525c930da --- /dev/null +++ b/build/arch-options/amd64 @@ -0,0 +1,21 @@ +# This file contains architecture specific variables for +# the 'amd64' architecture +# It is sourced by the build scripts + +archspec="amd64;x86;not-s390;not-m68k;not-powerpc;not-alpha" +kernelversion="2.6.16" +arch_listname="amd64" +# These two options should be set if condition 'smp' is set below +smp_config_section="Processor type and features" +smp_config_option="Symmetric multi-processing support" + +# Options below are assembled into one variable 'condition' +# in the build scripts +kernelpackage="common-kpkg" +fdisk="fdisk.txt;cfdisk.txt" +network="supports-tftp;supports-dhcp;supports-bootp;supports-nfsroot" +boot="bootable-disk;bootable-usb" +other="supports-pcmcia;supports-serial-console;rescue-needs-root-disk;workaround-bug-99926" +smp="supports-smp-sometimes" +goodies="supports-lang-chooser" +status="checked" diff --git a/build/arch-options/arm b/build/arch-options/arm index 3f19744b9..b249ff39f 100644 --- a/build/arch-options/arm +++ b/build/arch-options/arm @@ -2,7 +2,7 @@ # the 'arm' architecture # It is sourced by the build scripts -archspec="arm;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="arm;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="arm" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/hppa b/build/arch-options/hppa index d5d9d6c04..baeda6a3b 100644 --- a/build/arch-options/hppa +++ b/build/arch-options/hppa @@ -2,7 +2,7 @@ # the 'hppa' architecture # It is sourced by the build scripts -archspec="hppa;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="hppa;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="hppa" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/i386 b/build/arch-options/i386 index f38051c6d..c92f4047d 100644 --- a/build/arch-options/i386 +++ b/build/arch-options/i386 @@ -2,7 +2,7 @@ # the 'i386' architecture # It is sourced by the build scripts -archspec="i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="i386;x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="boot" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/ia64 b/build/arch-options/ia64 index 6c89cab3c..8f86ad8d1 100644 --- a/build/arch-options/ia64 +++ b/build/arch-options/ia64 @@ -2,7 +2,7 @@ # the 'ia64' architecture # It is sourced by the build scripts -archspec="ia64;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="ia64;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="ia64" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/m68k b/build/arch-options/m68k index e97b8d087..7396bbb6b 100644 --- a/build/arch-options/m68k +++ b/build/arch-options/m68k @@ -2,7 +2,7 @@ # the 'm68k' architecture # It is sourced by the build scripts -archspec="m68k;not-i386;not-s390;not-powerpc;not-alpha" +archspec="m68k;not-x86;not-s390;not-powerpc;not-alpha" kernelversion="2.4.27" arch_listname="68k" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/mips b/build/arch-options/mips index 2cef322c5..bd6ba9586 100644 --- a/build/arch-options/mips +++ b/build/arch-options/mips @@ -2,7 +2,7 @@ # the 'mips' architecture # It is sourced by the build scripts -archspec="mips;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="mips;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="mips" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/mipsel b/build/arch-options/mipsel index 36ed4b4f3..61bdea1f4 100644 --- a/build/arch-options/mipsel +++ b/build/arch-options/mipsel @@ -2,7 +2,7 @@ # the 'mipsel' architecture # It is sourced by the build scripts -archspec="mipsel;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="mipsel;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="mips" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/powerpc b/build/arch-options/powerpc index 478d7ba05..1d970d18f 100644 --- a/build/arch-options/powerpc +++ b/build/arch-options/powerpc @@ -2,7 +2,7 @@ # the 'powerpc' architecture # It is sourced by the build scripts -archspec="powerpc;not-s390;not-m68k;not-i386;not-alpha" +archspec="powerpc;not-s390;not-m68k;not-x86;not-alpha" kernelversion="2.6.16" arch_listname="powerpc" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/s390 b/build/arch-options/s390 index 7b140dfca..7a3483e48 100644 --- a/build/arch-options/s390 +++ b/build/arch-options/s390 @@ -2,7 +2,7 @@ # the 's390' architecture # It is sourced by the build scripts -archspec="s390;not-powerpc;not-m68k;not-i386;not-alpha" +archspec="s390;not-powerpc;not-m68k;not-x86;not-alpha" kernelversion="2.6.16" arch_listname="s390" # These two options should be set if condition 'smp' is set below diff --git a/build/arch-options/sparc b/build/arch-options/sparc index 18313677c..8244e8fa5 100644 --- a/build/arch-options/sparc +++ b/build/arch-options/sparc @@ -2,7 +2,7 @@ # the 'sparc' architecture # It is sourced by the build scripts -archspec="sparc;not-i386;not-s390;not-m68k;not-powerpc;not-alpha" +archspec="sparc;not-x86;not-s390;not-m68k;not-powerpc;not-alpha" kernelversion="2.6.16" arch_listname="sparc" # These two options should be set if condition 'smp' is set below diff --git a/build/entities/common.ent b/build/entities/common.ent index 10da8335f..2e7e61da6 100644 --- a/build/entities/common.ent +++ b/build/entities/common.ent @@ -17,7 +17,7 @@ <!-- proper nouns for architectures --> <!ENTITY arch-title - "<phrase arch='alpha'>Alpha</phrase><phrase arch='arm'>ARM</phrase><phrase arch='hppa'>PA-RISC</phrase><phrase arch='i386'>Intel x86</phrase><phrase arch='ia64'>IA-64</phrase><phrase arch='m68k'>Motorola 680x0</phrase><phrase arch='mips'>Mips</phrase><phrase arch='mipsel'>Mipsel</phrase><phrase arch='powerpc'>PowerPC</phrase><phrase arch='sparc'>SPARC</phrase><phrase arch='s390'>S/390</phrase>"> + "<phrase arch='amd64'>AMD64</phrase><phrase arch='alpha'>Alpha</phrase><phrase arch='arm'>ARM</phrase><phrase arch='hppa'>PA-RISC</phrase><phrase arch='i386'>Intel x86</phrase><phrase arch='ia64'>IA-64</phrase><phrase arch='m68k'>Motorola 680x0</phrase><phrase arch='mips'>Mips</phrase><phrase arch='mipsel'>Mipsel</phrase><phrase arch='powerpc'>PowerPC</phrase><phrase arch='sparc'>SPARC</phrase><phrase arch='s390'>S/390</phrase>"> <!-- general things from installer --> <!ENTITY enterkey "<keycap>Enter</keycap>"> diff --git a/ca/administrivia/administrivia.xml b/ca/administrivia/administrivia.xml index 5a8035678..ee1f90315 100644 --- a/ca/administrivia/administrivia.xml +++ b/ca/administrivia/administrivia.xml @@ -130,7 +130,7 @@ La secció del manual sobre instal·lacions amb chroot (<xref linkend="linux-upgrade"/>) procedeix, en part, de documents propietat de Karsten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> La secció del manual sobre instal·lacions de plip (<xref linkend="plip"/>) està basada en el diff --git a/ca/appendix/chroot-install.xml b/ca/appendix/chroot-install.xml index f00801b4d..893b508e2 100644 --- a/ca/appendix/chroot-install.xml +++ b/ca/appendix/chroot-install.xml @@ -410,7 +410,7 @@ la particiórel. Fixeu-vos que <command>debootstrap</command> no instal·la cap carregador d'arrencada, encara que podeu utilitzar l'<command>aptitude</command> dins el chroot per tal de fer-ho. -</para><para arch="i386"> +</para><para arch="x86"> Comproveu l'informació de <userinput>info grub</userinput> o <userinput>man lilo.conf</userinput> per com configurar el carregador d'arrencada. Si el @@ -421,7 +421,7 @@ podeu copiar-lo al nou sistema i editar-lo allí. Després de editar-lo, executeu lilo (recordeu que utilitzarà el <filename>lilo.conf</filename> relatiu al sistema des d'on el crideu). -</para><para arch="i386"> +</para><para arch="x86"> Ací teniu un exemple bàsic de <filename>/etc/lilo.conf</filename>: diff --git a/ca/appendix/plip.xml b/ca/appendix/plip.xml index bfe4cb7e1..82a5ff7ac 100644 --- a/ca/appendix/plip.xml +++ b/ca/appendix/plip.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 39463 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Instal·lació de &debian; per Parallel Line IP (PLIP)</title> <para> diff --git a/ca/boot-installer/boot-installer.xml b/ca/boot-installer/boot-installer.xml index 6e157a432..60859684e 100644 --- a/ca/boot-installer/boot-installer.xml +++ b/ca/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Arrencada de l'instal·lador en l'arquitectura &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/ca/boot-installer/i386.xml b/ca/boot-installer/i386.xml index 0f8beac93..b96326461 100644 --- a/ca/boot-installer/i386.xml +++ b/ca/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 38231 --> - <sect2 arch="i386"><title>Arrencada des d'un CD-ROM</title> + <sect2 arch="x86"><title>Arrencada des d'un CD-ROM</title> &boot-installer-intro-cd.xml; @@ -74,7 +74,7 @@ Boots the <quote>bf2.4</quote> flavor. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -105,7 +105,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Arrencada des del Linux utilitzant el <command>LILO</command> o el <command>GRUB</command></title> @@ -203,7 +203,7 @@ d'haver cap diferència entre el <command>GRUB</command> i el </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Arrencada des d'un llapis USB</title> <para> @@ -218,7 +218,7 @@ els paràmetres d'arrencada opcionals o únicament prémer &enterkey; </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Arrencada des dels disquets</title> <para> @@ -280,7 +280,7 @@ s'iniciarà automàticament. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Arrencada amb el TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Arrencada amb el TFTP</title> &boot-installer-intro-net.xml; @@ -326,7 +326,7 @@ que permeten l'arrencada via TFTP. </sect3> </sect2> - <sect2 arch="i386"><title>L'indicador d'arrencada</title> + <sect2 arch="x86"><title>L'indicador d'arrencada</title> <para> Quan arrenqui l'instal·lador us apareixerà una pantalla gràfica diff --git a/ca/boot-installer/intro-cd.xml b/ca/boot-installer/intro-cd.xml index fa8770197..b82cb09b6 100644 --- a/ca/boot-installer/intro-cd.xml +++ b/ca/boot-installer/intro-cd.xml @@ -7,7 +7,7 @@ La manera més fàcil per a la majoria de la gent serà utilitzar un conjunt de CD de Debian. Si disposeu d'un conjunt de CD i el vostre ordinador permet arrencar directament des del CD, fantàstic! Només -<phrase arch="i386"> +<phrase arch="x86"> heu de configurar el sistema perquè arrenqui des d'un CD tal i com es descriu a <xref linkend="boot-dev-select"/>, </phrase> diff --git a/ca/boot-installer/parameters.xml b/ca/boot-installer/parameters.xml index 3d098c3d6..f077495dd 100644 --- a/ca/boot-installer/parameters.xml +++ b/ca/boot-installer/parameters.xml @@ -230,7 +230,7 @@ el paràmetre <userinput>debian-installer/framebuffer=false</userinput>, o bogl, una pantalla en blanc o que es quedi congelat durant uns quants minuts després d'iniciar la instal·lació. -</para><para arch="i386"> +</para><para arch="x86"> Per deshabilitar la utilització del framebufer al nucli també podeu utilitzar l'argument <userinput>video=vga16:off</userinput>. La problemàtica relacionada diff --git a/ca/boot-installer/trouble.xml b/ca/boot-installer/trouble.xml index 2b98065d1..c6cc81c70 100644 --- a/ca/boot-installer/trouble.xml +++ b/ca/boot-installer/trouble.xml @@ -67,7 +67,7 @@ l'instal·lador, assegureu-vos que teniu configurat </para><para> Sovint, els problemes desapareixen si traieu maquinari addicional i -perifèrics, i proveu aleshores d'arrencar de nou. <phrase arch="i386">Els +perifèrics, i proveu aleshores d'arrencar de nou. <phrase arch="x86">Els mòdems interns, les targetes de so, i els dispositius Plug-n-Play poden ser especialment problemàtics.</phrase> @@ -81,7 +81,7 @@ veure el nucli, com ara <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Problemes d'instal·lació usuals en &arch-title;</title> <para> diff --git a/ca/hardware/hardware-supported.xml b/ca/hardware/hardware-supported.xml index 542636dc1..7f749bcb6 100644 --- a/ca/hardware/hardware-supported.xml +++ b/ca/hardware/hardware-supported.xml @@ -218,7 +218,7 @@ correu debian-&architecture;</ulink>. <sect2 id="gfx" arch="not-s390"><title>Targeta gràfica</title> -<para arch="i386"> +<para arch="x86"> Hauríeu d'utilitzar una interfície de pantalla compatible amb VGA per la consola del terminal. Quasi totes les targetes gràfiques modernes són @@ -258,7 +258,7 @@ pel BCM91250A. </sect2> - <sect2 arch="i386" id="laptops"><title>Ordinadors portàtils</title> + <sect2 arch="x86" id="laptops"><title>Ordinadors portàtils</title> <para> També estan suportats els ordinadors portàtils. Moltes vegades contenen diff --git a/ca/hardware/installation-media.xml b/ca/hardware/installation-media.xml index 290499577..8be166e02 100644 --- a/ca/hardware/installation-media.xml +++ b/ca/hardware/installation-media.xml @@ -48,7 +48,7 @@ no suporte arrencar des de CD-ROM, podeu utilitzar-lo junt a altres tècniques d'instal·lació al vostre sistema, i una vegada que heu arrencat el sistema per altres mitjans, mireu <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Estan suportats, tant els CD-ROM SCSI com els IDE/ATAPI. També estan suportats tots els CD no estàndard que suporte Linux als discs d'arrencada @@ -58,7 +58,7 @@ d'aquestes interfícies. El <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> conté informació en profunditat de com fer servir CD-ROM a Linux. -</para><para arch="i386"> +</para><para arch="x86"> Les unitats de CD-ROM USB també estan suportades, igual que tots els dispositius FireWire que suporten els controladors ohci1394 i sbp2. @@ -211,14 +211,14 @@ compilar el vostre nucli). Suportar la major quantitat de dispositius possible és el que es desitja en general, per assegurar que Debian pugui instal·lar-se a tot el maquinari possible. -</para><para arch="i386"> +</para><para arch="x86"> Normalment, la instal·lació de Debian inclou el suport per disquets, discs IDE, disqueteres IDE, dispositius IDE per port paral·lel, controladores SCSI i discos, USB i FireWire. Els sistemes de fitxers suportats inclouen FAT, les extensions Win-32 FAT (VFAT), i NTFS. -</para><para arch="i386"> +</para><para arch="x86"> Les interfícies de disc que emulen la interfície de disc dur <quote>AT</quote> — que s'anomenen MFM,RLL, IDE o ATA estan suportades. diff --git a/ca/hardware/network-cards.xml b/ca/hardware/network-cards.xml index b9b45b8d2..86f60be1c 100644 --- a/ca/hardware/network-cards.xml +++ b/ca/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Maquinari per a la connexió de xarxes</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -21,7 +21,7 @@ funcionen amb els discs d'instal·lació. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> Igual com per a l'XDSI (RDSI), el protocol D-channel per als (antics) German 1TR6 no funciona. Les plaques Spellcaster BRI XDSI tampoc no diff --git a/ca/hardware/supported-peripherals.xml b/ca/hardware/supported-peripherals.xml index 04b9d0802..374f915b8 100644 --- a/ca/hardware/supported-peripherals.xml +++ b/ca/hardware/supported-peripherals.xml @@ -10,13 +10,13 @@ com ara ratolins, impressores, escànners, PCMCIA i dispositius USB. De tota manera, la major part d'aquests dispositius no són necessaris durant la instal·lació del sistema. -</para><para arch="i386"> +</para><para arch="x86"> El maquinari USB generalment funciona correctament, només alguns teclats USB necessiten configuració addicional (consulteu <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> De nou, consulteu el <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -60,7 +60,7 @@ GNU/Linux. Malauradament, és força rar trobar cap fabricant que vengui màquines &arch-title; noves. -</para><para arch="i386"> +</para><para arch="x86"> Si heu de comprar una màquina amb Windows inclòs, llegiu amb cura la llicència de programari que ve amb el Windows; potser podeu rebutjar la @@ -110,7 +110,7 @@ important. </sect2> - <sect2 arch="i386"><title>Maquinari específic de Windows</title> + <sect2 arch="x86"><title>Maquinari específic de Windows</title> <para> Una tendència molesta és la proliferació de mòdems i impressores específiques diff --git a/ca/hardware/supported/i386.xml b/ca/hardware/supported/i386.xml index 5b8e2086f..763db87c5 100644 --- a/ca/hardware/supported/i386.xml +++ b/ca/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"><title>Suport de CPU, plaques base i vídeo</title> + <sect2 arch="x86"><title>Suport de CPU, plaques base i vídeo</title> <para> La informació completa pertinent als dispositius suportats es pot trobar al diff --git a/ca/howto/installation-howto.xml b/ca/howto/installation-howto.xml index b5f89104b..db9eefc1b 100644 --- a/ca/howto/installation-howto.xml +++ b/ca/howto/installation-howto.xml @@ -83,7 +83,7 @@ conjunt de CDs de Debian. </para><para> Descarregueu la que preferiu i graveu-la a un CD. -<phrase arch="i386">Per arrencar el CD, necessiteu canviar la configuració de +<phrase arch="x86">Per arrencar el CD, necessiteu canviar la configuració de la vostra BIOS, com s'explica a la <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> Per arrencar un PowerMac des de CD, premeu la tecla <keycap>c</keycap> mentre @@ -158,7 +158,7 @@ Hi ha formes més flexibles per preparar un llapis de memòria per fer ús del debian-installer, i també és possible que funcioni amb llapis de memòria mes petits. Per més detalls, podeu mirar <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Algunes BIOS poden arrencar directament de dispositius USB, i d'altres no. Heu de configurar la vostra BIOS per que arrenque des del «disc extraïble» o @@ -184,7 +184,7 @@ i configuració d'arrencada de xarxa. Els fitxers que podeu trobar a <filename>netboot/</filename> poden utilitzar-se per arrencar de la xarxa el &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> La manera més fàcil per configurar-ho és probablement l'arrencada amb PXE. Desempaqueteu amb el tar el fitxer <filename>netboot/pxeboot.tar.gz</filename> @@ -208,7 +208,7 @@ Descarregueu <filename>hd-media/initrd.gz</filename>, directori principal del vostre disc dur. Assegureu-vos de que la imatge del CD ha de tenir el nom acabat amb <literal>.iso</literal>. Ara tan sols us queda arrencar el linux amb el initrd. -<phrase arch="i386"> +<phrase arch="x86"> A la <xref linkend="boot-initrd" /> s'explica com fer-ho. </phrase> @@ -224,7 +224,7 @@ A la <xref linkend="boot-initrd" /> s'explica com fer-ho. Una vegada l'instal·lador ha començat, voreu la pantalla de benvinguda. Premeu &enterkey; per arrencar, o llegiu les instruccions per seleccionar altres mètodes i paràmetres (vegeu la <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Si voleu utilitzar el nucli 2.4, escriviu <userinput>install24</userinput> a la petició «<prompt>boot:</prompt>». <footnote><para> @@ -266,7 +266,7 @@ l'oportunitat de triar si particionar automàticament el disc sencer, o l'espai buit. Es el que us recomaneu si sou nous usuaris o si teniu pressa, en altre cas, trieu «manual» des del menú. -</para><para arch="i386"> +</para><para arch="x86"> Si teniu una partició amb DOS o Windows que voleu conservar, aneu amb molt de compte amb la partició automàtica. Si seleccioneu @@ -295,7 +295,7 @@ sistema base, la qual cosa tardarà una mica. Desprès s'instal·larà el nucli. L'últim pas és la instal·lació del gestor d'arrencada. Si l'instal·lador detecta altres sistemes operatius al vostre ordinador, els afegirà al menú d'arrencada i ho farà saber. -<phrase arch="i386">Per defecte el GRUB s'instal·larà al sector d'arrencada +<phrase arch="x86">Per defecte el GRUB s'instal·larà al sector d'arrencada del vostre primer disc dur, cosa que normalment serà una bona elecció. Podreu canviar-lo i instal·lar-lo a un altre lloc si ho desitgeu. </phrase> diff --git a/ca/install-methods/boot-drive-files.xml b/ca/install-methods/boot-drive-files.xml index f707a6cc0..1b112ee00 100644 --- a/ca/install-methods/boot-drive-files.xml +++ b/ca/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ utilitzant aquesta tècnica. Açò evita tota la confusió de mitjans extraïble com trobar i gravar imatges de CD o barallar-se amb nombrosos i poc fiables disquets. -</para><para arch="i386"> +</para><para arch="x86"> L'instal·lador no pot arrencar des d'un sistema de fitxers NTFS. @@ -40,7 +40,7 @@ depenent de si el sistema és un model <quote>NewWorld</quote> o un </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Arrencada de l'instal·lador des de disc dur fent ús de <command>LILO</command> o <command>GRUB</command></title> <para> diff --git a/ca/install-methods/boot-usb-files.xml b/ca/install-methods/boot-usb-files.xml index ee32f8f32..b1d5e4507 100644 --- a/ca/install-methods/boot-usb-files.xml +++ b/ca/install-methods/boot-usb-files.xml @@ -24,7 +24,7 @@ possible configurar amb llapis amb menys capacitat si seguiu <sect2 id="usb-copy-easy"> <title>Copiant els fitxers — la manera fàcil</title> -<para arch="i386"> +<para arch="x86"> Hi ha un fitxer complet <filename>hd-media/boot.img.gz</filename> que conté tots el fitxers de l'instal·lador (incloent el nucli) així com @@ -59,10 +59,10 @@ pel vostre llapis USB. <para> Desprès d'això, munteu el llapis de memòria USB (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), que ara tindrà -<phrase arch="i386">un sistema de fitxers FAT</phrase> +<phrase arch="x86">un sistema de fitxers FAT</phrase> <phrase arch="powerpc">un sistema de fitxers HFS</phrase> en ell, i copieu una imatge ISO de targeta de negocis o netinst a dins. Adoneu-vos que el nom del fitxer ha d'acabar en <filename>.iso</filename>. @@ -112,7 +112,7 @@ i activeu la protecció d'escriptura. </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Arrencada des d'un llapis USB</title> <warning><para> diff --git a/ca/install-methods/install-tftp.xml b/ca/install-methods/install-tftp.xml index 86ad72c5f..6c9418dbb 100644 --- a/ca/install-methods/install-tftp.xml +++ b/ca/install-methods/install-tftp.xml @@ -73,7 +73,7 @@ qualsevol servidor de qualsevol plataforma que implemente aquests protocols. Els exemples d'aquesta secció ofereixen instruccions per al SunOS 4.x, el SunOS 5.x (i.e. Solaris), i el GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> El mètode PXE d'arrencada TFTP, o entorn d'execució d'arrencada prèvia, requereix un servidor TFTP que permeta l'ús de <userinput>tsize</userinput>. @@ -163,7 +163,7 @@ el RAMdisk a través del TFTP mateix. Per arrencar en xarxa, feu servir <filename>yaboot-netboot.conf</filename>. Només cal reanomenar-lo com <filename>yaboot.conf</filename> al directori del TFTP. -</para><para arch="i386"> +</para><para arch="x86"> Per a arrencar amb PXE, sols cal el tarball <filename>netboot/netboot.tar.gz</filename>. Simplement extragueu-lo diff --git a/ca/install-methods/tftp/dhcp.xml b/ca/install-methods/tftp/dhcp.xml index 94626ef2b..b56da7b68 100644 --- a/ca/install-methods/tftp/dhcp.xml +++ b/ca/install-methods/tftp/dhcp.xml @@ -51,7 +51,7 @@ reengegueu-lo amb <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Habilitar l'arranc amb PXE a la configuració del servidor de DHCP</title> <para> Hi ha un altre exemple de <filename>dhcp.conf</filename> que fa servir el diff --git a/ca/install-methods/usb-setup/i386.xml b/ca/install-methods/usb-setup/i386.xml index d4b554241..b0d07c353 100644 --- a/ca/install-methods/usb-setup/i386.xml +++ b/ca/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Particionar un llapis USB a &arch-title;</title> <para> diff --git a/ca/partitioning/device-names.xml b/ca/partitioning/device-names.xml index 2d8fc5778..b2257d6c5 100644 --- a/ca/partitioning/device-names.xml +++ b/ca/partitioning/device-names.xml @@ -67,12 +67,12 @@ pot mostrar-se com a <filename>/dev/hda</filename> a la Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> El primer disc XT s'anomena <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> El segon disc XT s'anomena <filename>/dev/xdb</filename>. @@ -124,7 +124,7 @@ controladores), l'ordre de les unitats pot ser confús. La millor solució en aquest cas és estar atent als missatges d'arrencada, assumint que sabeu els models de les unitats i/o les seues capacitats. -</para><para arch="i386"> +</para><para arch="x86"> Linux representa les particions primàries fent servir el nom del disc, més els números 1 al 4. Per exemple, la primera partició primària al diff --git a/ca/partitioning/partition-programs.xml b/ca/partitioning/partition-programs.xml index d43879ed1..a2850d9f7 100644 --- a/ca/partitioning/partition-programs.xml +++ b/ca/partitioning/partition-programs.xml @@ -20,7 +20,7 @@ per a la vostra arquitectura. És l'eina de Debian recomanada per particionar. Aquesta navalla suïssa també pot redimensionar particions, crear sistemes de fitxers -<phrase arch="i386"> (<quote>formatar</quote> en terminologia de Windows)</phrase> +<phrase arch="x86"> (<quote>formatar</quote> en terminologia de Windows)</phrase> i associar-los a punts de muntatge. </para></listitem> @@ -141,7 +141,7 @@ sistema de destí. Després d'instal·lar el nucli i els mòduls, executeu: # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">Recordeu que heu de marcar la partició d'arrencada com a +<phrase arch="x86">Recordeu que heu de marcar la partició d'arrencada com a <quote>Arrencable</quote>.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/ca/partitioning/partition/i386.xml b/ca/partitioning/partition/i386.xml index 9e73ca871..9535f9ffe 100644 --- a/ca/partitioning/partition/i386.xml +++ b/ca/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 39465 --> - <sect2 arch="i386"><title>Particionat per a &arch-title;</title> + <sect2 arch="x86"><title>Particionat per a &arch-title;</title> <para> Si teniu instal·lat un altre sistema operatiu com el DOS o el Windows i diff --git a/ca/post-install/kernel-baking.xml b/ca/post-install/kernel-baking.xml index b878ceab9..dfa16afe7 100644 --- a/ca/post-install/kernel-baking.xml +++ b/ca/post-install/kernel-baking.xml @@ -160,7 +160,7 @@ com qualsevol altre paquet. Heu d'executar, com a superusuari, </phrase> La part <replaceable>subarquitectura</replaceable> és una subarquitectura opcional -<phrase arch="i386"> com per exemple <quote>i586</quote>, </phrase> +<phrase arch="x86"> com per exemple <quote>i586</quote>, </phrase> en funció de les opcions del nucli seleccionades. L'ordre <userinput>dpkg -i</userinput> instal·larà el nucli, diff --git a/ca/post-install/reactivating-win.xml b/ca/post-install/reactivating-win.xml index 968e6483e..163221ed1 100644 --- a/ca/post-install/reactivating-win.xml +++ b/ca/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivant DOS i Windows</title> <para> diff --git a/ca/post-install/rescue.xml b/ca/post-install/rescue.xml index ec75780e0..e06ea545a 100644 --- a/ca/post-install/rescue.xml +++ b/ca/post-install/rescue.xml @@ -42,7 +42,7 @@ els dispositius RAID i LVM i les creades directament als discs. L'instal·lador intentarà donar-vos accés a l'indicador de l'intèrpret d'ordres del sistema de fitxers seleccionat amb el qual intentar reparar el sistema. -<phrase arch="i386"> +<phrase arch="x86"> Per exemple, si heu de tornar a instal·lar el carregador d'arrencada GRUB al registre d'arrencada del primer disc dur, podríeu utilitzar l'ordre <userinput>grub-install '(hd0)'</userinput>. diff --git a/ca/preparing/bios-setup/i386.xml b/ca/preparing/bios-setup/i386.xml index 3327f3737..d54a2fd1a 100644 --- a/ca/preparing/bios-setup/i386.xml +++ b/ca/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"><title>Invocant el Menú de configuració de la BIOS</title> + <sect2 arch="x86" id="bios-setup"><title>Invocant el Menú de configuració de la BIOS</title> <para> @@ -104,7 +104,7 @@ de prova o programari gratuït. Proveu de buscar a </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Selecció del dispositiu d'arrencada</title> + <sect2 arch="x86" id="boot-dev-select"><title>Selecció del dispositiu d'arrencada</title> <para> @@ -231,7 +231,7 @@ desar els canvis al vostre ordinador. Sovint es tracta de </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Paràmetres de la BIOS miscel·lànies</title> <sect3 id="cd-settings"><title>Paràmetres del CD-ROM</title> diff --git a/ca/preparing/minimum-hardware-reqts.xml b/ca/preparing/minimum-hardware-reqts.xml index 97778d5dc..583a542ae 100644 --- a/ca/preparing/minimum-hardware-reqts.xml +++ b/ca/preparing/minimum-hardware-reqts.xml @@ -16,7 +16,7 @@ maquinari del que es recomana a la taula que trobareu a continuació. De tota manera, la majoria d'usuaris s'arrisquen a tenir frustracions si ignoren aquests suggeriments. -</para><para arch="i386"> +</para><para arch="x86"> Un Pentium 100 és el mínim recomanat per a un sistema d'escriptori, i un Pentium II-300 per a un servidor. diff --git a/ca/preparing/needed-info.xml b/ca/preparing/needed-info.xml index 4436611c1..aec9bd891 100644 --- a/ca/preparing/needed-info.xml +++ b/ca/preparing/needed-info.xml @@ -51,8 +51,8 @@ Sol contenir informació d'utilitat per a la configuració i ús del maquinari. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">COM ES FA sobre compatibilitat de maquinari amb el Linux (en anglès)</ulink> @@ -178,7 +178,7 @@ Els embalatges i les caixes del maquinari. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> La finestra Sistema del Tauler de Control del Windows. @@ -218,7 +218,7 @@ xarxa i el correu electrònic. </row> <row arch="not-s390"><entry>Quin ordre tenen al sistema.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Si són IDE o SCSI (en la majoria d'ordinadors, IDE).</entry> </row> <row arch="m68k"> @@ -300,19 +300,19 @@ el maquinari per al Linux millora constantment. Tanmateix, el Linux encara no treballa amb tants tipus diferents de maquinari com altres sistemes operatius. -</para><para arch="i386"> +</para><para arch="x86"> En particular, el Linux sol no poder treballar amb maquinari que requereix que s'execute una versió de Windows per funcionar. -</para><para arch="i386"> +</para><para arch="x86"> Tot i que es pot fer que algun maquinari específic per al Windows funcione amb el Linux, això suposa molt d'esforç. A més, els controladors de Linux per a maquinari específic per al Windows solen funcionar només amb un nucli específic de Linux. Per tant, poden esdevenir obsolets ràpidament. -</para><para arch="i386"> +</para><para arch="x86"> Els anomenats win-mòdems són el tipus més usual d'aquest maquinari. Tanmateix, hi ha també impressores i altres dispositius que també poden diff --git a/ca/preparing/non-debian-partitioning.xml b/ca/preparing/non-debian-partitioning.xml index 7f5369dcf..564e3c17d 100644 --- a/ca/preparing/non-debian-partitioning.xml +++ b/ca/preparing/non-debian-partitioning.xml @@ -20,7 +20,7 @@ cas, una màquina vol dir hoste VM o LPAR. Si ja teniu un sistema operatiu al vostre sistema -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -47,7 +47,7 @@ necessitareu una partició dedicada per l'arrel de Debian. Podeu trobar informació de la configuració de la vostra partició utilitzant una eina de particionament pel vostre sistema operatiu <phrase -arch="i386">, com l'fdisk o el PartitionMagic</phrase><phrase +arch="x86">, com l'fdisk o el PartitionMagic</phrase><phrase arch="powerpc">, com el Drive Setup, HD Toolkit, o les MacTools</phrase><phrase arch="m68k">, com l'HD SC Setup, HDToolBox, o l'SCSITool</phrase><phrase arch="s390">, com el VM diskmap</phrase>. Les eines de particionament @@ -97,7 +97,7 @@ els materials següents, ja que podeu trobar circumstàncies especials, com l'ordre de les particions existents dins el mapa de particions, que obliga a que particioneu abans de instal·lar de tota manera. -</para><para arch="i386"> +</para><para arch="x86"> Si teniu a la vostra màquina un sistema de fitxers FAT o bé NTFS, que utilitzen el DOS i el Windows, podeu esperar i utilitzar el programa de diff --git a/ca/preparing/nondeb-part/i386.xml b/ca/preparing/nondeb-part/i386.xml index a6cd399eb..eb3001a9b 100644 --- a/ca/preparing/nondeb-part/i386.xml +++ b/ca/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386"><title>Particionar des del DOS o el Windows</title> + <sect2 arch="x86"><title>Particionar des del DOS o el Windows</title> <para> Si esteu manipulant particions FAT o NTFS, és recomanable que o bé diff --git a/ca/preparing/pre-install-bios-setup.xml b/ca/preparing/pre-install-bios-setup.xml index cfa8c1dce..4aef49b7e 100644 --- a/ca/preparing/pre-install-bios-setup.xml +++ b/ca/preparing/pre-install-bios-setup.xml @@ -57,7 +57,7 @@ FIXME: cal més descripció sobre això. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> Les millors plaques base permeten l'ús de RAM de paritat, que us indicaran si aquesta té un error fins i tot en un únic bit. Tanmateix, no poden @@ -68,7 +68,7 @@ plaques base que permeten l'ús de mòduls de memòria de paritat i de paritat real; vegeu <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Si teniu RAM de paritat real i la placa base la pot fer servir, no dubteu a habilitar els ajusts de la BIOS que interrompen el funcionament de la placa @@ -76,7 +76,7 @@ quan es detecten errors de paritat de la memòria. </para> - <sect3 arch="i386"><title>El commutador turbo</title> + <sect3 arch="x86"><title>El commutador turbo</title> <para> Molts sistemes tenen un commutador <emphasis>turbo</emphasis> que controla @@ -90,7 +90,7 @@ maquinari) pot manipular el programari de control del commutador turbo. </para> </sect3> - <sect3 arch="i386"><title>Les CPU Cyrix i els errors de disquet</title> + <sect3 arch="x86"><title>Les CPU Cyrix i els errors de disquet</title> <para> Molts usuaris de CPU Cyrix han hagut de deshabilitar la memòria cau de llurs @@ -109,7 +109,7 @@ commutar del codi 16 bits al de 32. </para> </sect3> - <sect3 arch="i386"><title>Configuració dels perifèrics</title> + <sect3 arch="x86"><title>Configuració dels perifèrics</title> <para> Potser hàgeu de canviar alguns ajusts o ponts de les targetes dels perifèrics @@ -127,7 +127,7 @@ de RAM del sistema. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>Funcionalitats USB de la BIOS i teclats</title> <para> diff --git a/ca/using-d-i/modules/clock-setup.xml b/ca/using-d-i/modules/clock-setup.xml index 5f6b8b34b..1ab01a3e6 100644 --- a/ca/using-d-i/modules/clock-setup.xml +++ b/ca/using-d-i/modules/clock-setup.xml @@ -17,7 +17,7 @@ Al mode expert sempre podreu escollir si el rellotge és en UTC o no. <phrase arch="m68k;powerpc">El rellotge del Macintosh normalment està configurat en hora local. Si voleu un arranc dual, seleccioneu hora local en comptes de GMT.</phrase> -<phrase arch="i386">Els sistemes que (també) tenen Dos o Windows normalment +<phrase arch="x86">Els sistemes que (també) tenen Dos o Windows normalment estan configurats amb hora local. Si vole fer arranc dual, seleccioneu hora local en comptes de GMT.</phrase> diff --git a/ca/using-d-i/modules/i386/grub-installer.xml b/ca/using-d-i/modules/i386/grub-installer.xml index 6d2a375e9..98aa47945 100644 --- a/ca/using-d-i/modules/i386/grub-installer.xml +++ b/ca/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instal·lació del carregador d'arrencada <command>grub</command> en un disc dur</title> diff --git a/ca/using-d-i/modules/i386/lilo-installer.xml b/ca/using-d-i/modules/i386/lilo-installer.xml index c03bf88ae..8a858fd3d 100644 --- a/ca/using-d-i/modules/i386/lilo-installer.xml +++ b/ca/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instal·lació del carregador d'arrencada <command>LILO</command> a un disc dur</title> <para> diff --git a/cheatsheet.xml b/cheatsheet.xml index f5c152635..413a219e0 100644 --- a/cheatsheet.xml +++ b/cheatsheet.xml @@ -112,7 +112,7 @@ condition. For example, <code> -<para arch="i386"> +<para arch="x86"> A paragraph only interesting for i386 users </para> diff --git a/cs/administrivia/administrivia.xml b/cs/administrivia/administrivia.xml index 9d6f1f02b..d415278ae 100644 --- a/cs/administrivia/administrivia.xml +++ b/cs/administrivia/administrivia.xml @@ -118,7 +118,7 @@ a bohaté zdroje informací spravují. linkend="linux-upgrade"/>) je částečně odvozena z dokumentů na něž vlastní copyright Karsten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> Kapitola zabývající se instalací přes (<xref linkend="plip"/>) je založena na <ulink diff --git a/cs/appendix/chroot-install.xml b/cs/appendix/chroot-install.xml index 21f41551e..34c5a25f7 100644 --- a/cs/appendix/chroot-install.xml +++ b/cs/appendix/chroot-install.xml @@ -404,7 +404,7 @@ instalované jádro s novou kořenovou oblastí. Pamatujte, že debootstrap zavaděč neinstaluje, takže jej budete muset doinstalovat zvlášť (např. pomocí apt-get uvnitř chrootovaného prostředí). -</para><para arch="i386"> +</para><para arch="x86"> Návod k nastavení zavaděče prozradí příkaz <userinput>info grub</userinput> nebo <userinput>man lilo.conf</userinput>. Pokud si @@ -415,7 +415,7 @@ zkopírovat do nového systému, zde ho upravit a spustit <command>lilo</command> (použije konfigurační soubor systému, ze kterého jej spouštíte). -</para><para arch="i386"> +</para><para arch="x86"> Pro inspiraci nabízíme minimální <filename>/etc/lilo.conf</filename>: diff --git a/cs/appendix/plip.xml b/cs/appendix/plip.xml index 1e881f2d8..53f3b1aa5 100644 --- a/cs/appendix/plip.xml +++ b/cs/appendix/plip.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 29687 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Instalace &debian;u přes paralelní port (PLIP)</title> <para> diff --git a/cs/boot-installer/boot-installer.xml b/cs/boot-installer/boot-installer.xml index 037e3a1fc..29aa8c6b0 100644 --- a/cs/boot-installer/boot-installer.xml +++ b/cs/boot-installer/boot-installer.xml @@ -6,7 +6,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Zavedení instalátoru na &arch-title;</title> <para> </para> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/cs/boot-installer/i386.xml b/cs/boot-installer/i386.xml index 4fa4ae61d..09d455e49 100644 --- a/cs/boot-installer/i386.xml +++ b/cs/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 38231 --> - <sect2 arch="i386"><title>Zavedení z CD-ROM</title> + <sect2 arch="x86"><title>Zavedení z CD-ROM</title> &boot-installer-intro-cd.xml; @@ -73,7 +73,7 @@ Zavede jádro <quote>bf2.4</quote>. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Zavedení z DOSové oblasti</title> &boot-installer-intro-hd.xml; @@ -105,7 +105,7 @@ bf2.4. Příznakem tohoto problému je chybová hláška END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Zavedení z Linuxu programem <command>LILO</command> nebo <command>GRUB</command></title> <para> @@ -194,7 +194,7 @@ zavaděči žádný rozdíl. </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Zavedení z USB <quote>klíčenky</quote></title> <para> @@ -208,7 +208,7 @@ nebo prostě zmáčknout &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Zavedení z disket</title> <para> @@ -261,7 +261,7 @@ se její obsah natáhne do paměti a automaticky se spustí program </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Zavedení z TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Zavedení z TFTP</title> &boot-installer-intro-net.xml; @@ -307,7 +307,7 @@ zavádět z TFTP. </sect3> </sect2> - <sect2 arch="i386"><title>Zaváděcí výzva</title> + <sect2 arch="x86"><title>Zaváděcí výzva</title> <para> Při zavádění instalačního programu se objeví grafická obrazovka diff --git a/cs/boot-installer/intro-cd.xml b/cs/boot-installer/intro-cd.xml index 63c5c3bcc..649bf4727 100644 --- a/cs/boot-installer/intro-cd.xml +++ b/cs/boot-installer/intro-cd.xml @@ -5,7 +5,7 @@ Pro většinu lidí bude nejjednodušší použít sadu debianích CD. Pokud tuto sadu máte a váš počítač podporuje zavádění z CD, <phrase -arch="i386"> nastavte podle <xref linkend="boot-dev-select"/> zavádění +arch="x86"> nastavte podle <xref linkend="boot-dev-select"/> zavádění z CD,</phrase> vložte CD do mechaniky, restartujte počítač a přejděte k další kapitole. diff --git a/cs/boot-installer/parameters.xml b/cs/boot-installer/parameters.xml index 66fa7d9d6..708da9d2a 100644 --- a/cs/boot-installer/parameters.xml +++ b/cs/boot-installer/parameters.xml @@ -214,7 +214,7 @@ můžete framebuffer vypnout parametrem <userinput>debian-installer/framebuffer=false</userinput>, nebo krátce <userinput>fb=false</userinput>. -</para><para arch="i386"> +</para><para arch="x86"> K vypnutí framebufferu též můžete použít parametr <userinput>video=vga16:off</userinput>. Tyto problémy byly hlášeny na diff --git a/cs/boot-installer/trouble.xml b/cs/boot-installer/trouble.xml index c5f66af81..ca6415f90 100644 --- a/cs/boot-installer/trouble.xml +++ b/cs/boot-installer/trouble.xml @@ -64,7 +64,7 @@ Instalační systém totiž tuto volbou vyžaduje. </para><para> Často pomůže, pokud z počítače vyjmete přídavná zařízení a -znovu zkusíte zavést systém. <phrase arch="i386">Obzvláště +znovu zkusíte zavést systém. <phrase arch="x86">Obzvláště problematické mohou být interní modemy, zvukové karty a zařízení Plug-n-Play.</phrase> @@ -77,7 +77,7 @@ zaváděcím parametrem <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Běžné instalační problémy na &arch-title;</title> <para> @@ -150,7 +150,7 @@ Při zadávání rozsahů do instalačního programu vynechejte všechny </para> </sect3> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Systém zamrzne během nahrávání USB modulů</title> <para> diff --git a/cs/hardware/hardware-supported.xml b/cs/hardware/hardware-supported.xml index 310180a1c..db306e9e8 100644 --- a/cs/hardware/hardware-supported.xml +++ b/cs/hardware/hardware-supported.xml @@ -221,7 +221,7 @@ Také bude užitečné sledovat diskuzní list <sect2 id="gfx" arch="not-s390"><title>Grafické karty</title> -<para arch="i386"> +<para arch="x86"> Pro výstup v textovém režimu potřebujete grafickou kartu kompatibilní se standardem VGA, což dnes téměř každá grafická karta splňuje. @@ -259,7 +259,7 @@ url="&url-bcm91250a-hardware;">seznam kompatibilního hardwaru</ulink>. </para> </sect2> - <sect2 arch="i386" id="laptops"><title>Notebooky</title> + <sect2 arch="x86" id="laptops"><title>Notebooky</title> <para> diff --git a/cs/hardware/installation-media.xml b/cs/hardware/installation-media.xml index 91e676f7d..8d6e4b7a4 100644 --- a/cs/hardware/installation-media.xml +++ b/cs/hardware/installation-media.xml @@ -45,7 +45,7 @@ I v případě, že váš počítač neumí zavádět systém přímo z CD, mů CD-ROM využít po počátečním zavedení systému z jiného média, viz <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Využít můžete jak SCSI, tak IDE/ATAPI CD/DVD-ROM. Navíc jsou podporována i stará nestandardní rozhraní jako Mitsumi a Matsushita, @@ -55,7 +55,7 @@ Je rovněž nepravděpodobné, že by z těchto mechanik šlo zavést operační systém. Vyčerpávající informace o CD mechanikách v Linuxu najdete v <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink>. -</para><para arch="i386"> +</para><para arch="x86"> Podporovány jsou také externí USB CD-ROM mechaniky a některá FireWire zařízení pracující s ovladači ohci1394 a sbp2. @@ -206,7 +206,7 @@ návod o přípravě vlastního jádra (<xref linkend="kernel-baking"/>). Podpora co nejvíce zařízení na instalačních discích je žádoucí pro snadnou instalaci na libovolném hardwaru. -</para><para arch="i386"> +</para><para arch="x86"> Instalační systém Debianu obsahuje podporu pro disketové mechaniky, IDE disky, disketové mechaniky IDE, IDE disky na paralelním portu, @@ -214,7 +214,7 @@ IDE disky, disketové mechaniky IDE, IDE disky na paralelním portu, souborovými systémy FAT, FAT s rozšířením Win-32 (VFAT), NTFS a dalšími. -</para><para arch="i386"> +</para><para arch="x86"> Podporovány jsou také disky emulující AT rozhraní. Bývají označeny jako MFM, RLL, IDE nebo ATA. Podpora starých 8 bitových řadičů diff --git a/cs/hardware/network-cards.xml b/cs/hardware/network-cards.xml index 17663a014..5eb8525c6 100644 --- a/cs/hardware/network-cards.xml +++ b/cs/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Hardware pro připojení k síti</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -22,7 +22,7 @@ si sestavit vlastní jádro s příslušnou podporou a nahradit jím jádro instalační (viz <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> Z oblasti ISDN není v sadě zaváděcích médií zahrnuta podpora pro protokol D-channel německé sítě 1TR6 a karty Spellcaster BRI. diff --git a/cs/hardware/supported-peripherals.xml b/cs/hardware/supported-peripherals.xml index bbbc34855..7e777181c 100644 --- a/cs/hardware/supported-peripherals.xml +++ b/cs/hardware/supported-peripherals.xml @@ -9,12 +9,12 @@ V Linuxu můžete používat nejrůznější hardwarové vybavení jako myši, tiskárny, scannery, televizní karty a zařízení PCMCIA a USB. Většina z nich však není pro instalaci nutná. -<phrase arch="i386"> +<phrase arch="x86"> Některé USB klávesnice mohou vyžadovat speciální nastavení (viz <xref linkend="usb-keyboard-config"/>). </phrase> -</para><para arch="i386"> +</para><para arch="x86"> Znovu vás odkazujeme na <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>, kde zjistíte, zda pro @@ -57,7 +57,7 @@ je se systémem GNU/Linux plně kompatibilní. Bohužel je dnes těžké najít obchodníka prodávajícího vůbec nějaké novější modely &arch-title;. -</para><para arch="i386"> +</para><para arch="x86"> Budete-li nuceni zakoupit počítač se systémem Windows, přečtěte si pozorně jejich licenci, jestli můžete software odmítnout a zda vám @@ -105,7 +105,7 @@ představuje důležitou skupinu zákazníků. </sect2> - <sect2 arch="i386"><title>Zařízení určená speciálně pro Windows</title> + <sect2 arch="x86"><title>Zařízení určená speciálně pro Windows</title> <para> Znepokojivým trendem je rozšíření modemů a tiskáren určených pouze pro diff --git a/cs/hardware/supported/i386.xml b/cs/hardware/supported/i386.xml index 065a1a6fd..3d5ff9e6d 100644 --- a/cs/hardware/supported/i386.xml +++ b/cs/hardware/supported/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 11648 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Procesory, základní desky a grafické karty</title> <para> diff --git a/cs/howto/installation-howto.xml b/cs/howto/installation-howto.xml index 76bd8deb9..2caf0d5a7 100644 --- a/cs/howto/installation-howto.xml +++ b/cs/howto/installation-howto.xml @@ -83,7 +83,7 @@ vám bude stačit pouze první obraz.) Stáhněte si preferovaný obraz a vypalte jej na CD. -<phrase arch="i386"> +<phrase arch="x86"> Pro zavedení z CD možná budete muset změnit nastavení v BIOSu, viz <xref linkend="bios-setup"/>. @@ -166,7 +166,7 @@ z nichž některé jsou popsány v kapitole <xref linkend="boot-usb-files"/>. (Například návod, jak použít klíčenku menší než 256 MB.) -</para><para arch="i386"> +</para><para arch="x86"> Některé BIOSy umí zavádět přímo z USB, jiným je třeba pomoci. Hledejte menu, které povolí zavádění z <quote>removable drive</quote> nebo @@ -189,7 +189,7 @@ Další z možností, jak zavést &d-i; je pomocí sítě. Konkrétní postup závisí na vaší architektuře a síťovém prostředí. Obecně budete potřebovat soubory z adresáře <filename>netboot/</filename>. -</para><para arch="i386"> +</para><para arch="x86"> Nejjednodušší cesta je asi přes PXE. Do adresáře <filename>/var/lib/tftpboot</filename> (nebo jiného podle vašeho tftp @@ -213,7 +213,7 @@ kořenového adresáře pevného disku. Ujistěte se, že obraz CD má příponu <filename>.iso</filename>. Nyní již jen stačí zavést stažené jádro vmlinuz spolu s jeho ramdiskem initrd. -<phrase arch="i386"> +<phrase arch="x86"> Postup naleznete v kapitole <xref linkend="boot-initrd"/>. </phrase> @@ -228,7 +228,7 @@ Postup naleznete v kapitole <xref linkend="boot-initrd"/>. Po startu instalačního programu budete uvítáni úvodní obrazovkou. Nyní si můžete buď přečíst návod pro různé způsoby zavádění (viz <xref linkend="boot-parms"/>), nebo jednoduše stisknout &enterkey; a zavést -instalaci. <phrase arch="i386"> Chcete-li použít jádro řady 2.4, +instalaci. <phrase arch="x86"> Chcete-li použít jádro řady 2.4, napište na výzvě <prompt>boot:</prompt> <userinput>linux24</userinput>. <footnote> <para> Jádro 2.6 není k dispozici při zavádění z disket. </para> </footnote> </phrase> @@ -265,7 +265,7 @@ je doporučený způsob rozdělení disku pro začátečníky nebo pro lidi ve spěchu. Pokud nechcete využít této možnosti, vyberte z menu ruční nastavení tabulky oblastí. -</para><para arch="i386"> +</para><para arch="x86"> Máte-li stávající DOSové nebo windowsové oblasti, které chcete zachovat, buďte s automatickým dělením velmi opatrní. Pokud vyberete @@ -295,7 +295,7 @@ což může chvíli trvat. Následovat bude instalace jádra. Posledním krokem je instalace zavaděče. Pokud instalátor rozpozná na počítači jiné operační systémy, přidá je do zaváděcího menu. -<phrase arch="i386"> +<phrase arch="x86"> Implicitně se GRUB nainstaluje do hlavního zaváděcího záznamu prvního disku. K dispozici však máte i možnost instalovat zavaděč kamkoliv jinam. diff --git a/cs/install-methods/boot-drive-files.xml b/cs/install-methods/boot-drive-files.xml index e39fcce1c..1d2fe7902 100644 --- a/cs/install-methods/boot-drive-files.xml +++ b/cs/install-methods/boot-drive-files.xml @@ -15,7 +15,7 @@ Můžete tak dosáhnout <quote>čistě síťové</quote> instalace a vyhnout se vzrušující loterii při použití spousty nespolehlivých disket, potažmo neskladných CD. -</para><para arch="i386"> +</para><para arch="x86"> Instalační program nelze zavést ze souborů umístěných na oblasti NTFS. @@ -39,7 +39,7 @@ novější (NewWorld) nebo starší (OldWorld) Macintosh. </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Zavedení instalačního systému programem <command>LILO</command> nebo <command>GRUB</command></title> <para> diff --git a/cs/install-methods/boot-usb-files.xml b/cs/install-methods/boot-usb-files.xml index 5e3e1be31..09f292f0d 100644 --- a/cs/install-methods/boot-usb-files.xml +++ b/cs/install-methods/boot-usb-files.xml @@ -24,7 +24,7 @@ linkend="usb-copy-flexible"/>. <sect2 id="usb-copy-easy"> <title>Kopírování souborů — jednoduchá cesta</title> -<para arch="i386"> +<para arch="x86"> K dispozici máte soubor <filename>hd-media/boot.img.gz</filename>, který obsahuje všechny instalační soubory (včetně jádra), zavaděč @@ -56,9 +56,9 @@ přesvědčte, že pro svou klíčenku používáte správné jméno zařízení </para></warning><para> Na klíčence nyní bude jedna velká oblast typu <phrase -arch="i386">FAT16.</phrase> <phrase arch="powerpc">HFS.</phrase> +arch="x86">FAT16.</phrase> <phrase arch="powerpc">HFS.</phrase> Připojte ji (<userinput>mount <replaceable -arch="i386">/dev/sda</replaceable> <replaceable +arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>) a nakopírujte na ni ISO obraz malého instalačního CD (netinst). Na názvu obrazu nezáleží, ale musí končit příponou <filename>.iso</filename>. Nyní @@ -74,7 +74,7 @@ hotovo. Pokud máte rádi více pružnosti, nebo jen chcete zjistit <quote>co se děje za oponou</quote>, můžete použít nástedující metodu<phrase -arch="not-i386">.</phrase><phrase arch="i386">, ve které mj. ukážeme, +arch="not-x86">.</phrase><phrase arch="x86">, ve které mj. ukážeme, jak místo celého USB zařízení použít pouze první oblast.</phrase> </para> @@ -112,7 +112,7 @@ Jestliže jste hotovi, odpojte klíčenku (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Problémy se zaváděním z USB klíčenky</title> <warning><para> diff --git a/cs/install-methods/install-tftp.xml b/cs/install-methods/install-tftp.xml index d5903305b..c709bd50b 100644 --- a/cs/install-methods/install-tftp.xml +++ b/cs/install-methods/install-tftp.xml @@ -72,7 +72,7 @@ libovolné platformě, která jej implementuje. Ukázky v této kapitole se vztahují k operačním systémům SunOS 4.x, SunOS 5.x (neboli Solaris) a GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> Abyste mohli využít PXE (Pre-boot Execution Environment) metodu TFTP zavádění, musíte mít TFTP server s podporou @@ -161,7 +161,7 @@ RAMdisku. Pro zavádění ze sítě použijte soubor <filename>yaboot-netboot.conf</filename>, který v TFTP adresáři přejmenujete na <filename>yaboot.conf</filename>. -</para><para arch="i386"> +</para><para arch="x86"> Pro PXE zavádění by mělo být vše potřebné v souboru <filename>netboot/netboot.tar.gz</filename>. Tento archiv stačí diff --git a/cs/install-methods/tftp/dhcp.xml b/cs/install-methods/tftp/dhcp.xml index 59b262b13..e20916d94 100644 --- a/cs/install-methods/tftp/dhcp.xml +++ b/cs/install-methods/tftp/dhcp.xml @@ -53,7 +53,7 @@ restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Povolení PXE zavádění</title> <para> Další příklad souboru <filename>dhcp.conf</filename> tentokrát využívá diff --git a/cs/install-methods/usb-setup/i386.xml b/cs/install-methods/usb-setup/i386.xml index 6016e62fa..47fbef63b 100644 --- a/cs/install-methods/usb-setup/i386.xml +++ b/cs/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Rozdělení USB zařízení</title> <note><para> diff --git a/cs/partitioning/device-names.xml b/cs/partitioning/device-names.xml index d6b7d0c87..5a14d73db 100644 --- a/cs/partitioning/device-names.xml +++ b/cs/partitioning/device-names.xml @@ -66,12 +66,12 @@ pdisk (např. to co se v pdisku zobrazuje jako </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Prvnímu XT disku odpovídá <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Druhému XT disku odpovídá <filename>/dev/xdb</filename>. @@ -118,7 +118,7 @@ na disku <filename>sda</filename> by byly pojmenovány Máte-li v počítači dva SCSI řadiče, pořadí disků zjistíte ze zpráv, které Linux vypisuje při startu. -</para><para arch="i386"> +</para><para arch="x86"> Primární oddíly jsou v Linuxu reprezentovány názvem disku a číslem oddílu 1 až 4. Například <filename>/dev/hda1</filename> odpovídá diff --git a/cs/partitioning/partition-programs.xml b/cs/partitioning/partition-programs.xml index b047d8700..f77e80d42 100644 --- a/cs/partitioning/partition-programs.xml +++ b/cs/partitioning/partition-programs.xml @@ -18,7 +18,7 @@ Pro váš typ počítače jsou k dispozici: Doporučený nástroj, který umí kromě dělení disků i měnit velikost oblastí, vytvářet souborové -systémy <phrase arch="i386"> (v řeči Windows +systémy <phrase arch="x86"> (v řeči Windows <quote>formátovat</quote>) </phrase> a přiřadit je k přípojným bodům. </para></listitem> @@ -141,7 +141,7 @@ konzoli: <prompt>#</prompt> <userinput>chmod 660 hda21</userinput> </screen></informalexample> -<phrase arch="i386">Nezapomeňte označit zaváděcí oddíl jako +<phrase arch="x86">Nezapomeňte označit zaváděcí oddíl jako <quote>aktivní</quote> (bootable).</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/cs/partitioning/partition/i386.xml b/cs/partitioning/partition/i386.xml index c96152685..7551441c6 100644 --- a/cs/partitioning/partition/i386.xml +++ b/cs/partitioning/partition/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 35590 --> - <sect2 arch="i386"><title>Dělení disku na &arch-title;</title> + <sect2 arch="x86"><title>Dělení disku na &arch-title;</title> <para> BIOS osobních počítačů obvykle přidává další omezení na rozdělení diff --git a/cs/partitioning/partitioning.xml b/cs/partitioning/partitioning.xml index d24ed60e8..f91734e74 100644 --- a/cs/partitioning/partitioning.xml +++ b/cs/partitioning/partitioning.xml @@ -8,8 +8,8 @@ Menu <quote>Rozdělit pevný disk</quote> vám nabídne disky k rozdělení a spustí program, který provede záznam do tabulky oddílů. Musíte vytvořit alespoň jeden oddíl <quote>Linux native</quote> <phrase -arch="i386">(typ 83)</phrase> a nejspíš budete chtít vytvořit i oddíl -<quote>Linux swap</quote> <phrase arch="i386">(typ 82)</phrase> pro +arch="x86">(typ 83)</phrase> a nejspíš budete chtít vytvořit i oddíl +<quote>Linux swap</quote> <phrase arch="x86">(typ 82)</phrase> pro virtuální paměť. </para> diff --git a/cs/post-install/kernel-baking.xml b/cs/post-install/kernel-baking.xml index 3d6aab8f3..83fe18495 100644 --- a/cs/post-install/kernel-baking.xml +++ b/cs/post-install/kernel-baking.xml @@ -167,7 +167,7 @@ root napište </phrase> <replaceable>podarchitektura</replaceable> je volitelné upřesnění -architektury, <phrase arch="i386"> např. <quote>i586</quote>, +architektury, <phrase arch="x86"> např. <quote>i586</quote>, </phrase> které jste zadali při konfiguraci jádra. <userinput>dpkg -i</userinput> nainstaluje jádro spolu s doprovodnými soubory. Jedná se třeba o soubory diff --git a/cs/post-install/reactivating-win.xml b/cs/post-install/reactivating-win.xml index 2912dd405..9608a4615 100644 --- a/cs/post-install/reactivating-win.xml +++ b/cs/post-install/reactivating-win.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reaktivace DOS a Windows</title> <para> diff --git a/cs/post-install/rescue.xml b/cs/post-install/rescue.xml index 0a44c19fc..82b67d12d 100644 --- a/cs/post-install/rescue.xml +++ b/cs/post-install/rescue.xml @@ -41,7 +41,7 @@ Pokud to bude jen trochu možné, instalátor vám nyní nabídne příkazový řádek ve vybraném souborovém systému, který teď můžete použít pro provedení nezbytných záchranných prací. -<phrase arch="i386"> +<phrase arch="x86"> Například potřebujete-li přeinstalovat zavaděč GRUB do hlavního zaváděcího záznamu (MBR) prvního disku, můžete použít příkaz <userinput>grub-install '(hd0)'</userinput>. diff --git a/cs/preparing/bios-setup/i386.xml b/cs/preparing/bios-setup/i386.xml index fc4d3c84a..968cc7749 100644 --- a/cs/preparing/bios-setup/i386.xml +++ b/cs/preparing/bios-setup/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"> + <sect2 arch="x86" id="bios-setup"> <title>Vyvolání menu systému BIOS</title> <para> @@ -102,7 +102,7 @@ nějaký najít na <ulink url="&url-simtel;"></ulink>. </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"> + <sect2 arch="x86" id="boot-dev-select"> <title>Výběr zaváděcího zařízení</title> <para> @@ -212,7 +212,7 @@ Uložte změny. (Obvykle musíte stisknout klávesu <keycap>F10</keycap>.) </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Různá nastavení BIOSu</title> <sect3 id="cd-settings"><title>Nastavení CD-ROM</title> diff --git a/cs/preparing/minimum-hardware-reqts.xml b/cs/preparing/minimum-hardware-reqts.xml index f8b877ec4..f82bbab27 100644 --- a/cs/preparing/minimum-hardware-reqts.xml +++ b/cs/preparing/minimum-hardware-reqts.xml @@ -14,7 +14,7 @@ Skutečné minimální požadavky mohou být nižší než uvádí tabulka, ale většina uživatelů by asi nebyla spokojena s rychlostí systému. Vždy záleží na konkrétních požadavcích a možnostech. -</para><para arch="i386"> +</para><para arch="x86"> Pro pracovní stanice je minimální doporučený procesor Pentium 100 a pro server Pentium II-300. diff --git a/cs/preparing/needed-info.xml b/cs/preparing/needed-info.xml index 346b1ce4a..f574483a0 100644 --- a/cs/preparing/needed-info.xml +++ b/cs/preparing/needed-info.xml @@ -52,8 +52,8 @@ různého hardwaru. </para> <!-- Arch list needed for proper xml --> -<itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> +<itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -169,7 +169,7 @@ Z krabic, ve kterých byly části hardware zabaleny. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Z Ovládacích panelů systému Windows. @@ -206,7 +206,7 @@ mohou pomoci při nastavení sítě a elektronické pošty. <entry>Počet.</entry> </row><row arch="not-s390"> <entry>Jejich pořadí v systému.</entry> -</row><row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +</row><row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Typ IDE nebo SCSI (většina počítačů má disky IDE)</entry> </row><row arch="m68k"> <entry>Typ IDE nebo SCSI (většina počítačů m68k má disky SCSI)</entry> @@ -299,12 +299,12 @@ Mnoho značkových výrobků pracuje pod Linuxem bez problémů a podpora hardwaru pro Linux se zlepšuje každým dnem. Přes to všechno Linux nepodporuje tolik typů hardwaru jako některé jiné operační systémy. -</para><para arch="i386"> +</para><para arch="x86"> Pod Linuxem obvykle nepoběží hardware, který ke své činnosti vyžaduje některou verzi Windows. -</para><para arch="i386"> +</para><para arch="x86"> Přestože některý Windows-specifický hardware můžete pod Linuxem rozchodit, obvykle to vyžaduje spoustu další práce. Navíc linuxové @@ -312,7 +312,7 @@ ovladače pro windowsový hardware bývají svázány s konkrétním jádrem a tudíž mohou rychle zastarat, respektive vás nutí zůstat u staršího jádra (které třeba obsahuje bezpečnostní chybu). -</para><para arch="i386"> +</para><para arch="x86"> Nejrozšířenějšími ukázkami tohoto hardwaru jsou takzvané win-modemy. Windows-specifické však mohou být i tiskárny a jiná diff --git a/cs/preparing/non-debian-partitioning.xml b/cs/preparing/non-debian-partitioning.xml index 6222182bb..f4fa460e7 100644 --- a/cs/preparing/non-debian-partitioning.xml +++ b/cs/preparing/non-debian-partitioning.xml @@ -21,7 +21,7 @@ znamená <quote>LPAR</quote> nebo <quote>VM guest</quote>. Jestliže už na počítači máte nějaký operační systém -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -48,7 +48,7 @@ oblast pro kořenový souborový systém. </para><para> Informace o aktuálním rozdělení disku můžete získat dělicím programem -svého stávajícího operačního systému<phrase arch="i386">, jako je +svého stávajícího operačního systému<phrase arch="x86">, jako je fdisk nebo PartitionMagic</phrase><phrase arch="powerpc">, jako je Drive Setup, HD Toolkit nebo MacTools</phrase><phrase arch="m68k">, jako je HD SC Setup, HDToolBox nebo SCSITool</phrase><phrase @@ -93,7 +93,7 @@ kapitolu přečíst, protože někdy mohou nastat okolnosti, které vás k rozdělení disku před instalací stejně donutí (například vynucené pořadí některých oblastí). -</para><para arch="i386"> +</para><para arch="x86"> S rozdělováním můžete rovněž počkat, pokud máte ve svém počítači oblast(i) se souborovým systémem FAT nebo NTFS. Tyto oblasti můžete diff --git a/cs/preparing/nondeb-part/i386.xml b/cs/preparing/nondeb-part/i386.xml index c7557fbe1..bc29fd020 100644 --- a/cs/preparing/nondeb-part/i386.xml +++ b/cs/preparing/nondeb-part/i386.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 36732 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Dělení disku v systémech DOS a Windows</title> <para> diff --git a/cs/preparing/pre-install-bios-setup.xml b/cs/preparing/pre-install-bios-setup.xml index 8c01d6c89..dc7809367 100644 --- a/cs/preparing/pre-install-bios-setup.xml +++ b/cs/preparing/pre-install-bios-setup.xml @@ -56,7 +56,7 @@ mem souboru zavaděče. FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> Kvalitní základní desky podporují paritní RAM a jsou schopny upozornit na jednobitovou chybu v paměti. Bohužel nedokáží chybná data opravit a @@ -66,7 +66,7 @@ důvodu jsou nejlepší systémy vybaveny základními deskami podporujícími paritní a pravou paritní paměť. Více k tomuto tématu <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Pokud máte skutečně paritní paměťové moduly a základní desku, která je podporuje, povolte v systému BIOS všechna nastavení, která při chybě @@ -74,7 +74,7 @@ parity způsobí přerušení. </para> - <sect3 arch="i386"><title>Přepínač TURBO</title> + <sect3 arch="x86"><title>Přepínač TURBO</title> <para> Systémy s volbou rychlosti běhu CPU nastavte na vyšší rychlost, a @@ -87,7 +87,7 @@ trvala celé hodiny). </para> </sect3> - <sect3 arch="i386"><title>Procesory Cyrix a chyby při čtení disket</title> + <sect3 arch="x86"><title>Procesory Cyrix a chyby při čtení disket</title> <para> Mnozí majitelé procesorů Cyrix byli donuceni po dobu instalace Linuxu @@ -105,7 +105,7 @@ zjednat nápravu. Pro zvědavé: Máme podezření, že po přechodu z 16 do </para> </sect3> - <sect3 arch="i386"><title>Nastavení přídavných zařízení</title> + <sect3 arch="x86"><title>Nastavení přídavných zařízení</title> <para> Mimo nastavení v systému BIOS je někdy třeba změnit konfiguraci @@ -123,7 +123,7 @@ do 1 MB) nebo alespoň 1 MB nad celkovou pamětí vašeho systému. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>BIOS a USB klávesnice</title> <para> diff --git a/cs/using-d-i/modules/clock-setup.xml b/cs/using-d-i/modules/clock-setup.xml index 83cec09b1..5c07bcd46 100644 --- a/cs/using-d-i/modules/clock-setup.xml +++ b/cs/using-d-i/modules/clock-setup.xml @@ -16,7 +16,7 @@ se otázka zobrazí vždy. Hardwarové hodiny v Macintoshích jsou standardně nastaveny na místní čas. Jestliže budete mít duální zavádění, tak možnost UTC zamítněte. -</phrase><phrase arch="i386"> +</phrase><phrase arch="x86"> Jestli budou na počítači i Windows nebo DOS, možnost hardwarových hodin v UTC zamítněte, protože zmíněné systémy s touto možností diff --git a/cs/using-d-i/modules/i386/grub-installer.xml b/cs/using-d-i/modules/i386/grub-installer.xml index 9b58596de..436314217 100644 --- a/cs/using-d-i/modules/i386/grub-installer.xml +++ b/cs/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalovat zavaděč <command>Grub</command> na pevný disk</title> <para> diff --git a/cs/using-d-i/modules/i386/lilo-installer.xml b/cs/using-d-i/modules/i386/lilo-installer.xml index a834130a6..c050d1bb4 100644 --- a/cs/using-d-i/modules/i386/lilo-installer.xml +++ b/cs/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalovat zavaděč <command>LILO</command> na pevný disk</title> <para> diff --git a/da/appendix/chroot-install.xml b/da/appendix/chroot-install.xml index ba3835a43..104e156ec 100644 --- a/da/appendix/chroot-install.xml +++ b/da/appendix/chroot-install.xml @@ -436,7 +436,7 @@ the installed kernel with your new root partition. Note that debootstrap does not install a boot loader, though you can use apt-get inside your Debian chroot to do so. -</para><para arch="i386"> +</para><para arch="x86"> Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the @@ -447,7 +447,7 @@ add an entry for the Debian install to your existing grub edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from). -</para><para arch="i386"> +</para><para arch="x86"> Here is a basic <filename>/etc/lilo.conf</filename> as an example: diff --git a/da/boot-installer/i386.xml b/da/boot-installer/i386.xml index b2c62bea7..4aafec5c2 100644 --- a/da/boot-installer/i386.xml +++ b/da/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22664 untranslated --> - <sect2 arch="i386"><title>Booting from a CD-ROM</title> + <sect2 arch="x86"><title>Booting from a CD-ROM</title> &boot-installer-intro-cd.xml; @@ -74,7 +74,7 @@ Boots the `bf2.4' flavor. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -107,7 +107,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Booting from linux using <command>LILO</command> or <command>GRUB</command></title> @@ -195,7 +195,7 @@ or <command>LILO</command>. </para> </sect2> - <sect2 arch="i386" id="usb-boot"> + <sect2 arch="x86" id="usb-boot"> <title>Booting from USB memory stick</title> <para> @@ -218,7 +218,7 @@ When it asks for the root floppy, simply press &enterkey;. You should see </para> </sect2> - <sect2 arch="i386" id="floppy-boot"> + <sect2 arch="x86" id="floppy-boot"> <title>Booting from Floppies</title> <para> @@ -278,7 +278,7 @@ contents are loaded into memory. The installer program </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title> &boot-installer-intro-net.xml; @@ -324,7 +324,7 @@ provides bootdiskettes and even bootroms that do a TFTPboot. </sect3> </sect2> - <sect2 arch="i386"><title>i386 Boot Parameters</title> + <sect2 arch="x86"><title>i386 Boot Parameters</title> <para> When the installer boots, you will be presented with the boot prompt, @@ -382,7 +382,7 @@ console features. See <xref linkend="boot-parms"/> for details. </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>System freeze during the PCMCIA configuration phase</title> <para> @@ -411,7 +411,7 @@ installer. </para> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>System freeze while loading the USB modules</title> <para> diff --git a/da/boot-installer/intro-cd.xml b/da/boot-installer/intro-cd.xml index 890f52072..9f603991c 100644 --- a/da/boot-installer/intro-cd.xml +++ b/da/boot-installer/intro-cd.xml @@ -6,7 +6,7 @@ The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply -<phrase arch="i386"> +<phrase arch="x86"> configure your system for booting off a CD as described in <xref linkend="boot-dev-select"/>, </phrase> diff --git a/da/boot-installer/parameters.xml b/da/boot-installer/parameters.xml index 1677efd2a..ba48ef64c 100644 --- a/da/boot-installer/parameters.xml +++ b/da/boot-installer/parameters.xml @@ -208,7 +208,7 @@ you can disable the feature by the parameter symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="i386"> +</para><para arch="x86"> The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell diff --git a/da/boot-installer/trouble.xml b/da/boot-installer/trouble.xml index feed8da58..18067e318 100644 --- a/da/boot-installer/trouble.xml +++ b/da/boot-installer/trouble.xml @@ -67,7 +67,7 @@ your kernel. The installer requires </para><para> Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> </para><para> diff --git a/da/boot-new/modules/ppp.xml b/da/boot-new/modules/ppp.xml index a707fd2b1..868963085 100644 --- a/da/boot-new/modules/ppp.xml +++ b/da/boot-new/modules/ppp.xml @@ -44,7 +44,7 @@ Edit <filename>/etc/ppp/peers/provider</filename> and replace <userinput>/dev/ttyS<replaceable>#</replaceable></userinput> where <replaceable>#</replaceable> stands for the number of your serial port. In Linux, serial ports are counted from 0; your first serial -port <phrase arch="i386">(i.e., <userinput>COM1</userinput>)</phrase> +port <phrase arch="x86">(i.e., <userinput>COM1</userinput>)</phrase> is <filename>/dev/ttyS0</filename> under Linux. <phrase arch="powerpc;m68k">On Macintoshes with serial ports, the diff --git a/da/boot-new/modules/timezone.xml b/da/boot-new/modules/timezone.xml index e7edc7917..e0c8ee4e7 100644 --- a/da/boot-new/modules/timezone.xml +++ b/da/boot-new/modules/timezone.xml @@ -13,7 +13,7 @@ may help you decide on the correct option. <phrase arch="m68k;powerpc">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> -<phrase arch="i386">Systems that (also) run Dos or Windows are normally +<phrase arch="x86">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> diff --git a/da/hardware/hardware-supported.xml b/da/hardware/hardware-supported.xml index b9e6c2417..6c3602fc5 100644 --- a/da/hardware/hardware-supported.xml +++ b/da/hardware/hardware-supported.xml @@ -218,7 +218,7 @@ as well. <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title> -<para arch="i386"> +<para arch="x86"> You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with @@ -256,7 +256,7 @@ the BCM1250 is available. </sect2> - <sect2 arch="i386" id="laptops"><title>Laptops</title> + <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> Laptops are also supported. Laptops are often specialized or contain diff --git a/da/hardware/installation-media.xml b/da/hardware/installation-media.xml index 88ff2c209..05aca1ccd 100644 --- a/da/hardware/installation-media.xml +++ b/da/hardware/installation-media.xml @@ -50,7 +50,7 @@ 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 <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the @@ -60,7 +60,7 @@ them to work, and booting off these non-standard interfaces is unlikely. The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux. -</para><para arch="i386"> +</para><para arch="x86"> USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers. @@ -197,14 +197,14 @@ 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. -</para><para arch="i386"> +</para><para arch="x86"> Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The file systems supported include FAT, Win-32 FAT extensions (VFAT), and NTFS, among others. -</para><para arch="i386"> +</para><para arch="x86"> The disk interfaces that emulate the ``AT'' hard disk interface which are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit diff --git a/da/hardware/network-cards.xml b/da/hardware/network-cards.xml index 4b7bd9f31..c98b29234 100644 --- a/da/hardware/network-cards.xml +++ b/da/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -24,7 +24,7 @@ cards and protocols. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the diff --git a/da/hardware/supported-peripherals.xml b/da/hardware/supported-peripherals.xml index bedc8ed93..35fe2ccb6 100644 --- a/da/hardware/supported-peripherals.xml +++ b/da/hardware/supported-peripherals.xml @@ -9,13 +9,13 @@ Linux 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. -</para><para arch="i386"> +</para><para arch="x86"> USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Again, see the <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -56,7 +56,7 @@ be sure that the hardware is well-supported by GNU/Linux. Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all. -</para><para arch="i386"> +</para><para arch="x86"> 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 @@ -105,7 +105,7 @@ is an important market. </sect2> - <sect2 arch="i386"><title>Windows-specific Hardware</title> + <sect2 arch="x86"><title>Windows-specific Hardware</title> <para> A disturbing trend is the proliferation of Windows-specific modems and diff --git a/da/hardware/supported/i386.xml b/da/hardware/supported/i386.xml index 725a5169b..6159a9fc9 100644 --- a/da/hardware/supported/i386.xml +++ b/da/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title> + <sect2 arch="x86"><title>CPU, Main Boards, and Video Support</title> <para> Complete information concerning supported peripherals can be found at diff --git a/da/howto/installation-howto.xml b/da/howto/installation-howto.xml index 41c2c648f..fc7612447 100644 --- a/da/howto/installation-howto.xml +++ b/da/howto/installation-howto.xml @@ -79,7 +79,7 @@ only need the first CD of the set. </para><para> Download whichever type you prefer and burn it to a CD. -<phrase arch="i386">To boot the CD, you may need to change your BIOS +<phrase arch="x86">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See @@ -151,7 +151,7 @@ There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a "removable drive" or even a "USB-ZIP" to @@ -170,7 +170,7 @@ It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into @@ -193,7 +193,7 @@ existing hard disk, which can have a different OS on it. Download and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in ".iso". Now it's just a matter of booting linux with the initrd. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> explains one way to do it. </phrase> @@ -208,7 +208,7 @@ booting linux with the initrd. Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> If you want a 2.6 kernel, type <userinput>linux26</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> @@ -270,7 +270,7 @@ which can take a while. That is followed by installing a kernel. The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. -<phrase arch="i386">By default GRUB will be installed to the master boot +<phrase arch="x86">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase> diff --git a/da/install-methods/automatic-install.xml b/da/install-methods/automatic-install.xml index 32aea456c..6ec9c2dfc 100644 --- a/da/install-methods/automatic-install.xml +++ b/da/install-methods/automatic-install.xml @@ -76,7 +76,7 @@ ISO image to include your preconfiguraton file. See the manual page for mkisofs for details. Alternatively, put the preseed file on a floppy, and use preseed/file=/floppy/preseed.cfg -</para><para arch="i386"> +</para><para arch="x86"> If you'll be booting from a USB memory stick, then you can simply copy your preconfiguration file onto the memory stick's filesystem, and edit the diff --git a/da/install-methods/boot-drive-files.xml b/da/install-methods/boot-drive-files.xml index 438b17072..2aba36d30 100644 --- a/da/install-methods/boot-drive-files.xml +++ b/da/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks. -</para><para arch="i386"> +</para><para arch="x86"> The installer cannot boot from files on an NTFS file system. @@ -39,7 +39,7 @@ model. </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Hard disk installer booting using <command>LILO</command> or <command>GRUB</command></title> <para> diff --git a/da/install-methods/install-tftp.xml b/da/install-methods/install-tftp.xml index d132f014b..46b6037a8 100644 --- a/da/install-methods/install-tftp.xml +++ b/da/install-methods/install-tftp.xml @@ -107,7 +107,7 @@ reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. -</para><note arch="i386"><para> +</para><note arch="x86"><para> To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> @@ -165,7 +165,7 @@ images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory. -</para><para arch="i386"> +</para><para arch="x86"> For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this diff --git a/da/install-methods/tftp/dhcp.xml b/da/install-methods/tftp/dhcp.xml index 42231a63f..6132f3ef7 100644 --- a/da/install-methods/tftp/dhcp.xml +++ b/da/install-methods/tftp/dhcp.xml @@ -55,7 +55,7 @@ restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Enabling PXE Booting in the DHCP configuration</title> <para> Here is another example for a <filename>dhcp.conf</filename> using the diff --git a/da/partitioning/device-names.xml b/da/partitioning/device-names.xml index 354845a93..94206995a 100644 --- a/da/partitioning/device-names.xml +++ b/da/partitioning/device-names.xml @@ -67,12 +67,12 @@ up as <filename>/dev/hda</filename> in Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The first XT disk is named <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The second XT disk is named <filename>/dev/xdb</filename>. @@ -125,7 +125,7 @@ the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities. -</para><para arch="i386"> +</para><para arch="x86"> Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the diff --git a/da/partitioning/partition-programs.xml b/da/partitioning/partition-programs.xml index e346349e2..271ef4604 100644 --- a/da/partitioning/partition-programs.xml +++ b/da/partitioning/partition-programs.xml @@ -19,7 +19,7 @@ your architecture. <listitem><para> Recommended partitioning tool in Debian. This swiss army knife can -also create filesystems <phrase arch="i386"> (<quote>format</quote> in +also create filesystems <phrase arch="x86"> (<quote>format</quote> in Windows speak) </phrase> and assign them to the mountpoints. </para></listitem> @@ -149,7 +149,7 @@ chgrp disk hda21 chmod 660 hda21 </screen></informalexample> -</para><para arch="i386"> +</para><para arch="x86"> Remember to mark your boot partition as ``Bootable''. diff --git a/da/partitioning/partition/i386.xml b/da/partitioning/partition/i386.xml index 1b2794b45..26c3e4296 100644 --- a/da/partitioning/partition/i386.xml +++ b/da/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>Partitioning for &arch-title;</title> + <sect2 arch="x86"><title>Partitioning for &arch-title;</title> <para> The PC BIOS generally adds additional constraints for disk diff --git a/da/post-install/kernel-baking.xml b/da/post-install/kernel-baking.xml index 4a164343d..8b808858f 100644 --- a/da/post-install/kernel-baking.xml +++ b/da/post-install/kernel-baking.xml @@ -23,7 +23,7 @@ APM or SMP </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The compact and idepci flavors don't come with sound. Although the vanilla kernel does, it might not work for other reasons. @@ -174,7 +174,7 @@ like any package. As root, do <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as ``i586'', </phrase> +<phrase arch="x86"> such as ``i586'', </phrase> depending on what kernel options you set. <userinput>dpkg -i kernel-image...</userinput> will install the kernel, along with some other nice supporting files. For instance, diff --git a/da/post-install/reactivating-win.xml b/da/post-install/reactivating-win.xml index ce176c254..52da42e89 100644 --- a/da/post-install/reactivating-win.xml +++ b/da/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 16560 untranslated --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivating DOS and Windows</title> <para> diff --git a/da/preparing/bios-setup/i386.xml b/da/preparing/bios-setup/i386.xml index 46df78793..119ec2fa9 100644 --- a/da/preparing/bios-setup/i386.xml +++ b/da/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 18674 untranslated --> - <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> + <sect2 arch="x86" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> <para> @@ -101,7 +101,7 @@ try using a shareware/freeware program. Try looking in </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title> + <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title> <para> @@ -229,7 +229,7 @@ save the changes on your computer. Often, you must press </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Miscellaneous BIOS Settings</title> <sect3 id="cd-settings"><title>CD-ROM Settings</title> diff --git a/da/preparing/minimum-hardware-reqts.xml b/da/preparing/minimum-hardware-reqts.xml index 62f2cf987..5a3641a4c 100644 --- a/da/preparing/minimum-hardware-reqts.xml +++ b/da/preparing/minimum-hardware-reqts.xml @@ -15,7 +15,7 @@ Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions. -</para><para arch="i386"> +</para><para arch="x86"> A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server. diff --git a/da/preparing/needed-info.xml b/da/preparing/needed-info.xml index a794642ed..d2a59b07a 100644 --- a/da/preparing/needed-info.xml +++ b/da/preparing/needed-info.xml @@ -44,7 +44,7 @@ Often contains useful information on configuring or using your hardware. </para> <itemizedlist> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -166,7 +166,7 @@ The cases and boxes for each piece of hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The System window in the Windows Control Panel. @@ -283,19 +283,19 @@ Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems. -</para><para arch="i386"> +</para><para arch="x86"> In particular, Linux usually cannot run hardware that requires a running version of Windows to work. -</para><para arch="i386"> +</para><para arch="x86"> Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete. -</para><para arch="i386"> +</para><para arch="x86"> So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific. diff --git a/da/preparing/non-debian-partitioning.xml b/da/preparing/non-debian-partitioning.xml index ed5529957..c09859b73 100644 --- a/da/preparing/non-debian-partitioning.xml +++ b/da/preparing/non-debian-partitioning.xml @@ -20,7 +20,7 @@ an LPAR or VM guest in this case. If you already have an operating system on your system -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -48,7 +48,7 @@ root. You can find information about your current partition setup by using a partitioning tool for your current operating system -<phrase arch="i386">, such as fdisk or PartitionMagic</phrase> +<phrase arch="x86">, such as fdisk or PartitionMagic</phrase> <phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase> @@ -103,7 +103,7 @@ special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway. -</para><para arch="i386"> +</para><para arch="x86"> If your machine has a FAT filesystem, as used by DOS and older versions of Windows, you can wait and use Debian installer's partitioning program to diff --git a/da/preparing/nondeb-part/i386.xml b/da/preparing/nondeb-part/i386.xml index 389121384..a6d1f1be7 100644 --- a/da/preparing/nondeb-part/i386.xml +++ b/da/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 22664 untranslated --> - <sect2 arch="i386"><title>Partitioning From DOS or Windows</title> + <sect2 arch="x86"><title>Partitioning From DOS or Windows</title> <para> If you are manipulating existing FAT or NTFS partitions, it is diff --git a/da/preparing/pre-install-bios-setup.xml b/da/preparing/pre-install-bios-setup.xml index c386a4eb6..049d336bb 100644 --- a/da/preparing/pre-install-bios-setup.xml +++ b/da/preparing/pre-install-bios-setup.xml @@ -54,7 +54,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they @@ -65,7 +65,7 @@ in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to @@ -73,7 +73,7 @@ interrupt on memory parity errors. </para> - <sect3 arch="i386"><title>The Turbo Switch</title> + <sect3 arch="x86"><title>The Turbo Switch</title> <para> Many systems have a <emphasis>turbo</emphasis> switch that controls @@ -87,7 +87,7 @@ accidentally touch the software control for the turbo switch. </para> </sect3> - <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title> + <sect3 arch="x86"><title>Cyrix CPUs and Floppy Disk Errors</title> <para> Many users of Cyrix CPUs have had to disable the cache in their @@ -106,7 +106,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code. </para> </sect3> - <sect3 arch="i386"><title>Peripheral Hardware Settings</title> + <sect3 arch="x86"><title>Peripheral Hardware Settings</title> <para> You may have to change some settings or jumpers on your computer's @@ -124,7 +124,7 @@ amount of RAM in your system. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"><title>USB keyboards</title> + <sect3 arch="x86" id="usb-keyboard-config"><title>USB keyboards</title> <para> If you have no AT-style keyboard and only a USB model, you may need diff --git a/da/using-d-i/modules/i386/grub-installer.xml b/da/using-d-i/modules/i386/grub-installer.xml index 64e1e7ffb..fdb192e37 100644 --- a/da/using-d-i/modules/i386/grub-installer.xml +++ b/da/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 untranslated --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>Grub</command> Boot Loader on a Hard Disk</title> <para> diff --git a/da/using-d-i/modules/i386/lilo-installer.xml b/da/using-d-i/modules/i386/lilo-installer.xml index ba7a5b17e..0f38f727d 100644 --- a/da/using-d-i/modules/i386/lilo-installer.xml +++ b/da/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22664 untranslated --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>LILO</command> Boot Loader on a Hard Disk</title> <para> diff --git a/de/administrivia/administrivia.xml b/de/administrivia/administrivia.xml index 14f9359fe..d1f1f61c7 100644 --- a/de/administrivia/administrivia.xml +++ b/de/administrivia/administrivia.xml @@ -126,7 +126,7 @@ Der Abschnitt <xref linkend="linux-upgrade"/> dieses Handbuchs stammt teilweise aus Dokumenten, die unter dem Copyright von Karsten M. Self stehen. -</para><para arch="i386"> +</para><para arch="x86"> Der Abschnitt <xref linkend="plip"/> basierte auf dem <ulink url="&url-plip-install-howto;">PLIP-Install-HowTo</ulink> diff --git a/de/appendix/chroot-install.xml b/de/appendix/chroot-install.xml index a2b59b961..7f74d1c13 100644 --- a/de/appendix/chroot-install.xml +++ b/de/appendix/chroot-install.xml @@ -416,7 +416,7 @@ Bedenken Sie, dass debootstrap keinen Bootloader installiert, allerdings können Sie apt-get in Ihrer Debian-chroot-Umgebung benutzen, um dies zu erledigen. -</para><para arch="i386"> +</para><para arch="x86"> Lesen Sie <userinput>info grub</userinput> oder <userinput>man lilo.conf</userinput>, um Informationen über die Einrichtung des Bootloaders @@ -428,7 +428,7 @@ neues Debian-System kopieren und dort bearbeiten. Rufen Sie danach <command>lilo (bedenken Sie: lilo nutzt die <filename>lilo.conf</filename> relativ zum System, von dem aus Sie es aufrufen). -</para><para arch="i386"> +</para><para arch="x86"> Hier ein grundsätzliches Beispiel einer <filename>/etc/lilo.conf</filename>: diff --git a/de/appendix/plip.xml b/de/appendix/plip.xml index dc4643d39..32f2d1b39 100644 --- a/de/appendix/plip.xml +++ b/de/appendix/plip.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 29687 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>&debian; über Parallel Line IP (PLIP) installieren</title> <para> diff --git a/de/boot-installer/boot-installer.xml b/de/boot-installer/boot-installer.xml index 2c02028c7..de878ca14 100644 --- a/de/boot-installer/boot-installer.xml +++ b/de/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when all archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Starten des Installers auf &arch-title;-Systemen</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/de/boot-installer/i386.xml b/de/boot-installer/i386.xml index cc0d742ae..b00a23d5c 100644 --- a/de/boot-installer/i386.xml +++ b/de/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 38231 --> - <sect2 arch="i386"><title>Von einer CD-ROM starten</title> + <sect2 arch="x86"><title>Von einer CD-ROM starten</title> &boot-installer-intro-cd.xml; @@ -79,7 +79,7 @@ Boots the <quote>bf2.4</quote> flavor. <!-- in the german translation. Holger Wansing --> <!-- - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -110,7 +110,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Von Linux aus booten mittels <command>lilo</command> oder <command>grub</command></title> @@ -199,7 +199,7 @@ und <command>lilo</command>. </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Von einem USB-Memory-Stick booten</title> <para> Wir nehmen an, Sie haben alles wie unter @@ -212,7 +212,7 @@ Boot-Parameter eintippen oder einfach &enterkey; drücken. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Von Floppy-Disketten booten</title> <para> @@ -275,7 +275,7 @@ startet automatisch. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Mit TFTP booten</title> + <sect2 arch="x86" id="boot-tftp"><title>Mit TFTP booten</title> &boot-installer-intro-net.xml; @@ -321,7 +321,7 @@ bietet Bootdisketten und sogar BootROMs an, die einen TFTP-Boot durchführen. </sect3> </sect2> - <sect2 arch="i386"><title>Der Boot-Prompt</title> + <sect2 arch="x86"><title>Der Boot-Prompt</title> <para> Wenn der Installer startet, sollte Ihnen ein hübscher grafischer Bildschirm diff --git a/de/boot-installer/intro-cd.xml b/de/boot-installer/intro-cd.xml index b0f06c292..4eb0b396f 100644 --- a/de/boot-installer/intro-cd.xml +++ b/de/boot-installer/intro-cd.xml @@ -6,7 +6,7 @@ Für viele Leute wird der einfachste Weg der sein, einen Satz Debian-CDs zu benutzen. Wenn Sie die CDs haben und Ihr Rechner kann direkt von CD booten – super! -<phrase arch="i386"> +<phrase arch="x86"> Konfigurieren Sie das System, so dass es von CD startet (wie in <xref linkend="boot-dev-select"/> beschrieben). </phrase> diff --git a/de/boot-installer/parameters.xml b/de/boot-installer/parameters.xml index bbce4b17e..c99f3ec6c 100644 --- a/de/boot-installer/parameters.xml +++ b/de/boot-installer/parameters.xml @@ -231,7 +231,7 @@ Symptome für diese Probleme können Fehlermeldungen betreffend Bildschirm oder ein Einfrieren des Systems ein paar Minuten nach dem Installationsstart. -</para><para arch="i386"> +</para><para arch="x86"> Manchmal muss auch <userinput>video=vga16:off</userinput> benutzt werden, um die Verwendung des Framebuffers durch den Kernel zu deaktivieren. Solche diff --git a/de/boot-installer/trouble.xml b/de/boot-installer/trouble.xml index 63a7388cd..3d33ee6a4 100644 --- a/de/boot-installer/trouble.xml +++ b/de/boot-installer/trouble.xml @@ -70,7 +70,7 @@ in Ihrem Kernel aktiviert ist. Der Installer benötigt Oft können Probleme gelöst werden, indem man Erweiterungen und Peripheriegeräte entfernt und dann erneut bootet. -<phrase arch="i386">Speziell interne Modems, Soundkarten und +<phrase arch="x86">Speziell interne Modems, Soundkarten und Plug-n-Play-Geräte können problematisch sein.</phrase> </para><para> @@ -84,7 +84,7 @@ des Speichers vor dem Kernel verbirgt bzw. limitiert, z.B. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Häufige Installationsprobleme unter &arch-title;</title> <para> diff --git a/de/hardware/hardware-supported.xml b/de/hardware/hardware-supported.xml index 07d299d0c..330d73ac1 100644 --- a/de/hardware/hardware-supported.xml +++ b/de/hardware/hardware-supported.xml @@ -221,7 +221,7 @@ zu kontaktieren. <sect2 id="gfx" arch="not-s390"><title>Grafikkarten</title> -<para arch="i386"> +<para arch="x86"> Sie sollten eine VGA-kompatible Grafikschnittstelle für das Konsolen-Terminal verwenden. Nahezu jede moderne Grafikkarte ist zu @@ -262,7 +262,7 @@ für die Evaluation-Boards ist verfügbar. </sect2> - <sect2 arch="i386" id="laptops"><title>Laptops</title> + <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> Auch Laptops werden unterstützt. Laptops sind oftmals spezialisiert diff --git a/de/hardware/installation-media.xml b/de/hardware/installation-media.xml index 62918ac69..b6c7439bc 100644 --- a/de/hardware/installation-media.xml +++ b/de/hardware/installation-media.xml @@ -51,7 +51,7 @@ unterstützt, können Sie die CD-ROM in Kombination mit den anderen Techniken verwenden, um Ihr System zu installieren, sobald Sie auf anderem Wege gebootet haben; siehe <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Sowohl SCSI- als auch IDE/ATAPI-CD-ROMs werden unterstützt. Zusätzlich werden alle nicht-standardkonformen CD-Anschlüsse, die von Linux unterstützt @@ -62,7 +62,7 @@ zu bringen, und das Booten von diesen Nicht-Standard-Anschlüssen ist eher unwahrscheinlich. Das <ulink url="&url-cd-howto;">Linux-CD-ROM-HowTo</ulink> enthält ausführliche Informationen über die Verwendung von CD-ROMs unter Linux. -</para><para arch="i386"> +</para><para arch="x86"> Es können auch externe USB-CD-ROM-Geräte verwendet werden, genauso wie FireWire-Geräte, die von den ohci1394 und sbp2-Treibern unterstützt werden. @@ -220,14 +220,14 @@ Grundsätzlich ist Unterstützung für möglichst viele Geräte wünschenswert, sicherzustellen, dass Debian auf einer umfangreichen Palette von Hardware installiert werden kann. -</para><para arch="i386"> +</para><para arch="x86"> Grundsätzlich beinhaltet das Debian-Installationssystem Unterstützung für Disketten, IDE-Laufwerke, IDE-Disketten, Parallel-Port-IDE-Geräte, SCSI-Controller und -Laufwerke, USB und FireWire. Zu den unterstützten Dateisystemen gehören FAT, Win-32 FAT-Erweiterungen (VFAT) und NTFS. -</para><para arch="i386"> +</para><para arch="x86"> Die Festplatten-Schnittstellen, die das <quote>AT</quote>-Festplatten-Interface emulieren – oft auch MFM, RLL, IDE oder ATA genannt – werden unterstützt. diff --git a/de/hardware/network-cards.xml b/de/hardware/network-cards.xml index ad8d2888f..90a7c55d4 100644 --- a/de/hardware/network-cards.xml +++ b/de/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Hardware für Netzwerkverbindungen</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -23,7 +23,7 @@ weder die Karten noch die Protokolle. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> Bei ISDN wird das D-Channel-Protokoll für das (alte) deutsche 1TR6 nicht unterstützt; Spellcaster BRI-ISDN-Boards werden ebenfalls nicht vom &d-i; diff --git a/de/hardware/supported-peripherals.xml b/de/hardware/supported-peripherals.xml index 0ec2ff895..f16c13fe0 100644 --- a/de/hardware/supported-peripherals.xml +++ b/de/hardware/supported-peripherals.xml @@ -9,13 +9,13 @@ Linux unterstützt eine breite Auswahl an Hardware-Geräten wie Mäuse, Drucker, Scanner, PCMCIA- und USB-Geräte. Allerdings werden die meisten dieser Geräte während der Installation des Systems nicht benötigt. -</para><para arch="i386"> +</para><para arch="x86"> USB-Hardware funktioniert im Allgemeinen ausgezeichnet, nur einige USB-Tastaturen können eine zusätzliche Konfiguration benötigen (siehe <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Hier wiederum der Hinweis, im <ulink url="&url-hardware-howto;">Linux-Hardware-Kompatibilitäts-HowTo</ulink> @@ -61,7 +61,7 @@ Ihre Hardware von GNU/Linux gut unterstützt wird. Unglücklicherweise ist es sehr schwierig, Anbieter zu finden, die überhaupt neue &arch-title;-Hardware verkaufen. -</para><para arch="i386"> +</para><para arch="x86"> Wenn Sie ein Gerät mit mitgeliefertem Windows kaufen müssen, lesen Sie die Software-Lizenz aufmerksam durch, die Sie mit Windows erhalten; es ist @@ -112,7 +112,7 @@ Community einen wichtigen Markt darstellt. </sect2> - <sect2 arch="i386"><title>Windows-spezifische Hardware</title> + <sect2 arch="x86"><title>Windows-spezifische Hardware</title> <para> Ein beunruhigender Trend ist die Verbreitung von Windows-spezifischen diff --git a/de/hardware/supported/i386.xml b/de/hardware/supported/i386.xml index e847f5b1a..d56428df3 100644 --- a/de/hardware/supported/i386.xml +++ b/de/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"><title>CPUs, Mainboards und Grafikunterstützung</title> + <sect2 arch="x86"><title>CPUs, Mainboards und Grafikunterstützung</title> <para> Vollständige Informationen zu unterstützter Peripherie finden Sie im diff --git a/de/howto/installation-howto.xml b/de/howto/installation-howto.xml index c43b323ff..0a56d4c2f 100644 --- a/de/howto/installation-howto.xml +++ b/de/howto/installation-howto.xml @@ -82,7 +82,7 @@ nur die erste CD aus dem Satz. </para><para> Laden Sie das Image herunter, das Sie bevorzugen, und brennen Sie es auf CD. -<phrase arch="i386">Um von CD zu booten, müssen Sie unter Umständen die +<phrase arch="x86">Um von CD zu booten, müssen Sie unter Umständen die BIOS-Einstellungen ändern, wie in <xref linkend="bios-setup" /> beschrieben.</phrase> <phrase arch="powerpc">Um einen PowerMac von CD zu starten, drücken Sie während @@ -161,7 +161,7 @@ Debian-Installers einzurichten und es ist auch möglich, es mit kleineren Speicher-Sticks hinzubekommen. Details finden Sie im <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Bei einigen Systemen kann das BIOS direkt vom USB-Speicher starten, bei anderen nicht. Eventuell müssen Sie das BIOS konfigurieren, von einem @@ -188,7 +188,7 @@ Die verschiedenen Varianten des Bootens per Netzwerk sind abhängig von der Architektur und den Netzwerk-Boot-Einstellungen. Sie können die Dateien unter <filename>netboot/</filename> nutzen, um den &d-i; per Netzwerk zu starten. -</para><para arch="i386"> +</para><para arch="x86"> Am einfachsten einzurichten ist wahrscheinlich der PXE-Netzwerkboot. Entpacken Sie mittels <command>untar</command> die Datei @@ -212,7 +212,7 @@ die sogar ein anderes Betriebssystem enthalten kann. Laden Sie und ein Debian-CD-Image in das Wurzelverzeichnis der Festplatte. Stellen Sie sicher, dass der Dateiname des CD-Images auf <literal>.iso</literal> endet. Jetzt ist es lediglich erforderlich, Linux mit der initrd zu starten. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> beschreibt einen Weg, wie dies funktioniert. </phrase> @@ -227,7 +227,7 @@ endet. Jetzt ist es lediglich erforderlich, Linux mit der initrd zu starten. Sobald der Installer startet, werden Sie mit einem Startbildschirm begrüßt. Drücken Sie &enterkey;, um zu starten, oder lesen Sie die Instruktionen über andere Boot-Methoden und Parameter (siehe <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Wollen Sie einen 2.4er Kernel installieren, tippen Sie am <prompt>boot:</prompt>-Prompt <userinput>install24</userinput> ein. <footnote><para> @@ -274,7 +274,7 @@ Dies wird empfohlen für neue Benutzer oder falls Sie es eilig haben; Wenn Sie jedoch keine automatische Partitionierung wollen, wählen Sie <quote>manuell</quote> aus dem Menü. -</para><para arch="i386"> +</para><para arch="x86"> Wenn Sie eine vorhandene DOS- oder Windows-Partition auf dem Rechner haben und auch behalten möchten, seien Sie mit der automatischen @@ -310,7 +310,7 @@ der Kernel installiert. Der letzte Schritt ist die Installation des Bootloaders. Wenn der Installer ein anderes Betriebssystem auf Ihrem Rechner erkennt, wird es zum Bootmenü hinzugefügt und Sie werden darüber informiert. -<phrase arch="i386">Standardmäßig wird der Bootloader GRUB in den +<phrase arch="x86">Standardmäßig wird der Bootloader GRUB in den Master-Boot-Record der ersten Festplatte installiert, was meistens eine gute Wahl ist. Sie haben aber die Möglichkeit, diese Auswahl zu überschreiben und ihn anderswo zu installieren. diff --git a/de/install-methods/boot-drive-files.xml b/de/install-methods/boot-drive-files.xml index 200958144..a9ef81a28 100644 --- a/de/install-methods/boot-drive-files.xml +++ b/de/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ durchführen. Dies vermeidet das ganze Theater mit den Wechselmedien, wie das Auffinden und Brennen von CD-Images oder den Kampf mit den vielen oder mit defekten Floppy-Disks. -</para><para arch="i386"> +</para><para arch="x86"> Der Installer kann jedoch nicht von Dateien auf einem NTFS-Dateisystem booten. @@ -41,7 +41,7 @@ von Festplatte zu booten, abhängig davon, ob es ein <quote>NewWorld</quote>- od </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Booten des Installers von Festplatte mittels <command>lilo</command> oder <command>grub</command></title> <para> diff --git a/de/install-methods/boot-usb-files.xml b/de/install-methods/boot-usb-files.xml index bc4567e16..481754c74 100644 --- a/de/install-methods/boot-usb-files.xml +++ b/de/install-methods/boot-usb-files.xml @@ -24,7 +24,7 @@ richten). <sect2 id="usb-copy-easy"> <title>Die Dateien kopieren – der einfache Weg</title> -<para arch="i386"> +<para arch="x86"> Es gibt ein <quote>Alles-in-einem</quote>-Image <filename>hd-media/boot.img.gz</filename>, das alle Dateien des Installers enthält (inklusive des Kernels) wie auch @@ -60,9 +60,9 @@ für Ihren USB-Stick verwenden. <para> Danach hängen Sie den USB-Memory-Stick ins Dateisystem ein -(<userinput>mount <replaceable arch="i386">/dev/sda</replaceable> +(<userinput>mount <replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> -/mnt</userinput>), der jetzt ein <phrase arch="i386">FAT-Dateisystem</phrase> +/mnt</userinput>), der jetzt ein <phrase arch="x86">FAT-Dateisystem</phrase> <phrase arch="powerpc">HFS-Dateisystem</phrase> enthält, und kopieren ein Debian-<quote>netinst</quote>- oder -<quote>businesscard</quote>-ISO-Image dorthin. Achten Sie darauf, @@ -120,7 +120,7 @@ den Schreibschutz. </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Vom USB-Stick booten</title> <warning><para> diff --git a/de/install-methods/install-tftp.xml b/de/install-methods/install-tftp.xml index bd6e89fce..a79336a33 100644 --- a/de/install-methods/install-tftp.xml +++ b/de/install-methods/install-tftp.xml @@ -76,7 +76,7 @@ auf jeder Plattform benutzt werden, der diese Protokolle implementiert hat. In den Beispielen in diesem Abschnitt geben wir Kommandos für SunOS 4.x, SunOS 5.x (a.k.a. Solaris) und GNU/Linux an. -<note arch="i386"><para> +<note arch="x86"><para> Um die Pre-Boot-Execution-Environment- (PXE) Methode von TFTP zu nutzen, benötigen Sie einen TFTP-Server mit Unterstützung für @@ -172,7 +172,7 @@ benutzen Sie die Datei <filename>yaboot-netboot.conf</filename>; benennen sie sie einfach in <filename>yaboot.conf</filename> im TFTP-Verzeichnis um. -</para><para arch="i386"> +</para><para arch="x86"> Um per PXE zu booten, müssen Sie nur den <filename>netboot/netboot.tar.gz</filename>-Tarball einrichten. diff --git a/de/install-methods/tftp/dhcp.xml b/de/install-methods/tftp/dhcp.xml index 5663c80ec..9f45571d2 100644 --- a/de/install-methods/tftp/dhcp.xml +++ b/de/install-methods/tftp/dhcp.xml @@ -52,7 +52,7 @@ neu. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>PXE-Boot aktivieren in der DHCP-Konfiguration</title> <para> Hier ist ein weiteres Beispiel der <filename>dhcpd.conf</filename>, das diff --git a/de/install-methods/usb-setup/i386.xml b/de/install-methods/usb-setup/i386.xml index 86191d1b4..bbde209ab 100644 --- a/de/install-methods/usb-setup/i386.xml +++ b/de/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Partitionieren eines USB-Sticks auf &arch-title;-Systemen</title> <para> diff --git a/de/partitioning/device-names.xml b/de/partitioning/device-names.xml index 608449d5a..7a85f6242 100644 --- a/de/partitioning/device-names.xml +++ b/de/partitioning/device-names.xml @@ -69,12 +69,12 @@ angezeigt wird, kann unter Debian <filename>/dev/hda</filename> sein. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Die erste XT-Festplatte heißt <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Die zweite XT-Festplatte heißt <filename>/dev/xdb</filename>. @@ -126,7 +126,7 @@ kann die Reihenfolge der Festplatten sehr konfus sein. Die beste Lösung ist in diesem Fall, die Boot-Meldungen zu beobachten, zumindest wenn Sie die Festplatten-Modelle und/oder deren Größe kennen. -</para><para arch="i386"> +</para><para arch="x86"> Linux stellt die primären Partitionen als Bezeichnung der Festplatte plus einer Zahl von 1 bis 4 dar. Zum Beispiel ist die erste primäre diff --git a/de/partitioning/partition-programs.xml b/de/partitioning/partition-programs.xml index c195cd341..6c0e770a0 100644 --- a/de/partitioning/partition-programs.xml +++ b/de/partitioning/partition-programs.xml @@ -21,7 +21,7 @@ Programme, die für Ihre Architektur verfügbar sind: Das bevorzugte Partitionierungswerkzeug in Debian. Dieses Schweizer Messer unter den Partitionierungsprogrammen kann auch die Größe von bestehenden Partitionen verändern sowie Dateisysteme erstellen -<phrase arch="i386"> (in der Windows-Sprache <quote>formatieren</quote>) </phrase> +<phrase arch="x86"> (in der Windows-Sprache <quote>formatieren</quote>) </phrase> und die Einhängepunkte zuweisen. </para></listitem> @@ -148,7 +148,7 @@ installiert sind, führen Sie Folgendes aus: # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">Denken Sie daran, Ihre Boot-Partition als +<phrase arch="x86">Denken Sie daran, Ihre Boot-Partition als <quote>Bootable</quote> (bootfähig) zu kennzeichnen.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/de/partitioning/partition/i386.xml b/de/partitioning/partition/i386.xml index a0a5feeec..850b5f0f5 100644 --- a/de/partitioning/partition/i386.xml +++ b/de/partitioning/partition/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 35590 --> - <sect2 arch="i386"><title>Partitionieren auf &arch-title;-Systemen</title> + <sect2 arch="x86"><title>Partitionieren auf &arch-title;-Systemen</title> <para> Wenn Sie bereits ein anderes Betriebssystem wie DOS oder Windows auf Ihrem diff --git a/de/post-install/kernel-baking.xml b/de/post-install/kernel-baking.xml index 743b68f3d..9bce80dfc 100644 --- a/de/post-install/kernel-baking.xml +++ b/de/post-install/kernel-baking.xml @@ -169,7 +169,7 @@ ein Paket installieren. Tippen Sie als root ein: ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> Der Teil <replaceable>subarchitecture</replaceable> im Dateinamen ist eine -optionale Bezeichnung für die Unterarchitektur, <phrase arch="i386"> wie +optionale Bezeichnung für die Unterarchitektur, <phrase arch="x86"> wie z.B. <quote>i586</quote>, </phrase> abhängig davon, welche Kerneloptionen Sie gesetzt haben. <userinput>dpkg -i ...</userinput> installiert den Kernel diff --git a/de/post-install/reactivating-win.xml b/de/post-install/reactivating-win.xml index 390b9a1eb..a49f09322 100644 --- a/de/post-install/reactivating-win.xml +++ b/de/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>DOS und Windows reaktivieren</title> <para> diff --git a/de/post-install/rescue.xml b/de/post-install/rescue.xml index 997089cc6..8f30bdbe8 100644 --- a/de/post-install/rescue.xml +++ b/de/post-install/rescue.xml @@ -44,7 +44,7 @@ Falls möglich präsentiert der Installer Ihnen jetzt eine Shell-Eingabeaufforderung in dem Dateisystem, dass Sie ausgewählt haben, die Sie für nötige Reparaturen verwenden können. -<phrase arch="i386"> +<phrase arch="x86"> Wenn Sie z.B. den GRUB-Bootloader neu in den Master Boot Record Ihrer ersten Festplatte installieren müssen, können Sie dort <userinput>grub-install '(hd0)'</userinput> eingeben, um dies zu erledigen. diff --git a/de/preparing/bios-setup/i386.xml b/de/preparing/bios-setup/i386.xml index d1b4e19d2..c9c8a5e65 100644 --- a/de/preparing/bios-setup/i386.xml +++ b/de/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"><title>Das BIOS-Setup-Menü aufrufen</title> + <sect2 arch="x86" id="bios-setup"><title>Das BIOS-Setup-Menü aufrufen</title> <para> @@ -104,7 +104,7 @@ Shareware/Freeware-Programm zu benutzen. Werfen Sie einen Blick auf </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Das Start-Laufwerk auswählen (Boot Device Selection)</title> + <sect2 arch="x86" id="boot-dev-select"><title>Das Start-Laufwerk auswählen (Boot Device Selection)</title> <para> @@ -235,7 +235,7 @@ drücken. </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Verschiedene BIOS-Einstellungen</title> <sect3 id="cd-settings"><title>CD-ROM-Einstellungen</title> diff --git a/de/preparing/minimum-hardware-reqts.xml b/de/preparing/minimum-hardware-reqts.xml index 237445ea0..45de9b76c 100644 --- a/de/preparing/minimum-hardware-reqts.xml +++ b/de/preparing/minimum-hardware-reqts.xml @@ -16,7 +16,7 @@ aufgelisteten Hardware auskommen. Die meisten Benutzer riskieren jedoch, im Nachhinein frustriert zu sein, wenn Sie diese Empfehlungen ignorieren. -</para><para arch="i386"> +</para><para arch="x86"> Für Desktop-Systeme wird mindestens ein Pentium 100 empfohlen und für einen Server mindestens ein Pentium II-300. diff --git a/de/preparing/needed-info.xml b/de/preparing/needed-info.xml index c43f4dc92..ac5cce139 100644 --- a/de/preparing/needed-info.xml +++ b/de/preparing/needed-info.xml @@ -53,8 +53,8 @@ Enthält oft nützliche Informationen zum Konfigurieren oder Verwenden Ihrer Har <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> -<itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> +<itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux-Hardware-Kompatibilitäts-HowTo</ulink> @@ -175,7 +175,7 @@ Die Verpackung Ihrer Hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Das System-Fenster in der Windows-Systemsteuerung. @@ -214,7 +214,7 @@ E-Mail verraten. </row> <row arch="not-s390"><entry>Deren Reihenfolge im System.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Ob IDE oder SCSI (die meisten Rechner haben IDE).</entry> </row> <row arch="m68k"> @@ -295,19 +295,19 @@ Viele Markenprodukte funktionieren problemlos unter Linux. Zudem verbessert sich Hardware für Linux täglich. Linux unterstützt jedoch nicht so viele verschiedene Typen von Hardware wie manch anderes Betriebssystem. -</para><para arch="i386"> +</para><para arch="x86"> Im Besonderen kann Linux normalerweise keine Hardware betreiben, die eine laufende Windows-Version benötigt. -</para><para arch="i386"> +</para><para arch="x86"> Einige Windows-spezifische Hardware kann jedoch mit etwas Aufwand unter Linux lauffähig gemacht werden. Außerdem sind Treiber für Windows-spezifische Hardware meist für einen speziellen Linux-Kernel angepasst. Aus diesem Grund können sie schnell überholt sein. -</para><para arch="i386"> +</para><para arch="x86"> So genannte Win-Modems sind der gängigste Typ dieser Hardware. Drucker und andere Geräte können jedoch ebenfalls Windows-spezifisch diff --git a/de/preparing/non-debian-partitioning.xml b/de/preparing/non-debian-partitioning.xml index 8c8e3c16c..86459d24a 100644 --- a/de/preparing/non-debian-partitioning.xml +++ b/de/preparing/non-debian-partitioning.xml @@ -21,7 +21,7 @@ Rechner ist in diesem Fall ein LPAR oder VM-Gast gemeint. Wenn Sie bereits ein Betriebssystem auf Ihrem Rechner haben -<phrase arch="i386"> +<phrase arch="x86"> (z.B. Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -48,7 +48,7 @@ Sie brauchen mindestens eine eigene Partition für das Debian-Root-Verzeichnis. Sie können Informationen über Ihre bisherigen Partitionen mittels eines Partitionierungs-Tools Ihres aktuellen Betriebssystems bekommen<phrase -arch="i386">, wie etwa fdisk oder PartitionMagic</phrase><phrase +arch="x86">, wie etwa fdisk oder PartitionMagic</phrase><phrase arch="powerpc">, wie etwa Drive Setup, HD Toolkit oder MacTools</phrase><phrase arch="m68k">, wie etwa HD SC Setup, HDToolBox oder SCSITool</phrase><phrase arch="s390">, wie dem VM diskmap</phrase>. @@ -102,7 +102,7 @@ der existierenden Partitionen innerhalb der Partitionstabelle) gibt, die Sie dazu zwingen könnten, die Partitionierung doch vor dem Debian-Installationsprozess durchzuführen. -</para><para arch="i386"> +</para><para arch="x86"> Wenn Ihr Rechner ein FAT- oder NTFS-Dateisystem enthält, wie es von DOS und Windows genutzt wird, können Sie mit dem Partitionieren warten diff --git a/de/preparing/nondeb-part/i386.xml b/de/preparing/nondeb-part/i386.xml index 96b901fb5..e226a854a 100644 --- a/de/preparing/nondeb-part/i386.xml +++ b/de/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386"><title>Partitionieren unter MS-DOS oder Windows</title> + <sect2 arch="x86"><title>Partitionieren unter MS-DOS oder Windows</title> <para> Wenn Sie vorhandene FAT- oder NTFS-Partitionen verändern, wird empfohlen, diff --git a/de/preparing/pre-install-bios-setup.xml b/de/preparing/pre-install-bios-setup.xml index 66ff13394..92c1aae52 100644 --- a/de/preparing/pre-install-bios-setup.xml +++ b/de/preparing/pre-install-bios-setup.xml @@ -58,7 +58,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> Wirklich gute Mainboards unterstützen RAM mit Parity und informieren den Benutzer, falls das System einen Single-Bit-Fehler im RAM hat. @@ -69,7 +69,7 @@ unbemerkt Fehler in Ihre Daten eingeschleust werden. Deswegen haben die besten S Motherboards, die Parity und True-Parity-Speichermodule unterstützen; siehe auch <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Wenn Sie True-Parity-Speicher haben und Ihr Motherboard damit umgehen kann, stellen Sie sicher, dass die entsprechenden BIOS-Einstellungen @@ -78,7 +78,7 @@ auftritt. </para> - <sect3 arch="i386"><title>Der Turbo-Schalter</title> + <sect3 arch="x86"><title>Der Turbo-Schalter</title> <para> Viele Systeme haben einen <emphasis>Turbo</emphasis>-Schalter, der den @@ -93,7 +93,7 @@ verändern könnte. </para> </sect3> - <sect3 arch="i386"><title>Cyrix-CPUs und Disketten-Fehler</title> + <sect3 arch="x86"><title>Cyrix-CPUs und Disketten-Fehler</title> <para> Viele Nutzer von Cyrix-CPUs mussten den Cache/Zwischenspeicher @@ -113,7 +113,7 @@ ist. </para> </sect3> - <sect3 arch="i386"><title>Hardware-Einstellungen für Peripheriegeräte</title> + <sect3 arch="x86"><title>Hardware-Einstellungen für Peripheriegeräte</title> <para> Sie müssen eventuell einige Einstellungen oder Jumper auf Erweiterungskarten Ihres @@ -131,7 +131,7 @@ mindestens 1 Megabyte oberhalb des insgesamt verfügbaren Arbeitsspeichers. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>USB-Bios-Support und Tastaturen</title> <para> diff --git a/de/using-d-i/modules/clock-setup.xml b/de/using-d-i/modules/clock-setup.xml index ce8b2917c..8078d6d93 100644 --- a/de/using-d-i/modules/clock-setup.xml +++ b/de/using-d-i/modules/clock-setup.xml @@ -20,7 +20,7 @@ UTC eingestellt ist oder nicht. normalerweise auf die lokale Zeit eingestellt. Wenn Sie den Rechner mit mehreren Betriebssystemen parallel betreiben möchten, setzen Sie die Uhr auf lokale Zeit statt auf GMT/UTC.</phrase> -<phrase arch="i386">Systeme, auf denen (auch) Dos oder Windows läuft, sind +<phrase arch="x86">Systeme, auf denen (auch) Dos oder Windows läuft, sind normalerweise auf lokale Zeit eingestellt. Wenn Sie den Rechner mit mehreren Betriebssystemen parallel betreiben möchten, setzen Sie die Uhr auf lokale Zeit statt auf GMT/UTC.</phrase> diff --git a/de/using-d-i/modules/i386/grub-installer.xml b/de/using-d-i/modules/i386/grub-installer.xml index 3d6436cf3..73aaec6f4 100644 --- a/de/using-d-i/modules/i386/grub-installer.xml +++ b/de/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Den <command>grub</command>-Bootloader auf Festplatte installieren (grub-installer)</title> <para> diff --git a/de/using-d-i/modules/i386/lilo-installer.xml b/de/using-d-i/modules/i386/lilo-installer.xml index 5c00bda89..839ec1a67 100644 --- a/de/using-d-i/modules/i386/lilo-installer.xml +++ b/de/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Den <command>lilo</command>-Bootloader auf Festplatte installieren (lilo-installer)</title> <para> diff --git a/debian/changelog b/debian/changelog index fb8ef5542..c0bf5c321 100644 --- a/debian/changelog +++ b/debian/changelog @@ -11,12 +11,13 @@ installation-guide (2006xxxx) UNRELEASED; urgency=low * Add /srv in overview of directory tree in partitioning appendix. * Update section on partitioning using LVM to reflect recent changes. * Apply various patches by or based on suggestions from Nathanael Nerode. + * Add variant for the AMD64 architecture. Closes: #305977. [ Miroslav Kure ] * Update information about booting with encrypted partitions. Closes: #378651. - -- Frans Pop <fjp@debian.org> Thu, 3 Aug 2006 13:35:41 +0200 + -- Frans Pop <fjp@debian.org> Mon, 7 Aug 2006 17:42:30 +0200 installation-guide (20060726) unstable; urgency=low diff --git a/en/administrivia/administrivia.xml b/en/administrivia/administrivia.xml index 65d862709..43cfb2531 100644 --- a/en/administrivia/administrivia.xml +++ b/en/administrivia/administrivia.xml @@ -131,7 +131,7 @@ The section on chrooted installations in this manual (<xref linkend="linux-upgrade"/>) was derived in part from documents copyright Karsten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> The section on installations over plip in this manual (<xref linkend="plip"/>) was based on the diff --git a/en/appendix/chroot-install.xml b/en/appendix/chroot-install.xml index aacc62271..a3f707b03 100644 --- a/en/appendix/chroot-install.xml +++ b/en/appendix/chroot-install.xml @@ -403,7 +403,7 @@ the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so. -</para><para arch="i386"> +</para><para arch="x86"> Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the @@ -414,7 +414,7 @@ add an entry for the Debian install to your existing grub edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from). -</para><para arch="i386"> +</para><para arch="x86"> Here is a basic <filename>/etc/lilo.conf</filename> as an example: diff --git a/en/appendix/plip.xml b/en/appendix/plip.xml index a8acd8e76..69548ac2a 100644 --- a/en/appendix/plip.xml +++ b/en/appendix/plip.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Installing &debian; over Parallel Line IP (PLIP)</title> <para> diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml index a1845a192..61c60df6f 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/en/boot-installer/i386.xml b/en/boot-installer/i386.xml index d58bea242..fbdb87ba5 100644 --- a/en/boot-installer/i386.xml +++ b/en/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect2 arch="i386"><title>Booting from a CD-ROM</title> + <sect2 arch="x86"><title>Booting from a CD-ROM</title> &boot-installer-intro-cd.xml; @@ -74,7 +74,7 @@ Boots the <quote>bf2.4</quote> flavor. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -105,7 +105,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Booting from Linux Using <command>LILO</command> or <command>GRUB</command></title> @@ -192,7 +192,7 @@ or <command>LILO</command>. </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Booting from USB Memory Stick</title> <para> @@ -206,7 +206,7 @@ arguments, or just hit &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Booting from Floppies</title> <para> @@ -266,7 +266,7 @@ contents are loaded into memory. The installer program </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title> &boot-installer-intro-net.xml; @@ -312,7 +312,7 @@ provides bootdiskettes and even bootroms that do a TFTPboot. </sect3> </sect2> - <sect2 arch="i386"><title>The Boot Prompt</title> + <sect2 arch="x86"><title>The Boot Prompt</title> <para> When the installer boots, you should be presented with a friendly graphical diff --git a/en/boot-installer/intro-cd.xml b/en/boot-installer/intro-cd.xml index d32a37e9a..523976a08 100644 --- a/en/boot-installer/intro-cd.xml +++ b/en/boot-installer/intro-cd.xml @@ -6,7 +6,7 @@ The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply -<phrase arch="i386"> +<phrase arch="x86"> configure your system for booting off a CD as described in <xref linkend="boot-dev-select"/>, </phrase> diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml index f261a694e..9c6c34904 100644 --- a/en/boot-installer/parameters.xml +++ b/en/boot-installer/parameters.xml @@ -220,7 +220,7 @@ you can disable the feature by the parameter about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="i386"> +</para><para arch="x86"> The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index 17d1bbc6a..8ff3536cb 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -67,7 +67,7 @@ your kernel. The installer requires </para><para> Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> </para><para> @@ -80,7 +80,7 @@ kernel sees, such as <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Common &arch-title; Installation Problems</title> <para> diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml index ed20c71df..a515df480 100644 --- a/en/hardware/hardware-supported.xml +++ b/en/hardware/hardware-supported.xml @@ -222,7 +222,7 @@ as well. <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title> -<para arch="i386"> +<para arch="x86"> You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with @@ -260,7 +260,7 @@ listing</ulink> for Broadcom evaluation boards is available. </sect2> - <sect2 arch="i386" id="laptops"><title>Laptops</title> + <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> Laptops are also supported. Laptops are often specialized or contain diff --git a/en/hardware/installation-media.xml b/en/hardware/installation-media.xml index cade1842f..41204f979 100644 --- a/en/hardware/installation-media.xml +++ b/en/hardware/installation-media.xml @@ -50,7 +50,7 @@ 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 <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the @@ -60,7 +60,7 @@ them to work, and booting off these non-standard interfaces is unlikely. The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux. -</para><para arch="i386"> +</para><para arch="x86"> USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers. @@ -214,14 +214,14 @@ 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. -</para><para arch="i386"> +</para><para arch="x86"> Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS. -</para><para arch="i386"> +</para><para arch="x86"> Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old diff --git a/en/hardware/network-cards.xml b/en/hardware/network-cards.xml index 69b7ed1aa..bf77e7303 100644 --- a/en/hardware/network-cards.xml +++ b/en/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -23,7 +23,7 @@ cards and protocols. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the diff --git a/en/hardware/supported-peripherals.xml b/en/hardware/supported-peripherals.xml index f2ca41329..0a7254a9b 100644 --- a/en/hardware/supported-peripherals.xml +++ b/en/hardware/supported-peripherals.xml @@ -9,13 +9,13 @@ Linux 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. -</para><para arch="i386"> +</para><para arch="x86"> USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Again, see the <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -58,7 +58,7 @@ be sure that the hardware is well-supported by GNU/Linux. Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all. -</para><para arch="i386"> +</para><para arch="x86"> 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 @@ -108,7 +108,7 @@ is an important market. </sect2> - <sect2 arch="i386"><title>Windows-specific Hardware</title> + <sect2 arch="x86"><title>Windows-specific Hardware</title> <para> A disturbing trend is the proliferation of Windows-specific modems and diff --git a/en/hardware/supported/i386.xml b/en/hardware/supported/i386.xml index c1a709bf7..9c8438575 100644 --- a/en/hardware/supported/i386.xml +++ b/en/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- $Id$ --> - <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title> + <sect2 arch="x86"><title>CPU, Main Boards, and Video Support</title> <para> Complete information concerning supported peripherals can be found at diff --git a/en/howto/installation-howto.xml b/en/howto/installation-howto.xml index 57d51fb17..103200c7f 100644 --- a/en/howto/installation-howto.xml +++ b/en/howto/installation-howto.xml @@ -79,7 +79,7 @@ only need the first CD of the set. </para><para> Download whichever type you prefer and burn it to a CD. -<phrase arch="i386">To boot the CD, you may need to change your BIOS +<phrase arch="x86">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See @@ -152,7 +152,7 @@ There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a @@ -175,7 +175,7 @@ It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into @@ -198,7 +198,7 @@ existing hard disk, which can have a different OS on it. Download and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> explains one way to do it. </phrase> @@ -213,7 +213,7 @@ it's just a matter of booting linux with the initrd. Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> @@ -255,7 +255,7 @@ opportunity to automatically partition either an entire drive, or free space on a drive. This is recommended for new users or anyone in a hurry, but if you do not want to autopartition, choose manual from the menu. -</para><para arch="i386"> +</para><para arch="x86"> If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, @@ -282,7 +282,7 @@ which can take a while. That is followed by installing a kernel. The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. -<phrase arch="i386">By default GRUB will be installed to the master boot +<phrase arch="x86">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase> diff --git a/en/install-methods/boot-drive-files.xml b/en/install-methods/boot-drive-files.xml index 39c36d50e..22f9b3a2d 100644 --- a/en/install-methods/boot-drive-files.xml +++ b/en/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks. -</para><para arch="i386"> +</para><para arch="x86"> The installer cannot boot from files on an NTFS file system. @@ -39,7 +39,7 @@ depending on whether the system is a <quote>NewWorld</quote> or an </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Hard disk installer booting using <command>LILO</command> or <command>GRUB</command></title> <para> diff --git a/en/install-methods/boot-usb-files.xml b/en/install-methods/boot-usb-files.xml index ab26b6c6b..df1d34704 100644 --- a/en/install-methods/boot-usb-files.xml +++ b/en/install-methods/boot-usb-files.xml @@ -23,7 +23,7 @@ setups are possible if you follow <xref linkend="usb-copy-flexible"/>). <sect2 id="usb-copy-easy"> <title>Copying the files — the easy way</title> -<para arch="i386"> +<para arch="x86"> There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well @@ -57,10 +57,10 @@ that you use the correct device name for your USB stick. <para> After that, mount the USB memory stick (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), which will now have -<phrase arch="i386">a FAT filesystem</phrase> +<phrase arch="x86">a FAT filesystem</phrase> <phrase arch="powerpc">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. @@ -110,7 +110,7 @@ When you are done, unmount the USB memory stick (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Booting the USB stick</title> <warning><para> diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 45ad26d1b..39c528be2 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -70,7 +70,7 @@ which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> @@ -161,7 +161,7 @@ images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory. -</para><para arch="i386"> +</para><para arch="x86"> For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this diff --git a/en/install-methods/tftp/dhcp.xml b/en/install-methods/tftp/dhcp.xml index ee18f73e4..fb9c624ea 100644 --- a/en/install-methods/tftp/dhcp.xml +++ b/en/install-methods/tftp/dhcp.xml @@ -52,7 +52,7 @@ restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Enabling PXE Booting in the DHCP configuration</title> <para> Here is another example for a <filename>dhcp.conf</filename> using the diff --git a/en/install-methods/usb-setup/i386.xml b/en/install-methods/usb-setup/i386.xml index 567a5e837..c35ef1e24 100644 --- a/en/install-methods/usb-setup/i386.xml +++ b/en/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>USB stick partitioning on &arch-title;</title> <para> diff --git a/en/partitioning/device-names.xml b/en/partitioning/device-names.xml index 3190bc8f7..5f3b3c17d 100644 --- a/en/partitioning/device-names.xml +++ b/en/partitioning/device-names.xml @@ -67,12 +67,12 @@ up as <filename>/dev/hda</filename> in Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The first XT disk is named <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The second XT disk is named <filename>/dev/xdb</filename>. @@ -125,7 +125,7 @@ the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities. -</para><para arch="i386"> +</para><para arch="x86"> Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml index 6514f910d..9783c19c2 100644 --- a/en/partitioning/partition-programs.xml +++ b/en/partitioning/partition-programs.xml @@ -20,7 +20,7 @@ your architecture. Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems -<phrase arch="i386"> (<quote>format</quote> in Windows speak)</phrase> +<phrase arch="x86"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints. </para></listitem> @@ -140,7 +140,7 @@ on the target system. After installing the kernel and modules, execute: # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">Remember to mark your boot partition as +<phrase arch="x86">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/en/partitioning/partition/i386.xml b/en/partitioning/partition/i386.xml index 52ce988ac..55681bd39 100644 --- a/en/partitioning/partition/i386.xml +++ b/en/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- $Id$ --> - <sect2 arch="i386"><title>Partitioning for &arch-title;</title> + <sect2 arch="x86"><title>Partitioning for &arch-title;</title> <para> If you have an existing other operating system such as DOS or Windows and diff --git a/en/post-install/kernel-baking.xml b/en/post-install/kernel-baking.xml index 8871fb075..5f91d9ed1 100644 --- a/en/post-install/kernel-baking.xml +++ b/en/post-install/kernel-baking.xml @@ -158,7 +158,7 @@ like any package. As root, do </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as <quote>i586</quote>, </phrase> +<phrase arch="x86"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, diff --git a/en/post-install/reactivating-win.xml b/en/post-install/reactivating-win.xml index 728585b9b..8559462c3 100644 --- a/en/post-install/reactivating-win.xml +++ b/en/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- $Id$ --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivating DOS and Windows</title> <para> diff --git a/en/post-install/rescue.xml b/en/post-install/rescue.xml index c774069ba..6feaff0c9 100644 --- a/en/post-install/rescue.xml +++ b/en/post-install/rescue.xml @@ -42,7 +42,7 @@ If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. -<phrase arch="i386"> +<phrase arch="x86"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. diff --git a/en/preparing/bios-setup/i386.xml b/en/preparing/bios-setup/i386.xml index e5e884612..7d19431f2 100644 --- a/en/preparing/bios-setup/i386.xml +++ b/en/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- $Id$ --> - <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> + <sect2 arch="x86" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> <para> @@ -102,7 +102,7 @@ try using a shareware/freeware program. Try looking in </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title> + <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title> <para> @@ -230,7 +230,7 @@ save the changes on your computer. Often, you must press </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Miscellaneous BIOS Settings</title> <sect3 id="cd-settings"><title>CD-ROM Settings</title> diff --git a/en/preparing/minimum-hardware-reqts.xml b/en/preparing/minimum-hardware-reqts.xml index 3dffd6e91..0def42ddb 100644 --- a/en/preparing/minimum-hardware-reqts.xml +++ b/en/preparing/minimum-hardware-reqts.xml @@ -15,7 +15,7 @@ Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions. -</para><para arch="i386"> +</para><para arch="x86"> A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server. diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml index 53f7ea264..8f68abd37 100644 --- a/en/preparing/needed-info.xml +++ b/en/preparing/needed-info.xml @@ -52,8 +52,8 @@ Often contains useful information on configuring or using your hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -175,7 +175,7 @@ The cases and boxes for each piece of hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The System window in the Windows Control Panel. @@ -215,7 +215,7 @@ networking and e-mail. </row> <row arch="not-s390"><entry>Their order on the system.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Whether IDE or SCSI (most computers are IDE).</entry> </row> <row arch="m68k"> @@ -296,19 +296,19 @@ Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems. -</para><para arch="i386"> +</para><para arch="x86"> In particular, Linux usually cannot run hardware that requires a running version of Windows to work. -</para><para arch="i386"> +</para><para arch="x86"> Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete. -</para><para arch="i386"> +</para><para arch="x86"> So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific. diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml index 6e444855a..0f95aefe4 100644 --- a/en/preparing/non-debian-partitioning.xml +++ b/en/preparing/non-debian-partitioning.xml @@ -20,7 +20,7 @@ means an LPAR or VM guest in this case. If you already have an operating system on your system -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -47,7 +47,7 @@ root. You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase -arch="i386">, such as fdisk or PartitionMagic</phrase><phrase +arch="x86">, such as fdisk or PartitionMagic</phrase><phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always @@ -97,7 +97,7 @@ special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway. -</para><para arch="i386"> +</para><para arch="x86"> If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to diff --git a/en/preparing/nondeb-part/i386.xml b/en/preparing/nondeb-part/i386.xml index 3846cec48..4346fe83f 100644 --- a/en/preparing/nondeb-part/i386.xml +++ b/en/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- $Id$ --> - <sect2 arch="i386"><title>Partitioning From DOS or Windows</title> + <sect2 arch="x86"><title>Partitioning From DOS or Windows</title> <para> If you are manipulating existing FAT or NTFS partitions, it is diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml index 369fb6922..03be8cd7b 100644 --- a/en/preparing/pre-install-bios-setup.xml +++ b/en/preparing/pre-install-bios-setup.xml @@ -54,7 +54,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they @@ -65,7 +65,7 @@ in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to @@ -73,7 +73,7 @@ interrupt on memory parity errors. </para> - <sect3 arch="i386"><title>The Turbo Switch</title> + <sect3 arch="x86"><title>The Turbo Switch</title> <para> Many systems have a <emphasis>turbo</emphasis> switch that controls @@ -87,7 +87,7 @@ accidentally touch the software control for the turbo switch. </para> </sect3> - <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title> + <sect3 arch="x86"><title>Cyrix CPUs and Floppy Disk Errors</title> <para> Many users of Cyrix CPUs have had to disable the cache in their @@ -106,7 +106,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code. </para> </sect3> - <sect3 arch="i386"><title>Peripheral Hardware Settings</title> + <sect3 arch="x86"><title>Peripheral Hardware Settings</title> <para> You may have to change some settings or jumpers on your computer's @@ -124,7 +124,7 @@ amount of RAM in your system. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>USB BIOS support and keyboards</title> <para> diff --git a/en/using-d-i/modules/clock-setup.xml b/en/using-d-i/modules/clock-setup.xml index 8f6f76822..2d9b00c82 100644 --- a/en/using-d-i/modules/clock-setup.xml +++ b/en/using-d-i/modules/clock-setup.xml @@ -18,7 +18,7 @@ whether or not the clock is set to UTC. <phrase arch="m68k;powerpc">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> -<phrase arch="i386">Systems that (also) run Dos or Windows are normally +<phrase arch="x86">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> diff --git a/en/using-d-i/modules/i386/grub-installer.xml b/en/using-d-i/modules/i386/grub-installer.xml index 77cdd9a45..814ad824b 100644 --- a/en/using-d-i/modules/i386/grub-installer.xml +++ b/en/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>Grub</command> Boot Loader on a Hard Disk</title> <para> diff --git a/en/using-d-i/modules/i386/lilo-installer.xml b/en/using-d-i/modules/i386/lilo-installer.xml index ef517fc1d..9b2ead402 100644 --- a/en/using-d-i/modules/i386/lilo-installer.xml +++ b/en/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>LILO</command> Boot Loader on a Hard Disk</title> <para> diff --git a/es/administrivia/administrivia.xml b/es/administrivia/administrivia.xml index 5afb7d927..222f5425c 100644 --- a/es/administrivia/administrivia.xml +++ b/es/administrivia/administrivia.xml @@ -127,7 +127,7 @@ La seccin en este manual de instalaciones en entornos de chroot (<xref linkend="linux-upgrade"/>) se ha basado en parte de documentos sobre los que Karsten M. Self tiene derechos de copia. -</para><para arch="i386"> +</para><para arch="x86"> La seccin en este manual que cubre las instalaciones a travs plip (<xref linkend="plip"/>) est basada en el diff --git a/es/appendix/chroot-install.xml b/es/appendix/chroot-install.xml index 0746e1605..e6e451447 100644 --- a/es/appendix/chroot-install.xml +++ b/es/appendix/chroot-install.xml @@ -427,7 +427,7 @@ para cargar el ncleo instalado en su nueva particin raz. Tenga en cuenta que debootstrap no instala un gestor de arranque, pero puede usar apt-get dentro de su jaula Debian para hacer esto. -</para><para arch="i386"> +</para><para arch="x86"> Use <userinput>info grub</userinput> o <userinput>man lilo.conf</userinput> para leer las instrucciones sobre cmo @@ -439,7 +439,7 @@ nuevo sistema y editarlo all. Ejecute lilo una vez termine de editar el fichero (recuerde que ste usar el <filename>lilo.conf</filename> relativo al sistema desde el cual lo ejecute). -</para><para arch="i386"> +</para><para arch="x86"> Aqu tiene un ejemplo bsico de /etc/lilo.conf: diff --git a/es/appendix/plip.xml b/es/appendix/plip.xml index 92166d8fb..446ffea70 100644 --- a/es/appendix/plip.xml +++ b/es/appendix/plip.xml @@ -3,7 +3,7 @@ <!-- revisado por ender, 31 dic 2005 --> <!-- traducido por jfs, 30 dic 2005 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Instalar &debian; a travs de una lnea IP paralela (PLIP)</title> <para> diff --git a/es/boot-installer/boot-installer.xml b/es/boot-installer/boot-installer.xml index ee3037a9f..12b0e3d39 100644 --- a/es/boot-installer/boot-installer.xml +++ b/es/boot-installer/boot-installer.xml @@ -6,7 +6,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Arranque del instalador en &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/es/boot-installer/i386.xml b/es/boot-installer/i386.xml index 8f7cb274d..45ee8d48a 100644 --- a/es/boot-installer/i386.xml +++ b/es/boot-installer/i386.xml @@ -4,7 +4,7 @@ <!-- revisado Francisco Garca <franciscomanuel.garcia@hispalinux.es>, 27 enero 2005 --> <!-- revisado rudy, 24 feb. 2005 --> - <sect2 arch="i386"><title>Arranque desde un CD-ROM</title> + <sect2 arch="x86"><title>Arranque desde un CD-ROM</title> &boot-installer-intro-cd.xml; @@ -77,7 +77,7 @@ Arranca la variante <quote>bf2.4</quote>. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Arranque desde una particin de DOS</title> &boot-installer-intro-hd.xml; @@ -108,7 +108,7 @@ la variante bf2.4. El sntoma de este problema es el mensaje de error END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Arranque desde linux usando <command>LILO</command> o <command>GRUB</command></title> @@ -198,7 +198,7 @@ Desde este momento en adelante, no habr diferencia entre </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Arranque desde un dispositivo de memoria USB</title> <para> @@ -213,7 +213,7 @@ ingresar argumentos de arranque adicionales o simplemente presionar </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Arranque desde disquetes</title> <para> @@ -276,7 +276,7 @@ automticamente. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Arranque con TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Arranque con TFTP</title> &boot-installer-intro-net.xml; @@ -324,7 +324,7 @@ arranque usando TFTP. </sect2> - <sect2 arch="i386"><title>El cursor de arranque</title> + <sect2 arch="x86"><title>El cursor de arranque</title> <para> Cuando arranca el instalador, se le presentar una pantalla grfica amigable diff --git a/es/boot-installer/intro-cd.xml b/es/boot-installer/intro-cd.xml index 926dfd34d..df445dd3b 100644 --- a/es/boot-installer/intro-cd.xml +++ b/es/boot-installer/intro-cd.xml @@ -7,7 +7,7 @@ Para la mayora de personas la forma ms fcil es usar un juego de CDs de Debian. Si tiene un juego de CDs y su mquina puede arrancar directamente desde el CD, excelente!. Simplemente -<phrase arch="i386"> +<phrase arch="x86"> configure su sistema para arrancar desde un CD como se describe en la <xref linkend="boot-dev-select"/>, </phrase> diff --git a/es/boot-installer/parameters.xml b/es/boot-installer/parameters.xml index 10ffaaef7..914911edb 100644 --- a/es/boot-installer/parameters.xml +++ b/es/boot-installer/parameters.xml @@ -240,7 +240,7 @@ Algunos sntomas de este problema son mensajes que traten sobre <quote>bterm</qu la aparicin de una pantalla en blanco o que el sistema se quede congelado algunos minutos despus de iniciarse la instalacin. -</para><para arch="i386"> +</para><para arch="x86"> Tambin puede utilizar el argumento <userinput>video=vga16:off</userinput> para deshabilitar el uso del ncleo framebuffer. Los problemas antes indicados se han diff --git a/es/boot-installer/trouble.xml b/es/boot-installer/trouble.xml index b76b1e8a8..be0565053 100644 --- a/es/boot-installer/trouble.xml +++ b/es/boot-installer/trouble.xml @@ -76,7 +76,7 @@ para el instalador. A menudo, se pueden solventar los problemas desconectando algunos perifricos y elementos aadidos e intentando de nuevo el arranque. -<phrase arch="i386">Algunos mdems internos, tarjetas de sonido, y +<phrase arch="x86">Algunos mdems internos, tarjetas de sonido, y dispositivos Plug-n-Play pueden ser especialmente problemticos. </phrase> @@ -91,7 +91,7 @@ bloquea cuando arranca el ncleo, utilice, por ejemplo, </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Problemas comnes durante la instalacin en &arch-title;</title> <para> diff --git a/es/hardware/hardware-supported.xml b/es/hardware/hardware-supported.xml index 4447dfee3..16433870e 100644 --- a/es/hardware/hardware-supported.xml +++ b/es/hardware/hardware-supported.xml @@ -220,7 +220,7 @@ url="&url-list-subscribe;">lista de correo de debian-&arch-listname;</ulink>. <sect2 id="gfx" arch="not-s390"><title>Tarjeta grfica</title> -<para arch="i386"> +<para arch="x86"> Debe utilizar una interfaz de visualizacin compatible con VGA para la terminal de consola. Prcticamente cualquier tarjeta de vdeo moderna es @@ -259,7 +259,7 @@ compatibilidad</ulink> para las placas de evaluacin Broadcom. </para> </sect2> - <sect2 arch="i386" id="laptops"><title>Ordenadores porttiles</title> + <sect2 arch="x86" id="laptops"><title>Ordenadores porttiles</title> <para> Tambin se soportan los ordenadores porttiles. stos generalmente son diff --git a/es/hardware/installation-media.xml b/es/hardware/installation-media.xml index 01e21246a..18f42e327 100644 --- a/es/hardware/installation-media.xml +++ b/es/hardware/installation-media.xml @@ -55,7 +55,7 @@ para instalar su sistema, una vez arrancado a travs de otros mecanismos incluso si su sistema no soporta el arranque desde CD-ROM, consulte el <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Se soportan tanto CD-ROMs IDE/ATAPI como SCSI. Adems, todas las interfaces no estndar de CD soportadas por Linux estn soportadas por @@ -66,7 +66,7 @@ funcionar, y el arranque desde estas interfaces no estndar es poco probable. El <ulink url="&url-cd-howto;">CMO de Linux CD-ROM</ulink> contiene informacin en detalle sobre el uso de CD-ROMs con Linux. -</para><para arch="i386"> +</para><para arch="x86"> Tambin existe soporte para unidades de CD-ROM USB, as como los dispositivos FireWire que estn soportados por los controladores ohci1394 y sbp2. @@ -227,14 +227,14 @@ ncleo). Para poder asegurar que Debian pueda instalarse en la mayor cantidad de hardware posible se incluye soporte para el rango ms amplio de dispositivos posibles. -</para><para arch="i386"> +</para><para arch="x86"> Generalmente, el sistema de instalacin de Debian incluye soporte para disquetes, unidades IDE, disquetes IDE, dispositivos IDE en el puerto paralelo, controladoras y unidades SCSI. Los sistemas de ficheros soportados incluyen, entre otros: MINIX, FAT, extensiones FAT Win-32 (VFAT) y NTFS. -</para><para arch="i386"> +</para><para arch="x86"> Se ofrece soporte para las interfaces de disco que emulan la interfaz de disco duro <quote>AT</quote>, con frecuencia llamadas MFM, RLL, IDE o ATA. Se diff --git a/es/hardware/network-cards.xml b/es/hardware/network-cards.xml index 840a62d63..4fd37a1d5 100644 --- a/es/hardware/network-cards.xml +++ b/es/hardware/network-cards.xml @@ -5,7 +5,7 @@ <sect1 id="network-cards"> <title>Hardware de conectividad de red</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -26,7 +26,7 @@ tarjetas como los protocolos. soporte cualquier otra tarjeta y luego sustituirlo en el instalador (vea <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> Con respecto a RDSI (ISDN), el protocolo de canal D para el (antiguo) 1TR6 alemn no est soportado; las tarjetas RDSI Spellcaster BRI diff --git a/es/hardware/supported-peripherals.xml b/es/hardware/supported-peripherals.xml index 6f757a67a..ea0e20aa9 100644 --- a/es/hardware/supported-peripherals.xml +++ b/es/hardware/supported-peripherals.xml @@ -12,13 +12,13 @@ pueden ser: ratones, impresoras, escneres y dispositivos PCMCIA y USB. Sin embargo, muchos de stos no son necesarios durante la instalacin del sistema. -</para><para arch="i386"> +</para><para arch="x86"> Generalmente el hardware USB funciona bien, solamente puede ser necesario configuracin adicional con algunos teclados USB (consulte <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Consulte el <ulink url="&url-hardware-howto;">CMO de compatibilidad hardware de Linux</ulink> para determinar si Linux ofrece soporte para @@ -62,7 +62,7 @@ hardware est bien soportado por GNU/Linux. Desafortunadamente es muy raro encontrar un fabricante que venda mquinas nuevas &arch-title;. -</para><para arch="i386"> +</para><para arch="x86"> Consulte detenidamente la licencia de software que viene con Windows si tiene que comprar un equipo que provea este sistema operativo @@ -115,7 +115,7 @@ mercado importante. </sect2> - <sect2 arch="i386"><title>Hardware especfico para Windows</title> + <sect2 arch="x86"><title>Hardware especfico para Windows</title> <para> Una tendencia preocupante es la proliferacin de mdems e impresoras diff --git a/es/hardware/supported/i386.xml b/es/hardware/supported/i386.xml index 3a1380f5e..6f5bafa92 100644 --- a/es/hardware/supported/i386.xml +++ b/es/hardware/supported/i386.xml @@ -4,7 +4,7 @@ <!-- revisado por nahoo, 11 octubre 2004 --> <!-- revisado por Rudy Godoy, 22 feb. 2005 --> - <sect2 arch="i386"><title>Soporte de CPU, placas base y vdeo</title> + <sect2 arch="x86"><title>Soporte de CPU, placas base y vdeo</title> <para> Puede encontrar informacin detallada respecto a los dispositivos diff --git a/es/howto/installation-howto.xml b/es/howto/installation-howto.xml index 84eaef4d2..9606e8ee3 100644 --- a/es/howto/installation-howto.xml +++ b/es/howto/installation-howto.xml @@ -80,7 +80,7 @@ primer CD del conjunto de CDs de Debian. </para><para> Descargue la imagen que prefiera y grbela en un CD. -<phrase arch="i386">Para arrancar el CD, puede que necesite modificar la +<phrase arch="x86">Para arrancar el CD, puede que necesite modificar la configuracin de su BIOS, como se detalla en <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> Para arrancar un PowerMac desde el CD, pulse la tecla <keycap>c</keycap> @@ -169,7 +169,7 @@ ms detalles, vea <xref linkend="boot-usb-files" />. El arranque de sistemas desde dispositivos de almacenamiento USB requiere el uso manual de OpenFirmware. Para ms indicaciones, vea <xref linkend="usb-boot" />. -</para><para arch="i386"> +</para><para arch="x86"> Algunas BIOS pueden arrancar directamente desde dispositivos de almacenamiento USB, pero otras no. Puede que necesite configurar su BIOS @@ -190,7 +190,7 @@ arquitectura y configuracin de arranque desde red. Los ficheros en <filename>netboot/</filename> pueden usarse para arrancar el &d-i; desde la red. -</para><para arch="i386"> +</para><para arch="x86"> La forma ms fcil de configurar el arranque desde red probablemente sea usando PXE. Extraiga el fichero @@ -214,7 +214,7 @@ diferente. Descargue <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, y una imagen de CD de Debian en el directorio de nivel ms alto en el disco duro. Asegrese de que la imagen de CD tiene un nombre de fichero que termine en <literal>.iso</literal>. Ahora slo es cuestin -de arrancar linux con initrd. <phrase arch="i386"> <xref +de arrancar linux con initrd. <phrase arch="x86"> <xref linkend="boot-initrd" /> explica una forma de hacerlo. </phrase> </para> @@ -227,7 +227,7 @@ linkend="boot-initrd" /> explica una forma de hacerlo. </phrase> Una vez que se inicie el instalador, se le mostrar una pantalla inicial de bienvenida. Pulse &enterkey; para arrancar, o lea las instrucciones para obtener informacin de otros mtodos y parmetros para la instalacin (vea <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Si desea un ncleo 2.4, escriba <userinput>install24</userinput> en el cursor <prompt>boot:</prompt>. <footnote><para> @@ -272,7 +272,7 @@ su disco. Esta opcin es la ms recomendable para usuarios noveles o alguien con prisa. Escoja la configuracin manual en el men si no desea particionado automtico. -</para><para arch="i386"> +</para><para arch="x86"> Si tiene una particin DOS o Windows que quiera preservar, tenga cuidado con el particionado automtico. Si elije particionado manual, puede usar el instalador @@ -300,7 +300,7 @@ la instalacin del ncleo. El ltimo paso es la instalacin del gestor de arranque. El instalador aadir automticamente al men de arranque y mostrar un aviso si detecta otros sistemas operativos en su ordenador. -<phrase arch="i386">GRUB se instala de forma predeterminada en el sector de +<phrase arch="x86">GRUB se instala de forma predeterminada en el sector de arranque del primer disco duro, lo que generalmente es una buena eleccin. Podr cambiarlo e instalarlo en otra ubicacin si as lo desea.</phrase> diff --git a/es/install-methods/boot-drive-files.xml b/es/install-methods/boot-drive-files.xml index 2a2e25494..2e83ce943 100644 --- a/es/install-methods/boot-drive-files.xml +++ b/es/install-methods/boot-drive-files.xml @@ -18,7 +18,7 @@ usando esta tcnica. Esto evita todas las molestias de los medios extrables, como encontrar y quemar las imgenes de CD o batallar con muchos, y poco fiables, disquetes. -</para><para arch="i386"> +</para><para arch="x86"> El instalador no puede arrancar desde ficheros ubicados en un sistema de ficheros NTFS. @@ -43,7 +43,7 @@ desde disco duro, dependiendo de si el sistema es un modelo <quote>NewWorld</quo </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Arranque desde el disco duro usando <command>LILO</command> o <command>GRUB</command></title> <para> diff --git a/es/install-methods/boot-usb-files.xml b/es/install-methods/boot-usb-files.xml index b2eb7a9d1..943209d98 100644 --- a/es/install-methods/boot-usb-files.xml +++ b/es/install-methods/boot-usb-files.xml @@ -26,7 +26,7 @@ Note que el dispositivo USB, deber tener por lo menos una capacidad de 256 MB <sect2 id="usb-copy-easy"> <title>Copiado de los ficheros — la forma fcil</title> -<para arch="i386"> +<para arch="x86"> Existe un fichero todo en uno <filename>hd-media/boot.img.gz</filename> que contiene todos los ficheros del instalador (incluyendo el ncleo) @@ -66,11 +66,11 @@ su memoria USB. <para> Despus, monte la memoria USB (<userinput> -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), que ahora tendr un sistema de ficheros -<phrase arch="i386">FAT</phrase> +<phrase arch="x86">FAT</phrase> <phrase arch="powerpc">HFS</phrase> en ella, y copie una imagen ISO netinst o bussinesscard de Debian en ella. Por favor, tenga en cuenta que el nombre del fichero debe terminar en @@ -122,7 +122,7 @@ Cuando finalice, desmonte el dispositivo USB (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Arranque con la memoria USB</title> <warning><para> diff --git a/es/install-methods/install-tftp.xml b/es/install-methods/install-tftp.xml index 57b942f8a..7143721bc 100644 --- a/es/install-methods/install-tftp.xml +++ b/es/install-methods/install-tftp.xml @@ -76,7 +76,7 @@ usar cualquier servidor, en cualquier plataforma, que implemente este protocolo. En los ejemplos de esta seccin, mostraremos rdenes para SunOS 4.x, SunOS 5.x (conocido tambin como Solaris) y GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> Para usar el mtodo de arranque de TFTP llamado Pre-boot Execution Environment (PXE) tiene que utilizar un servidor @@ -171,7 +171,7 @@ arranque a travs de red, use <filename>yaboot-netboot.conf</filename>. Simplemente renmbrelo a <filename>yaboot.conf</filename> en el directorio de TFTP. -</para><para arch="i386"> +</para><para arch="x86"> Para arranque PXE, todo lo que necesitar es colocar el fichero tar <filename>netboot/netboot.tar.gz</filename>. Simplemente diff --git a/es/install-methods/tftp/dhcp.xml b/es/install-methods/tftp/dhcp.xml index 0655d7f31..c5f85c256 100644 --- a/es/install-methods/tftp/dhcp.xml +++ b/es/install-methods/tftp/dhcp.xml @@ -53,7 +53,7 @@ reincielo con <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Habilitar el arranque PXE en la configuracin DHCP</title> <para> Aqu hay otro ejemplo para un <filename>dhcp.conf</filename> usando el diff --git a/es/install-methods/usb-setup/i386.xml b/es/install-methods/usb-setup/i386.xml index 136b1fbb0..478ad8a0f 100644 --- a/es/install-methods/usb-setup/i386.xml +++ b/es/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Particionado de las memorias USB en &arch-title;</title> <para> diff --git a/es/partitioning/device-names.xml b/es/partitioning/device-names.xml index 687b800e7..037c5db8b 100644 --- a/es/partitioning/device-names.xml +++ b/es/partitioning/device-names.xml @@ -69,12 +69,12 @@ programa para mac pdisk (p. ej. lo que se muestra como </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> El primer disco XT se llama <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> El segundo disco XT se llama <filename>/dev/xdb</filename>. @@ -127,7 +127,7 @@ controladores), el orden de las unidades puede confundirse. La mejor solucin para este caso es revisar los mensajes de arranque del sistema, asumiendo que conoce los modelos de los dispositivos y/o las capacidades. -</para><para arch="i386"> +</para><para arch="x86"> Linux representa la particin primaria como el nombre del dispositivo, ms un nmero del 1 al 4. Por ejemplo, la primera particin en la primera diff --git a/es/partitioning/partition-programs.xml b/es/partitioning/partition-programs.xml index b0fdd20e3..80413be8b 100644 --- a/es/partitioning/partition-programs.xml +++ b/es/partitioning/partition-programs.xml @@ -22,7 +22,7 @@ pueden aplicar a su arquitectura. Herramienta original de Linux para particionar discos. Esta navaja suiza tambin puede ajustar el tamao de las particiones, -crear sistemas de ficheros <phrase arch="i386"> +crear sistemas de ficheros <phrase arch="x86"> (como se llama en Windows a <quote>formatear</quote>) </phrase> y asignarlos a sus respectivos puntos de montaje. @@ -152,7 +152,7 @@ sus mdulos deber ejecutar: # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">No se olvide de marcar su particin +<phrase arch="x86">No se olvide de marcar su particin como <quote>Bootable</quote> (arrancable).</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/es/partitioning/partition/i386.xml b/es/partitioning/partition/i386.xml index 3031ebd02..5b2fed87e 100644 --- a/es/partitioning/partition/i386.xml +++ b/es/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 35590 --> <!-- revisado por rudy, 24 feb. 2005 --> - <sect2 arch="i386"><title>Particionado en &arch-title;</title> + <sect2 arch="x86"><title>Particionado en &arch-title;</title> <para> Puede tener que ajustar el tamao de su particin para disponer diff --git a/es/post-install/kernel-baking.xml b/es/post-install/kernel-baking.xml index 8694b7058..64cc9f692 100644 --- a/es/post-install/kernel-baking.xml +++ b/es/post-install/kernel-baking.xml @@ -172,7 +172,7 @@ personalizado como cualquier paquete. Como superusuario, ejecute </phrase> La parte <replaceable>subarquitectura</replaceable> es una subarquitectura opcional, -<phrase arch="i386"> como <quote>i586</quote>, </phrase> dependiendo de las opciones +<phrase arch="x86"> como <quote>i586</quote>, </phrase> dependiendo de las opciones que haya establecido en el ncleo. <userinput>dpkg -i</userinput> instalar el ncleo, junto con otros ficheros de soporte. Por ejemplo, diff --git a/es/post-install/reactivating-win.xml b/es/post-install/reactivating-win.xml index e9e8bd3c3..5a411a709 100644 --- a/es/post-install/reactivating-win.xml +++ b/es/post-install/reactivating-win.xml @@ -3,7 +3,7 @@ <!-- actualizada orig. ver.: Rudy, 5 diciembre 2004 --> <!-- revisado Rudy Godoy, 23 feb. 2005 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivar DOS y Windows</title> <para> diff --git a/es/post-install/rescue.xml b/es/post-install/rescue.xml index aa0821b56..c24d0496b 100644 --- a/es/post-install/rescue.xml +++ b/es/post-install/rescue.xml @@ -44,7 +44,7 @@ El instalador le presentar, si puede, un intrprete de lnea de rdenes en el sistema de ficheros que ha seleccionado para que lleve a cabo las reparaciones que necesite. -<phrase arch="i386"> +<phrase arch="x86"> Por ejemplo, si necesita reinstalar el cargador de arranque GRUB en el <quote>master boot record</quote> del primer disco duro, puede ejecutar la orden <userinput>grub-install '(hd0)'</userinput> para hacerlo. diff --git a/es/preparing/bios-setup/i386.xml b/es/preparing/bios-setup/i386.xml index 176e424a3..220410e7a 100644 --- a/es/preparing/bios-setup/i386.xml +++ b/es/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> <!-- revisado por nahoo, 24 octubre 2004 --> - <sect2 arch="i386" id="bios-setup"><title>Utilizacin del men de configuracin de la BIOS</title> + <sect2 arch="x86" id="bios-setup"><title>Utilizacin del men de configuracin de la BIOS</title> <para> @@ -102,7 +102,7 @@ Busque en <ulink url="&url-simtel;"></ulink>. </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Seleccin de dispositivo + <sect2 arch="x86" id="boot-dev-select"><title>Seleccin de dispositivo de arranque</title> <para> @@ -234,7 +234,7 @@ presionar <keycap>F10</keycap>. </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Configuraciones de la BIOS miscelneas</title> <sect3 id="cd-settings"><title>Configuraciones de CD-ROM</title> diff --git a/es/preparing/minimum-hardware-reqts.xml b/es/preparing/minimum-hardware-reqts.xml index 70a1b2ee1..4bdd4a715 100644 --- a/es/preparing/minimum-hardware-reqts.xml +++ b/es/preparing/minimum-hardware-reqts.xml @@ -17,7 +17,7 @@ hardware recomendado listado en la siguiente tabla. Sin embargo, la mayora de usuarios se arriesgan a terminar frustrados si ignoran estas sugerencias. -</para><para arch="i386"> +</para><para arch="x86"> Se recomienda como mnimo un Pentium de 100 Mhz para un sistema de escritorio y un Pentium II de 300 Mhz para un servidor. diff --git a/es/preparing/needed-info.xml b/es/preparing/needed-info.xml index c20f32017..87aa1fd9f 100644 --- a/es/preparing/needed-info.xml +++ b/es/preparing/needed-info.xml @@ -55,8 +55,8 @@ hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">CMO de compatibilidad de hardware de Linux</ulink> @@ -180,7 +180,7 @@ Las cajas y cubiertas de cada pieza de hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> La ventana del sistema en el panel de control de Windows. @@ -220,7 +220,7 @@ para configurar su red y su correo electrnico. </row> <row arch="not-s390"><entry>Su orden en el sistema.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Si es IDE SCSI (la mayora de ordenadores usan IDE).</entry> </row> <row arch="m68k"> @@ -303,12 +303,12 @@ Por otro lado, el hardware para Linux est mejorando cada da. Sin embargo, Linux todava no se puede ejecutar en tantos tipos de hardware como otros sistemas operativos. -</para><para arch="i386"> +</para><para arch="x86"> En particular, Linux normalmente no puede usar dispositivos que necesiten una versin de Windows ejecutndose para funcionar. -</para><para arch="i386"> +</para><para arch="x86"> Aunque algunos dispositivos especficos de Windows puedan usarse en Linux, normalmente requieren un esfuerzo adicional. Adems, @@ -316,7 +316,7 @@ los controladores de Linux de dispositivos especficos para Windows suelen ir ligados a un ncleo Linux en concreto. Como consecuencia, pueden volverse obsoletos rpidamente. -</para><para arch="i386"> +</para><para arch="x86"> Los dispositivos ms comunes de este tipo son los llamados winmdems. Sin embargo, las impresoras y otros dispositivos tambin pueden ser diff --git a/es/preparing/non-debian-partitioning.xml b/es/preparing/non-debian-partitioning.xml index 4c4ad0599..09be103cd 100644 --- a/es/preparing/non-debian-partitioning.xml +++ b/es/preparing/non-debian-partitioning.xml @@ -23,7 +23,7 @@ mquina significa un invitado LPAR o VM en este caso. Si ya tiene un sistema operativo en su ordenador -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -51,7 +51,7 @@ Debian. Puede encontrar informacin del estado actual de sus particiones usando una herramienta de particionado para su sistema operativo actual -<phrase arch="i386">, como fdisk o PartitionMagic</phrase> +<phrase arch="x86">, como fdisk o PartitionMagic</phrase> <phrase arch="powerpc">, como Drive Setup, HD Toolkit o MacTools</phrase> <phrase arch="m68k">, como HD SC Setup, HDToolBox o SCSITool</phrase> <phrase arch="s390">, como el VM diskmap</phrase> @@ -105,7 +105,7 @@ puesto que podra haber circunstancias especiales, tales como el orden de las particiones existentes en el mapa de particiones, que inevitablemente le fuercen a particionar antes de instalar. -</para><para arch="i386"> +</para><para arch="x86"> Si su mquina tiene un sistema de ficheros FAT o NTFS, como el que usa DOS y Windows, puede esperar y usar el diff --git a/es/preparing/nondeb-part/i386.xml b/es/preparing/nondeb-part/i386.xml index 23faa5057..193ef1cad 100644 --- a/es/preparing/nondeb-part/i386.xml +++ b/es/preparing/nondeb-part/i386.xml @@ -3,7 +3,7 @@ <!-- revisado por nahoo, 23 octubre 2004 --> <!-- revisado Rudy Godoy, 22 feb. 2005 --> - <sect2 arch="i386"><title>Particionado desde DOS o Windows</title> + <sect2 arch="x86"><title>Particionado desde DOS o Windows</title> <para> Es recomendable que use o bien el esquema mostrado a continuacin o diff --git a/es/preparing/pre-install-bios-setup.xml b/es/preparing/pre-install-bios-setup.xml index e4e71e158..6d404eee5 100644 --- a/es/preparing/pre-install-bios-setup.xml +++ b/es/preparing/pre-install-bios-setup.xml @@ -59,7 +59,7 @@ ARREGLAME: es necesaria ms informacin sobre ste problema. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> Las mejores placas base soportan RAM con paridad y le avisarn si se produce un fallo de bit simple en la RAM de su sistema. Desafortunadamente, no @@ -70,7 +70,7 @@ inadvertidamente insertando errores en sus datos. Por eso los mejores sistemas tienen placas base que soportan mdulos con paridad y con paridad real; consulte <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Asegrese de habilitar cualquier configuracin del BIOS que pueda causar la interrupcin de la placa base al producirse errores de paridad de @@ -78,7 +78,7 @@ memoria si tiene RAM de paridad real y su placa base puede manejarla. </para> - <sect3 arch="i386"><title>El interruptor turbo</title> + <sect3 arch="x86"><title>El interruptor turbo</title> <para> Muchos sistemas tienen un interruptor <emphasis>turbo</emphasis> que @@ -94,7 +94,7 @@ dispositivos hardware). </para> </sect3> - <sect3 arch="i386"><title>Procesadores Cyrix y errores de disquete</title> + <sect3 arch="x86"><title>Procesadores Cyrix y errores de disquete</title> <para> Muchos usuarios de procesadores Cyrix han tenido que deshabilitar la cach @@ -114,7 +114,7 @@ con la cach al pasar de cdigo de 16 a 32 bits. </para> </sect3> - <sect3 arch="i386"><title>Configuracin de hardware perifrico</title> + <sect3 arch="x86"><title>Configuracin de hardware perifrico</title> <para> Podra necesitar cambiar la configuracin o los conectores (jumpers, @@ -134,7 +134,7 @@ superior al total de la RAM instalada en su sistema. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"><title>Soporte de USB en la BIOS y teclados USB</title> + <sect3 arch="x86" id="usb-keyboard-config"><title>Soporte de USB en la BIOS y teclados USB</title> <para> Si no tiene teclados de estilo AT sino solamente un modelo USB, diff --git a/es/using-d-i/modules/clock-setup.xml b/es/using-d-i/modules/clock-setup.xml index 709fa6ec4..acae4f558 100644 --- a/es/using-d-i/modules/clock-setup.xml +++ b/es/using-d-i/modules/clock-setup.xml @@ -21,7 +21,7 @@ en el modo experto. generalmente estn fijados a la hora local. Si desea poder cargar dos sistemas operativos distintos debe elegir la hora local en lugar de la hora GMT.</phrase> -<phrase arch="i386">Los sistemas que tambin pueden ejecutar Dos +<phrase arch="x86">Los sistemas que tambin pueden ejecutar Dos o Windows estn fijados a la hora local. Si desea poder cargar dos sistemas operativos distintos debe elegir la hora local en lugar de la hora GMT.</phrase> diff --git a/es/using-d-i/modules/i386/grub-installer.xml b/es/using-d-i/modules/i386/grub-installer.xml index af7b3d961..c33500b6d 100644 --- a/es/using-d-i/modules/i386/grub-installer.xml +++ b/es/using-d-i/modules/i386/grub-installer.xml @@ -2,7 +2,7 @@ <!-- original version: 18640 --> <!-- revisado jfs, 31 octubre 2004 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalacin del gestor de arranque <command>Grub</command> en un disco duro</title> <para> diff --git a/es/using-d-i/modules/i386/lilo-installer.xml b/es/using-d-i/modules/i386/lilo-installer.xml index 052108f82..499131858 100644 --- a/es/using-d-i/modules/i386/lilo-installer.xml +++ b/es/using-d-i/modules/i386/lilo-installer.xml @@ -3,7 +3,7 @@ <!-- revisado jfs, 31 octubre 2004 --> <!-- revisado Rudy Godoy, 22 feb. 2005 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalacin del gestor de arranque <command>LILO</command> en un disco duro</title> <para> diff --git a/eu/appendix/chroot-install.xml b/eu/appendix/chroot-install.xml index 96b219177..c33424c64 100644 --- a/eu/appendix/chroot-install.xml +++ b/eu/appendix/chroot-install.xml @@ -487,7 +487,7 @@ Then install your choice using its package name. To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. -</para><para arch="i386"> +</para><para arch="x86"> Check <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install @@ -496,7 +496,7 @@ lilo.conf. You could also copy it to the new system and edit it there. After you are done editing, call lilo (remember it will use lilo.conf relative to the system you call it from). -</para><para arch="i386"> +</para><para arch="x86"> Here is a basic /etc/lilo.conf as an example: @@ -541,7 +541,7 @@ label=Debian On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. -</para><para arch="not-i386;not-powerpc"> +</para><para arch="not-x86;not-powerpc"> <phrase condition="FIXME"> FIXME: Someone may eventually supply an example for this architecture. diff --git a/eu/boot-installer/i386.xml b/eu/boot-installer/i386.xml index 0867c918a..6a2727f83 100644 --- a/eu/boot-installer/i386.xml +++ b/eu/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 16879 untranslated --> - <sect2 arch="i386"><title>Booting from a CD-ROM</title> + <sect2 arch="x86"><title>Booting from a CD-ROM</title> &boot-installer-intro-cd.xml; @@ -98,7 +98,7 @@ installing via this method. - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -130,7 +130,7 @@ bf2.4 flavor. The symptom of the problem is an </sect2> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Booting from linux using <command>LILO</command> or <command>GRUB</command></title> <para> @@ -273,7 +273,7 @@ your hard drive will be un-bootable for a short period of time. </para> </sect2> - <sect2 arch="i386" id="usb-boot"> + <sect2 arch="x86" id="usb-boot"> <title>Booting from USB memory stick</title> <para> @@ -296,7 +296,7 @@ it asks for the root floppy, simply press &enterkey;. You should see </para> </sect2> - <sect2 arch="i386" id="floppy-boot"> + <sect2 arch="x86" id="floppy-boot"> <title>Booting from Floppies</title> <para> @@ -374,7 +374,7 @@ contents are loaded into memory. The installer program </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title> &boot-installer-intro-net.xml; @@ -449,7 +449,7 @@ debian/dists/sarge/main/installer-i386/current/doc/INSTALLATION-HOWTO </sect3> </sect2> - <sect2 arch="i386"><title>i386 Boot Parameters</title> + <sect2 arch="x86"><title>i386 Boot Parameters</title> <para> If you are booting from the boot floppy or from CD-ROM you will be @@ -498,7 +498,7 @@ console features. See <xref linkend="boot-parms"/> for details. </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>System freeze during the PCMCIA configuration phase</title> <para> @@ -527,7 +527,7 @@ installer. </para> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>System freeze while loading the USB modules</title> <para> diff --git a/eu/boot-installer/intro-cd.xml b/eu/boot-installer/intro-cd.xml index 4959075fa..fd4655de0 100644 --- a/eu/boot-installer/intro-cd.xml +++ b/eu/boot-installer/intro-cd.xml @@ -7,7 +7,7 @@ The easiest route for most people will be to use a <ulink url="http://www.debian.org/CD/vendors/">set of Debian CDs</ulink>. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply -<phrase arch="i386"> +<phrase arch="x86"> configure your system for booting off a CD as described in <xref linkend="boot-dev-select"/>, </phrase> diff --git a/eu/boot-installer/parameters.xml b/eu/boot-installer/parameters.xml index b8a9c9784..5367d8c43 100644 --- a/eu/boot-installer/parameters.xml +++ b/eu/boot-installer/parameters.xml @@ -214,7 +214,7 @@ you can disable the feature by the parameter symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="i386"> +</para><para arch="x86"> The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell diff --git a/eu/boot-installer/trouble.xml b/eu/boot-installer/trouble.xml index 2db641c44..b393ca3d9 100644 --- a/eu/boot-installer/trouble.xml +++ b/eu/boot-installer/trouble.xml @@ -67,7 +67,7 @@ your kernel. The installer requires </para><para> Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> </para><para> @@ -168,7 +168,7 @@ report, this information will be included automatically. <informalexample><screen> -<phrase arch="i386"> +<phrase arch="x86"> flavor: <replaceable>flavor of image you are using</replaceable> </phrase> architecture: &architecture; diff --git a/eu/boot-new/modules/timezone.xml b/eu/boot-new/modules/timezone.xml index b6bdec6a2..0fad9e902 100644 --- a/eu/boot-new/modules/timezone.xml +++ b/eu/boot-new/modules/timezone.xml @@ -9,7 +9,7 @@ Ongietorri pantailaren ondoren denbora zonaldea ezartzea esaktuko da. Lehenik hardware erlojua ordu lokalean edo Greenwich Merdiano Orduan (GMT edo UTC) ezarriko den aukeratu behar da. Bistaraziko den orduak aukeraketa egiten lagundu beharko lizuke. <phrase arch="m68k;powerpc">Macintosh hardware ordualria normalean ordu lokalean ezarririk daude. Abiarazte dualeko sistema bat instalatu nahi ezkero aukeratu ordu lokala GMT orduaren ordez.</phrase> -<phrase arch="i386">Dos edo Windows ere instalaturik duten sistemek normalean ordu lokala erabiltzen dute. Abiarazte dualeko sistema bat instalatu nahi ezkero aukeratu ordu lokala GMT orduaren ordez.</phrase> +<phrase arch="x86">Dos edo Windows ere instalaturik duten sistemek normalean ordu lokala erabiltzen dute. Abiarazte dualeko sistema bat instalatu nahi ezkero aukeratu ordu lokala GMT orduaren ordez.</phrase> </para><para> diff --git a/eu/hardware/hardware-supported.xml b/eu/hardware/hardware-supported.xml index e27e3b428..e60c75021 100644 --- a/eu/hardware/hardware-supported.xml +++ b/eu/hardware/hardware-supported.xml @@ -205,7 +205,7 @@ erabiltzea. <sect2 id="gfx" arch="not-s390"><title>Txartel grafikoa</title> -<para arch="i386"> +<para arch="x86"> Zuk VGA edo baterqagarria den bistaratze interfaze bat izan duzu kontsola terminalerako. Gau egungo txartel grafiko berri guztiak @@ -228,7 +228,7 @@ XFree86 X11 sistema SGI Indy-etan bakarrik onartzen da. </para> </sect2> - <sect2 arch="i386" id="laptops"><title>Eramangarria</title> + <sect2 arch="x86" id="laptops"><title>Eramangarria</title> <para> Eramangarriak ere inartzen dita nahiz eta berezi edo jabetzapeko diff --git a/eu/hardware/installation-media.xml b/eu/hardware/installation-media.xml index eb2f62127..9db1339d1 100644 --- a/eu/hardware/installation-media.xml +++ b/eu/hardware/installation-media.xml @@ -49,7 +49,7 @@ beharko zenuke. NAhiz eta sistemak ez CD-ROM-etik abiarazterik onartu, berau beste instalazio medio batekin batera erabili daiteke; begiratu <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Bai SCSI bai IDE/ATAPI CD irakurleak onartzen dira, hauetaz gain estandarretik kanpoko eta linux kernelak onartzen dituen gailuak @@ -61,7 +61,7 @@ abiarazteak ez du funtzionatzen. CD-rom linuxen erabiltzeari buruzuko argibide sakonagoak ditu. -</para><para arch="i386"> +</para><para arch="x86"> USB CD-ROM gailuak ere onartzen dira, baita ere ohci1394 eta sbp2 driberrak onartzen dituzten firewire gailuak. @@ -217,7 +217,7 @@ sortzeko argibideentzat). Ahalik eta gailu gehienen onarpena ziurtatu dago orokorrean ahalik eta hardware ezberdinetan instalatu ahal izateko. -</para><para arch="i386"> +</para><para arch="x86"> Orokorrean, Debian instalazio sistemak disketeak, IDE gailuak, IDE diskete, ataka paralelozko IDE gailuak, SCSI kontrolatzaileak @@ -225,7 +225,7 @@ eta driberrak, USB eta firewire onartzen ditu. Onartutako fitxategi sistemak FAT, Win32 FAT gehiagrriak eta NFS dira beste askoren artean. -</para><para arch="i386"> +</para><para arch="x86"> "AT" emulazioa erabiltzen duten disko interfazeak (MFM, RLL, IDE, edo ATA) onartzen dira. IBM XT ordenagailuetan erabiltzen den 8 bit-etako diff --git a/eu/hardware/network-cards.xml b/eu/hardware/network-cards.xml index 2908c472e..eab9b259a 100644 --- a/eu/hardware/network-cards.xml +++ b/eu/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Sare Konexio Hardwarea</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -27,13 +27,13 @@ ertsonalak betezen dituen kernel bat sortu eta instalazio diskokoagatik alda dezakezu (begiratu <xref linkend="rescue-replace-kernel"/>). -</para><para arch="i386"> +</para><para arch="x86"> RDSI-rentzat D kanaelo 1TR6 (zaharakituriko) protokolo alemaniarra ez da onartzen; Spellcaster BRI ISDN txartelak ere ez ditu onartzen &d-i;-k -</para><para arch="i386"> +</para><para arch="x86"> Soinu gailuak ez daude gaiturik lehenespenetan, Baina lehe ezan bezala: Zure kernel pertsonalizaturari buzuko argibide iksuteko joan diff --git a/eu/hardware/supported-peripherals.xml b/eu/hardware/supported-peripherals.xml index ed1c41d7b..c669daf64 100644 --- a/eu/hardware/supported-peripherals.xml +++ b/eu/hardware/supported-peripherals.xml @@ -8,13 +8,13 @@ Linux-ek sagua, imprimagailua, eskanerrak, PCMCIA eta USB gailu ezberdin asko onartzen ditu. Hala ere gailu horietako gehienake ez dira instalazioan behar. -</para><para arch="i386"> +</para><para arch="x86"> USB hardwareak normalean egoki funtzionatzen du, bakarrik USB teklatu batzuek konfigurazio berezia behar dute. (ikusi <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Berririo ere, begiratu <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -55,7 +55,7 @@ zure hardwarea GNU/Linux-ek onartzen duela ziurtatzerakoan. Zoritxarrez nahiko arraroa da &arch-title; berriak saltzen dituen saltzailerik aurkitzea. -</para><para arch="i386"> +</para><para arch="x86"> Windows duen makina bat erosterakoan kontuz irakurri ezazu software lizentzia; agian lizentzia atzera bota zenezake eta saltzaileak @@ -105,7 +105,7 @@ linux merkatua garrantzitsua dela ohartuko dira. </sect2> -<sect2 arch="i386"><title>Windows-erako diseinaturiko Hardwarea</title> +<sect2 arch="x86"><title>Windows-erako diseinaturiko Hardwarea</title> <para> Beste joera arriskutsu bat Windosperako diseinaturiko inprimagailu diff --git a/eu/hardware/supported/i386.xml b/eu/hardware/supported/i386.xml index aaa9c7866..183a02aab 100644 --- a/eu/hardware/supported/i386.xml +++ b/eu/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"><title>CPU, Txarel nagusi eta Bideo Onarpena</title> + <sect2 arch="x86"><title>CPU, Txarel nagusi eta Bideo Onarpena</title> <para> Periferiko onarpenari buruzko argibide osoak diff --git a/eu/howto/installation-howto.xml b/eu/howto/installation-howto.xml index e17237837..f7adafcd4 100644 --- a/eu/howto/installation-howto.xml +++ b/eu/howto/installation-howto.xml @@ -79,7 +79,7 @@ CD-arekin aski izan beharko zenuke. </para><para> Deskargatu naiago duzun moetako eta graba ezazu CD batetan. -<phrase arch="i386">CD-tik abiaraz ahal izateko, agian zuk BIOS-eko ezarpenak +<phrase arch="x86">CD-tik abiaraz ahal izateko, agian zuk BIOS-eko ezarpenak aldatu behar izango dituzu, honi buruzko argibideak: <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> @@ -157,7 +157,7 @@ Badago debian installer erabiliaz memoria gailua erabiltzeko modu malguago bat, eta posible da memoria gutxiagoko gailuekin funtzionatzea. Xehetasunak ikusteko <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Zenbait BIOS erabiliaz usb biltegiratzetik zuzenean abiarazi daitezke. BIOS-a "gailu aldakorra" edo "USB_ZIP"-tik abiarazteko konfiguratu behar duzu, USB @@ -178,7 +178,7 @@ ezberdinak daude zure arkitektura eta sare-abiarazte konfigurazioaren arabera. <filename>netboot/</filename>-en dauden fitxategiak erabil ditzakezu &d-i; abiarazteko. -</para><para arch="i386"> +</para><para arch="x86"> Konfiguratzeko era errazena ziurrenik PXE sare-abiaraztea da.Despaketatu <filename>netboot/pxeboot.tar.gz</filename> fitxategia @@ -201,7 +201,7 @@ dagoeneko beste sistema eragile bat duen disko gogor batetatik. Deskargatu and a Debian CD irudia diska gogorreko erro karpetara. Ziurtatu CD irudia "*.iso" izeneko fitxategi bat dela. Orain aski da linux initrd erabiliaz abiaraztea. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" />-en argitzen da nola egin. </phrase> @@ -216,7 +216,7 @@ abiaraztea. Bein instalatzailea abiarazten denean sarrera pantaila agertuko da. Sakatu &enterkey; abiarazteko, edo irakurri beste abiarazte modu batzuetarako argibideak (ikusi <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> 2.6 kernel bat erabili nahi izan ezkero idatzi<userinput>linux26</userinput> <prompt>boot:</prompt> galderan. <footnote><para> @@ -276,7 +276,7 @@ Honen ondoren kernel instalazioa egingo da. Azkenengo pausua abiarazle bat instalatzea da. Instalatzaileak zure ordenagiluan beste sistema bat aurkituko balu, abiarazte menuan gehituko luke eta zuri honen berri emango lizuke. -<phrase arch="i386">Lehenespen bezala, arruntenean erabaki egokia den, +<phrase arch="x86">Lehenespen bezala, arruntenean erabaki egokia den, GRUB abiarzlea lehenengo diska gogorreko abiarazte grabaketa nagusian (MBR) grabatuko da. Zuri ezarpen hau aldatu eta GRUB beste edonon grabatzeko aukera emango zaizu. diff --git a/eu/install-methods/automatic-install.xml b/eu/install-methods/automatic-install.xml index 98cd14814..8a772e813 100644 --- a/eu/install-methods/automatic-install.xml +++ b/eu/install-methods/automatic-install.xml @@ -76,7 +76,7 @@ nerregin egin behar da berau gehitzeko. mkisofs manual orrialdea begiratu argibide gehiagorako. Betela fitxategia diskete batetan ipini eta 'preseed/file=/floppy/preseed.cfg' erabili. -</para><para arch="i386"> +</para><para arch="x86"> USB memoria baten bidez abiarazi nahi zain ezkeri, orduan kopiatu aurrekonfigurazio fitxategia memoriaren fitxategi sisteman eta diff --git a/eu/install-methods/boot-drive-files.xml b/eu/install-methods/boot-drive-files.xml index 93325cf72..d35becbda 100644 --- a/eu/install-methods/boot-drive-files.xml +++ b/eu/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and <xref linkend="unreliable-floppies"/> unreliable floppy disks. -</para><para arch="i386"> +</para><para arch="x86"> The installer cannot boot from files on an NTFS file system. @@ -39,7 +39,7 @@ model. </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Hard disk installer booting using <command>LILO</command> or <command>GRUB</command></title> <para> diff --git a/eu/install-methods/install-tftp.xml b/eu/install-methods/install-tftp.xml index ddb86ec70..63ef5de88 100644 --- a/eu/install-methods/install-tftp.xml +++ b/eu/install-methods/install-tftp.xml @@ -107,7 +107,7 @@ reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. -</para><note arch="i386"><para> +</para><note arch="x86"><para> To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> @@ -175,7 +175,7 @@ command to set the output to hex, then enter the individual components of the client IP one at a time. As for <replaceable>client-architecture</replaceable>, try out some values. -</para><para arch="i386"> +</para><para arch="x86"> For PXE booting, you can use the boot loader included with <classname>syslinux</classname>: <filename>pxelinux.0</filename>. The boot @@ -201,7 +201,7 @@ label lanlinux there may be problems mounting the initrd.gz file system once the kernel is booted. -</para><para arch="i386"> +</para><para arch="x86"> Finally, copy the <filename>vmlinuz</filename> and <filename>initrd.gz</filename> files (for the netboot installation method) diff --git a/eu/install-methods/tftp/dhcp.xml b/eu/install-methods/tftp/dhcp.xml index a6ba6286e..38dff015e 100644 --- a/eu/install-methods/tftp/dhcp.xml +++ b/eu/install-methods/tftp/dhcp.xml @@ -56,7 +56,7 @@ restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>PXE Booting</title> <para> Here is another example for a <filename>dhcp.conf</filename> using the diff --git a/eu/partitioning/device-names.xml b/eu/partitioning/device-names.xml index 7e32db30d..f049d2231 100644 --- a/eu/partitioning/device-names.xml +++ b/eu/partitioning/device-names.xml @@ -60,12 +60,12 @@ Partizioen hizkiak eta mac-erako pdisk programak erakusten dituenak ezberdinak i </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Lehen XT diskaren izena <filename>/dev/xda</filename> da. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Bigarren XT diskaren izena <filename>/dev/xdb</filename> da. </para></listitem> @@ -116,7 +116,7 @@ nahasteren bat edo beste sorrarazi dezakela. Irtenbide egokiena kasu honetan sistemaren abioko oharrak aztertzea da, baldin eta gailu motak eta/edo ezaugarriak ezagutzen badituzu. -</para><para arch="i386"> +</para><para arch="x86"> Linuxek lehen mailako partizioa gailuaren izenari 1etik 4rako zenbaki bat gehituz izendatzen du. Esaterako, lehen IDE unitateko lehen partizioa diff --git a/eu/partitioning/partition-programs.xml b/eu/partitioning/partition-programs.xml index 51a8923e6..fa6f11267 100644 --- a/eu/partitioning/partition-programs.xml +++ b/eu/partitioning/partition-programs.xml @@ -14,7 +14,7 @@ programen zerrenda bat dator. <term><command>partman</command></term>
<listitem><para>
Debianen partizio tresna gomendatua. Programa honek gauza anitzetarako
-balio du, hala nola <phrase arch="i386"> (<quote>formatudun</quote>) </phrase>
+balio du, hala nola <phrase arch="x86"> (<quote>formatudun</quote>) </phrase>
fitxategi sistemak sortu eta norberaren muntaia puntuei egokitzeko.
</para></listitem>
</varlistentry>
@@ -113,7 +113,7 @@ mknod hda21 b 3 21 chgrp disk hda21
chmod 660 hda21
</screen></informalexample>
-</para><para arch="i386">
+</para><para arch="x86">
Ez ahaztu partizioa ``Bootable''(abiarazgarria) gisa izendatzea.
</para><para condition="mac-fdisk.txt">
Ikusi
diff --git a/eu/partitioning/partition/i386.xml b/eu/partitioning/partition/i386.xml index 1b2794b45..26c3e4296 100644 --- a/eu/partitioning/partition/i386.xml +++ b/eu/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>Partitioning for &arch-title;</title> + <sect2 arch="x86"><title>Partitioning for &arch-title;</title> <para> The PC BIOS generally adds additional constraints for disk diff --git a/eu/post-install/kernel-baking.xml b/eu/post-install/kernel-baking.xml index 4a164343d..8b808858f 100644 --- a/eu/post-install/kernel-baking.xml +++ b/eu/post-install/kernel-baking.xml @@ -23,7 +23,7 @@ APM or SMP </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The compact and idepci flavors don't come with sound. Although the vanilla kernel does, it might not work for other reasons. @@ -174,7 +174,7 @@ like any package. As root, do <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as ``i586'', </phrase> +<phrase arch="x86"> such as ``i586'', </phrase> depending on what kernel options you set. <userinput>dpkg -i kernel-image...</userinput> will install the kernel, along with some other nice supporting files. For instance, diff --git a/eu/post-install/reactivating-win.xml b/eu/post-install/reactivating-win.xml index ce176c254..52da42e89 100644 --- a/eu/post-install/reactivating-win.xml +++ b/eu/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 16560 untranslated --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivating DOS and Windows</title> <para> diff --git a/eu/preparing/bios-setup/i386.xml b/eu/preparing/bios-setup/i386.xml index 1ee5be4cd..f9f796155 100644 --- a/eu/preparing/bios-setup/i386.xml +++ b/eu/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>Invoking the BIOS Set-Up Menu</title> + <sect2 arch="x86"><title>Invoking the BIOS Set-Up Menu</title> <para> @@ -101,7 +101,7 @@ try using a shareware/freeware program. Try looking in </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title> + <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title> <para> @@ -229,7 +229,7 @@ save the changes on your computer. Often, you must press </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Miscellaneous BIOS Settings</title> <sect3 id="cd-settings"><title>CD-ROM Settings</title> diff --git a/eu/preparing/minimum-hardware-reqts.xml b/eu/preparing/minimum-hardware-reqts.xml index 410bf6c71..d4c7c0327 100644 --- a/eu/preparing/minimum-hardware-reqts.xml +++ b/eu/preparing/minimum-hardware-reqts.xml @@ -15,7 +15,7 @@ Zure beharren arabera, zuk beheandagoen taula gomendaturiko beharrak baino gutxiagorekin lan egin ahal dezakezu. Hala ere erabiltzaile gehienak frustraturik sentituko dira gomendio horiek ez bete ezkero. -</para><para arch="i386"> +</para><para arch="x86"> Idazmahai makinetarako Pentium 100 bat gomendatzen da eta zerbitzarietarako Pentium II-300. diff --git a/eu/preparing/needed-info.xml b/eu/preparing/needed-info.xml index fdccf38b5..f65e7a0f3 100644 --- a/eu/preparing/needed-info.xml +++ b/eu/preparing/needed-info.xml @@ -45,7 +45,7 @@ information on configuring or using your hardware. </para> <itemizedlist> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -233,7 +233,7 @@ The cases and boxes for each piece of hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The System window in the Windows Control Panel. @@ -350,19 +350,19 @@ Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems. -</para><para arch="i386"> +</para><para arch="x86"> In particular, Linux usually cannot run hardware that requires a running version of Windows to work. -</para><para arch="i386"> +</para><para arch="x86"> Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete. -</para><para arch="i386"> +</para><para arch="x86"> So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific. diff --git a/eu/preparing/non-debian-partitioning.xml b/eu/preparing/non-debian-partitioning.xml index 5f9f67229..11bc81616 100644 --- a/eu/preparing/non-debian-partitioning.xml +++ b/eu/preparing/non-debian-partitioning.xml @@ -20,7 +20,7 @@ an LPAR or VM guest in this case. If you already have an operating system on your system -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -44,7 +44,7 @@ root. You can find information about your current partition setup by using a partitioning tool for your current operating system -<phrase arch="i386">, such as fdisk or PartitionMagic</phrase> +<phrase arch="x86">, such as fdisk or PartitionMagic</phrase> <phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase> @@ -63,7 +63,7 @@ backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it. -<phrase arch="i386"> Luckily, there is an alternative for some users; see +<phrase arch="x86"> Luckily, there is an alternative for some users; see <xref linkend="lossless"/>. </phrase> </para> diff --git a/eu/preparing/nondeb-part/i386.xml b/eu/preparing/nondeb-part/i386.xml index 43d0b622f..5ab8df92b 100644 --- a/eu/preparing/nondeb-part/i386.xml +++ b/eu/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>Partitioning From DOS or Windows</title> + <sect2 arch="x86"><title>Partitioning From DOS or Windows</title> <para> If you are manipulating existing FAT or NTFS partitions, it is diff --git a/eu/preparing/pre-install-bios-setup.xml b/eu/preparing/pre-install-bios-setup.xml index c4cdd6b7f..073d5d9b5 100644 --- a/eu/preparing/pre-install-bios-setup.xml +++ b/eu/preparing/pre-install-bios-setup.xml @@ -54,7 +54,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they @@ -65,7 +65,7 @@ in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to @@ -73,7 +73,7 @@ interrupt on memory parity errors. </para> - <sect3 arch="i386"><title>The Turbo Switch</title> + <sect3 arch="x86"><title>The Turbo Switch</title> <para> Many systems have a <emphasis>turbo</emphasis> switch that controls @@ -87,7 +87,7 @@ accidentally touch the software control for the turbo switch. </para> </sect3> - <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title> + <sect3 arch="x86"><title>Cyrix CPUs and Floppy Disk Errors</title> <para> Many users of Cyrix CPUs have had to disable the cache in their @@ -106,7 +106,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code. </para> </sect3> - <sect3 arch="i386"><title>Peripheral Hardware Settings</title> + <sect3 arch="x86"><title>Peripheral Hardware Settings</title> <para> You may have to change some settings or jumpers on your computer's @@ -124,7 +124,7 @@ amount of RAM in your system. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"><title>USB keyboards</title> + <sect3 arch="x86" id="usb-keyboard-config"><title>USB keyboards</title> <para> If you have no AT-style keyboard and only a USB model, you will need diff --git a/eu/using-d-i/modules/i386/grub-installer.xml b/eu/using-d-i/modules/i386/grub-installer.xml index cfd4ae55f..cb42e642a 100644 --- a/eu/using-d-i/modules/i386/grub-installer.xml +++ b/eu/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version; 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title><command>Grub</command> Abiarazlea Disko gogorrean instalatzen</title> <para> diff --git a/eu/using-d-i/modules/i386/lilo-installer.xml b/eu/using-d-i/modules/i386/lilo-installer.xml index 40962dc78..01dcce470 100644 --- a/eu/using-d-i/modules/i386/lilo-installer.xml +++ b/eu/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-15"?> <!-- original version: 14602 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title><command>LILO</command> Abiarazlea diska gogorrean instalatu</title> <para> diff --git a/fr/administrivia/administrivia.xml b/fr/administrivia/administrivia.xml index 08cdbc637..32e2534ae 100644 --- a/fr/administrivia/administrivia.xml +++ b/fr/administrivia/administrivia.xml @@ -128,7 +128,7 @@ La section de ce manuel <quote>Installer debian partir d'un systme Unix/Linux avec copyright Karsten M. Self. </para> -<para arch="i386"> +<para arch="x86"> La section sur l'installation avec plip (<xref linkend="plip"/>) est base sur le <ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> de Gilles Lamiral. diff --git a/fr/appendix/chroot-install.xml b/fr/appendix/chroot-install.xml index 2e796ee70..5780be357 100644 --- a/fr/appendix/chroot-install.xml +++ b/fr/appendix/chroot-install.xml @@ -408,7 +408,7 @@ d'amorage pour qu'il charge le noyau install avec votre nouvelle partition racine. <command>Debootstrap</command> n'installe pas de programme d'amorage mais vous pouvez utiliser <command>aptitude</command> pour en installer un. -</para><para arch="i386"> +</para><para arch="x86"> Faites <userinput>info grub</userinput> ou <userinput>man lilo.conf</userinput> pour connatre les instructions de @@ -421,7 +421,7 @@ nouveau systme et l'diter. Une fois que vous l'aurez modifi, lancez lilo (souvenez-vous que lilo utilise le fichier lilo.conf qui se trouve dans le mme systme que lui). -</para><para arch="i386"> +</para><para arch="x86"> Voici un exemple simple de fichier <filename>/etc/lilo.conf</filename> : diff --git a/fr/appendix/plip.xml b/fr/appendix/plip.xml index 4f12d7013..d87e8fd36 100644 --- a/fr/appendix/plip.xml +++ b/fr/appendix/plip.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 39463 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Installer &debian; grce au protocole PLIP (IP sur port parallle)</title> <para> diff --git a/fr/boot-installer/boot-installer.xml b/fr/boot-installer/boot-installer.xml index 1f30fd381..cc22035f6 100644 --- a/fr/boot-installer/boot-installer.xml +++ b/fr/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Dmarrer l'installateur sur &arch-title;</title> diff --git a/fr/boot-installer/i386.xml b/fr/boot-installer/i386.xml index d2ad7ef39..c424f939d 100644 --- a/fr/boot-installer/i386.xml +++ b/fr/boot-installer/i386.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 38231 --> - <sect2 arch="i386"><title>Amorcer depuis un cdrom</title> + <sect2 arch="x86"><title>Amorcer depuis un cdrom</title> &boot-installer-intro-cd.xml; @@ -77,7 +77,7 @@ Amorce la saveur bf2.4 . <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Amorcer depuis une partition DOS</title> &boot-installer-intro-hd.xml; @@ -109,7 +109,7 @@ d'tre utilis par la saveur bf2.4. Le symptme de ce problme est le message END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Amorcer partir de Linux avec <command>LILO</command> ou <command>GRUB</command></title> @@ -200,7 +200,7 @@ entre <command>GRUB</command> et <command>LILO</command>. </para> </sect2> -<sect2 arch="i386" condition="bootable-usb" id="usb-boot"> +<sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Amorcer sur une cl USB</title> <para> @@ -214,7 +214,7 @@ appuyer sur la touche &enterkey;. </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Amorcer depuis des disquettes</title> <para> @@ -276,7 +276,7 @@ automatiquement lanc. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Amorcer avec TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Amorcer avec TFTP</title> &boot-installer-intro-net.xml; @@ -318,7 +318,7 @@ disquettes d'amorage et mme des ROM qui permettent l'amorage par TFTP. </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>L'invite d'amorage</title> <para> Quand l'installateur dmarre, une invite d'amorage, <prompt>boot:</prompt> diff --git a/fr/boot-installer/intro-cd.xml b/fr/boot-installer/intro-cd.xml index a34b466be..a9e1d3943 100644 --- a/fr/boot-installer/intro-cd.xml +++ b/fr/boot-installer/intro-cd.xml @@ -6,7 +6,7 @@ La manire la plus facile est d'utiliser les cdroms Debian. Si vous avez un jeu de cdroms, et si votre machine peut s'amorcer depuis un cdrom, ce sera parfait ! Il suffit -<phrase arch="i386"> de configurer votre systme pour amorcer depuis +<phrase arch="x86"> de configurer votre systme pour amorcer depuis un cdrom, voyez la <xref linkend="boot-dev-select"/>, </phrase> de placer votre cdrom et de ramorcer. Vous pouvez continuer avec le diff --git a/fr/boot-installer/parameters.xml b/fr/boot-installer/parameters.xml index 100c45468..d6f08dfb3 100644 --- a/fr/boot-installer/parameters.xml +++ b/fr/boot-installer/parameters.xml @@ -227,7 +227,7 @@ Les symptmes de ce problme sont des messages d'erreur au sujet de bterm ou bogl, un cran noir, ou un blocage quelques minutes aprs le dbut de l'installation. -</para><para arch="i386"> +</para><para arch="x86"> Le paramtre <userinput>video=vga16:off</userinput> peut tre utilis pour dsactiver l'utilisation du tampon video par le noyau. Des problmes semblables ont diff --git a/fr/boot-installer/trouble.xml b/fr/boot-installer/trouble.xml index 501ebee95..d9c4c3501 100644 --- a/fr/boot-installer/trouble.xml +++ b/fr/boot-installer/trouble.xml @@ -69,7 +69,7 @@ pas dclar dans le noyau. L'installateur n'est pas compatible avec </para><para> Les problmes sont souvent rsolus en retirant priphriques et -extensions et en essayant de ramorcer. <phrase arch="i386">Modems internes, +extensions et en essayant de ramorcer. <phrase arch="x86">Modems internes, cartes son et priphriques Plug'n Play sont souvent la cause des problmes.</phrase> </para> @@ -83,7 +83,7 @@ prendre en compte, par exemple <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Problmes communs pour &arch-title;</title> <para> Certains problmes d'installation peuvent tre rsolus ou vits en diff --git a/fr/hardware/hardware-supported.xml b/fr/hardware/hardware-supported.xml index 7d184c051..477388413 100644 --- a/fr/hardware/hardware-supported.xml +++ b/fr/hardware/hardware-supported.xml @@ -217,7 +217,7 @@ produit sur une plateforme &arch-title;. Et prvenez aussi la <sect2 id="gfx" arch="not-s390"> <title>Cartes graphiques</title> -<para arch="i386"> +<para arch="x86"> Vous devriez utiliser une interface graphique compatible VGA pour le terminal de console. Pratiquement toutes les cartes graphiques modernes sont compatibles VGA. Les @@ -254,7 +254,7 @@ la carte BCM91250A. </sect2> - <sect2 arch="i386" id="laptops"><title>Portables</title> + <sect2 arch="x86" id="laptops"><title>Portables</title> <para> Les ordinateurs portables sont aussi supports. Les diff --git a/fr/hardware/installation-media.xml b/fr/hardware/installation-media.xml index 496ef7e17..872cb7c62 100644 --- a/fr/hardware/installation-media.xml +++ b/fr/hardware/installation-media.xml @@ -48,7 +48,7 @@ systme, une fois que vous avez dmarr par d'autres moyens ; voyez le <xref linkend="boot-installer"/>. </para> -<para arch="i386"> +<para arch="x86"> Les cdroms de type SCSI et IDE/ATAPI sont reconnus. De plus, toutes les interfaces de cdrom non standard reconnues par Linux sont reconnues par les @@ -62,7 +62,7 @@ informations dtailles sur l'utilisation des cdroms avec Linux. </para> -<para arch="i386"> +<para arch="x86"> Les lecteurs USB sont reconnus, comme le sont les priphriques FireWire reconnus par les pilotes ohci1394 et sbp2. </para> @@ -214,7 +214,7 @@ s'assurer que l'on puisse installer Debian sur le plus de matriel possible. </para> -<para arch="i386"> +<para arch="x86"> En gnral, le systme d'installation Debian reconnat les disquettes, les disques IDE, les disquettes IDE, les priphriques IDE sur le port parallle, les contrleurs et disques SCSI, les priphriques USB et FireWire. Les @@ -222,7 +222,7 @@ systmes de fichiers reconnus comprennent FAT, les extensions FAT Win-32 (VFAT), NTFS et d'autres encore. </para> -<para arch="i386"> +<para arch="x86"> Les interfaces disque qui mulent l'interface du disque dur AT , qu'on appelle souvent MFM, RLL, IDE ou ATA, sont reconnues. Les trs vieux contrleurs de diff --git a/fr/hardware/network-cards.xml b/fr/hardware/network-cards.xml index 2b2af7e51..417a8d0de 100644 --- a/fr/hardware/network-cards.xml +++ b/fr/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Matriel de connexion rseau</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> La plupart des cartes PCI et beaucoup d'anciennes cartes ISA sont @@ -23,7 +23,7 @@ otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> </para> -<para arch="i386"> +<para arch="x86"> Pour ce qui est du RNIS, le protocole sur canal D pour l'1TR6 allemand n'est pas reconnu ; les cartes Spellcaster BRI ISDN ne sont pas reconnues non plus par l'installateur Debian. diff --git a/fr/hardware/supported-peripherals.xml b/fr/hardware/supported-peripherals.xml index 35b57c7dc..af0f766c9 100644 --- a/fr/hardware/supported-peripherals.xml +++ b/fr/hardware/supported-peripherals.xml @@ -11,13 +11,13 @@ PCMCIA et USB, etc. Cependant aucun de ces priphriques n'est requis lors de l'installation du systme. </para> -<para arch="i386"> +<para arch="x86"> Le matriel USB fonctionne correctement mais certains claviers USB peuvent ncessiter une configuration supplmentaire (voyez la <xref linkend="usb-keyboard-config"/>). </para> -<para arch="i386"> +<para arch="x86"> Encore une fois, reportez-vous au <ulink url="&url-hardware-howto;">HOWTO sur la compatibilit des matriels avec Linux</ulink> pour dterminer si votre matriel est reconnu par Linux. @@ -62,7 +62,7 @@ Malheureusement, il est assez rare de trouver un vendeur qui livre des machines &arch-title; neuves. </para> -<para arch="i386"> +<para arch="x86"> Si vous devez acheter un ordinateur fourni avec Windows, lisez attentivement la licence logicielle accompagnant Windows ; vous pourrez peut-tre rejeter la licence et obtenir un rabais de votre vendeur. Une recherche sur internet @@ -108,7 +108,7 @@ raliseront que la communaut du logiciel libre est un march important. </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Matriels spcifiques Windows</title> <para> diff --git a/fr/hardware/supported/i386.xml b/fr/hardware/supported/i386.xml index f5bac3982..4ade0a92d 100644 --- a/fr/hardware/supported/i386.xml +++ b/fr/hardware/supported/i386.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 11648 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Microprocesseurs, cartes mre et cartes vido</title> <para> diff --git a/fr/howto/installation-howto.xml b/fr/howto/installation-howto.xml index 3c644ef47..d9a3f3867 100644 --- a/fr/howto/installation-howto.xml +++ b/fr/howto/installation-howto.xml @@ -76,7 +76,7 @@ l'installation. Seul le premier cdrom de cet ensemble est ncessaire. </para><para> Tlchargez l'image que vous prfrez et gravez-la sur un cdrom. -<phrase arch="i386">Pour amorcer partir du cdrom, vous devrez sans doute +<phrase arch="x86">Pour amorcer partir du cdrom, vous devrez sans doute changer la configuration du BIOS ; c'est expliqu dans la <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> @@ -153,7 +153,7 @@ Il y a d'autres moyens, plus souples, de mettre en oeuvre une cl USB et l'installateur Debian peut fonctionner avec des cls qui possdent moins de mmoire. Pour des prcisions, voyez la <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Certains BIOS peuvent lancer directement des priphriques USB, d'autres non. Il vous faudra configurer le BIOS et permettre l'amorage d'un @@ -178,7 +178,7 @@ Les diffrentes mthodes pour cet amorage rseau dpendent de l'architecture et de la configuration. Les fichiers dans <filename>netboot/</filename> servent l'amorage de l'installateur. -</para><para arch="i386"> +</para><para arch="x86"> La mthode la plus facile est l'amorage de type PXE. Extrayez les fichiers de <filename>netboot/pxeboot.tar.gz</filename> dans le rpertoire @@ -202,7 +202,7 @@ d'exploitation. Tlchargez <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename> et une image CD dans le rpertoire racine du disque. Assurez-vous que le nom de l'image CD se termine par <literal>.iso</literal>. Maintenant, il suffit d'amorcer Linux avec initrd. -<phrase arch="i386"> +<phrase arch="x86"> La <xref linkend="boot-initrd" /> explique comment faire. </phrase> @@ -218,7 +218,7 @@ Aprs le dmarrage de l'installateur, l'cran initial est affich. Appuyez sur la touche &enterkey; pour amorcer, ou bien lisez les instructions sur les autres mthodes d'amorage et sur les paramtres (voyez la <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Si vous voulez un noyau de la srie 2.4, saisissez <userinput>install24</userinput> l'invite <prompt>boot:</prompt> <footnote> @@ -268,7 +268,7 @@ gens presss. Si vous ne voulez pas du partitionnement automatique, choisissez de partitionner vous-mme. </para> -<para arch="i386"> +<para arch="x86"> Si vous voulez prserver une partition DOS ou Windows, faites attention en utilisant le partitionnement automatique. Si vous utilisez le partitionnement @@ -302,7 +302,7 @@ ce qui peut prendre du temps. Puis le noyau est install. La dernire tape est l'installation d'un programme d'amorage. Si l'installateur a dtect d'autres systmes d'exploitation sur la machine, il les ajoutera au menu du programme d'amorage. -<phrase arch="i386">GRUB est par dfaut install sur le secteur principal +<phrase arch="x86">GRUB est par dfaut install sur le secteur principal d'amorage du premier disque dur, ce qui est une bonne ide. Mais vous avez la possibilit d'annuler ce choix et de l'installer ailleurs. </phrase> diff --git a/fr/install-methods/boot-drive-files.xml b/fr/install-methods/boot-drive-files.xml index 5558fa755..8c7abf8c1 100644 --- a/fr/install-methods/boot-drive-files.xml +++ b/fr/install-methods/boot-drive-files.xml @@ -17,7 +17,7 @@ les manipulations pnibles des supports amovibles, comme de trouver puis de graver des images de cdrom ou de manipuler un nombre faramineux de disquettes peu fiables. -</para><para arch="i386"> +</para><para arch="x86"> L'installateur ne peut tre amorc par des fichiers placs sur un systme de fichiers NTFS. @@ -43,7 +43,7 @@ que le systme est un modle <quote>NewWorld</quote> ou un modle </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Dmarrage du programme d'installation avec <command>LILO</command> ou <command>GRUB</command></title> <para> diff --git a/fr/install-methods/boot-usb-files.xml b/fr/install-methods/boot-usb-files.xml index 42b09a3f1..334f7200c 100644 --- a/fr/install-methods/boot-usb-files.xml +++ b/fr/install-methods/boot-usb-files.xml @@ -22,7 +22,7 @@ tailles infrieures, voyez <xref linkend="usb-copy-flexible"/>. <sect2 id="usb-copy-easy"> <title>Copie des fichiers — la mthode simple</title> -<para arch="i386"> +<para arch="x86"> Le fichier <filename>hd-media/boot.img.gz</filename> contient tous les fichiers de l'installateur, le noyau et le programme @@ -55,10 +55,10 @@ le bon priphrique pour votre cl ! <para> Montez ensuite la cl (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), qui aura maintenant un systme de fichiers -<phrase arch="i386">FAT</phrase> +<phrase arch="x86">FAT</phrase> <phrase arch="powerpc">HFS</phrase>, et copiez une image ISO de type <quote>netinst</quote> ou <quote>businesscard</quote>. Le nom de ce fichier doit se terminer par <filename>.iso</filename>. Dmontez la cl (<userinput>umount /mnt</userinput>) @@ -109,7 +109,7 @@ et activez la protection contre l'criture. </sect2> <!-- TODO: doesn't this section belong later? --> -<sect2 arch="i386"> +<sect2 arch="x86"> <title>Amorcer la cl USB</title> <warning><para> diff --git a/fr/install-methods/install-tftp.xml b/fr/install-methods/install-tftp.xml index 58e710b3f..372ca1012 100644 --- a/fr/install-methods/install-tftp.xml +++ b/fr/install-methods/install-tftp.xml @@ -77,7 +77,7 @@ implmentent ces protocoles peut tre utilis. Dans les exemples qui vont suivre, on donnera les commandes pour SunOS 4.x, SunOS 5.x (mieux connu sous le nom de Solaris) et GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> Pour utiliser la mthode de dmarrage par l'excution d'un environnement de pr-amorage (PXE) de TFTP, vous avez besoin d'un serveur TFTP avec @@ -169,7 +169,7 @@ travers TFTP. Pour amorcer sur le rseau, utilisez <filename>yaboot.conf</filename> dans le rpertoire TFTP. </para> -<para arch="i386"> +<para arch="x86"> Pour le dmarrage PXE, tout ce dont vous avez besoin est dans l'archive <filename>netboot/netboot.tar.gz</filename>. Extrayez les fichiers dans le diff --git a/fr/install-methods/tftp/dhcp.xml b/fr/install-methods/tftp/dhcp.xml index 1eaaddc5c..64938fdf9 100644 --- a/fr/install-methods/tftp/dhcp.xml +++ b/fr/install-methods/tftp/dhcp.xml @@ -53,7 +53,7 @@ relancez <command>dhcpd</command> par </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Amorage PXE et configuration de DHCP</title> <para> Voici un autre exemple de fichier <filename>dhcp.conf</filename> utilisant diff --git a/fr/install-methods/usb-setup/i386.xml b/fr/install-methods/usb-setup/i386.xml index b75a655d8..d05d8f70d 100644 --- a/fr/install-methods/usb-setup/i386.xml +++ b/fr/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Partitionner un priphrique USB sur &arch-title;</title> <para> diff --git a/fr/partitioning/device-names.xml b/fr/partitioning/device-names.xml index 8b5a90467..894d1c7e1 100644 --- a/fr/partitioning/device-names.xml +++ b/fr/partitioning/device-names.xml @@ -69,12 +69,12 @@ pdisk (ce que pdisk affiche comme tant <filename>/dev/hdc</filename> peut </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Le premier disque XT est nomm <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Le second disque XT est nomm <filename>/dev/xdb</filename>. @@ -125,7 +125,7 @@ l'ordre de nommage des disques peut-tre embrouill. La meilleure solution est de regarder les messages au dmarrage, en supposant que vous connaissiez les modles ou les tailles des disques. -</para><para arch="i386"> +</para><para arch="x86"> Linux reprsente les partitions primaires par le nom du disque, suivi des nombres 1 4. Par exemple la premire partition sur le premier diff --git a/fr/partitioning/partition-programs.xml b/fr/partitioning/partition-programs.xml index abd4709d6..25bd1e0bb 100644 --- a/fr/partitioning/partition-programs.xml +++ b/fr/partitioning/partition-programs.xml @@ -20,7 +20,7 @@ Voici les programmes qui sont disponibles sur votre architecture : C'est le partitionneur que recommande Debian. Ce <quote>couteau suisse</quote> sait aussi redimensionner des partitions et monter des systmes de fichiers -<phrase arch="i386"> (<quote>formater</quote> en langage Windows)</phrase> +<phrase arch="x86"> (<quote>formater</quote> en langage Windows)</phrase> sur des points de montage. </para></listitem> @@ -142,7 +142,7 @@ modules, excutez : # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386"> +<phrase arch="x86"> N'oubliez pas de rendre amorable votre partition racine. </phrase> diff --git a/fr/partitioning/partition/i386.xml b/fr/partitioning/partition/i386.xml index 9ea96f325..26148a1f2 100644 --- a/fr/partitioning/partition/i386.xml +++ b/fr/partitioning/partition/i386.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 39465 --> - <sect2 arch="i386"><title>Partitionnement pour &arch-title;</title> + <sect2 arch="x86"><title>Partitionnement pour &arch-title;</title> <para> Si vous voulez prserver un systme d'exploitation existant comme diff --git a/fr/post-install/kernel-baking.xml b/fr/post-install/kernel-baking.xml index 5596635cc..d164ea9f1 100644 --- a/fr/post-install/kernel-baking.xml +++ b/fr/post-install/kernel-baking.xml @@ -165,7 +165,7 @@ tapez </phrase> La partie <replaceable>subarchitecture</replaceable> est une sous-architecture optionnelle, -<phrase arch="i386"> telle que <quote>i586</quote>, </phrase> +<phrase arch="x86"> telle que <quote>i586</quote>, </phrase> suivant les options de compilation que vous avez dfinies. <userinput>dpkg -i</userinput> installera votre noyau ainsi que les autres fichiers qui lui seront ncessaires. diff --git a/fr/post-install/reactivating-win.xml b/fr/post-install/reactivating-win.xml index 37d090749..0bbedcad1 100644 --- a/fr/post-install/reactivating-win.xml +++ b/fr/post-install/reactivating-win.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Ractiver DOS et Windows</title> <para> diff --git a/fr/post-install/rescue.xml b/fr/post-install/rescue.xml index f46bc46aa..f8c563d26 100644 --- a/fr/post-install/rescue.xml +++ b/fr/post-install/rescue.xml @@ -41,7 +41,7 @@ S'il le peut, l'installateur affichera l'invite d'un interprteur de commandes d le systme de fichiers que vous avez slectionn ; et vous pourrez l'utiliser pour effectuer les corrections ncessaires. -<phrase arch="i386"> +<phrase arch="x86"> Par exemple, pour rinstaller le programme d'amorage GRUB sur le secteur principal d'amorage du premier disque dur, vous pouvez lancer la commande <userinput>grub-install '(hd0)'</userinput>. diff --git a/fr/preparing/bios-setup/i386.xml b/fr/preparing/bios-setup/i386.xml index 8db2ed95b..f11540203 100644 --- a/fr/preparing/bios-setup/i386.xml +++ b/fr/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"> + <sect2 arch="x86" id="bios-setup"> <title>Le menu de configuration du BIOS</title> <para> @@ -104,7 +104,7 @@ Consultez <ulink url="&url-simtel;"></ulink>. </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Slection du priphrique d'amorage</title> + <sect2 arch="x86" id="boot-dev-select"><title>Slection du priphrique d'amorage</title> <para> @@ -234,7 +234,7 @@ Souvent, vous devez appuyer sur <keycap>F10</keycap>. </para> </sect3> </sect2> -<sect2 arch="i386"> +<sect2 arch="x86"> <title>Autres rglages du BIOS</title> diff --git a/fr/preparing/minimum-hardware-reqts.xml b/fr/preparing/minimum-hardware-reqts.xml index 0c9b7b0aa..a846db273 100644 --- a/fr/preparing/minimum-hardware-reqts.xml +++ b/fr/preparing/minimum-hardware-reqts.xml @@ -14,7 +14,7 @@ Selon vos besoins, vous pouvez continuer avec du matriel infrieur au matriel recommand dans le tableau ci-dessous. Cependant, la plupart des utilisateurs seront frustrs s'ils ignorent ces suggestions. -</para><para arch="i386"> +</para><para arch="x86"> Un Pentium 100 est la configuration minimale recommande pour une machine de bureau, et un Pentium II-300 pour un serveur. diff --git a/fr/preparing/needed-info.xml b/fr/preparing/needed-info.xml index 9e5be861b..5666da475 100644 --- a/fr/preparing/needed-info.xml +++ b/fr/preparing/needed-info.xml @@ -46,9 +46,9 @@ configuration de votre matriel. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">HOWTO sur la compatibilit des matriels avec Linux</ulink> @@ -168,7 +168,7 @@ pour connatre cette combinaison. Il s'agit souvent de la touche Les botes et cartons de chaque pice ; </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> La fentre Systme dans le panneau de configuration de Windows ; @@ -208,7 +208,7 @@ configuration du rseau et du courrier. </row> <row arch="not-s390"><entry>Leur ordre dans le systme</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>S'ils sont IDE ou SCSI (la plupart sont IDE)</entry> </row> <row arch="m68k"> @@ -291,19 +291,19 @@ De plus, le matriel pour Linux est amlior chaque jour. Cependant, Linux ne peut pas utiliser autant de matriels que d'autres systmes d'exploitation. -</para><para arch="i386"> +</para><para arch="x86"> En particulier, Linux n'est pas compatible avec le matriel qui ncessite Windows pour fonctionner. -</para><para arch="i386"> +</para><para arch="x86"> Bien que Linux puisse faire fonctionner certains matriels spcifiques Windows, le faire demande un effort supplmentaire. D'autre part, les pilotes Linux pour ce type de matriel sont souvent dpendants d'une version du noyau, et sont donc rapidement obsoltes. -</para><para arch="i386"> +</para><para arch="x86"> Les dnomms <quote>win-modems</quote> sont le cas le plus courant de ce type de matriel. Mais des imprimantes et d'autres priphriques peuvent diff --git a/fr/preparing/non-debian-partitioning.xml b/fr/preparing/non-debian-partitioning.xml index 0639ac43a..8ea73a0d9 100644 --- a/fr/preparing/non-debian-partitioning.xml +++ b/fr/preparing/non-debian-partitioning.xml @@ -21,7 +21,7 @@ De mme, une machine signifie une LPAR ou VM. Si vous avez dj un systme d'exploitation sur votre machine -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD…) </phrase> @@ -43,7 +43,7 @@ racine du systme Debian. </para><para> Vous pouvez trouver des informations sur le partitionnement actuel -en utilisant un outil appropri pour votre systme d'exploitation<phrase arch="i386">, tel que fdisk ou PartitionMagic</phrase><phrase arch="powerpc">, +en utilisant un outil appropri pour votre systme d'exploitation<phrase arch="x86">, tel que fdisk ou PartitionMagic</phrase><phrase arch="powerpc">, tel que Drive Setup, HD Toolkit ou MacTools</phrase><phrase arch="m68k">, tel que HD SC Setup, HDToolBox ou SCSITool</phrase><phrase arch="s390">, tel que le diskmap VM</phrase>. Les outils de partitionnement permettent @@ -96,7 +96,7 @@ Vous devriez nanmoins continuer de lire les paragraphes suivants, car il existe certains cas qui obligent partitionner avant de dmarrer l'installation. -</para><para arch="i386"> +</para><para arch="x86"> Si votre machine possde un systme de fichiers FAT ou NTFS, utilis par DOS et Windows, vous pouvez attendre et utiliser le partitionneur de l'installateur Debian pour redimensionner le systme de diff --git a/fr/preparing/nondeb-part/i386.xml b/fr/preparing/nondeb-part/i386.xml index 1b146a06f..63f8717c4 100644 --- a/fr/preparing/nondeb-part/i386.xml +++ b/fr/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386"><title>Partitionnement depuis DOS ou Windows</title> + <sect2 arch="x86"><title>Partitionnement depuis DOS ou Windows</title> <para> Si vous manipulez des partitions FAT ou NTFS existantes, il est diff --git a/fr/preparing/pre-install-bios-setup.xml b/fr/preparing/pre-install-bios-setup.xml index 8d613b3ec..53e9f4e9a 100644 --- a/fr/preparing/pre-install-bios-setup.xml +++ b/fr/preparing/pre-install-bios-setup.xml @@ -60,7 +60,7 @@ FIXME: description plus pousse ncessaire. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> Les meilleures cartes mres supportent la mmoire parit et vous indiqueront si votre systme possde une telle mmoire. @@ -72,7 +72,7 @@ vos donnes. En conclusion, les meilleurs systmes ont des cartes mres qui acceptent la mmoire parit et des barrettes SIMM parit relle ; voir : <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Si vous avez de la mmoire vive parit relle et que votre carte mre peut en tenir compte, activez tous les rglages du BIOS qui causeront @@ -80,7 +80,7 @@ l'interruption par la carte mre en cas d'erreur de parit mmoire. </para> - <sect3 arch="i386"><title>Le bouton-poussoir turbo </title> + <sect3 arch="x86"><title>Le bouton-poussoir turbo </title> <para> Beaucoup de systmes ont un bouton-poussoir <emphasis>turbo</emphasis> qui @@ -94,7 +94,7 @@ bouton-poussoir turbo. </para> </sect3> - <sect3 arch="i386"><title>CPU Cyrix et erreurs de disquettes</title> + <sect3 arch="x86"><title>CPU Cyrix et erreurs de disquettes</title> <para> Beaucoup d'utilisateurs de processeur Cyrix ont d dsactiver le cache dans @@ -115,7 +115,7 @@ invalide aprs un passage du code 16-bit en code 32-bit. </para> </sect3> - <sect3 arch="i386"><title>Configuration matrielle</title> + <sect3 arch="x86"><title>Configuration matrielle</title> <para> Vous devrez peut-tre modifier certaines configurations ou certains @@ -135,7 +135,7 @@ haute que le total de votre mmoire RAM (ou mmoire vive) de votre systme. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>BIOS et Claviers USB</title> <para> diff --git a/fr/using-d-i/modules/clock-setup.xml b/fr/using-d-i/modules/clock-setup.xml index 75ccf76e5..8fffcacaa 100644 --- a/fr/using-d-i/modules/clock-setup.xml +++ b/fr/using-d-i/modules/clock-setup.xml @@ -18,7 +18,7 @@ En mode expert il est toujours possible de rgler l'horloge sur UTC. <phrase arch="m68k;powerpc">Les horloges des machines Macintosh utilisent normalement une heure locale. Si vous dsirez amorcer plusieurs systmes, slectionnez heure locale plutt que GMT.</phrase> -<phrase arch="i386">Les machines qui tournent (aussi) sous Dos ou Windows sont +<phrase arch="x86">Les machines qui tournent (aussi) sous Dos ou Windows sont normalement rgles sur l'heure locale. Si vous dsirez utiliser plusieurs systmes, slectionnez heure locale plutt que GMT.</phrase> diff --git a/fr/using-d-i/modules/i386/grub-installer.xml b/fr/using-d-i/modules/i386/grub-installer.xml index b98b612ea..165146507 100644 --- a/fr/using-d-i/modules/i386/grub-installer.xml +++ b/fr/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 18640 --> -<sect3 arch="i386"> +<sect3 arch="x86"> <title>Installer le programme d'amorage <command>Grub</command> sur un disque dur</title> diff --git a/fr/using-d-i/modules/i386/lilo-installer.xml b/fr/using-d-i/modules/i386/lilo-installer.xml index 2ec21c38e..4c0c28867 100644 --- a/fr/using-d-i/modules/i386/lilo-installer.xml +++ b/fr/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Installer le programme d'amorage <command>LILO</command> sur un disque dur</title> diff --git a/it/administrivia/administrivia.xml b/it/administrivia/administrivia.xml index 9b994138f..8df41348f 100644 --- a/it/administrivia/administrivia.xml +++ b/it/administrivia/administrivia.xml @@ -232,7 +232,7 @@ Una parte della sezione di questo manuale sull'installazione con chroot (<xref linkend="linux-upgrade"/>) è derivata da alcuni documenti sotto il copyright di Karsten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> <!-- The section on installations over plip in this manual diff --git a/it/appendix/chroot-install.xml b/it/appendix/chroot-install.xml index 14e384410..326220154 100644 --- a/it/appendix/chroot-install.xml +++ b/it/appendix/chroot-install.xml @@ -646,7 +646,7 @@ affinché carichi il kernel installato con la nuova partizione di root. Si noti che debootstrap non installa di suo un boot loader, lo si può fare tramite apt-get dall'interno della chroot Debian. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Check <userinput>info grub</userinput> or <userinput>man @@ -670,7 +670,7 @@ sistema e lì modificarlo opportunamente. Dopo averlo modificato eseguire lilo (ricordandosi che usa il <filename>lilo.conf</filename> relativo al sistema su cui viene lanciato). -</para><para arch="i386"> +</para><para arch="x86"> <!-- Here is a basic <filename>/etc/lilo.conf</filename> as an example: diff --git a/it/appendix/plip.xml b/it/appendix/plip.xml index 17bd4a214..76fd06457 100644 --- a/it/appendix/plip.xml +++ b/it/appendix/plip.xml @@ -2,7 +2,7 @@ <!-- original version: 29687 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <!-- <title>Installing &debian; over Parallel Line IP (PLIP)</title> --> <title>Installazione di &debian; via Parallel Line IP (PLIP)</title> <para> diff --git a/it/boot-installer/boot-installer.xml b/it/boot-installer/boot-installer.xml index 6c98fde40..5951ff0ba 100644 --- a/it/boot-installer/boot-installer.xml +++ b/it/boot-installer/boot-installer.xml @@ -8,7 +8,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <!-- <title>Booting the Installer on &arch-title;</title> --> <title>Avvio dell'installatore su &arch-title;</title> diff --git a/it/boot-installer/i386.xml b/it/boot-installer/i386.xml index 9c9233560..942b6044b 100644 --- a/it/boot-installer/i386.xml +++ b/it/boot-installer/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 38231 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Booting from a CD-ROM</title> --> <title>Avvio da CD-ROM</title> @@ -106,7 +106,7 @@ Avvia la versione <quote>bf2.4</quote>. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> <title>Avvio da una partizione DOS</title> @@ -151,7 +151,7 @@ compressed format</computeroutput>. END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <!-- <title>Booting from Linux using <command>LILO</command> or <command>GRUB</command></title> --> <title>Avvio di Linux usando <command>LILO</command> o @@ -311,7 +311,7 @@ D'ora in poi non ci sono differenze fra <command>GRUB</command> e </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <!-- <title>Booting from USB Memory Stick</title> --> <title>Avvio da chiavetta USB</title> <para> @@ -335,7 +335,7 @@ opzionali oppure premere &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <!-- <title>Booting from Floppies</title> --> <title>Avvio da dischetti</title> <para> @@ -448,7 +448,7 @@ installazione <command>debian-installer</command> parte automaticamente. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"> + <sect2 arch="x86" id="boot-tftp"> <!-- <title>Booting with TFTP</title> --> <title>Avvio con TFTP</title> @@ -529,7 +529,7 @@ fornisce dischetti d'avvio e bootrom per l'avvio TFTP. </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>The Boot Prompt</title> --> <title>Il prompt boot</title> <para> diff --git a/it/boot-installer/intro-cd.xml b/it/boot-installer/intro-cd.xml index 7626c3d4e..b37a872e0 100644 --- a/it/boot-installer/intro-cd.xml +++ b/it/boot-installer/intro-cd.xml @@ -13,7 +13,7 @@ Il metodo più semplice per la maggior parte degli utenti è di servirsi dei CD Debian. Se si possiedono i CD Debian e se la macchina in uso supporta l'avvio da CDROM, bene! Si può semplicemente -<phrase arch="i386"> +<phrase arch="x86"> <!-- configure your system for booting off a CD as described in diff --git a/it/boot-installer/parameters.xml b/it/boot-installer/parameters.xml index 55f2b8eda..c71d3143f 100644 --- a/it/boot-installer/parameters.xml +++ b/it/boot-installer/parameters.xml @@ -397,7 +397,7 @@ crea problemi è possibile disabilitarlo usando il parametro messaggi d'errore riguardo bterm o bogl, lo schermo nero oppure un blocco entro pochi minuti dall'inizio dell'installazione. -</para><para arch="i386"> +</para><para arch="x86"> <!-- The <userinput>video=vga16:off</userinput> argument may also be used diff --git a/it/boot-installer/trouble.xml b/it/boot-installer/trouble.xml index 0ec626f1a..16207f2f1 100644 --- a/it/boot-installer/trouble.xml +++ b/it/boot-installer/trouble.xml @@ -120,12 +120,12 @@ per l'installatore. <!-- Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> --> Spesso i problemi possono essere risolti staccando le periferiche esterne -e riprovando l'avvio.<phrase arch="i386"> I modem interni, le schede +e riprovando l'avvio.<phrase arch="x86"> I modem interni, le schede audio e i dispositivi Plug-n-Play possono essere particolarmente problematici.</phrase> @@ -146,7 +146,7 @@ memoria visibile dal kernel, per esempio con <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <!-- <title>Common &arch-title; Installation Problems</title> --> <title>Problemi comuni di installazione su &arch-title;</title> <para> diff --git a/it/hardware/hardware-supported.xml b/it/hardware/hardware-supported.xml index c874d4297..0483f440f 100644 --- a/it/hardware/hardware-supported.xml +++ b/it/hardware/hardware-supported.xml @@ -265,7 +265,7 @@ problema, assicurandosi di indicare che il bug affligge la piattaforma <sect2 id="gfx" arch="not-s390"> <!-- <title>Graphics Card</title> --> <title>Schede video</title> -<para arch="i386"> +<para arch="x86"> <!-- You should be using a VGA-compatible display interface for the console @@ -337,7 +337,7 @@ con le schede di prototipazione della Broadcom. </para> </sect2> - <sect2 arch="i386" id="laptops"> + <sect2 arch="x86" id="laptops"> <!-- <title>Laptops</title> --> <title>Portatili</title> <para> diff --git a/it/hardware/installation-media.xml b/it/hardware/installation-media.xml index cd87d5e35..f37f5788e 100644 --- a/it/hardware/installation-media.xml +++ b/it/hardware/installation-media.xml @@ -94,7 +94,7 @@ possibile usare il CD-ROM assieme ad un'altra tecnica per l'installazione del sistema, dopo che il sistema d'installazione è stato avviato in un altro modo; vedere <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all @@ -115,7 +115,7 @@ l'avvio da queste interfacce. Il <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contiene delle informazioni più approfondite sull'uso dei CD-ROM con Linux. -</para><para arch="i386"> +</para><para arch="x86"> <!-- USB CD-ROM drives are also supported, as are FireWire devices that @@ -412,7 +412,7 @@ personalizzato). Il supporto per la maggior quantità di dispositivi è desiderabile in generale per permettere che Debian possa essere installata sul numero maggiore possibile di combinazioni di hardware. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Generally, the Debian installation system includes support for floppies, @@ -427,7 +427,7 @@ porta parallela, i controller e i dispositivi SCSI, USB e FireWire. I filesystem supportati comprendono FAT, le estensioni Win-32 FAT (VFAT) e NTFS. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Disk interfaces that emulate the <quote>AT</quote> hard disk interface diff --git a/it/hardware/network-cards.xml b/it/hardware/network-cards.xml index 484c70692..83379f1d5 100644 --- a/it/hardware/network-cards.xml +++ b/it/hardware/network-cards.xml @@ -5,7 +5,7 @@ <sect1 id="network-cards"> <!-- <title>Network Connectivity Hardware</title> --> <title>Schede di rete</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -38,7 +38,7 @@ schede che i protocolli. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> <!-- As for ISDN, the D-channel protocol for the (old) German 1TR6 is not diff --git a/it/hardware/supported-peripherals.xml b/it/hardware/supported-peripherals.xml index 88bdbfb5c..18dbd1e73 100644 --- a/it/hardware/supported-peripherals.xml +++ b/it/hardware/supported-peripherals.xml @@ -18,7 +18,7 @@ come per esempio mouse, stampanti, dispositivi PCMCIA e USB. Tuttavia molte di queste periferiche non sono necessarie durante l'installazione del sistema. -</para><para arch="i386"> +</para><para arch="x86"> <!-- USB hardware generally works fine, only some @@ -30,7 +30,7 @@ L'hardware USB generalmente funziona correttamente, solo qualche tastiera USB a volte può richiedere qualche configurazione aggiuntiva (si veda <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> <!-- Again, see the @@ -113,7 +113,7 @@ new &arch-title; machines at all. Sfortunatamente, è abbastanza difficile trovare un venditore che distribuisca macchine &arch-title; nuove. -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you do have to buy a machine with Windows bundled, carefully read @@ -208,7 +208,7 @@ comunità del software libero è un mercato importante. </para> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Windows-specific Hardware</title> --> <title>Hardware specifico per Windows</title> <para> diff --git a/it/hardware/supported/i386.xml b/it/hardware/supported/i386.xml index c1979d9e3..ed8c61090 100644 --- a/it/hardware/supported/i386.xml +++ b/it/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>CPU, Main Boards, and Video Support</title> --> <title>CPU, schede madri e video supportate</title> <para> diff --git a/it/howto/installation-howto.xml b/it/howto/installation-howto.xml index 0d7e82cc9..d4b693b99 100644 --- a/it/howto/installation-howto.xml +++ b/it/howto/installation-howto.xml @@ -146,7 +146,7 @@ il primo CD della serie. <!-- Download whichever type you prefer and burn it to a CD. -<phrase arch="i386">To boot the CD, you may need to change your BIOS +<phrase arch="x86">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See @@ -155,7 +155,7 @@ To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See --> Scaricare il tipo che si preferisce e masterizzare l'immagine su un CD. -<phrase arch="i386"> +<phrase arch="x86"> Per fare l'avvio da CD potrebbe essere necessario modificare la configurazione del BIOS del proprio computer come spiegato in <xref linkend="bios-setup" />. @@ -295,7 +295,7 @@ C'è un altro modo, più flessibile, per preparare una chiavetta con il debian-installer che permette anche l'uso di penne più piccole. Per i dettagli si veda <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Some BIOSes can boot USB storage directly, and some cannot. You may need to @@ -339,7 +339,7 @@ l'avvio da rete dipendono dall'architetettura e dalla configurazione. I file in <filename>netboot/</filename> possono essere usati per l'avvio dalla rete del &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> <!-- The easiest thing to set up is probably PXE netbooting. Untar the @@ -374,7 +374,7 @@ existing hard disk, which can have a different OS on it. Download and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> explains one way to do it. </phrase> --> @@ -386,7 +386,7 @@ Scaricare <filename>hd-media/initrd.gz</filename>, directory principale del disco fisso, assicurarsi che il nome del file con l'immagine abbia estensione <literal>.iso</literal>. Adesso si deve solamente avviare Linux con initrd. -<phrase arch="i386"> +<phrase arch="x86"> In <xref linkend="boot-initrd" /> è spiegato come farlo. </phrase> @@ -403,7 +403,7 @@ In <xref linkend="boot-initrd" /> è spiegato come farlo. Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. --> @@ -412,7 +412,7 @@ Una volta che l'installatore parte è mostrata una schermata iniziale. Premere &enterkey; per proseguire con l'installazione oppure leggere le istruzioni sugli altri metodi e i parametri di avvio (si consulti <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Se si vuole usare un kernel 2.4, inserire <userinput>install24</userinput> al prompt <prompt>boot:</prompt> @@ -492,7 +492,7 @@ Questa procedura è quella raccomandata per gli utenti inesperti e per coloro che hanno fretta, ma se non si vuole eseguire il partizionamento automatico si deve scegliere <quote>manuale</quote> dal menu. -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you have an existing DOS or Windows partition that you want to preserve, @@ -548,7 +548,7 @@ viene installato il kernel. The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. -<phrase arch="i386">By default GRUB will be installed to the master boot +<phrase arch="x86">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase> @@ -557,7 +557,7 @@ given the opportunity to override that choice and install it elsewhere. L'ultimo passo è installare un boot loader. Se l'installatore rileva la presenza di altri sistemi operativi sul computer è in grado di aggiungerli nel menu di avvio. -<phrase arch="i386"> +<phrase arch="x86"> GRUB viene installato nel master boot record del primo disco, normalmente questa è una buona scelta. Comunque viene data l'opportunità di cambiare questa scelta in modo da installarlo da qualche altra parte. diff --git a/it/install-methods/boot-drive-files.xml b/it/install-methods/boot-drive-files.xml index 877d951ee..9c4d8cdb5 100644 --- a/it/install-methods/boot-drive-files.xml +++ b/it/install-methods/boot-drive-files.xml @@ -31,7 +31,7 @@ puramente da rete evitando tutte le noie dei supporti rimovibili come la ricerca e la masterizzazione delle immagini dei CD o la lotta con troppi e inaffidabili dischetti. -</para><para arch="i386"> +</para><para arch="x86"> <!-- The installer cannot boot from files on an NTFS file system. @@ -75,7 +75,7 @@ o <quote>OldWorld</quote>. </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <!-- <title>Hard disk installer booting using <command>LILO</command> or <command>GRUB</command></title> --> <title>Avvio dell'installatore da disco fisso con <command>LILO</command> o diff --git a/it/install-methods/boot-usb-files.xml b/it/install-methods/boot-usb-files.xml index 0e52f3591..168282718 100644 --- a/it/install-methods/boot-usb-files.xml +++ b/it/install-methods/boot-usb-files.xml @@ -41,7 +41,7 @@ fare anche installazioni più piccole seguendo <sect2 id="usb-copy-easy"> <!-- <title>Copying the files — the easy way</title> --> <title>Copia dei file — il modo semplice</title> -<para arch="i386"> +<para arch="x86"> <!-- There is an all-in-one file <filename>hd-media/boot.img.gz</filename> @@ -97,10 +97,10 @@ fare attenzione a usare il nome corretto per il device della chiavetta USB. <!-- After that, mount the USB memory stick (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), which will now have -<phrase arch="i386">a FAT filesystem</phrase> +<phrase arch="x86">a FAT filesystem</phrase> <phrase arch="powerpc">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. @@ -108,10 +108,10 @@ Unmount the stick (<userinput>umount /mnt</userinput>) and you are done. --> Poi montare la chiavetta USB (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), che adesso avrà -<phrase arch="i386">un filesystem FAT,</phrase> +<phrase arch="x86">un filesystem FAT,</phrase> <phrase arch="powerpc">un filesystem HFS,</phrase> e copiarci l'immagine ISO netinst o businesscard Debian. Si noti che il nome del file deve avere estensione <filename>.iso</filename>. Infine smontare la @@ -191,7 +191,7 @@ Conclusa la copia dei file, smontare la chiavetta USB (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Booting the USB stick</title> --> <title>Avvio da chiavetta USB</title> <warning><para> diff --git a/it/install-methods/install-tftp.xml b/it/install-methods/install-tftp.xml index 9ce4a31c8..5a92842f8 100644 --- a/it/install-methods/install-tftp.xml +++ b/it/install-methods/install-tftp.xml @@ -151,7 +151,7 @@ architettura che implementi questo protocollo. Negli esempi di questa sezione sono presentati i comandi per SunOS 4.x, SunOS 5.x (noti come Solaris) e GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> <!-- To use the Pre-boot Execution Environment (PXE) method of TFTP @@ -314,7 +314,7 @@ sempre tramite TFTP. Per l'avvio dalla rete usare <filename>yaboot-netboot.conf</filename>, lo si deve copiare nella directory TFTP e poi rinominarlo in <filename>yaboot.conf</filename>. -</para><para arch="i386"> +</para><para arch="x86"> <!-- For PXE booting, everything you should need is set up in the diff --git a/it/install-methods/tftp/dhcp.xml b/it/install-methods/tftp/dhcp.xml index 06d5aa332..6bc3118f1 100644 --- a/it/install-methods/tftp/dhcp.xml +++ b/it/install-methods/tftp/dhcp.xml @@ -80,7 +80,7 @@ riavviarlo con <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>Enabling PXE Booting in the DHCP configuration</title> --> <title>Abilitare l'avvio PXE nella configurazione di DHCP</title> <para> diff --git a/it/install-methods/usb-setup/i386.xml b/it/install-methods/usb-setup/i386.xml index d9a65a22b..4509526c7 100644 --- a/it/install-methods/usb-setup/i386.xml +++ b/it/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 36841 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>USB stick partitioning on &arch-title;</title> --> <title>Partizionamento della chiavetta USB su &arch-title;</title> <para> diff --git a/it/partitioning/device-names.xml b/it/partitioning/device-names.xml index f7639c827..1162f4b15 100644 --- a/it/partitioning/device-names.xml +++ b/it/partitioning/device-names.xml @@ -123,7 +123,7 @@ chiamarsi <filename>/dev/hda</filename> in Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The first XT disk is named <filename>/dev/xda</filename>. @@ -132,7 +132,7 @@ The first XT disk is named <filename>/dev/xda</filename>. Il primo disco XT chiamato <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The second XT disk is named <filename>/dev/xdb</filename>. @@ -230,7 +230,7 @@ In questo caso, la soluzione migliore consiste nell'osservare i messaggi di boot, a patto di saper distinguere i due dischi dal nome del modello e/o dalla capacit. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Linux represents the primary partitions as the drive name, plus the diff --git a/it/partitioning/partition-programs.xml b/it/partitioning/partition-programs.xml index a369b7e83..1baaa8093 100644 --- a/it/partitioning/partition-programs.xml +++ b/it/partitioning/partition-programs.xml @@ -30,13 +30,13 @@ dell'architettura. <!-- Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems -<phrase arch="i386"> (<quote>format</quote> in Windows speak)</phrase> +<phrase arch="x86"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints. --> Lo strumento di partizionamento raccomandato da Debian. Questo <quote>coltellino svizzero</quote> dai mille usi, pu anche ridimensionare -le partizioni, creare file system <phrase arch="i386">(ossia +le partizioni, creare file system <phrase arch="x86">(ossia <quote>formattarli</quote> nel gergo di Windows)</phrase> e assegnarli ai punti di montaggio. @@ -228,11 +228,11 @@ e i moduli, si eseguir: </screen></informalexample> <!-- -<phrase arch="i386">Remember to mark your boot partition as +<phrase arch="x86">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase> --> -<phrase arch="i386">Occorre anche ricordarsi di marcare la partizione di boot +<phrase arch="x86">Occorre anche ricordarsi di marcare la partizione di boot come <quote>Avviabile</quote>.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/it/partitioning/partition/i386.xml b/it/partitioning/partition/i386.xml index 57c78c859..a270b673e 100644 --- a/it/partitioning/partition/i386.xml +++ b/it/partitioning/partition/i386.xml @@ -3,7 +3,7 @@ <!-- original version: 35590 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Partitioning for &arch-title;</title> --> <title>Partizionare per &arch-title;</title> <para> diff --git a/it/post-install/kernel-baking.xml b/it/post-install/kernel-baking.xml index f9bdbb21e..5f6fd9917 100644 --- a/it/post-install/kernel-baking.xml +++ b/it/post-install/kernel-baking.xml @@ -304,7 +304,7 @@ like any package. As root, do </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as <quote>i586</quote>, </phrase> +<phrase arch="x86"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, @@ -330,7 +330,7 @@ personalizzato come qualsiasi altro pacchetto. Da root eseguire </phrase> La parte <replaceable>sottoarchitettura</replaceable> è opzionale e indica la sottoarchitettura, -<phrase arch="i386"> per esempio <quote>i586</quote>, </phrase> +<phrase arch="x86"> per esempio <quote>i586</quote>, </phrase> in base alle opzioni del kernel sono state attivate. <userinput>dpkg -i</userinput> installa il kernel più alcuni file di supporto. Per esempio sono installati i file diff --git a/it/post-install/reactivating-win.xml b/it/post-install/reactivating-win.xml index 117f0a340..7b2df7267 100644 --- a/it/post-install/reactivating-win.xml +++ b/it/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <!-- <title>Reactivating DOS and Windows</title> --> <title>Riattivazione di DOS e Windows</title> <para> diff --git a/it/post-install/rescue.xml b/it/post-install/rescue.xml index 86e445d59..599a34f38 100644 --- a/it/post-install/rescue.xml +++ b/it/post-install/rescue.xml @@ -81,7 +81,7 @@ Se possibile l'installatore fornisce una shell sul filesystem che si è scelto, questa shell può essere usata per effettuare qualsiasi operazione necessaria al ripristino. -<phrase arch="i386"> +<phrase arch="x86"> <!-- For example, if you need to reinstall the GRUB boot loader into the master diff --git a/it/preparing/bios-setup/i386.xml b/it/preparing/bios-setup/i386.xml index 057364adf..1e74b1229 100644 --- a/it/preparing/bios-setup/i386.xml +++ b/it/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"> + <sect2 arch="x86" id="bios-setup"> <!-- <title>Invoking the BIOS Set-Up Menu</title> --> <title>Invocare il menu di configurazione del BIOS</title> <para> @@ -162,7 +162,7 @@ cercare in <ulink url="&url-simtel;"></ulink>. </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"> + <sect2 arch="x86" id="boot-dev-select"> <!-- <title>Boot Device Selection</title> --> <title>Selezione del dispositivo di boot</title> <para> @@ -389,7 +389,7 @@ rendere effettive le modifiche. Spesso di deve premere <keycap>F10</keycap>. </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Miscellaneous BIOS Settings</title> --> <title>Opzioni varie del BIOS</title> diff --git a/it/preparing/minimum-hardware-reqts.xml b/it/preparing/minimum-hardware-reqts.xml index 989c365d8..ddcc0ae95 100644 --- a/it/preparing/minimum-hardware-reqts.xml +++ b/it/preparing/minimum-hardware-reqts.xml @@ -29,7 +29,7 @@ A seconda delle proprie necessità si potrebbe aver a che fare con qualcosa meno di quanto raccomandato nella tabella seguente. Comunque, la maggior parte degli utenti diventa frustrata se ignora questi suggerimenti. -</para><para arch="i386"> +</para><para arch="x86"> <!-- A Pentium 100 is the minimum recommended for desktop diff --git a/it/preparing/needed-info.xml b/it/preparing/needed-info.xml index f591a9f47..d15a907c4 100644 --- a/it/preparing/needed-info.xml +++ b/it/preparing/needed-info.xml @@ -75,8 +75,8 @@ Contiene informazioni utili sulla configurazione o l'utilizzo dell'hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> -<itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> +<itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -243,7 +243,7 @@ Confezioni e scatole dei componenti hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The System window in the Windows Control Panel. @@ -303,7 +303,7 @@ rete e della posta elettronica. Il loro ordine sul sistema.</entry> </row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry><!-- Whether IDE or SCSI (most computers are IDE). --> Se è IDE o SCSI (la maggior parte dei computer usa IDE).</entry> </row> @@ -426,7 +426,7 @@ l'hardware per Linux cresce quotidianamente anche se, purtroppo, ancora Linux non funziona su parecchi tipi di hardware su cui invece funzionano altri sistemi operativi. -</para><para arch="i386"> +</para><para arch="x86"> <!-- In particular, Linux usually cannot run hardware that requires a @@ -436,7 +436,7 @@ running version of Windows to work. In particolare Linux non può funzionare sull'hardware che richiede Windows per funzionare. -</para><para arch="i386"> +</para><para arch="x86"> <!-- Although some Windows-specific hardware can be made to run on Linux, @@ -450,7 +450,7 @@ funzionare sotto Linux, farlo di solito richiede del lavoro aggiuntivo. Inoltre i driver Linux per l'hardware specifico per Windows sono specifici per una versione del kernel, quindi diventano rapidamente obsoleti. -</para><para arch="i386"> +</para><para arch="x86"> <!-- So called win-modems are the most common type of this hardware. diff --git a/it/preparing/non-debian-partitioning.xml b/it/preparing/non-debian-partitioning.xml index c4c765374..72a6c2f28 100644 --- a/it/preparing/non-debian-partitioning.xml +++ b/it/preparing/non-debian-partitioning.xml @@ -39,7 +39,7 @@ If you already have an operating system on your system Se sul proprio sistema è già presente un sistema operativo -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -76,7 +76,7 @@ ma tale questione non verrà affrontata in questo documento. Come minimo <!-- You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase -arch="i386">, such as fdisk or PartitionMagic</phrase><phrase +arch="x86">, such as fdisk or PartitionMagic</phrase><phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always @@ -85,7 +85,7 @@ provide a way to show existing partitions without making changes. Si possono ottenere delle informazioni sull'attuale configurazione delle partizioni usando un programma per il partizionamento per il sistema -operativo che si sta attualmente usando<phrase arch="i386">, per esempio +operativo che si sta attualmente usando<phrase arch="x86">, per esempio fdisk o PartitionMagic</phrase><phrase arch="powerpc">, per esempio Drive Setup, HD Toolkit o MacTools</phrase><phrase arch="m68k">, per esempio HD SC Setup, HDToolBox o SCSITool</phrase><phrase arch="s390">, per esempio @@ -179,7 +179,7 @@ delle partizioni esistenti all'interno della mappa delle partizioni, che rendono obbligatorio il ripartizionamenro del disco prima di procedere all'installazione. -</para><para arch="i386"> +</para><para arch="x86"> <!-- If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, diff --git a/it/preparing/nondeb-part/i386.xml b/it/preparing/nondeb-part/i386.xml index e1ac2bb99..c973e6a3d 100644 --- a/it/preparing/nondeb-part/i386.xml +++ b/it/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Partitioning From DOS or Windows</title> --> <title>Partizionare da DOS o Windows</title> <para> diff --git a/it/preparing/pre-install-bios-setup.xml b/it/preparing/pre-install-bios-setup.xml index de610a132..1c728ab67 100644 --- a/it/preparing/pre-install-bios-setup.xml +++ b/it/preparing/pre-install-bios-setup.xml @@ -96,7 +96,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> <!-- The very best motherboards support parity RAM and will actually tell @@ -118,7 +118,7 @@ di errori nei propri dati. Perciò i sistemi migliori hanno schede madri che supportano la parità e i moduli di memoria a parità reale, si veda <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you do have true-parity RAM and your motherboard can handle it, be @@ -132,7 +132,7 @@ il lavoro della scheda madre quando rileva un errore di parità. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>The Turbo Switch</title> --> <title>L'interruttore turbo</title> <para> @@ -157,7 +157,7 @@ accidentalmente toccare il controllo software del turbo. </para> </sect3> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>Cyrix CPUs and Floppy Disk Errors</title> --> <title>Errori dei dischetti con le CPU Cyrix</title> <para> @@ -194,7 +194,7 @@ dall'invalidazione della cache a seguito di un passaggio da codice a </para> </sect3> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>Peripheral Hardware Settings</title> --> <title>Impostazioni delle periferiche</title> <para> @@ -230,7 +230,7 @@ sistema. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <!-- <title>USB keyboards</title> --> <title>Tastiere USB</title> <para> diff --git a/it/using-d-i/modules/clock-setup.xml b/it/using-d-i/modules/clock-setup.xml index 8d3ba64e4..d0292e311 100644 --- a/it/using-d-i/modules/clock-setup.xml +++ b/it/using-d-i/modules/clock-setup.xml @@ -28,7 +28,7 @@ whether or not the clock is set to UTC. <phrase arch="m68k;powerpc">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> -<phrase arch="i386">Systems that (also) run Dos or Windows are normally +<phrase arch="x86">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> --> @@ -38,7 +38,7 @@ computer è regolato con l'ora locale o con UTC. <phrase arch="m68k;powerpc">L'orologio hardware dei Macintosh è normalmente regolato con l'ora locale, se si vuole un sistema dual-boot scegliere l'ora locale invece di GMT.</phrase> -<phrase arch="i386">I sistemi su cui viene usato (anche) Dos o Windows sono +<phrase arch="x86">I sistemi su cui viene usato (anche) Dos o Windows sono normalmente regolati con l'ora locale, se si vuole un sistema dual-boot scegliere l'ora locale invece di GMT.</phrase> diff --git a/it/using-d-i/modules/i386/grub-installer.xml b/it/using-d-i/modules/i386/grub-installer.xml index 0bafa2f8c..3830ad345 100644 --- a/it/using-d-i/modules/i386/grub-installer.xml +++ b/it/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>Install the <command>Grub</command> Boot Loader on a Hard Disk</title> --> <title>Installazione del boot loader <command>Grub</command> sul diff --git a/it/using-d-i/modules/i386/lilo-installer.xml b/it/using-d-i/modules/i386/lilo-installer.xml index 811b18ba4..b71456c1e 100644 --- a/it/using-d-i/modules/i386/lilo-installer.xml +++ b/it/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <!-- <title>Install the <command>LILO</command> Boot Loader on a Hard Disk</title> --> <title>Installazione del boot loader <command>LILO</command> sul diff --git a/ja/administrivia/administrivia.xml b/ja/administrivia/administrivia.xml index fbfeaab3f..3ab28b499 100644 --- a/ja/administrivia/administrivia.xml +++ b/ja/administrivia/administrivia.xml @@ -240,7 +240,7 @@ documents copyright Karsten M. Self. (<xref linkend="linux-upgrade"/>) は、 Karsten M. 自身が著作権を持つドキュメントの一部が元になっています。 -</para><para arch="i386"> +</para><para arch="x86"> <!-- The section on installations over plip in this manual diff --git a/ja/appendix/chroot-install.xml b/ja/appendix/chroot-install.xml index d6e56ddbb..4c0826f99 100644 --- a/ja/appendix/chroot-install.xml +++ b/ja/appendix/chroot-install.xml @@ -611,7 +611,7 @@ debootstrap ϡ֡ȥȡ뤷ʤȤդƤ ȤϸäƤ⡢åȥåפ뤿 Debian chroot apt-get Ѥ뤳ȤǤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- Check <userinput>info grub</userinput> or <userinput>man @@ -635,7 +635,7 @@ lilo.conf ǤϿƥˤԡԽƤ (lilo ƤӽФƥȴطȤΡ <filename>lilo.conf</filename> ȤȤȤФƤƤ) -</para><para arch="i386"> +</para><para arch="x86"> <!-- Here is a basic <filename>/etc/lilo.conf</filename> as an example: diff --git a/ja/appendix/plip.xml b/ja/appendix/plip.xml index 129807cdb..caa2083bf 100644 --- a/ja/appendix/plip.xml +++ b/ja/appendix/plip.xml @@ -2,7 +2,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 29687 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <!-- <title>Installing &debian; over Parallel Line IP (PLIP)</title> --> diff --git a/ja/boot-installer/boot-installer.xml b/ja/boot-installer/boot-installer.xml index 7d1d9bbee..e54aebb8a 100644 --- a/ja/boot-installer/boot-installer.xml +++ b/ja/boot-installer/boot-installer.xml @@ -6,7 +6,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>&arch-title; ǤΥȡεư</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/ja/boot-installer/i386.xml b/ja/boot-installer/i386.xml index 56b6f6f63..febab4377 100644 --- a/ja/boot-installer/i386.xml +++ b/ja/boot-installer/i386.xml @@ -2,7 +2,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 38231 --> - <sect2 arch="i386"><title>CD-ROM εư</title> + <sect2 arch="x86"><title>CD-ROM εư</title> &boot-installer-intro-cd.xml; @@ -76,7 +76,7 @@ Boots the <quote>bf2.4</quote> flavor. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>DOS ѡƥεư</title> &boot-installer-intro-hd.xml; @@ -126,7 +126,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title><command>LILO</command> <command>GRUB</command> Ѥ Linux εư</title> @@ -276,7 +276,7 @@ initrd ΥѤ <userinput>ramdisk_size</userinput> Ρ </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>USB ꥹƥåεư</title> <para> @@ -298,7 +298,7 @@ arguments, or just hit &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>եåԡεư</title> <para> @@ -414,7 +414,7 @@ root եåԡ &enterkey; ȡ </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>TFTP Ǥεư</title> + <sect2 arch="x86" id="boot-tftp"><title>TFTP Ǥεư</title> &boot-installer-intro-net.xml; @@ -482,7 +482,7 @@ TFTP ֡ȤԤ֡ȥǥåȤȥ֡ ROM Ƥޤ </sect3> </sect2> - <sect2 arch="i386"><title>֡ȥץץ</title> + <sect2 arch="x86"><title>֡ȥץץ</title> <para> <!-- diff --git a/ja/boot-installer/intro-cd.xml b/ja/boot-installer/intro-cd.xml index 588b56f3a..281324936 100644 --- a/ja/boot-installer/intro-cd.xml +++ b/ja/boot-installer/intro-cd.xml @@ -8,7 +8,7 @@ The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply -<phrase arch="i386"> +<phrase arch="x86"> configure your system for booting off a CD as described in <xref linkend="boot-dev-select"/>, </phrase> @@ -19,7 +19,7 @@ Debian CD åȤȤΤִñϩȻפޤ CD åȤ˼긵ˤꡢ ĥȡ뤹ޥ CD ľܵưǤ褦ʤ顢 ĥƤޤ! ñ -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-dev-select"/> ˽äơ CD 鵯ưǤ褦ƥꤷȡ </phrase> diff --git a/ja/boot-installer/parameters.xml b/ja/boot-installer/parameters.xml index 178d4f6bd..c37026e8a 100644 --- a/ja/boot-installer/parameters.xml +++ b/ja/boot-installer/parameters.xml @@ -360,7 +360,7 @@ starting the install. bterm bogl ˴ؤ륨顼å䡢ðŤʲ̡ ȡ뤬Ϥޤäƿʬ˥եǤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- The <userinput>video=vga16:off</userinput> argument may also be used diff --git a/ja/boot-installer/trouble.xml b/ja/boot-installer/trouble.xml index a54f55680..59f7fda91 100644 --- a/ja/boot-installer/trouble.xml +++ b/ja/boot-installer/trouble.xml @@ -117,12 +117,12 @@ your kernel. The installer requires <!-- Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> --> ޤߥɤյ곰ƺƵưƤߤȡ Τ褦꤬Ǥ뤳Ȥ褯ޤ -<phrase arch="i386">¢ǥࡢɥɡ +<phrase arch="x86">¢ǥࡢɥɡ Plug-n-Play ǥХʤɤäȤʤ꤬Ǥ</phrase> </para><para> @@ -141,7 +141,7 @@ kernel sees, such as <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <!-- <title>Common &arch-title; Installation Problems</title> --> diff --git a/ja/hardware/hardware-supported.xml b/ja/hardware/hardware-supported.xml index e31b2704f..e0ab0b41f 100644 --- a/ja/hardware/hardware-supported.xml +++ b/ja/hardware/hardware-supported.xml @@ -278,7 +278,7 @@ as well. <sect2 id="gfx" arch="not-s390"><title>եå</title> -<para arch="i386"> +<para arch="x86"> <!-- You should be using a VGA-compatible display interface for the console @@ -346,7 +346,7 @@ Broadcom ɾܡѤ<ulink url="&url-bcm91250a-hardware;">ߴꥹ</ulink </sect2> - <sect2 arch="i386" id="laptops"><title>åץȥåץԥ塼</title> + <sect2 arch="x86" id="laptops"><title>åץȥåץԥ塼</title> <para> <!-- diff --git a/ja/hardware/installation-media.xml b/ja/hardware/installation-media.xml index 373461b1a..c47bae98b 100644 --- a/ja/hardware/installation-media.xml +++ b/ja/hardware/installation-media.xml @@ -84,7 +84,7 @@ CD-ROM εưǤʤƥǤϡ ȡ CD-ROM Ȥޤ <xref linkend="boot-installer"/> Ȥư¾ˡǵưƤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all @@ -105,7 +105,7 @@ Linux CD-ROM Ѥ뤿ξܺ٤ʾϡ <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> ˤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- USB CD-ROM drives are also supported, as are FireWire devices that @@ -369,7 +369,7 @@ Debian εưǥˤϡޤޤʥƥ˺бͥ뤬 ޤޤʥϡɥسμ¤ Debian ȡ뤹ˤ ǤǥХݡȤΤ˾ޤǤ礦 -</para><para arch="i386"> +</para><para arch="x86"> <!-- Generally, the Debian installation system includes support for floppies, @@ -382,7 +382,7 @@ Win-32 FAT extensions (VFAT) and NTFS. SCSI ȥȥɥ饤֡USBFireWire ݡȤƤޤ ݡȤƤե륷ƥϡFATWin-32 ĥ FAT (VFAT)NTFS Ǥ -</para><para arch="i386"> +</para><para arch="x86"> <!-- Disk interfaces that emulate the <quote>AT</quote> hard disk interface diff --git a/ja/hardware/network-cards.xml b/ja/hardware/network-cards.xml index 4f6399d23..63629f94f 100644 --- a/ja/hardware/network-cards.xml +++ b/ja/hardware/network-cards.xml @@ -5,7 +5,7 @@ <sect1 id="network-cards"> <title>ͥåȥ³</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -44,7 +44,7 @@ otherwise unsupported card and then substitute in the installer (see ȡ֤뤳ȤϲǽǤ (<xref linkend="rescue-replace-kernel"/> )--> -</para><para arch="i386"> +</para><para arch="x86"> <!-- As for ISDN, the D-channel protocol for the (old) German 1TR6 is not diff --git a/ja/hardware/supported-peripherals.xml b/ja/hardware/supported-peripherals.xml index c3242a146..7dc4360f0 100644 --- a/ja/hardware/supported-peripherals.xml +++ b/ja/hardware/supported-peripherals.xml @@ -15,7 +15,7 @@ Linux ϡޥץʡPCMCIA USB ǥХʤɤ ޤޤʥϡɥбƤޤ ƥΥȡˡΥǥХɬפʤ櫓ǤϤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- USB hardware generally works fine, only some @@ -26,7 +26,7 @@ USB ϡɥϤƤޤưޤ USB ܡɤɲ꤬ɬפ⤷ޤ (<xref linkend="usb-keyboard-config"/> ) -</para><para arch="i386"> +</para><para arch="x86"> <!-- Again, see the @@ -105,7 +105,7 @@ new &arch-title; machines at all. --> ǰʤ顢 &arch-title; ޥв٤٥ ۤȤɤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you do have to buy a machine with Windows bundled, carefully read @@ -198,7 +198,7 @@ is an important market. </sect2> - <sect2 arch="i386"><title>Windows òϡɥ</title> + <sect2 arch="x86"><title>Windows òϡɥ</title> <para> <!-- diff --git a/ja/hardware/supported/i386.xml b/ja/hardware/supported/i386.xml index c7838c94b..cf23eb0b2 100644 --- a/ja/hardware/supported/i386.xml +++ b/ja/hardware/supported/i386.xml @@ -3,7 +3,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"><title>CPUޥܡɡӥǥΥݡ</title> + <sect2 arch="x86"><title>CPUޥܡɡӥǥΥݡ</title> <para> <!-- diff --git a/ja/howto/installation-howto.xml b/ja/howto/installation-howto.xml index 3e63b27d7..2b6ed8735 100644 --- a/ja/howto/installation-howto.xml +++ b/ja/howto/installation-howto.xml @@ -151,10 +151,10 @@ Download whichever type you prefer and burn it to a CD. --> ߤΥפɤơCD ˾ƤƤ <!-- -<phrase arch="i386">To boot the CD, you may need to change your BIOS +<phrase arch="x86">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend="bios-setup" />.</phrase> --> -<phrase arch="i386">CD 鵯ưˤϡ<xref linkend="bios-setup" /> +<phrase arch="x86">CD 鵯ưˤϡ<xref linkend="bios-setup" /> Ƥ褦ˡBIOS ѹɬפ뤫⤷ޤ</phrase> <phrase arch="powerpc"> <!-- @@ -283,7 +283,7 @@ sticks. For details, see <xref linkend="boot-usb-files" />. ˡꡢäȾʥΥꥹƥåưޤ ܺ٤ϡ<xref linkend="boot-usb-files" /> -</para><para arch="i386"> +</para><para arch="x86"> <!-- Some BIOSes can boot USB storage directly, and some cannot. You may need to @@ -325,7 +325,7 @@ The files in <filename>netboot/</filename> can be used to netboot &d-i;. netboot Τ͡ˡϡƥ netboot åȥåפ˰¸ޤ <filename>netboot/</filename> ʲΥեϡ&d-i; netboot 뤿˻ѤǤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- The easiest thing to set up is probably PXE netbooting. Untar the @@ -368,7 +368,7 @@ it's just a matter of booting linux with the initrd. Debian CD ϡɥǥΰ־Υǥ쥯ȥ˥ɤƤ CD Υե̾ <literal>.iso</literal> ǽäƤ뤳ȤΤƤ initrd linux εưˤǤ -<phrase arch="i386"> +<phrase arch="x86"> <!-- <xref linkend="boot-initrd" /> explains one way to do it. --> @@ -394,7 +394,7 @@ methods and parameters (see <xref linkend="boot-parms" />). ȡ餬Ω夬Ȥˡޤν̤ɽޤ ư뤿 &enterkey; ¾εưˡѥΤ ɤǤ (<xref linkend="boot-parms" />) -<phrase arch="i386"> +<phrase arch="x86"> <!-- If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. @@ -469,7 +469,7 @@ but if you do not want to autopartition, choose manual from the menu. 뵡ͿޤϿ桼ޤǤïˤǤޤ ưʬ˾ޤʤϥ˥塼ޥ˥奢Ӥޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you have an existing DOS or Windows partition that you want to preserve, @@ -522,11 +522,11 @@ and let you know. ڥ졼ƥƥФϡȡ餬֡ȥ˥塼 äΤ餻ޤ <!-- -<phrase arch="i386">By default GRUB will be installed to the master boot +<phrase arch="x86">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. --> -<phrase arch="i386">GRUB ϡǥեȤ 1 ϡɥɥ饤֤ +<phrase arch="x86">GRUB ϡǥեȤ 1 ϡɥɥ饤֤ ޥ֡ȥ쥳ɤ˥ȡ뤵졢̤ˤɤǤ ̵ˤ¾ξ˥ȡ뤹뵡Ϳޤ </phrase> diff --git a/ja/install-methods/boot-drive-files.xml b/ja/install-methods/boot-drive-files.xml index 887748332..e6ced5d80 100644 --- a/ja/install-methods/boot-drive-files.xml +++ b/ja/install-methods/boot-drive-files.xml @@ -31,7 +31,7 @@ unreliable floppy disks. ȤäࡼХ֥ǥΤ٤Ƥη뤳ȤǤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- The installer cannot boot from files on an NTFS file system. @@ -75,7 +75,7 @@ depending on whether the system is a <quote>NewWorld</quote> or an </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title><command>LILO</command> <command>GRUB</command>ѤϡɥǥΥȡεư</title> <para> diff --git a/ja/install-methods/boot-usb-files.xml b/ja/install-methods/boot-usb-files.xml index bdadbb3e8..03692d279 100644 --- a/ja/install-methods/boot-usb-files.xml +++ b/ja/install-methods/boot-usb-files.xml @@ -39,7 +39,7 @@ USB ƥåϾʤȤ 128 MB ΥʤФʤޤ <sect2 id="usb-copy-easy"> <title>եΥԡ — ñˡ</title> -<para arch="i386"> +<para arch="x86"> <!-- There is an all-in-one file <filename>hd-media/boot.img.gz</filename> @@ -94,19 +94,19 @@ USB ƥåǥХ̾ǧƻѤƤ <!-- After that, mount the USB memory stick (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), which will now have -<phrase arch="i386">a FAT filesystem</phrase> +<phrase arch="x86">a FAT filesystem</phrase> <phrase arch="powerpc">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done. --> θ塢USB ꥹƥå -(<phrase arch="i386">FAT ե륷ƥ</phrase> +(<phrase arch="x86">FAT ե륷ƥ</phrase> <phrase arch="powerpc">HFS ե륷ƥ</phrase>ˤʤäƤ) ޥȤ -(<userinput>mount <replaceable arch="i386">/dev/sda</replaceable> +(<userinput>mount <replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>) Debian netinst ̾ɷ ISO ԡƤ @@ -189,7 +189,7 @@ When you are done, unmount the USB memory stick (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <!-- <title>Booting the USB stick</title> --> diff --git a/ja/install-methods/install-tftp.xml b/ja/install-methods/install-tftp.xml index cde4a448b..a26d2cd08 100644 --- a/ja/install-methods/install-tftp.xml +++ b/ja/install-methods/install-tftp.xml @@ -139,7 +139,7 @@ Trivial File Transfer Protocol (TFTP) ϡ ǤϡSunOS 4.x, SunOS 5.x (Solaris), GNU/Linux Ǥޤ -<note arch="i386"><para> +<note arch="x86"><para> <!-- To use the Pre-boot Execution Environment (PXE) method of TFTP @@ -147,7 +147,7 @@ booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>. -</para><note arch="i386"><para> +</para><note arch="x86"><para> --> TFTP ֡Ȥ Pre-boot Execution Environment (PXE) ˡѤˤϡ <userinput>tsize</userinput>ݡȤ TFTP Фɬפˤʤޤ @@ -297,7 +297,7 @@ NewWorld Power Macintosh ޥǤϡ <filename>yaboot.conf</filename> Ȥ̾Ѥơ TFTP Υǥ쥯ȥ֤Ƥ -</para><para arch="i386"> +</para><para arch="x86"> <!-- For PXE booting, everything you should need is set up in the diff --git a/ja/install-methods/tftp/dhcp.xml b/ja/install-methods/tftp/dhcp.xml index 0e3d0a635..74fab66e4 100644 --- a/ja/install-methods/tftp/dhcp.xml +++ b/ja/install-methods/tftp/dhcp.xml @@ -76,7 +76,7 @@ restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>DHCP Ǥ PXE ưͭ</title> <para> <!-- diff --git a/ja/install-methods/usb-setup/i386.xml b/ja/install-methods/usb-setup/i386.xml index 64b7da9db..25700f66d 100644 --- a/ja/install-methods/usb-setup/i386.xml +++ b/ja/install-methods/usb-setup/i386.xml @@ -2,7 +2,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 36841--> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>&arch-title; Ǥ USB ƥåΥѡƥʬ</title> <para> diff --git a/ja/partitioning/device-names.xml b/ja/partitioning/device-names.xml index 957d4bef5..025593dc6 100644 --- a/ja/partitioning/device-names.xml +++ b/ja/partitioning/device-names.xml @@ -112,7 +112,7 @@ Debian Ǥ <filename>/dev/hda</filename> ɽޤ) </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The first XT disk is named <filename>/dev/xda</filename>. @@ -120,7 +120,7 @@ The first XT disk is named <filename>/dev/xda</filename>. 1 XT ǥ <filename>/dev/xda</filename> ̾դ롣 </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The second XT disk is named <filename>/dev/xdb</filename>. @@ -210,7 +210,7 @@ and/or capacities. ɥ饤֤Υǥ̤ΤäƤʤ顢 ֡ȥåܤΤǤɤǤ礦 -</para><para arch="i386"> +</para><para arch="x86"> <!-- Linux represents the primary partitions as the drive name, plus the diff --git a/ja/partitioning/partition-programs.xml b/ja/partitioning/partition-programs.xml index 5a6142d4a..f05ed2ce7 100644 --- a/ja/partitioning/partition-programs.xml +++ b/ja/partitioning/partition-programs.xml @@ -31,12 +31,12 @@ your architecture. <!-- Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems -<phrase arch="i386"> (<quote>format</quote> in Windows speak)</phrase> +<phrase arch="x86"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints. --> Debian 侩ΥѡƥʬġǤΥߡʥդϡ ѡƥѹꡢե륷ƥ -<phrase arch="i386"> (Windows ǸȤ <quote>եޥå</quote>) </phrase> +<phrase arch="x86"> (Windows ǸȤ <quote>եޥå</quote>) </phrase> ꡢޥȥݥȤꤷꤹ뤳ȤǤޤ </para></listitem> @@ -212,10 +212,10 @@ on the target system. After installing the kernel and modules, execute: </screen></informalexample> <!-- -<phrase arch="i386">Remember to mark your boot partition as +<phrase arch="x86">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase> --> -<phrase arch="i386">֡ȥѡƥ +<phrase arch="x86">֡ȥѡƥ <quote>ưǽ (Bootable)</quote>˥ޡΤ˺ʤ</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/ja/partitioning/partition/i386.xml b/ja/partitioning/partition/i386.xml index 834afe257..ca241c2dd 100644 --- a/ja/partitioning/partition/i386.xml +++ b/ja/partitioning/partition/i386.xml @@ -3,7 +3,7 @@ <!-- original version: 39465 --> - <sect2 arch="i386"><title>&arch-title; ǤΥѡƥʬ</title> + <sect2 arch="x86"><title>&arch-title; ǤΥѡƥʬ</title> <para> <!-- diff --git a/ja/post-install/kernel-baking.xml b/ja/post-install/kernel-baking.xml index 5916760b8..8c6239285 100644 --- a/ja/post-install/kernel-baking.xml +++ b/ja/post-install/kernel-baking.xml @@ -278,7 +278,7 @@ like any package. As root, do </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as <quote>i586</quote>, </phrase> +<phrase arch="x86"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, @@ -303,7 +303,7 @@ you'll need to install that package as well. </phrase> ¹ԤƤ<replaceable>subarchitecture</replaceable> ϡ ͥΥץꤵ줿 -<phrase arch="i386"> <quote>i586</quote> Τ褦</phrase> +<phrase arch="x86"> <quote>i586</quote> Τ褦</phrase> ǤդΥ֥ƥɽƤޤ ޤ <userinput>dpkg -i</userinput> ȤȡͥȰ ΩŪʥե⤤Ĥȡ뤵ޤ㤨 diff --git a/ja/post-install/reactivating-win.xml b/ja/post-install/reactivating-win.xml index ec8d7e853..7c7c2a5a5 100644 --- a/ja/post-install/reactivating-win.xml +++ b/ja/post-install/reactivating-win.xml @@ -3,7 +3,7 @@ <!-- original version: 28672 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>DOS Windows ѤǤ褦ˤ</title> <para> diff --git a/ja/post-install/rescue.xml b/ja/post-install/rescue.xml index b5ee073b1..1eae5cd1f 100644 --- a/ja/post-install/rescue.xml +++ b/ja/post-install/rescue.xml @@ -77,7 +77,7 @@ repairs. ǽǤм˥ȡϡե륷ƥˤ롢 ɤɬפʽ¹Ԥ뤿ˤȤ륷ץץȤޤ -<phrase arch="i386"> +<phrase arch="x86"> <!-- For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command diff --git a/ja/preparing/bios-setup/i386.xml b/ja/preparing/bios-setup/i386.xml index 432c101e5..34ce985a4 100644 --- a/ja/preparing/bios-setup/i386.xml +++ b/ja/preparing/bios-setup/i386.xml @@ -3,7 +3,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386" id="bios-setup"><title>BIOS ˥塼εư</title> + <sect2 arch="x86" id="bios-setup"><title>BIOS ˥塼εư</title> <para> @@ -167,7 +167,7 @@ BIOS CMOS ˥塼ʤΤ⤢ޤ </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>֡ȥǥХ</title> + <sect2 arch="x86" id="boot-dev-select"><title>֡ȥǥХ</title> <para> @@ -373,7 +373,7 @@ save the changes on your computer. Often, you must press </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>¾ BIOS </title> <sect3 id="cd-settings"><title>CD-ROM </title> diff --git a/ja/preparing/minimum-hardware-reqts.xml b/ja/preparing/minimum-hardware-reqts.xml index c02da9e73..60d85ac90 100644 --- a/ja/preparing/minimum-hardware-reqts.xml +++ b/ja/preparing/minimum-hardware-reqts.xml @@ -27,7 +27,7 @@ risk being frustrated if they ignore these suggestions. Τ̵뤷ϡ ǽ⤯ʤäƤޤȻפޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- A Pentium 100 is the minimum recommended for desktop diff --git a/ja/preparing/needed-info.xml b/ja/preparing/needed-info.xml index abe3ef2a2..efb573fbf 100644 --- a/ja/preparing/needed-info.xml +++ b/ja/preparing/needed-info.xml @@ -82,8 +82,8 @@ Often contains useful information on configuring or using your hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <!-- <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -254,7 +254,7 @@ The cases and boxes for each piece of hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> <!-- The System window in the Windows Control Panel. @@ -315,7 +315,7 @@ networking and e-mail. <row arch="not-s390"><entry>Their order on the system.</entry></row> <row arch="not-s390;not-m68k"> "not-m68k;not-s390" would really turn out to be everything... -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Whether IDE or SCSI (most computers are IDE).</entry> </row> <row arch="m68k"> @@ -333,7 +333,7 @@ networking and e-mail. </row> <row arch="not-s390"><entry>ƥǤ³</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>IDE SCSI (Υԥ塼 IDE)</entry> </row> <row arch="m68k"> @@ -484,7 +484,7 @@ run as many different types of hardware as some operating systems. Ǥޤ Linux ϡ OS ۤɤˤ¿¿ͤʥϡɥбƤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- In particular, Linux usually cannot run hardware that requires a @@ -493,7 +493,7 @@ running version of Windows to work. äˡLinux ̾ΥС Windows ɬפȤ ϡɥưȤϤǤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- Although some Windows-specific hardware can be made to run on Linux, @@ -507,7 +507,7 @@ Linux ưǤΤϤޤ̾;ʬϫϤɬפȤʤޤ Linux ͥ˰¸Τˤʤޤ äơ˸ŤΤˤʤäƤޤޤ -</para><para arch="i386"> +</para><para arch="x86"> <!-- So called win-modems are the most common type of this hardware. diff --git a/ja/preparing/non-debian-partitioning.xml b/ja/preparing/non-debian-partitioning.xml index 475949f08..63ade5d0e 100644 --- a/ja/preparing/non-debian-partitioning.xml +++ b/ja/preparing/non-debian-partitioning.xml @@ -35,7 +35,7 @@ If you already have an operating system on your system --> ƥ˴˥ڥ졼ƥƥ -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -72,14 +72,14 @@ Linux Windows MacOS ΥѡƥˤϥȡǤޤ <!-- You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase -arch="i386">, such as fdisk or PartitionMagic</phrase><phrase +arch="x86">, such as fdisk or PartitionMagic</phrase><phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes. --> ߤΥѡƥϡ<phrase -arch="i386">fdisk PartitionMagic</phrase><phrase +arch="x86">fdisk PartitionMagic</phrase><phrase arch="powerpc">Drive Setup, HD Toolkit, MacTools</phrase><phrase arch="m68k">HD SC Setup, HDToolBox, SCSITool</phrase><phrase arch="s390">VM diskmap</phrase>Τ褦ʡ @@ -173,7 +173,7 @@ Debian ȡΥѡƥʬץǺȤԤäƹޤ ˤƤ⥤ȡ˥ѡƥʬȤ ʤФʤʤ褦ʾ⤢뤫Ǥ -</para><para arch="i386"> +</para><para arch="x86"> <!-- If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to diff --git a/ja/preparing/nondeb-part/i386.xml b/ja/preparing/nondeb-part/i386.xml index c90966346..99a404c9a 100644 --- a/ja/preparing/nondeb-part/i386.xml +++ b/ja/preparing/nondeb-part/i386.xml @@ -3,7 +3,7 @@ <!-- original version: 36732 --> - <sect2 arch="i386"><title>DOS Windows Υѡƥʬ</title> + <sect2 arch="x86"><title>DOS Windows Υѡƥʬ</title> <para> <!-- diff --git a/ja/preparing/pre-install-bios-setup.xml b/ja/preparing/pre-install-bios-setup.xml index 95b22793c..cb9260452 100644 --- a/ja/preparing/pre-install-bios-setup.xml +++ b/ja/preparing/pre-install-bios-setup.xml @@ -90,7 +90,7 @@ FIXME: äɬס </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> <!-- The very best motherboards support parity RAM and will actually tell @@ -112,7 +112,7 @@ parity and true-parity memory modules; see ʪΥѥƥդ⥸塼ȹ礻ȤȤˤʤޤ <xref linkend="Parity-RAM"/> -</para><para arch="i386"> +</para><para arch="x86"> <!-- If you do have true-parity RAM and your motherboard can handle it, be @@ -125,7 +125,7 @@ interrupt on memory parity errors. </para> - <sect3 arch="i386"><title>ܥå</title> + <sect3 arch="x86"><title>ܥå</title> <para> <!-- @@ -149,7 +149,7 @@ BIOS Ǥ褦ʤ顢 </para> </sect3> - <sect3 arch="i386"><title>Cyrix CPU ȥեåԡǥΥ顼</title> + <sect3 arch="x86"><title>Cyrix CPU ȥեåԡǥΥ顼</title> <para> <!-- @@ -186,7 +186,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code. </para> </sect3> - <sect3 arch="i386"><title>յ</title> + <sect3 arch="x86"><title>յ</title> <para> <!-- @@ -219,7 +219,7 @@ amount of RAM in your system. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>USB BIOS ݡȤȥܡ</title> <para> diff --git a/ja/using-d-i/modules/clock-setup.xml b/ja/using-d-i/modules/clock-setup.xml index 23ecd4bc6..e148eee76 100644 --- a/ja/using-d-i/modules/clock-setup.xml +++ b/ja/using-d-i/modules/clock-setup.xml @@ -30,7 +30,7 @@ whether or not the clock is set to UTC. <phrase arch="m68k;powerpc">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> -<phrase arch="i386">Systems that (also) run Dos or Windows are normally +<phrase arch="x86">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> --> @@ -39,7 +39,7 @@ instead of GMT.</phrase> <phrase arch="m68k;powerpc">Macintosh Υϡɥåϡ ̾˥åȤƤޤǥ奢֡Ȥϡ GMT ǤϤʤƤ</phrase> -<phrase arch="i386">DOS Windows (Ǥ) ư륷ƥ̾ +<phrase arch="x86">DOS Windows (Ǥ) ư륷ƥ̾ ˥åȤƤޤ ǥ奢֡Ȥϡ GMT ǤϤʤƤ</phrase> diff --git a/ja/using-d-i/modules/i386/grub-installer.xml b/ja/using-d-i/modules/i386/grub-installer.xml index f87fb2257..e29ed9a87 100644 --- a/ja/using-d-i/modules/i386/grub-installer.xml +++ b/ja/using-d-i/modules/i386/grub-installer.xml @@ -2,7 +2,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>ϡɥǥؤ <command>Grub</command> ֡ȥΥȡ</title> <para> diff --git a/ja/using-d-i/modules/i386/lilo-installer.xml b/ja/using-d-i/modules/i386/lilo-installer.xml index 6d82d2218..9baffe8f7 100644 --- a/ja/using-d-i/modules/i386/lilo-installer.xml +++ b/ja/using-d-i/modules/i386/lilo-installer.xml @@ -2,7 +2,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>ϡɥǥؤ <command>LILO</command> ֡ȥΥȡ</title> <para> diff --git a/nl/administrivia/administrivia.xml b/nl/administrivia/administrivia.xml index 755206e5b..bda5de650 100644 --- a/nl/administrivia/administrivia.xml +++ b/nl/administrivia/administrivia.xml @@ -131,7 +131,7 @@ The section on chrooted installations in this manual (<xref linkend="linux-upgrade"/>) was derived in part from documents copyright Karsten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> The section on installations over plip in this manual (<xref linkend="plip"/>) was based on the diff --git a/nl/appendix/chroot-install.xml b/nl/appendix/chroot-install.xml index 33acc1e47..3239a6998 100644 --- a/nl/appendix/chroot-install.xml +++ b/nl/appendix/chroot-install.xml @@ -403,7 +403,7 @@ the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so. -</para><para arch="i386"> +</para><para arch="x86"> Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the @@ -414,7 +414,7 @@ add an entry for the Debian install to your existing grub edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from). -</para><para arch="i386"> +</para><para arch="x86"> Here is a basic <filename>/etc/lilo.conf</filename> as an example: diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml index 858f97d4d..f3d889ecf 100644 --- a/nl/appendix/plip.xml +++ b/nl/appendix/plip.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 39463 untranslated --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Installing &debian; over Parallel Line IP (PLIP)</title> <para> diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml index 0a5a08799..797bc7dcf 100644 --- a/nl/boot-installer/boot-installer.xml +++ b/nl/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/nl/boot-installer/i386.xml b/nl/boot-installer/i386.xml index ab6130b4b..04a390056 100644 --- a/nl/boot-installer/i386.xml +++ b/nl/boot-installer/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 38231 untranslated --> - <sect2 arch="i386"><title>Booting from a CD-ROM</title> + <sect2 arch="x86"><title>Booting from a CD-ROM</title> &boot-installer-intro-cd.xml; @@ -74,7 +74,7 @@ Boots the <quote>bf2.4</quote> flavor. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Booting from a DOS partition</title> &boot-installer-intro-hd.xml; @@ -105,7 +105,7 @@ bf2.4 flavor. The symptom of the problem is an END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Booting from Linux Using <command>LILO</command> or <command>GRUB</command></title> @@ -192,7 +192,7 @@ or <command>LILO</command>. </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Booting from USB Memory Stick</title> <para> @@ -206,7 +206,7 @@ arguments, or just hit &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Booting from Floppies</title> <para> @@ -266,7 +266,7 @@ contents are loaded into memory. The installer program </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title> &boot-installer-intro-net.xml; @@ -312,7 +312,7 @@ provides bootdiskettes and even bootroms that do a TFTPboot. </sect3> </sect2> - <sect2 arch="i386"><title>The Boot Prompt</title> + <sect2 arch="x86"><title>The Boot Prompt</title> <para> When the installer boots, you should be presented with a friendly graphical diff --git a/nl/boot-installer/intro-cd.xml b/nl/boot-installer/intro-cd.xml index 8a3e1b20a..2e8898998 100644 --- a/nl/boot-installer/intro-cd.xml +++ b/nl/boot-installer/intro-cd.xml @@ -6,7 +6,7 @@ The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply -<phrase arch="i386"> +<phrase arch="x86"> configure your system for booting off a CD as described in <xref linkend="boot-dev-select"/>, </phrase> diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml index e8e0d8cb3..3f5672214 100644 --- a/nl/boot-installer/parameters.xml +++ b/nl/boot-installer/parameters.xml @@ -220,7 +220,7 @@ you can disable the feature by the parameter about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="i386"> +</para><para arch="x86"> The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml index bd3a3be40..18c9916bf 100644 --- a/nl/boot-installer/trouble.xml +++ b/nl/boot-installer/trouble.xml @@ -67,7 +67,7 @@ your kernel. The installer requires </para><para> Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="i386">Internal modems, sound +then trying booting again. <phrase arch="x86">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase> </para><para> @@ -80,7 +80,7 @@ kernel sees, such as <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Common &arch-title; Installation Problems</title> <para> diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index 8d077a974..60ae21274 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -222,7 +222,7 @@ as well. <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title> -<para arch="i386"> +<para arch="x86"> You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with @@ -260,7 +260,7 @@ listing</ulink> for Broadcom evaluation boards is available. </sect2> - <sect2 arch="i386" id="laptops"><title>Laptops</title> + <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> Laptops are also supported. Laptops are often specialized or contain diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml index 34a6e015f..cdcb110bc 100644 --- a/nl/hardware/installation-media.xml +++ b/nl/hardware/installation-media.xml @@ -50,7 +50,7 @@ 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 <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the @@ -60,7 +60,7 @@ them to work, and booting off these non-standard interfaces is unlikely. The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux. -</para><para arch="i386"> +</para><para arch="x86"> USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers. @@ -214,14 +214,14 @@ 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. -</para><para arch="i386"> +</para><para arch="x86"> Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS. -</para><para arch="i386"> +</para><para arch="x86"> Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml index deb384f58..55d1ba8f7 100644 --- a/nl/hardware/network-cards.xml +++ b/nl/hardware/network-cards.xml @@ -4,7 +4,7 @@ <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -23,7 +23,7 @@ cards and protocols. otherwise unsupported card and then substitute in the installer (see <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml index 43512b498..1cb38ab47 100644 --- a/nl/hardware/supported-peripherals.xml +++ b/nl/hardware/supported-peripherals.xml @@ -9,13 +9,13 @@ Linux 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. -</para><para arch="i386"> +</para><para arch="x86"> USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Again, see the <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -58,7 +58,7 @@ be sure that the hardware is well-supported by GNU/Linux. Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all. -</para><para arch="i386"> +</para><para arch="x86"> 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 @@ -108,7 +108,7 @@ is an important market. </sect2> - <sect2 arch="i386"><title>Windows-specific Hardware</title> + <sect2 arch="x86"><title>Windows-specific Hardware</title> <para> A disturbing trend is the proliferation of Windows-specific modems and diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml index 725a5169b..6159a9fc9 100644 --- a/nl/hardware/supported/i386.xml +++ b/nl/hardware/supported/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 11648 untranslated --> - <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title> + <sect2 arch="x86"><title>CPU, Main Boards, and Video Support</title> <para> Complete information concerning supported peripherals can be found at diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml index 438c3be8a..4f4e4b67b 100644 --- a/nl/howto/installation-howto.xml +++ b/nl/howto/installation-howto.xml @@ -79,7 +79,7 @@ only need the first CD of the set. </para><para> Download whichever type you prefer and burn it to a CD. -<phrase arch="i386">To boot the CD, you may need to change your BIOS +<phrase arch="x86">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See @@ -152,7 +152,7 @@ There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a @@ -175,7 +175,7 @@ It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into @@ -198,7 +198,7 @@ existing hard disk, which can have a different OS on it. Download and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> explains one way to do it. </phrase> @@ -213,7 +213,7 @@ it's just a matter of booting linux with the initrd. Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> @@ -255,7 +255,7 @@ opportunity to automatically partition either an entire drive, or free space on a drive. This is recommended for new users or anyone in a hurry, but if you do not want to autopartition, choose manual from the menu. -</para><para arch="i386"> +</para><para arch="x86"> If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, @@ -282,7 +282,7 @@ which can take a while. That is followed by installing a kernel. The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. -<phrase arch="i386">By default GRUB will be installed to the master boot +<phrase arch="x86">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase> diff --git a/nl/install-methods/boot-drive-files.xml b/nl/install-methods/boot-drive-files.xml index 1cea9d4f6..3c471f6f7 100644 --- a/nl/install-methods/boot-drive-files.xml +++ b/nl/install-methods/boot-drive-files.xml @@ -16,7 +16,7 @@ technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks. -</para><para arch="i386"> +</para><para arch="x86"> The installer cannot boot from files on an NTFS file system. @@ -39,7 +39,7 @@ depending on whether the system is a <quote>NewWorld</quote> or an </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Hard disk installer booting using <command>LILO</command> or <command>GRUB</command></title> <para> diff --git a/nl/install-methods/boot-usb-files.xml b/nl/install-methods/boot-usb-files.xml index fb4198303..8187b3ddd 100644 --- a/nl/install-methods/boot-usb-files.xml +++ b/nl/install-methods/boot-usb-files.xml @@ -23,7 +23,7 @@ setups are possible if you follow <xref linkend="usb-copy-flexible"/>). <sect2 id="usb-copy-easy"> <title>Copying the files — the easy way</title> -<para arch="i386"> +<para arch="x86"> There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well @@ -57,10 +57,10 @@ that you use the correct device name for your USB stick. <para> After that, mount the USB memory stick (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), which will now have -<phrase arch="i386">a FAT filesystem</phrase> +<phrase arch="x86">a FAT filesystem</phrase> <phrase arch="powerpc">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. @@ -110,7 +110,7 @@ When you are done, unmount the USB memory stick (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Booting the USB stick</title> <warning><para> diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index 51730ad2a..6900aac44 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -70,7 +70,7 @@ which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> @@ -161,7 +161,7 @@ images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory. -</para><para arch="i386"> +</para><para arch="x86"> For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml index f51eb2622..4e292ceef 100644 --- a/nl/install-methods/tftp/dhcp.xml +++ b/nl/install-methods/tftp/dhcp.xml @@ -52,7 +52,7 @@ restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Enabling PXE Booting in the DHCP configuration</title> <para> Here is another example for a <filename>dhcp.conf</filename> using the diff --git a/nl/install-methods/usb-setup/i386.xml b/nl/install-methods/usb-setup/i386.xml index a6e062902..8652b4845 100644 --- a/nl/install-methods/usb-setup/i386.xml +++ b/nl/install-methods/usb-setup/i386.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 36841 untranslated --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>USB stick partitioning on &arch-title;</title> <para> diff --git a/nl/partitioning/device-names.xml b/nl/partitioning/device-names.xml index 49effd568..fdd81d286 100644 --- a/nl/partitioning/device-names.xml +++ b/nl/partitioning/device-names.xml @@ -67,12 +67,12 @@ up as <filename>/dev/hda</filename> in Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The first XT disk is named <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> The second XT disk is named <filename>/dev/xdb</filename>. @@ -125,7 +125,7 @@ the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities. -</para><para arch="i386"> +</para><para arch="x86"> Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the diff --git a/nl/partitioning/partition-programs.xml b/nl/partitioning/partition-programs.xml index a5852ac9f..5d951dbb2 100644 --- a/nl/partitioning/partition-programs.xml +++ b/nl/partitioning/partition-programs.xml @@ -20,7 +20,7 @@ your architecture. Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems -<phrase arch="i386"> (<quote>format</quote> in Windows speak)</phrase> +<phrase arch="x86"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints. </para></listitem> @@ -140,7 +140,7 @@ on the target system. After installing the kernel and modules, execute: # chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">Remember to mark your boot partition as +<phrase arch="x86">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/nl/partitioning/partition/i386.xml b/nl/partitioning/partition/i386.xml index 6d864a2ba..979106c98 100644 --- a/nl/partitioning/partition/i386.xml +++ b/nl/partitioning/partition/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 39465 untranslated --> - <sect2 arch="i386"><title>Partitioning for &arch-title;</title> + <sect2 arch="x86"><title>Partitioning for &arch-title;</title> <para> If you have an existing other operating system such as DOS or Windows and diff --git a/nl/post-install/kernel-baking.xml b/nl/post-install/kernel-baking.xml index 433375fd7..9b021deed 100644 --- a/nl/post-install/kernel-baking.xml +++ b/nl/post-install/kernel-baking.xml @@ -158,7 +158,7 @@ like any package. As root, do </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, -<phrase arch="i386"> such as <quote>i586</quote>, </phrase> +<phrase arch="x86"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, diff --git a/nl/post-install/reactivating-win.xml b/nl/post-install/reactivating-win.xml index e34f01d12..413eaa571 100644 --- a/nl/post-install/reactivating-win.xml +++ b/nl/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 28672 untranslated --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reactivating DOS and Windows</title> <para> diff --git a/nl/post-install/rescue.xml b/nl/post-install/rescue.xml index 1ec1fd1b6..ca4eeb478 100644 --- a/nl/post-install/rescue.xml +++ b/nl/post-install/rescue.xml @@ -42,7 +42,7 @@ If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. -<phrase arch="i386"> +<phrase arch="x86"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml index 224945c26..26bfbea9f 100644 --- a/nl/preparing/bios-setup/i386.xml +++ b/nl/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 untranslated --> - <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> + <sect2 arch="x86" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> <para> @@ -102,7 +102,7 @@ try using a shareware/freeware program. Try looking in </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title> + <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title> <para> @@ -230,7 +230,7 @@ save the changes on your computer. Often, you must press </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Miscellaneous BIOS Settings</title> <sect3 id="cd-settings"><title>CD-ROM Settings</title> diff --git a/nl/preparing/minimum-hardware-reqts.xml b/nl/preparing/minimum-hardware-reqts.xml index 9866cec25..234f5c472 100644 --- a/nl/preparing/minimum-hardware-reqts.xml +++ b/nl/preparing/minimum-hardware-reqts.xml @@ -14,7 +14,7 @@ bent, kunt uitvoeren. Afhankelijk van uw behoeften, zou u op sommige punten met minder kunnen volstaan dan de in de tabel hieronder aanbevolen specificaties. -</para><para arch="i386"> +</para><para arch="x86"> Voor desktop systemen wordt tenminste een Pentium 100 aanbevolen; voor een server tenminste een Pentium II-300. diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml index 5b530d25e..67265b9dd 100644 --- a/nl/preparing/needed-info.xml +++ b/nl/preparing/needed-info.xml @@ -47,8 +47,8 @@ Bevat vaak bruikbare informatie over de configuratie of het gebruik van uw hardware. </para> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -169,7 +169,7 @@ De verpakkingen van uw hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> Het Systeem-venster in het Configuratiescherm (Control Panel) van Windows. @@ -209,7 +209,7 @@ uw netwerk en e-mail. </row> <row arch="not-s390"><entry>Hun volgorde in het systeem.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Zijn ze IDE of SCSI (de meeste computers hebben IDE).</entry> </row> <row arch="m68k"> @@ -293,19 +293,19 @@ Toch ondersteunt Linux nog niet dezelfde variteit aan apparatuur als sommige andere besturingssystemen. <!-- s/hardware for/hardware support for/ ? //--> -</para><para arch="i386"> +</para><para arch="x86"> In het bijzonder kan Linux geen hardware aansturen die vereist dat een versie van Microsoft Windows actief is. -</para><para arch="i386"> +</para><para arch="x86"> Hoewel het mogelijk is om sommige Windows-specifieke apparatuur onder Linux aan de praat te krijgen, vereist dit vaak extra inspanning. Daarnaast horen de stuurprogramma's voor Windows-specifieke apparatuur vaak bij n bepaalde versie van de Linux kernel waardoor ze snel verouderd kunnen raken. -</para><para arch="i386"> +</para><para arch="x86"> De meest voorkomende apparatuur van dit type zijn de zogenaamde win-modems. Maar ook printers en andere apparatuur kunnen Windows-specifiek zijn. diff --git a/nl/preparing/non-debian-partitioning.xml b/nl/preparing/non-debian-partitioning.xml index 1cb00e460..3c40183ef 100644 --- a/nl/preparing/non-debian-partitioning.xml +++ b/nl/preparing/non-debian-partitioning.xml @@ -21,7 +21,7 @@ Analoog dient u systeem of machine te lezen als LPAR of VM-guest. Als er al een besturingssysteem op uw systeem aanwezig is -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -48,7 +48,7 @@ partitie nodig hebben voor het root-bestandssysteem van Debian. U kunt informatie over uw huidige partitie-indeling vinden door gebruik te maken van een schijfindelingsprogramma voor uw huidige besturingssysteem<phrase -arch="i386">, zoals fdisk of PartitionMagic</phrase><phrase +arch="x86">, zoals fdisk of PartitionMagic</phrase><phrase arch="powerpc">, zoals Drive Setup, HD Toolkit of MacTools</phrase><phrase arch="m68k">, zoals HD SC Setup, HDToolBox of SCSITool</phrase><phrase arch="s390">, zoals de VM diskmap</phrase>. Schijfindelingsprogramma's @@ -103,7 +103,7 @@ informatie hieronder door te lezen omdat er bijzondere omstandigheden kunnen zijn — zoals de volgorde van bestaande partities in de partitie-index — waardoor u alsnog wordt gedwongen om te herindelen vr de installatie. -</para><para arch="i386"> +</para><para arch="x86"> Als uw machine een FAT of NTFS bestandssysteem heeft, zoals wordt gebruikt door DOS en Windows, kunt u wachten en het schijfindelingsprogramma van het Debian diff --git a/nl/preparing/nondeb-part/i386.xml b/nl/preparing/nondeb-part/i386.xml index eb0b6afb1..b5452a31e 100644 --- a/nl/preparing/nondeb-part/i386.xml +++ b/nl/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 36732 untranslated --> - <sect2 arch="i386"><title>Partitioning From DOS or Windows</title> + <sect2 arch="x86"><title>Partitioning From DOS or Windows</title> <para> If you are manipulating existing FAT or NTFS partitions, it is diff --git a/nl/preparing/pre-install-bios-setup.xml b/nl/preparing/pre-install-bios-setup.xml index 6692f33c3..3f79d9f20 100644 --- a/nl/preparing/pre-install-bios-setup.xml +++ b/nl/preparing/pre-install-bios-setup.xml @@ -58,7 +58,7 @@ FIXME: more description of this needed. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> De betere moederborden ondersteunen RAM met pariteitscontrole en kunnen u melden als uw systeem een fout van n bit in het geheugen heeft. Helaas @@ -69,7 +69,7 @@ fouten in uw gegevens ontstaan. Daarom beschikken de betere systemen over moederborden die geheugenmodules met 'parity' en 'true-parity' ondersteunen; zie ook <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Als u 'true-parity' RAM heeft en als dit door uw moederbord wordt ondersteund, activeer dan eventuele BIOS-instellingen die ervoor zorgen dat het moederbord @@ -77,7 +77,7 @@ een interrupt genereert bij pariteitsfouten in het geheugen. </para> - <sect3 arch="i386"><title>De turboschakelaar</title> + <sect3 arch="x86"><title>De turboschakelaar</title> <para> Veel systemen hebben een <emphasis>turboschakelaar</emphasis> die de @@ -91,7 +91,7 @@ apparatuur, per ongeluk de softwarematige besturing van de turboschakelaar raakt </para> </sect3> - <sect3 arch="i386"><title>Cyrix-CPU's en diskettefouten</title> + <sect3 arch="x86"><title>Cyrix-CPU's en diskettefouten</title> <para> Bij systemen met een Cyrix-CPU kan het noodzakelijk zijn om tijdens de @@ -111,7 +111,7 @@ naar 32-bit.) </para> </sect3> - <sect3 arch="i386"><title>Instellingen van randapparatuur</title> + <sect3 arch="x86"><title>Instellingen van randapparatuur</title> <para> Mogelijk moet u instellingen of jumpers op in uw computer aanwezige kaarten @@ -130,7 +130,7 @@ hoeveelheid RAM in uw systeem. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>USB BIOS instellingen en toetsenborden</title> <para> diff --git a/nl/using-d-i/modules/clock-setup.xml b/nl/using-d-i/modules/clock-setup.xml index 22e8dd023..e42cce2c4 100644 --- a/nl/using-d-i/modules/clock-setup.xml +++ b/nl/using-d-i/modules/clock-setup.xml @@ -19,7 +19,7 @@ klok staat ingesteld op UTC of niet. <phrase arch="m68k;powerpc">De interne klok van Macintosh computers staat gewoonlijk ingesteld op de lokale tijd. Selecteer lokaal in plaats van GMT als u meerdere besturingssystemen op uw computer wilt gebruiken.</phrase> -<phrase arch="i386">Systemen waarop (ook) Dos of Windows draait, staan +<phrase arch="x86">Systemen waarop (ook) Dos of Windows draait, staan gewoonlijk ingesteld op de lokale tijd. Selecteer lokaal in plaats van GMT als u meerdere besturingssystemen op uw computer wilt gebruiken.</phrase> diff --git a/nl/using-d-i/modules/i386/grub-installer.xml b/nl/using-d-i/modules/i386/grub-installer.xml index 64e1e7ffb..fdb192e37 100644 --- a/nl/using-d-i/modules/i386/grub-installer.xml +++ b/nl/using-d-i/modules/i386/grub-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 18640 untranslated --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>Grub</command> Boot Loader on a Hard Disk</title> <para> diff --git a/nl/using-d-i/modules/i386/lilo-installer.xml b/nl/using-d-i/modules/i386/lilo-installer.xml index 30726d83a..5223cb0f1 100644 --- a/nl/using-d-i/modules/i386/lilo-installer.xml +++ b/nl/using-d-i/modules/i386/lilo-installer.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 22935 untranslated --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Install the <command>LILO</command> Boot Loader on a Hard Disk</title> <para> diff --git a/pt_BR/administrivia/administrivia.xml b/pt_BR/administrivia/administrivia.xml index f6945bc29..a09fe71d1 100644 --- a/pt_BR/administrivia/administrivia.xml +++ b/pt_BR/administrivia/administrivia.xml @@ -131,7 +131,7 @@ A seção de instalações em chroot neste manual (<xref linkend="linux-upgrade"/>) foi derivada em parte de documentos sob copyright de Kersten M. Self. -</para><para arch="i386"> +</para><para arch="x86"> A seção de instalações sobre plip neste manual <xref linkend="plip"/>) foi baseada no diff --git a/pt_BR/appendix/chroot-install.xml b/pt_BR/appendix/chroot-install.xml index b3fa68c7c..2694ee6c3 100644 --- a/pt_BR/appendix/chroot-install.xml +++ b/pt_BR/appendix/chroot-install.xml @@ -422,7 +422,7 @@ instalado com sua nova partição raiz. Note que o debootstrap não instala um gerenciador de partida, você deverá executar um apt-get dentro do seu chroot da Debian para fazê-lo. -</para><para arch="i386"> +</para><para arch="x86"> Veja <userinput>info grub</userinput> ou <userinput>man lilo.conf</userinput> por instruções de como configurar um gerenciador de @@ -434,7 +434,7 @@ sistema e editá-lo lá. Após terminar a edição, execute o <command>lilo</com (lembre-se de usar o <filename>lilo.conf</filename> relativo ao sistema que está sendo instalado). -</para><para arch="i386"> +</para><para arch="x86"> Aqui está um arquivo <filename>/etc/lilo.conf</filename> básico como um exemplo: diff --git a/pt_BR/appendix/plip.xml b/pt_BR/appendix/plip.xml index 698fc8f0e..1f0e14cf0 100644 --- a/pt_BR/appendix/plip.xml +++ b/pt_BR/appendix/plip.xml @@ -3,7 +3,7 @@ <!-- translated by Marco Carvalho (macs) 2005.12.30 --> <!-- reviewed by Felipe Augusto van de Wiel (faw) 2005.12.31 --> - <sect1 id="plip" arch="i386"> + <sect1 id="plip" arch="x86"> <title>Instalando &debian; por Linha IP Paralela (PLIP)</title> <para> diff --git a/pt_BR/boot-installer/boot-installer.xml b/pt_BR/boot-installer/boot-installer.xml index b964f28a5..da00dceca 100644 --- a/pt_BR/boot-installer/boot-installer.xml +++ b/pt_BR/boot-installer/boot-installer.xml @@ -8,7 +8,7 @@ <!-- construção. --> <!-- A condição arch="..." pode ser apagada quando todas as arquiteturas --> <!-- estiverem presentes --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;x86;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Inicializando o Programa de Instalação na &arch-title;</title> <!-- Esta informação é dependente de arquitetura, por isto deixei a --> diff --git a/pt_BR/boot-installer/i386.xml b/pt_BR/boot-installer/i386.xml index 3798aa155..5904670a5 100644 --- a/pt_BR/boot-installer/i386.xml +++ b/pt_BR/boot-installer/i386.xml @@ -4,7 +4,7 @@ <!-- revised by Felipe Augusto van de Wiel (faw) 2006.05.31 --> <!-- updated 36744:38231 by Felipe Augusto van de Wiel (faw) 2006.06.26 --> - <sect2 arch="i386"><title>Inicializando o sistema através de um CD-ROM</title> + <sect2 arch="x86"><title>Inicializando o sistema através de um CD-ROM</title> &boot-installer-intro-cd.xml; @@ -77,7 +77,7 @@ Inicializa com o tipo <quote>bf2.4</quote>. <!-- FIXME the documented procedure does not exactly work, commented out until fixes - <sect2 arch="i386" id="install-from-dos"> + <sect2 arch="x86" id="install-from-dos"> <title>Inicializando a partir de uma partição DOS</title> &boot-installer-intro-hd.xml; @@ -109,7 +109,7 @@ tipo de imagem bf2.4. O sintoma deste problema é um erro END FIXME --> - <sect2 arch="i386" id="boot-initrd"> + <sect2 arch="x86" id="boot-initrd"> <title>Inicializando através do linux usando o <command>LILO</command> ou <command>GRUB</command></title> @@ -201,7 +201,7 @@ ou <command>LILO</command>. </para> </sect2> - <sect2 arch="i386" condition="bootable-usb" id="usb-boot"> + <sect2 arch="x86" condition="bootable-usb" id="usb-boot"> <title>Inicialização através de uma memory stick USB</title> <para> @@ -216,7 +216,7 @@ opcionais de partida ou apenas teclar &enterkey;. </para> </sect2> - <sect2 arch="i386" condition="supports-floppy-boot" id="floppy-boot"> + <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> <title>Inicialização através de disquetes</title> @@ -283,7 +283,7 @@ automaticamente carregado. </para> </sect2> - <sect2 arch="i386" id="boot-tftp"><title>Inicialização usando o TFTP</title> + <sect2 arch="x86" id="boot-tftp"><title>Inicialização usando o TFTP</title> &boot-installer-intro-net.xml; @@ -322,7 +322,7 @@ fornecem suporte de inicialização usando o protocolo TFTP. </sect2> - <sect2 arch="i386"><title>Parâmetros de inicialização</title> + <sect2 arch="x86"><title>Parâmetros de inicialização</title> <para> diff --git a/pt_BR/boot-installer/intro-cd.xml b/pt_BR/boot-installer/intro-cd.xml index 667d2ca88..8c9ad874f 100644 --- a/pt_BR/boot-installer/intro-cd.xml +++ b/pt_BR/boot-installer/intro-cd.xml @@ -8,7 +8,7 @@ O caminho mais fácil para a maioria das pessoas é usar um conjunto de CDs da Debian. Se tiver um conjunto de CDs e se sua máquina suportar a inicialização diretamente através de CD, ótimo! Simplesmente -<phrase arch="i386"> +<phrase arch="x86"> configure o sistema para dar a partida através de uma unidade de CD como descrito em <xref linkend="boot-dev-select"/>, diff --git a/pt_BR/boot-installer/parameters.xml b/pt_BR/boot-installer/parameters.xml index b51840a51..f21310162 100644 --- a/pt_BR/boot-installer/parameters.xml +++ b/pt_BR/boot-installer/parameters.xml @@ -233,7 +233,7 @@ problema em seu sistema, você pode desabilitar este recurso com o parâmetro sobre o bterm ou bogl, uma tela preta ou congelamento (<quote>freeze</quote>) alguns minutos após iniciar a instalação. -</para><para arch="i386"> +</para><para arch="x86"> O argumento <userinput>video=vga16:off</userinput> também pode ser usado para desativar o uso do framebuffer no kernel. Tais problemas foram reportados em diff --git a/pt_BR/boot-installer/trouble.xml b/pt_BR/boot-installer/trouble.xml index ed6ec093e..78a0012f9 100644 --- a/pt_BR/boot-installer/trouble.xml +++ b/pt_BR/boot-installer/trouble.xml @@ -75,7 +75,7 @@ kernel. O programa de instalação requer Alguns problemas podem ser resolvidos com freqüência removendo coisas adicionais e periféricos e então tentando novamente -iniciar. <phrase arch="i386">Modens internos, placas de som +iniciar. <phrase arch="x86">Modens internos, placas de som e dispositivos Plug-n-Play podem ser especialmente problemáticos.</phrase> </para><para> @@ -89,7 +89,7 @@ como <userinput>mem=512m</userinput>. </para> </sect2> - <sect2 arch="i386" id="i386-boot-problems"> + <sect2 arch="x86" id="i386-boot-problems"> <title>Problemas comuns de instalação na &arch-title;</title> <para> diff --git a/pt_BR/hardware/hardware-supported.xml b/pt_BR/hardware/hardware-supported.xml index 550d166ea..2d7810e20 100644 --- a/pt_BR/hardware/hardware-supported.xml +++ b/pt_BR/hardware/hardware-supported.xml @@ -224,7 +224,7 @@ debian-&arch-listname;</ulink> também. <sect2 id="gfx" arch="not-s390"><title>Placas de vídeo</title> -<para arch="i386"> +<para arch="x86"> Você deverá estar usando uma interface compatível com VGA para o terminal de console. Praticamente qualquer placa de vídeo moderna @@ -267,7 +267,7 @@ relacionada com placas de avaliação Broadcom. </sect2> - <sect2 arch="i386" id="laptops"><title>Notebooks</title> + <sect2 arch="x86" id="laptops"><title>Notebooks</title> <para> Os notebooks são bem suportados. Os notebooks são normalmente diff --git a/pt_BR/hardware/installation-media.xml b/pt_BR/hardware/installation-media.xml index fc3f7bda9..60eaebed5 100644 --- a/pt_BR/hardware/installation-media.xml +++ b/pt_BR/hardware/installation-media.xml @@ -56,7 +56,7 @@ você poderá usar um CD-ROM em conjunto com as outras técnicas de instalação em seu sistema, uma vez que inicializou por outras formas; veja <xref linkend="boot-installer"/>. -</para><para arch="i386"> +</para><para arch="x86"> Ambos os CD-ROMs SCSI e IDE/ATAPI são suportados. Em adição, todas as interfaces de CD não padrões suportadas pelo Linux @@ -67,7 +67,7 @@ para funcionarem e é improvável a inicialização sem o uso destes parâmetros. O <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contém dados atualizados de como utilizar CD-ROMs com o Linux. -</para><para arch="i386"> +</para><para arch="x86"> Unidades de CD-ROM USB também são suportadas, como são dispositivos FireWare pois são suportados pelos dispositivos ohci1394 e sbp2. @@ -224,14 +224,14 @@ próprio kernel). O suporte para a maior faixa de dispositivos possíveis é considerável em geral, para se assegurar que o Debian poderá ser instalado na maior quantidade de hardwares. -</para><para arch="i386"> +</para><para arch="x86"> Geralmente, o sistema de instalação da Debian inclui suporte para disquetes, controladoras IDE, disquetes IDE, dispositivos IDE de porta paralela, controladores e unidades SCSI, USB e FireWire. Os sistemas de arquivos suportados incluem FAT, extensões FAT para Win32 (VFAT), NTFS, entre outros. -</para><para arch="i386"> +</para><para arch="x86"> As interfaces de disco que emulam a interface de disco rígido <quote>AT</quote> — freqüentemente chamada de MFM, RLL, IDE ou diff --git a/pt_BR/hardware/network-cards.xml b/pt_BR/hardware/network-cards.xml index 0e27c6777..e2b12a12b 100644 --- a/pt_BR/hardware/network-cards.xml +++ b/pt_BR/hardware/network-cards.xml @@ -6,7 +6,7 @@ <sect1 id="network-cards"> <title>Placas de rede</title> -<para arch="i386"> +<para arch="x86"> <!-- last updated for kernel-image_2.0.36-2 --> @@ -25,7 +25,7 @@ uma placa não suportada e então substituir no sistema de instalação (veja <xref linkend="rescue-replace-kernel"/>). --> -</para><para arch="i386"> +</para><para arch="x86"> Como no ISDN, o protocolo D-channel para a (antiga) Alemã 1TR6 não é suportada; as placas Spellcaster BRI ISDN também não é diff --git a/pt_BR/hardware/supported-peripherals.xml b/pt_BR/hardware/supported-peripherals.xml index f18d069e9..677808fd5 100644 --- a/pt_BR/hardware/supported-peripherals.xml +++ b/pt_BR/hardware/supported-peripherals.xml @@ -12,12 +12,12 @@ como mouses, impressoras, scanners, PCMCIA e dispositivos USB. No entanto, a maioria destes dispositivos não são requeridos durante a instalação do sistema. -</para><para arch="i386"> +</para><para arch="x86"> O hardware USB geralmente funciona bem, somente teclados USB podem requerer configurações adicionais (veja <xref linkend="usb-keyboard-config"/>). -</para><para arch="i386"> +</para><para arch="x86"> Novamente, veja o <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> @@ -61,7 +61,7 @@ GNU/Linux. Infelizmente, é muito raro encontrar qualquer vendedor vendendo máquinas &arch-title; novas. -</para><para arch="i386"> +</para><para arch="x86"> Se tiver que comprar uma máquina com o Windows instalado, leia cuidadosamente a licença de software que vem com o @@ -114,7 +114,7 @@ mercado importante. </sect2> - <sect2 arch="i386"><title>Hardwares específicos para Windows</title> + <sect2 arch="x86"><title>Hardwares específicos para Windows</title> <para> Uma tendência que incomoda é a proliferação de modems e diff --git a/pt_BR/hardware/supported/i386.xml b/pt_BR/hardware/supported/i386.xml index 9b5e52d12..1db58d789 100644 --- a/pt_BR/hardware/supported/i386.xml +++ b/pt_BR/hardware/supported/i386.xml @@ -1,7 +1,7 @@ <!-- original version: 11648 --> - <sect2 arch="i386"><title>CPU, placas mãe e suporte a placas de vídeo</title> + <sect2 arch="x86"><title>CPU, placas mãe e suporte a placas de vídeo</title> <para> Informações completas sobre o suporte a periféricos podem ser diff --git a/pt_BR/howto/installation-howto.xml b/pt_BR/howto/installation-howto.xml index 88138ca4d..8380a2d7f 100644 --- a/pt_BR/howto/installation-howto.xml +++ b/pt_BR/howto/installation-howto.xml @@ -86,7 +86,7 @@ CD do conjunto. </para><para> Baixe o tipo de imagem que deseja e grave-a para um CD. -<phrase arch="i386">Para inicializar através do CD, você precisará +<phrase arch="x86">Para inicializar através do CD, você precisará alterar a configuração de sua BIOS como explicado em <xref linkend="bios-setup" />.</phrase> <phrase arch="powerpc"> Par inicializar no PowerMac através do CD, pressione <keycap>c</keycap> @@ -167,7 +167,7 @@ Existem outros métodos mais flexíveis de configurar uma memory stick para ser usada pelo debian-installer, sendo possível trabalhar com memory sticks pequenas. Para detalhes, veja <xref linkend="boot-usb-files" />. -</para><para arch="i386"> +</para><para arch="x86"> Alguns tipos de BIOS não podem inicializar diretamente de dispositivos USB. Você pode precisar configurar sua BIOS para inicializar através de um @@ -194,7 +194,7 @@ arquitetura e da configuração do netboot. Os arquivos em <filename>netboot/</filename> podem ser usados para fazer a inicialização via rede do &d-i;. -</para><para arch="i386"> +</para><para arch="x86"> A coisa mais fácil de configurar é provavelmente a inicialização através do PXE. Descompacte o arquivo <filename>netboot/pxeboot.tar.gz</filename> em @@ -218,7 +218,7 @@ diferente instalado. Baixe o arquivo e uma imagem de CD da Debian para o diretório raíz do disco rígido. Tenha certeza que o nome do arquivo da imagem de CD finalize com <literal>.iso</literal>. Agora resta apenas inicializar o linux com o initrd. -<phrase arch="i386"> +<phrase arch="x86"> <xref linkend="boot-initrd" /> explica a forma de como fazer isto. </phrase> @@ -233,7 +233,7 @@ certeza que o nome do arquivo da imagem de CD finalize com Assim que o programa de instalação for iniciado, você verá a tela inicial. Pressione &enterkey; para inicializar ou leia as instruções para outros métodos de inicialização e parâmetros (veja <xref linkend="boot-parms" />). -<phrase arch="i386"> +<phrase arch="x86"> Se desejar um kernel 2.4, digite <userinput>linux24</userinput> no aviso de <prompt>boot:</prompt>. <footnote><para> @@ -300,7 +300,7 @@ kernel. O último passo é instalar um gerenciador de partida. Caso o programa de instalação detectar outro sistema operacional em seu computador, ele o adicionará no menu de inicialização e lhe informará isto. -<phrase arch="i386">Por padrão, o GRUB será instalado no registro mestre de +<phrase arch="x86">Por padrão, o GRUB será instalado no registro mestre de inicialização de seu primeiro disco rígido, que é uma boa escolha. Você será capaz de alterar aquela escolha e instalá-lo em qualquer outro lugar. </phrase> diff --git a/pt_BR/install-methods/boot-drive-files.xml b/pt_BR/install-methods/boot-drive-files.xml index 0c5c95eb1..ee06be284 100644 --- a/pt_BR/install-methods/boot-drive-files.xml +++ b/pt_BR/install-methods/boot-drive-files.xml @@ -19,7 +19,7 @@ esta técnica. Isto evita a chatice de mídias removíveis, como o trabalho de procurar e queimar imagens de CD ou ter uma grande quantidade de disquetes não confiáveis. -</para><para arch="i386"> +</para><para arch="x86"> O programa de instalação não pode inicializar através de arquivos de um sistema NTFS. @@ -44,7 +44,7 @@ modelo <quote>NewWorld</quote> ou <quote>OldWorld</quote>. </para> - <sect2 arch="i386" id="files-lilo"> + <sect2 arch="x86" id="files-lilo"> <title>Iniciando o programa de instalação via disco rígido usando o <command>LILO</command> ou o <command>GRUB</command></title> <para> diff --git a/pt_BR/install-methods/boot-usb-files.xml b/pt_BR/install-methods/boot-usb-files.xml index b41506f0a..cc7aa080d 100644 --- a/pt_BR/install-methods/boot-usb-files.xml +++ b/pt_BR/install-methods/boot-usb-files.xml @@ -26,7 +26,7 @@ Note que a memória stick USB deverá ter pelo menos 256MB de tamanho <sect2 id="usb-copy-easy"> <title>Copiando os arquivos — o método fácil</title> -<para arch="i386"> +<para arch="x86"> Existe um arquivo <emphasis>tudo em um</emphasis> chamado <filename>hd-media/boot.img.gz</filename> que contém todos os arquivos @@ -62,10 +62,10 @@ sua memória USB. <para> Após isto, monte a memória stick USB (<userinput>mount -<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="x86">/dev/sda</replaceable> <replaceable arch="powerpc">/dev/sda2</replaceable> /mnt</userinput>), que agora terá um sistema -de arquivos <phrase arch="i386">FAT</phrase> +de arquivos <phrase arch="x86">FAT</phrase> <phrase arch="powerpc">HFS</phrase> dentro dele e copie a imagem ISO Debian netinst ou cartão de visita para lá. Note que o nome de arquivo deverá finalizar em @@ -120,7 +120,7 @@ Quando terminar, desmonte a memória stick USB (<userinput>umount </sect2> <!-- TODO: doesn't this section belong later? --> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Inicialização através da memória stick USB</title> <warning><para> diff --git a/pt_BR/install-methods/install-tftp.xml b/pt_BR/install-methods/install-tftp.xml index 945e19e5f..cc8fbcdc9 100644 --- a/pt_BR/install-methods/install-tftp.xml +++ b/pt_BR/install-methods/install-tftp.xml @@ -78,7 +78,7 @@ servidor, em qualquer plataforma que implementa estes protocolos poderá ser usados. Nos exemplos desta seção, nós mostraremos comando para o SunOS 4.x, SunOS 5.x (a.k.a. Solaris), e para o GNU/Linux. -<note arch="i386"><para> +<note arch="x86"><para> Para utilizar o método Pre-boot Execution Environment (PXE) de inicialização através de TFTP, você precisará configurar um servidor TFTP coom suporte a @@ -177,7 +177,7 @@ em RAM via TFTP. Para a inicialização via rede, use o <filename>yaboot-netboot.conf</filename>. Apenas renomeie este arquivo para <filename>yaboot.conf</filename> no diretório do TFTP. -</para><para arch="i386"> +</para><para arch="x86"> Para a inicialização usando o PXE, tudo que precisa fazer já está feito no arquivo tar <filename>netboot/netboot.tar.gz</filename>. Simplesmente descompacte este arquivo no diretório de imagem de inicialização do diff --git a/pt_BR/install-methods/tftp/dhcp.xml b/pt_BR/install-methods/tftp/dhcp.xml index cfcc77c23..c0eed3aac 100644 --- a/pt_BR/install-methods/tftp/dhcp.xml +++ b/pt_BR/install-methods/tftp/dhcp.xml @@ -51,7 +51,7 @@ reinice-o com <userinput>/etc/init.d/dhcpd restart</userinput>. </para> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Habilitando a inicialização através de PXE no servidor DHCP</title> <para> Aqui está outro exemplo para o <filename>dhcp.conf</filename> usando o diff --git a/pt_BR/install-methods/usb-setup/i386.xml b/pt_BR/install-methods/usb-setup/i386.xml index 731cc54e0..0af656786 100644 --- a/pt_BR/install-methods/usb-setup/i386.xml +++ b/pt_BR/install-methods/usb-setup/i386.xml @@ -3,7 +3,7 @@ <!-- revised by Herbert Parentes Fortes Neto (hpfn) 2006.05.02 --> <!-- revised by Felipe Augusto van de Wiel (faw) 2006.06.03 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Particionamento de memória stick USB na &arch-title;</title> <para> diff --git a/pt_BR/partitioning/device-names.xml b/pt_BR/partitioning/device-names.xml index e55517609..14ff65446 100644 --- a/pt_BR/partitioning/device-names.xml +++ b/pt_BR/partitioning/device-names.xml @@ -68,12 +68,12 @@ podem ser mostradas como <filename>/dev/hda</filename> na Debian). </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> O primeiro disco XT tem o nome <filename>/dev/xda</filename>. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> O segundo disco XT tem o nome <filename>/dev/xdb</filename>. @@ -124,7 +124,7 @@ a ordem das unidades podem se tornar confusas. A melhor solução neste caso é olhar as mensagens de inicialização, assumindo que conheça o modelo das unidades e/ou suas capacidades. -</para><para arch="i386"> +</para><para arch="x86"> O Linux representa as partições primárias como nomes de unidade acrescido de um número de 1 a 4. Por exemplo, a primeira partição primária no diff --git a/pt_BR/partitioning/partition-programs.xml b/pt_BR/partitioning/partition-programs.xml index 36edcc6f0..b83ec7416 100644 --- a/pt_BR/partitioning/partition-programs.xml +++ b/pt_BR/partitioning/partition-programs.xml @@ -21,7 +21,7 @@ programas aplicáveis para sua arquitetura. <listitem><para> Ferramenta de particionamento recomendada na Debian. Esse canivete suíço -também pode redimensionar, criar sistemas de arquivos <phrase arch="i386"> +também pode redimensionar, criar sistemas de arquivos <phrase arch="x86"> (<quote>formatar</quote> no mundo do Windows) </phrase> e te indicar pontos de montagem. @@ -145,7 +145,7 @@ kernel e módulos, execute: #chmod 660 hda21 </screen></informalexample> -<phrase arch="i386">Lembre-se de tornar sua partição de inicialização +<phrase arch="x86">Lembre-se de tornar sua partição de inicialização <quote>Inicializável</quote>.</phrase> </para><para condition="mac-fdisk.txt"> diff --git a/pt_BR/partitioning/partition/i386.xml b/pt_BR/partitioning/partition/i386.xml index 9f371c648..fe5d3ce49 100644 --- a/pt_BR/partitioning/partition/i386.xml +++ b/pt_BR/partitioning/partition/i386.xml @@ -3,7 +3,7 @@ <!-- revised by Felipe Augusto van de Wiel (faw) 2006.04.17 --> <!-- revised by Herbert P Fortes Neto (hpfn) 2006.04.13 --> - <sect2 arch="i386"><title>Particionamento para &arch-title;</title> + <sect2 arch="x86"><title>Particionamento para &arch-title;</title> <para> Se já tiver um sistema operacional tal como o DOS ou Windows e diff --git a/pt_BR/post-install/kernel-baking.xml b/pt_BR/post-install/kernel-baking.xml index f140f4762..4df1a6ab9 100644 --- a/pt_BR/post-install/kernel-baking.xml +++ b/pt_BR/post-install/kernel-baking.xml @@ -168,7 +168,7 @@ personalizado como qualquer pacote. Como root, execute o comando </phrase> A parte <replaceable>sub-arquitetura</replaceable> é uma sub-arquitetura opcional, -<phrase arch="i386"> tal como <quote>i586</quote>, </phrase> +<phrase arch="x86"> tal como <quote>i586</quote>, </phrase> dependendo das opções do kernel que escolheu. O comando <userinput>dpkg -i </userinput> instalará o kernel, junto com outros arquivos de suporte. Por exemplo, o diff --git a/pt_BR/post-install/reactivating-win.xml b/pt_BR/post-install/reactivating-win.xml index ef2a9de6e..1d209b50c 100644 --- a/pt_BR/post-install/reactivating-win.xml +++ b/pt_BR/post-install/reactivating-win.xml @@ -2,7 +2,7 @@ <!-- original version: 28672 --> <!-- reviewed by Felipe Augusto van de Wiel (faw) 2006.01.01 --> - <sect1 arch="i386" id="reactivating-win"> + <sect1 arch="x86" id="reactivating-win"> <title>Reativando o DOS e o Windows</title> <para> diff --git a/pt_BR/post-install/rescue.xml b/pt_BR/post-install/rescue.xml index 1dd73c91e..3d4acead9 100644 --- a/pt_BR/post-install/rescue.xml +++ b/pt_BR/post-install/rescue.xml @@ -44,7 +44,7 @@ bem como as criadas diretamente nos discos. Se possível, o instalador irá apresentar agora um prompt shell no sistema de arquivos que você escolheu, onde você poderá fazer qualquer reparo necessário. -<phrase arch="i386"> +<phrase arch="x86"> Por exemplo, se você precisa reinstalar o carregador de inicialização GRUB no master boot record do primeiro disco rígido, você poderá usar o comando <userinput>grub-install '(hd0)'</userinput> para isso. diff --git a/pt_BR/preparing/bios-setup/i386.xml b/pt_BR/preparing/bios-setup/i386.xml index 80b64eeee..9f7b8b403 100644 --- a/pt_BR/preparing/bios-setup/i386.xml +++ b/pt_BR/preparing/bios-setup/i386.xml @@ -3,7 +3,7 @@ <!-- revised by Herbert Parentes Fortes Neto (hpfn) 2006.05.02 --> <!-- revised by Felipe Augusto van de Wiel (faw) 2006.06.02 --> - <sect2 arch="i386" id="bios-setup"><title>Invocando o menu de configuração da BIOS </title> + <sect2 arch="x86" id="bios-setup"><title>Invocando o menu de configuração da BIOS </title> <para> @@ -104,7 +104,7 @@ poderá tentar usar um programa shareware/freeware. Tente vendo o endereço </para> </sect2> - <sect2 arch="i386" id="boot-dev-select"><title>Seleção do dispositivo de inicialização</title> + <sect2 arch="x86" id="boot-dev-select"><title>Seleção do dispositivo de inicialização</title> <para> @@ -236,7 +236,7 @@ deverá pressionar </sect3> </sect2> - <sect2 arch="i386"> + <sect2 arch="x86"> <title>Configurações diversas da BIOS</title> <sect3 id="cd-settings"><title>Configurações do CD-ROM</title> diff --git a/pt_BR/preparing/minimum-hardware-reqts.xml b/pt_BR/preparing/minimum-hardware-reqts.xml index 3fa6c2396..c3cf22ff9 100644 --- a/pt_BR/preparing/minimum-hardware-reqts.xml +++ b/pt_BR/preparing/minimum-hardware-reqts.xml @@ -16,7 +16,7 @@ Dependendo de suas necessidades, poderá trabalhar com um requerimento menor que o recomendado na tabela abaixo. No entanto, a maioria dos usuários correm o risco de ficar frustrados caso ignorem estas sugestões. -</para><para arch="i386"> +</para><para arch="x86"> Um Pentium 100 é o mínimo recomendado para um sistema desktop e um Pentium II-300 para um servidor. diff --git a/pt_BR/preparing/needed-info.xml b/pt_BR/preparing/needed-info.xml index 6bc30931b..27622549e 100644 --- a/pt_BR/preparing/needed-info.xml +++ b/pt_BR/preparing/needed-info.xml @@ -56,8 +56,8 @@ seu hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> -<listitem arch="i386"><para> + <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="x86"><para> <ulink url="&url-hardware-howto;">HOWTO de Compatibilidade de Hardware do Linux</ulink> @@ -181,7 +181,7 @@ Os casos relacionados com cada peça de hardware. </para></listitem> -<listitem arch="i386"><para> +<listitem arch="x86"><para> A janela de sistema no Painel de Controle do Windows. @@ -221,7 +221,7 @@ configurar em sua rede e e-mail. </row> <row arch="not-s390"><entry>Sua ordem no sistema.</entry></row> <!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc"> +<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> <entry>Quando são IDE ou SCSI (a maioria dos computadores são IDE).</entry> </row> <row arch="m68k"> @@ -303,12 +303,12 @@ satisfatória, o hardware para Linux está crescendo a cada dia. No entanto, o Linux ainda não tem suporte a tantos tipos de hardwares quanto em outros sistemas operacionais. -</para><para arch="i386"> +</para><para arch="x86"> Em particular, o Linux normalmente não funciona com hardwares que requerem Windows para funcionar. -</para><para arch="i386"> +</para><para arch="x86"> Embora alguns hardwares específicos para Windows podem ser colocados em funcionamento do Linux, fazê-lo normalmente requer um esforço extra. @@ -316,7 +316,7 @@ Em adição, controladores de Linux para hardwares específicos do Windows são geralmente ligados a uma versão do kernel do Linux. Assim eles podem se tornar obsoletos rapidamente. -</para><para arch="i386"> +</para><para arch="x86"> Os chamados win-modems são o tipo mais comum destes hardwares. Mas impressoras e outros equipamentos também podem ser específicos diff --git a/pt_BR/preparing/non-debian-partitioning.xml b/pt_BR/preparing/non-debian-partitioning.xml index 60fe75be6..bd12e2c34 100644 --- a/pt_BR/preparing/non-debian-partitioning.xml +++ b/pt_BR/preparing/non-debian-partitioning.xml @@ -21,7 +21,7 @@ uma LPAR ou hospedeiro VM neste caso. Caso já tenha um sistema operacional no seu sistema -<phrase arch="i386"> +<phrase arch="x86"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> @@ -49,7 +49,7 @@ de arquivos raiz da Debian. Você poderá encontrar informações sobre a configuração atual de particionamento usando uma ferramenta de particionamento para seu sistema operacional atual <phrase -arch="i386">, tal como o fdisk ou o PartitionMagic</phrase><phrase +arch="x86">, tal como o fdisk ou o PartitionMagic</phrase><phrase arch="powerpc">, tal como o Drive Setup, HD Toolkit ou MacTools</phrase><phrase arch="m68k">, tal como o HD SC Setup, HDToolBox ou SCSITool</phrase><phrase arch="s390">, tal como o VM diskmap</phrase>. As ferramentas de particionamento @@ -102,7 +102,7 @@ porque podem existir circunstâncias especiais como a ordem de partições existentes dentro do mapa de partição, isto lhe forçara a particionar antes de instalar. -</para><para arch="i386"> +</para><para arch="x86"> Caso sua máquina tenha um sistema de arquivos FAT ou NTFS, o mesmo usado pelo DOS e Windows, espere e use o programa de particionamento diff --git a/pt_BR/preparing/nondeb-part/i386.xml b/pt_BR/preparing/nondeb-part/i386.xml index c6def0073..73a0126db 100644 --- a/pt_BR/preparing/nondeb-part/i386.xml +++ b/pt_BR/preparing/nondeb-part/i386.xml @@ -3,7 +3,7 @@ <!-- revised by Herbert Parentes Fortes Neto (hpfn) 2006.05.02 --> <!-- revised by Felipe Augusto van de Wiel (faw) 2005.06.03 --> - <sect2 arch="i386"><title>Particionamento através do DOS ou Windows</title> + <sect2 arch="x86"><title>Particionamento através do DOS ou Windows</title> <para> Se estiver manipulando partições FAT ou NTFS existentes, é recomendado diff --git a/pt_BR/preparing/pre-install-bios-setup.xml b/pt_BR/preparing/pre-install-bios-setup.xml index 6bf1773ec..5c56d217d 100644 --- a/pt_BR/preparing/pre-install-bios-setup.xml +++ b/pt_BR/preparing/pre-install-bios-setup.xml @@ -60,7 +60,7 @@ FIXME: São necessárias mais descrições sobre isto. </emphasis></phrase> -</para><para arch="i386"> +</para><para arch="x86"> As melhores placas mãe suportam paridade na memória RAM e alertarão caso o seu sistema tenha um erro de um simples bit na RAM. Infelizmente, @@ -71,7 +71,7 @@ silenciosamente inserindo erros em seus dados. Assim, os melhores sistemas tem placas mãe que suportam paridade e módulos de memória com paridade verdadeira; veja <xref linkend="Parity-RAM"/>. -</para><para arch="i386"> +</para><para arch="x86"> Se tiver uma memória RAM com paridade verdadeira e sua placa mãe pode manipulá-la, tenha certeza de ativar suas configurações de BIOS que fazem @@ -79,7 +79,7 @@ sua placa mãe interromper caso ocorram erros de paridade na memória. </para> - <sect3 arch="i386"><title>A chave turbo</title> + <sect3 arch="x86"><title>A chave turbo</title> <para> Muitos sistemas tem uma chave <emphasis>turbo</emphasis> que controlam @@ -93,7 +93,7 @@ de hardware. </para> </sect3> - <sect3 arch="i386"><title>CPUs Cyrix e erros em disquetes</title> + <sect3 arch="x86"><title>CPUs Cyrix e erros em disquetes</title> <para> Muitos usuários de CPUs Cyrix tem tido que desativar o cache de @@ -113,7 +113,7 @@ problema com o cache sendo invalidado após uma mudança do código de </para> </sect3> - <sect3 arch="i386"><title>Configuração de periféricos no hardware</title> + <sect3 arch="x86"><title>Configuração de periféricos no hardware</title> <para> Você poderá ter que mudar algumas configurações ou jumpers nas @@ -132,7 +132,7 @@ de memória do seu sistema. </para> </sect3> - <sect3 arch="i386" id="usb-keyboard-config"> + <sect3 arch="x86" id="usb-keyboard-config"> <title>Suporte da USB na BIOS e teclados USB</title> <para> diff --git a/pt_BR/using-d-i/modules/clock-setup.xml b/pt_BR/using-d-i/modules/clock-setup.xml index 5f984fa9c..a0b844911 100644 --- a/pt_BR/using-d-i/modules/clock-setup.xml +++ b/pt_BR/using-d-i/modules/clock-setup.xml @@ -20,7 +20,7 @@ está ou não configurado para UTC. <phrase arch="m68k;powerpc">Relógios de hardware Macintosh são normalmente configurados para o horário local. Caso você queira um dual-boot, selecione o horário local, ao invés de GMT.</phrase> -<phrase arch="i386">Sistemas que (também) executam DOS ou Windows são +<phrase arch="x86">Sistemas que (também) executam DOS ou Windows são normalmente configurados para o horário local. Caso você queira um dual-boot, selecione o horário local, ao invés de GMT.</phrase> diff --git a/pt_BR/using-d-i/modules/i386/grub-installer.xml b/pt_BR/using-d-i/modules/i386/grub-installer.xml index 6bf39b892..233349861 100644 --- a/pt_BR/using-d-i/modules/i386/grub-installer.xml +++ b/pt_BR/using-d-i/modules/i386/grub-installer.xml @@ -1,6 +1,6 @@ <!-- original version: 18640 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalação do gerenciador de partida <command>Grub</command> no disco rígido</title> <para> diff --git a/pt_BR/using-d-i/modules/i386/lilo-installer.xml b/pt_BR/using-d-i/modules/i386/lilo-installer.xml index 0f943ad99..df8029647 100644 --- a/pt_BR/using-d-i/modules/i386/lilo-installer.xml +++ b/pt_BR/using-d-i/modules/i386/lilo-installer.xml @@ -1,6 +1,6 @@ <!-- original version: 22935 --> - <sect3 arch="i386"> + <sect3 arch="x86"> <title>Instalação do gerenciador de partida <command>LILO</command> no disco rígido</title> <para> |