summaryrefslogtreecommitdiff
path: root/it/preparing
diff options
context:
space:
mode:
Diffstat (limited to 'it/preparing')
-rw-r--r--it/preparing/bios-setup/s390.xml13
-rw-r--r--it/preparing/minimum-hardware-reqts.xml2
-rw-r--r--it/preparing/needed-info.xml19
-rw-r--r--it/preparing/non-debian-partitioning.xml2
-rw-r--r--it/preparing/nondeb-part/x86.xml10
5 files changed, 25 insertions, 21 deletions
diff --git a/it/preparing/bios-setup/s390.xml b/it/preparing/bios-setup/s390.xml
index 2412aaf4c..d1712f98d 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: 64916 -->
+<!-- original version: 64994 -->
<sect2 arch="s390">
<!-- <title>BIOS Setup</title> -->
@@ -133,7 +133,11 @@ You need to copy all the files from the <filename>generic</filename>
sub-directory to your CMS disk. Be sure to transfer
<filename>kernel.debian</filename> and
<filename>initrd.debian</filename> in binary mode with a fixed record
-length of 80 characters.
+length of 80 characters. <filename>parmfile.debian</filename> can
+be in either ASCII or EBCDIC format.
+
+A sample <filename>debian.exec</filename> script, which will punch the files in
+the proper order, is included with the images.
-->
È necessario copiare tutti i file dalla sotto-directory
@@ -141,6 +145,11 @@ length of 80 characters.
che il trasferimento di <filename>kernel.debian</filename> e
<filename>initrd.debian</filename> avvenga in modalità binaria e
con record di lunghezza fissa pari a 80 caratteri.
+<filename>parmfile.debian</filename> può essere in formato ASCII
+o EBCDIC.
+
+Un semplice script <filename>debian.exec</filename>, che prepara i
+file nell'ordine corretto, è incluso nelle immagini.
</para>
</sect2>
diff --git a/it/preparing/minimum-hardware-reqts.xml b/it/preparing/minimum-hardware-reqts.xml
index a97f9fe00..bdd4a1421 100644
--- a/it/preparing/minimum-hardware-reqts.xml
+++ b/it/preparing/minimum-hardware-reqts.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 64916 -->
+<!-- original version: 65193 -->
<sect1 id="minimum-hardware-reqts">
<!-- <title>Meeting Minimum Hardware Requirements</title> -->
diff --git a/it/preparing/needed-info.xml b/it/preparing/needed-info.xml
index 1fb0edf29..1b4b5c593 100644
--- a/it/preparing/needed-info.xml
+++ b/it/preparing/needed-info.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 64916 -->
+<!-- original version: 64991 -->
<sect1 id="needed-info">
<!-- <title>Information You Will Need</title> -->
@@ -102,23 +102,20 @@ Contiene informazioni utili sulla configurazione o l'utilizzo dell'hardware.
<para>
<!--
-Installation instructions and device drivers (DASD, XPRAM, Console,
-tape, z90 crypto, chandev, network) for Linux on &arch-title; using
-kernel 2.4
+Documentation of &arch-title;-specific boot sequence, commands and device
+drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)
-->
-Istruzioni per l'installazione e driver delle periferiche (DASD, XPRAM,
-Console, tape, z90 crypto, chandev, network) per Linux su &arch-title;
-con kernel 2.4.
+La documentazione specifica sulla sequenza d'avvio di &arch-title;, i
+comandi e i driver dei device (DASD, XPRAM, Console, OSA, HiperSocket
+e z/VM)
</para>
<itemizedlist>
<listitem><para>
-<ulink
-url="http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf">Device
-Drivers and Installation Commands</ulink>
+<ulink url="http://public.dhe.ibm.com/software/dw/linux390/docu/lk32dd04.pdf">Device Drivers, Features, and Commands (Linux Kernel 2.6.32)</ulink>
</para></listitem>
</itemizedlist>
@@ -588,7 +585,7 @@ un server DHCP le informazioni precedenti sono inutili poiché il server
DHCP le fornisce direttamente al proprio computer durante il processo
d'installazione.
-</para><para>
+</para><para arch="not-s390">
<!--
If you use a wireless network, you should also find out:
diff --git a/it/preparing/non-debian-partitioning.xml b/it/preparing/non-debian-partitioning.xml
index d29f70402..fdb80cde3 100644
--- a/it/preparing/non-debian-partitioning.xml
+++ b/it/preparing/non-debian-partitioning.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 64916 -->
+<!-- original version: 65194 -->
<sect1 id="non-debian-partitioning">
<!-- <title>Pre-Partitioning for Multi-Boot Systems</title> -->
diff --git a/it/preparing/nondeb-part/x86.xml b/it/preparing/nondeb-part/x86.xml
index 808e57763..9aeb8bed4 100644
--- a/it/preparing/nondeb-part/x86.xml
+++ b/it/preparing/nondeb-part/x86.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 64916 -->
+<!-- original version: 65195 -->
<sect2 arch="any-x86">
<!-- <title>Partitioning From DOS or Windows</title> -->
@@ -111,9 +111,8 @@ dato che questo diminuirebbe lo spazio libero che potete ricavare da essa.
</para><para>
<!--
-The first thing needed is a copy of <command>fips</command> which is
-available in the <filename>tools/</filename> directory on your nearest &debian;
-mirror. Unzip the archive and copy the files
+The first thing needed is a copy of <command>fips</command>.
+Unzip the archive and copy the files
<filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and
<filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can
be created using the command <filename>sys a:</filename> under DOS.
@@ -123,8 +122,7 @@ you use a disk compression driver or a disk manager. Create the disk
and read the documentation <emphasis>before</emphasis> you defragment the disk.
-->
-La prima cosa che serve è una copia di <command>fips</command>, ottenibile
-dalla directory <filename>tools/</filename> del mirror &debian; più vicino.
+La prima cosa che serve è una copia di <command>fips</command>.
Decomprimere l'archivio e copiare i file <filename>RESTORRB.EXE</filename>,
<filename>FIPS.EXE</filename> e <filename>ERRORS.TXT</filename> su un
dischetto avviabile. Il dischetto può essere reso avviabile usando il