summaryrefslogtreecommitdiff
path: root/it/preparing/bios-setup
diff options
context:
space:
mode:
authorLuca Monducci <luca.mo@tiscali.it>2006-04-29 13:03:34 +0000
committerLuca Monducci <luca.mo@tiscali.it>2006-04-29 13:03:34 +0000
commit56d549a1a48067e02d26ba2ffcb26742b368647e (patch)
treeb0e0d96c6a702db330bc32032bfff91ef1777fbc /it/preparing/bios-setup
parent970f71d7ee2ffe80db4e6207355a668c44e1d9d3 (diff)
downloadinstallation-guide-56d549a1a48067e02d26ba2ffcb26742b368647e.zip
Italian translation updated
Diffstat (limited to 'it/preparing/bios-setup')
-rw-r--r--it/preparing/bios-setup/i386.xml18
-rw-r--r--it/preparing/bios-setup/powerpc.xml11
-rw-r--r--it/preparing/bios-setup/s390.xml4
-rw-r--r--it/preparing/bios-setup/sparc.xml12
4 files changed, 24 insertions, 21 deletions
diff --git a/it/preparing/bios-setup/i386.xml b/it/preparing/bios-setup/i386.xml
index c4d815dee..16b7dd558 100644
--- a/it/preparing/bios-setup/i386.xml
+++ b/it/preparing/bios-setup/i386.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 -->
+<!-- original version: 36732 -->
<sect2 arch="i386" id="bios-setup">
@@ -204,17 +204,17 @@ si deve fare è abilitare il boot da CD nel BIOS del controller SCSI.
</para><para>
<!--
-Other popular option is to boot from a USB storage (also called USB
-memory stick or USB key). 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 <quote>USB-ZIP</quote> to
+Another popular option is to boot from a USB storage device (also called
+a USB memory stick or USB key). Some BIOSes can boot directly from a USB
+storage device, but some cannot. You may need to configure your BIOS to boot
+from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to
get it to boot from the USB device.
-->
-Un'altra possibilità molto comune è usare una memoria di massa USB (come
-una penna USB o una chiave USB) per l'avvio. Alcuni BIOS possono fare
-direttamente l'avvio da USB mentre altri no, potrebbe essere necessario
-configurare il BIOS in modo che faccia l'avvio da <quote>Disco
+Un'altra possibilità molto comune è fare l'avvio da una memoria di massa
+USB (spesso chiamata penna USB o chiave USB). Alcuni BIOS possono fare
+direttamente l'avvio da dispositivi USB mentre altri no, potrebbe essere
+necessario configurare il BIOS in modo che faccia l'avvio da <quote>Disco
rimovibile</quote> o da <quote>USB-ZIP</quote> per fare l'avvio dal
dispositivo USB.
diff --git a/it/preparing/bios-setup/powerpc.xml b/it/preparing/bios-setup/powerpc.xml
index 5b946e3fe..fa78b40b5 100644
--- a/it/preparing/bios-setup/powerpc.xml
+++ b/it/preparing/bios-setup/powerpc.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 -->
+<!-- original version: 36732 -->
<sect2 arch="powerpc" id="invoking-openfirmware">
@@ -78,7 +78,9 @@ patch is included in the <application>System Disk 2.3.1</application>
utility, available from Apple at
<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>.
After unpacking the utility in MacOS, and launching it, select the
-Save button to have the firmware patches installed to nvram.
+<guibutton>Save button</guibutton> to have the firmware patches
+installed to nvram.
+
-->
Sulle macchine OldWorld Beige G3, OpenFirmware (OF versioni 2.0f1 e 2.4)
@@ -87,8 +89,9 @@ fare il boot dal disco fisso, a meno che al firmware non venga applicata
una patch opportuna, come quella compresa nell'utility <application>System
Disk 2.3.1</application> scaricabile da Apple come
<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>.
-Scompattate l'utility in MacOS, avviarla e azionare il pulsante Save
-affinché le patch del firmware vengano installate nella nvram.
+Scompattate l'utility in MacOS, avviarla e azionare il pulsante
+<guibutton>Save</guibutton> affinché le patch del firmware vengano
+installate nella nvram.
</para>
</sect2>
diff --git a/it/preparing/bios-setup/s390.xml b/it/preparing/bios-setup/s390.xml
index 124aeda9b..03e43767e 100644
--- a/it/preparing/bios-setup/s390.xml
+++ b/it/preparing/bios-setup/s390.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 -->
+<!-- original version: 36732 -->
<sect2 arch="s390">
@@ -169,7 +169,7 @@ FTP.
<!--
The installation server needs to copy the exact directory structure
-from any &debian; mirror but of only the s390 and
+from any &debian; mirror, but only the s390 and
architecture-independent files are required. You can also copy the
contents of all installation CDs into such a directory tree.
-->
diff --git a/it/preparing/bios-setup/sparc.xml b/it/preparing/bios-setup/sparc.xml
index 6acfd8009..69e8be1b1 100644
--- a/it/preparing/bios-setup/sparc.xml
+++ b/it/preparing/bios-setup/sparc.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 -->
+<!-- original version: 36732 -->
<sect2 arch="sparc" id="invoking-openboot">
@@ -12,14 +12,14 @@ OpenBoot provides the basic functions needed to boot the &arch-title;
architecture. This is rather similar in function to the BIOS in the
x86 architecture, although much nicer. The Sun boot PROMs have a
built-in forth interpreter which lets you do quite a number of things
-with your machine, such as diagnostics, simple scripts, etc.
+with your machine, such as diagnostics and simple scripts.
-->
OpenBoot fornisce le funzioni di base necessarie a fare il boot
dell'architettura &arch-title;. Svolge delle mansioni abbastanza simili
a quelle del BIOS nell'architettura x86, tuttavia è fatto molto meglio.
Le PROM di boot Sun hanno incorporato un interprete Forth, che permette
-di fare un sacco di cose, come diagnostica, semplici script, ecc.
+di fare un sacco di cose, come diagnostica e semplici script.
</para><para>
@@ -69,7 +69,7 @@ si usa un emulatore di terminale diverso si consulti la sua documentazione.
<!--
You can use OpenBoot to boot from specific devices, and also to change
your default boot device. However, you need to know some details
-about how OpenBoot names devices; it's much different from Linux
+about how OpenBoot names devices; it's considerably different from Linux
device naming, described in <xref linkend="device-names"/>.
Also, the command will vary a bit, depending on what version of
OpenBoot you have. More information about OpenBoot can be found in
@@ -87,7 +87,7 @@ Si possono trovare più informazioni su OpenBoot nella
</para><para>
<!--
-Typically, with newer revisions, you can use OpenBoot device such as
+Typically, with newer revisions, you can use OpenBoot devices such as
<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious
meanings; the <quote>net</quote> device is for booting from the network.
@@ -96,7 +96,7 @@ such as <quote>disk2:a</quote> to boot disk2, first partition. Full
OpenBoot device names have the form
-->
-Tipicamente con le versioni più recenti si possono usare nomi di dispositivo
+Tipicamente con le versioni più recenti si possono usare dispositivi
OpenBoot quali <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
<quote>disk</quote> o <quote>disk2</quote>. Il loro significato è ovvio. Il
dispositivo <quote>net</quote> serve ad esempio per il boot via rete. In